Skills
98,067 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Reviews TypeScript code for project-specific quality patterns. Use when writing entities, services, repositories, comparators, formatters, bootstrap methods, deployment stages, diff support, or reviewing PRs with functional patterns. Do NOT use for general TypeScript tutorials or non-Configurator projects.
Verify assumptions before implementing large or risky changes to APIs, provider data, billing, pricing, quotas, or defaults. Use when a mistake could affect customers or the user asks if a change is safe to ship. Checks real-world impact beyond passing tests.
Plan and build a new callable Recursive Language Model with predict-rlm. Use when a user wants to design an RLM, assess whether an RLM fits a workflow, or implement an RLM package with structured boundaries, skills, host-side tools, custom adapters, or runtime-kernel extensions. For optimization of an existing RLM, use rlm-gepa instead.
Use for anything involving a roadmap (a phased multi-checkpoint plan tracked with markdown checkboxes under docs/<feature-slug>/) — creating one for a task too large for a single spec/plan (“roadmap”/“дорожная карта”, multi-week migration, multi-release rollout, phased rewrite), a generic “let's continue the roadmap” request that doesn't say whether that means documentation or implementation, taking the next unfinished checkpoint (“возьми следующую задачу в роадмапе”, “take the next roadmap task”, “next roadmap checkpoint”), or batch-drafting and validating several of its steps' specs/plans at once (“напиши несколько планов”, “пройтись по роадмапу”, “на все задачи роадмапа”). This skill is the single entry point for all of that — it reads the situation and routes to the right reference file itself
Use for Roblox Engine API lookup during implementation: finding the correct engine class or service, confirming properties, methods, events, callbacks, datatypes, enums, globals, and built-in libraries, and verifying parameter, return, and property usage for a known engine task. Prefer this skill when the problem is referential rather than architectural.
Use when making Roblox avatars/characters look accurate or varied — sourcing and applying clothing (shirts/kits), hair, and faces from the Marketplace catalog, validating them, rendering to hand-pick good ones, and doing nation/identity-weighted skin & hair. Covers the WebFetch catalog-API pipeline that the Studio search_asset tool can't do.
Provides comprehensive guidance for Rollup bundler including configuration, plugins, code splitting, tree shaking, and library bundling. Use when the user asks about Rollup, needs to bundle libraries, optimize output, or configure Rollup for production builds.
Use Roundfix to plan releases with the read-only Release Plan Command, clean CodeRabbit pull request feedback, diagnose runtime readiness with the Doctor Command, execute a Spec's Task Graph with the Implement Command, monitor Runs through the Supervisor Run Event Stream, reclaim Run storage with the GC Command, archive completed Specs, run its `--follow-up`, `--status` and `--unattended` Skill Modes, and, inside daemon-assigned Batch runs, follow the bounded Review Issue or Task resolution contract.
Design and review Rust async code around task ownership, suspension points, cancellation, blocking work, and runtime boundaries. Use when writing, refactoring, or reviewing futures, async functions, Tokio tasks, spawn, JoinHandle, Send futures, async traits, cancellation, or mutexes across await points.
Design and review thread-based Rust concurrency with explicit ownership, sharing, and synchronization choices. Use when writing, refactoring, or reviewing threads, scoped threads, channels, Arc, Mutex, RwLock, Condvar, atomics, OnceLock, LazyLock, Send, Sync, deadlocks, or shared state.
Use when preparing, containerizing, configuring, testing, or reviewing Rust services for deployment, especially Docker multi-stage builds, runtime configuration, environment overrides, secrets, health checks, SQLx offline builds, release profiles, image-size reduction, or production startup validation.
Use when modeling, validating, refactoring, or reviewing Rust service domain boundaries, especially when replacing primitive String fields with newtypes, parse-don't-validate constructors, private invariants, TryFrom/FromStr parsers, request DTO boundaries, or property tests.
Use when adding, changing, debugging, or reviewing Rust service error handling and observability, especially when separating domain errors from HTTP responses, adding thiserror/anyhow, implementing ResponseError or IntoResponse, adding tracing spans, redacting secrets, or diagnosing async failures.
Design and review Rust FFI boundaries that keep raw declarations isolated behind safe ownership, lifetime, error, and cleanup wrappers. Use when writing, refactoring, or reviewing unsafe extern blocks, C ABI wrappers, repr(C) types, CString, CStr, raw handles, Drop cleanup, bindgen, cbindgen, or panic-safe foreign boundaries.
GitHub Actions CI/CD for Rust+Node.js hybrid repos. Covers workflow structure, installable composite actions, artifact flow, caching, and dev versioning. Use when: (1) setting up or fixing GitHub Actions workflows, (2) adding CI for a Rust+Node.js project, (3) working with composite actions (setup-workspace, rust-cross-build, compute-version, wait-npm-propagation), (4) debugging CI failures, (5) setting up the cross-platform build matrix. Triggers on "CI", "workflow", "GitHub Actions", "cross-build", "artifact", or work in .github/workflows/.
Publish Rust binaries to npm using the optionalDependencies platform package pattern. Covers the full publish pipeline, version sync, workspace:* protocol, and platform package architecture. Use when: (1) publishing Rust binaries to npm, (2) setting up the platform package pattern (main + per-OS packages), (3) debugging publish failures, (4) managing version sync across pnpm + Cargo workspaces, (5) working with workspace:* protocol. Triggers on "publish", "platform packages", "optionalDependencies", "bin.js", "version sync", "workspace protocol", "npm tag", or "prepare-publish".
Design and review Rust trait APIs, generic bounds, dispatch models, and conversion contracts for clear public interfaces. Use when designing, refactoring, or reviewing traits, generics, trait objects, associated types, impl Trait, From/TryFrom, AsRef, Borrow, or crate APIs.
Designs and architects Salesforce solutions using the Well-Architected framework (Trusted, Easy, Adaptable), Architect Decision Guides, and integration patterns. Use when the user mentions Salesforce architecture, solution design, org strategy, data modeling, integration patterns, multi-cloud design, Agentforce architecture, Data 360, Experience Cloud, automation strategy, security/sharing model, governor limits, DevOps/ALM, ERDs, record-triggered automation, building forms, event-driven architecture, or migration/deployment strategy. Also triggers for phrases like "design my Salesforce," "best pattern for," or "review my Salesforce org."
Use when the user asks to create, scaffold, bootstrap, or add a new NestJS application or service — standalone or as a new app inside an Nx monorepo — including requests phrased as "make/create a new Nest app/service". Applies whenever the new app needs pino logging, a global exception filter + unified API response interceptor, this author's ESLint/Vitest/pre-commit/pre-push conventions, and baseline Dockerfile/docker-compose/Makefile/.env.example deployment files wired up.
Turn a user-provided video into an Apple-style, scroll-driven website with smooth canvas video scrubbing, optimized WebP frame sequences, progressive loading, and responsive motion. Use for cinematic product reveals, landing pages, scrollytelling, image-sequence animation, and scroll-controlled video; also optimize generated frame assets.
Build or update a GitHub Pages documentation site with the same design as fandhe-frontend. Covers Rust SSG, Markdown management, automated deployment with Actions, and branding configuration (the site table in nav.toml). Use for requests such as “I want to publish on GitHub Pages,” “create a docs site,” “use the same design as fandhe-frontend,” “update the Pages site,” or “bring the design up to date.” For publishing with Firebase, use setup-firebase-hosting; for a standalone HTML page, use create-html-report.
Integrate Shopify-validated Storefront or Customer Account GraphQL into Vercel Shop. Use after Shopify AI Toolkit has supplied and validated an API operation, or when adapting existing GraphQL to the template's operation placement, fragments, domain transforms, locale flow, cache role, invalidation, and route architecture.
Trigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to `sm swab`, `sm scour`, `sm buff`, `sm sail`, `sm refit`, or `sm doctor` so remediation follows the established rails. Also trigger when filing issues about slop-mop friction — use `sm barnacle file` / `/slopmop:sm-barnacle`, never `gh issue create`.
Every task that touches a project—implementing, refactoring, diagnosing failed checks, running a project command, or writing a pull request body. The baseline discipline underneath specialized skills: keep changes scoped, run the format and lint loop, map what the change puts at risk, and find out how the project is actually run. Applies even when the request never mentions formatting, linting, comments, dependencies, docs, or descriptions, and when you need one of the project's operations—tests, dev server, build, lint, deploy—and must find it documented or ask. Change-loop practices own progression after results; the conduct baseline applies when a session touches nothing.
Use when working with SpacetimeDB low-level formats and ABI details: BSATN, SATS JSON, AlgebraicValue, AlgebraicType, WebAssembly module ABI, host calls, buffers, reducer scheduling, table mutation, querying, or `bindings.h`. Triggers on: BSATN, SATS, AlgebraicValue, AlgebraicType, wasm ABI, module ABI, host calls.
Choose the planning form for new work and plan it before execution. Use this skill to decide whether the work is taskless, chat-only, a task file, a task file with subtasks, or multiple task files / backlog items, and to create the needed plan for non-trivial implementation work or investigation work that needs its own task.
Use when Stigg is being provisioned or has just been provisioned through Stripe Projects — `stripe projects add stigg/environment`, `stripe projects catalog`, `stripe projects rotate`/`remove` against Stigg, or when a `.env` already holds `STIGG_SERVER_API_KEY` / `STIGG_CLIENT_API_KEY` that Stripe Projects wrote. Also use when the user asks to add pricing, entitlements, feature gating, or usage metering to an app that is already using Stripe Projects, so the environment is provisioned from the terminal instead of by signing up in a browser. Covers what the provisioned credentials are and the first wiring of the server and client SDKs. Skip for Stigg work unrelated to Stripe Projects — load the `stigg` umbrella and its pillars instead.
A strategic thinking partner for Claude Code that separates deciding from building. Challenges assumptions, compares approaches, and hands execution a ready-to-run prompt in a fresh session. Handles skill routing, context handoff, and memory management. Use when: "plan my project", "advise on architecture", "what should I build next", "help me think through", "explore", "brainstorm", "how should I approach", "what's the right tool", "which skill do I use", "route this task", "hand off context", "manage my session". Triggers on: /strategic-partner, /advisor, /sp
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
Implement the Syncfusion JavaScript BlockEditor control - a modern block-based text editor with drag-and-drop, slash commands, extensive formatting capabilities, and real-time collaborative editing. Use this skill IMMEDIATELY for: BlockEditor implementation, block-based editors, content editing with blocks, document editors with block structure, text editing with modern UI, slash command menus, drag-and-drop content reordering, inline toolbars, collaborative editing features, real-time multi-user editing, Yjs integration, user presence and remote cursors, document version history, structured content creation, @mentions and labels, code blocks with syntax highlighting, tables and lists, collapsible sections, or any Syncfusion EJ2 BlockEditor control usage in JavaScript applications.
Implements the Syncfusion JavaScript SpeechToText control. Use this skill ALWAYS immediately for speech-to-text functionality, voice recognition, speech transcription, or microphone-based input in JavaScript applications. This skill provides guidance for implementing the SpeechToText control to transcribe spoken audio to text, handle speech recognition events, customize button appearance, set language options, manage listening states, and apply security best practices for voice input features.
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, implementing dark mode, debugging CSS variable issues, fixing theme switching, migrating from Tailwind v3, or encountering color/theming problems. Covers: @theme inline pattern, CSS variable architecture, dark mode with ThemeProvider, component composition, vite.config setup, common v4 gotchas, and production-tested patterns. Keywords: Tailwind v4, shadcn/ui, @tailwindcss/vite, @theme inline, dark mode, CSS variables, hsl() wrapper, components.json, React theming, theme switching, colors not working, variables broken, theme not applying, @plugin directive, typography plugin, forms plugin, prose class, @tailwindcss/typography, @tailwindcss/forms
Code-level craft for agent-built UI: semantic HTML, token-driven CSS (no hardcoded values), specificity discipline, component hygiene, zero inline styles, no dead code. The engineering half of "designed, not generated" — a beautiful page is betrayed by sloppy markup. Use when generating or auditing any frontend code. Stack on the design-taste core skill.
Configure Tavus CVI personas with custom LLMs, TTS engines, perception, and turn-taking. Use when customizing AI behavior, bringing your own LLM, configuring voice/TTS, enabling vision with Raven, or tuning conversation flow with Sparrow.
Chinese-first technical learning skill: quickly grasp technical concepts, read GitHub repositories/codebases, systematically study a topic, clarify technical questions, or generate reviewable HTML lessons. By default it initializes a learning area and produces HTML for main-line lectures, with adjustable pacing; technical terms keep their English or common abbreviations, but their role and boundaries must be explained in Chinese.
Ship changes via pull request in Tenzir projects. Use when the user wants to open a PR, push a branch, add or update changelog entries, create a pull request for review, or when they say "ship this", "open a PR", "send this for review", or "push and create a pull request." Also use for follow-up changes to an existing PR.
Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end. Use when testing batch import support tooling, debugging MCP tool responses or discovery (tools not appearing), or verifying the support API before deploying. Covers the discovery gate: hidden scope, is_staff, user:read, and why wildcard keys and OAuth never work.
Build, migrate, theme, drill down, and validate reusable Three.js 3D geographic maps and Earth View entrances for Vue or web dashboards. Use when Codex is asked to create or modify a pure Three.js globe, province-level, all-China, or world 3D maps; transition from an Earth View into the existing China map; switch map boundaries between provinces, country scope, world scope, city scope, or district scope; add hierarchical drilldown from world to country, China to province, province to city, city to district/county; replace GeoJSON, labels, scatter points, fly lines, terrain textures, or chase-light paths; derive a whole map color system from one theme color; or preserve an existing dark HUD-style 3D map visual across new regions.
Calculate training costs for Tinker fine-tuning jobs. Use when estimating costs for Tinker LLM training, counting tokens in datasets, or comparing Tinker model training prices. Tokenizes datasets using the correct model tokenizer and provides accurate cost estimates.
Spin up an isolated git worktree in its own tmux session — coding agent in one window, a shell in another, dev stack in a third — with the agent briefed and already working. Use for spinning up a worktree, starting a feature/branch/task in isolation, handing work to a fresh agent (Claude/Codex), or setting up an isolated tmux dev session.
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs. Use when issues or external PRs need categorising, verifying, and turning into agent-ready briefs. Triggers on: triage, triage the backlog, review these issues.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.