Loading...
Loading...
Found 552 Skills
Onboard prek (Rust-powered pre-commit) into any project and suggest hooks tailored to the language/framework. Use when the user says "add prek", "set up pre-commit hooks", "configure prek", "what hooks should I use", or when you notice a project without a prek.toml that would benefit from pre-commit checks. Also trigger when the user wants to add new hooks to an existing prek.toml, audit their hook config, or migrate from pre-commit to prek. Covers Rust, Python, TypeScript/JavaScript, Go, Ruby, and Shell projects. Do NOT use for husky, lint-staged, or CI pipeline hook configuration — this skill is specifically for prek.
Generate free AI textures/skins (camo, gold plated, carbon fiber, rust, etc.) for Roblox game assets like guns, weapons, tools, or any part/mesh, and apply them automatically inside Roblox Studio through the official Roblox Studio MCP — no manual clicking through Studio's Texture Generator plugin required. Use this whenever the user wants to texture, skin, retexture, or reskin a Roblox model/mesh/gun/weapon/part, asks for an AI-generated texture or decal for a Roblox object, or wants to automate the Studio texture workflow end-to-end. Also trigger if the user asks for "free" or "no-cost" image/texture generation in a Roblox context, even if they don't name a specific tool. Requires the Roblox Studio MCP connected with Studio open — if that's not available, say so clearly instead of guessing.
Dark, grim, gritty, rusty, abandoned, decayed, industrial, lonely, and melancholic mood direction for Blender.
Recommend YouTube videos worth watching on a topic — from your subscribed channels and beyond — ranked with reasons, skipping what you've already watched or summarised with video-lens. Activate on "what should I watch about AI", "new Kubernetes videos this week", "recommend cooking videos", "catch me up on my AI channels", "what did I miss on YouTube", "anything good on Rust lately", "set up video recommendations", "import my YouTube takeout", "sync my YouTube", "add this channel to my AI topic", "mute this channel".
Interactive setup guide for using Infisical as a secret management tool in your projects. Helps users integrate Infisical into local development (CLI), Docker containers (build-time and runtime secret injection), CI/CD pipelines (GitHub Actions, GitLab CI), Kubernetes (Operator + CRDs), and application code (all 9 SDKs: Node.js, Python, Go, Java, .NET, Ruby, PHP, Rust, C++). Also walks through choosing and configuring any of the 13 machine identity auth methods (Universal, Token, Kubernetes, GCP, AliCloud, AWS, Azure, TLS Cert, OCI, OIDC, JWT, LDAP, SPIFFE). Use this skill whenever someone asks about: using Infisical, injecting secrets, infisical run, infisical init, connecting their app to Infisical, Docker secrets, Kubernetes secrets operator, machine identity setup, SDK initialization, CI/CD secret injection, or 'how do I get my secrets into my app'. Not for the Kubernetes Operator CRDs (infisical-kubernetes-operator), rendering secrets to files (infisical-agent), pushing secrets outward (infisical-secret-syncs), or human SSO login (infisical-sso).
Apply the Unix philosophy (Eric S. Raymond's 17 rules, McIlroy's "do one thing well", Rob Pike's rules on measurement and data) when designing, writing, refactoring, or reviewing software in any programming language. Use this skill whenever the user asks to design a module, service, CLI, API, library, or package; write or refactor non-trivial code; review a pull request or code for quality; split a large function, class, or service; decide between a clever and a simple approach; or asks about modularity, composability, simplicity, error handling, or "clean" design, even if they never mention Unix. Works for Go, TypeScript/JavaScript, Python, Java/Kotlin, Rust, Haskell, Lean 4 (programs and proofs), and other languages.
FigCraft is an open-source, pure-Rust, offline interface-design, prototyping and whiteboard app (a clean-room reimplementation of the Figma Design workflow): frames, auto layout, components, styles, variables, vector networks, prototyping, Dev Mode and board files, on macOS, Windows, Linux, FreeBSD and the web. Trigger it whenever the user mentions FigCraft or a `.figcraft` file, asks what it can or cannot do, which formats it opens or writes, how to script, automate, batch or headlessly drive it (figcraft-cli, MCP, the JSON control channel), wants assets prepared for a design file, needs output verified or repaired, or asks to troubleshoot it — and when the app is not named but the job is one of its jobs: "make a mockup", "design a screen / landing page / dashboard", "build a design system", "export these frames to PNG/PDF/SVG", "open this .fig or Figma file JSON", "convert this Sketch file", "prototype this flow", "hand this off to a developer", "make a retro board". Do not guess capabilities from Figma knowledge — FigCraft is not Figma and runs no Figma plugins.
MUST USE whenever writing, editing, refactoring, or reviewing code in Python, TypeScript, JavaScript, Rust, Go, C, C++, Zig, Java, C#, or Lua. Enforces a mandatory 10 ms code-readability gate that catches what compilers and formatters miss: AI slop, narrator comments, swallowed errors, deep nesting, `*Factory`/`*Manager` ceremony, cryptic 1-2 char variable golf, magic-number indexing, and copy-pasted blocks. Run before finishing every coding turn—no exceptions.
Know a signed-in user's name, email or organization in a canister, not only their principal. Internet Identity signs an attribute bundle alongside the delegation, and the backend verifies the signer, the frontend origin and a nonce it issued itself before believing any of it. Use when a canister must know something about the caller beyond their principal: filling a profile, showing a name the user never typed into your app, contacting them, or gating access or an allowlist on an address the user provably controls; and when the backend rejects a bundle the frontend has just obtained. Covers the frontend request, scoping attributes to the account signed in with, and the identity-attributes library for Motoko and Rust. Assumes sign-in already works: load user-sign-in first. Do NOT use for the sign-in flow itself, for an email address the user typed in (that is ordinary app input, which II has not checked), or for an agent or CLI acting as a user (agent-web-identity).
The normative Design Guides for Native Shell (NSH) apps. Read before designing or changing any screen, layout, spacing, visual hierarchy, color, density, component choice, interaction state, overlay, motion, data-heavy view or interface copy in an NSH app, in TSX or Rust, and before reviewing UI work for design quality. Also use when asked what the design rules are, or whether a UI decision follows them.
Notify your app's users from your canister, on their devices and even while the app is closed. Internet Identity delivers each notification (as web push), so there is no push service, no VAPID keys and no device tokens in the app: the canister addresses a user and II reaches their browsers. Covers asking the user's consent in the frontend (requestNotificationConsent, getNotificationConsentStatus, revokeNotificationConsent, needing @icp-sdk/auth 11.1.0), the /.well-known/ii-notification-senders document, and sending with the identity-notifications library from Motoko or Rust. Use when an app must tell a user something while they are not looking at it, when adding notifications, web push or a notifications toggle, or when the user consented and nothing arrives. Assumes sign-in already works and the app's primary origin is settled: load user-sign-in first. Do NOT use for in-app notification UI or email, or for reaching anyone who is not a signed-in user of this app.
Receive email in an Internet Computer canister through the SMTP Gateway Protocol. Covers implementing smtp_request and smtp_request_validate, addressing (user@<canister-id>.icp0.io, custom domains, handing mail to another canister with /.well-known/ic-smtp-canister-id), how the gateway turns reply codes into SMTP (5xx bounces, everything else retries, 550 rejects one recipient), what actually arrives (raw headers, raw MIME body, a per-attempt message_id, no sender authentication), the ic-smtp-gateway-protocol Rust crate, and the optional chunked upload for messages over 2 MiB. Use when a canister must receive or process inbound email, when implementing the SMTP gateway Candid interface, or when mail to a canister bounces, is retried, or never arrives. Do NOT use for sending email from a canister (the gateway is inbound only; call an email API with https-outcalls) or for serving HTTP from a canister.