Skills
Do not edit this file. pnpm census writes it from the live registries.
Skills (82)
A skill is the source of truth for its topic. Each skill has one tool. The guardrails page lists the rules that a skill checks.
The router directory, skills/rule/, has no skill tool.
So the catalog has 82 skills and skills/ has 83 directories.
| Area | Skills | Covers |
|---|---|---|
| ai | 5 | Building agents: prompting, context, evals, agent architecture |
| backend | 9 | Services and APIs: Node frameworks, API design, backend security |
| data | 9 | Databases and storage, and the shape and validation of the data that reaches them |
| devops | 5 | Pipelines, containers, observability, testing, versioning |
| frontend | 7 | Frameworks and the code that runs in a browser |
| meta | 5 | |
| platform | 5 | Where the code ships: web, desktop, mobile, library, agent |
| process | 11 | How work is done: reviews, ADRs, changelogs, handoffs, simplicity |
| styleguide | 15 | The rules code is written to, per language and concern |
| toolchain | 9 | Build tools, linters, package manager, commit hooks |
| ui | 2 | The design system and its components |
ai
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-ai |
rule_tool_ai |
all | Use when building an AI agent or an AI feature, to route to the right ai-* skill. Covers evals, context engineering, agent architecture, prompting, and where a model belongs in a product. |
rule-ai-agent-architecture |
rule_tool_ai_agent_architecture |
all | Use when building or reviewing an agent, an MCP server, or a tool surface. Covers what actually happens at the API boundary when a tool call happens, why the harness and not the model decides quality, loops against graphs, what MCP does and does not give you, tool granularity and naming, and exposing an application as a tool surface. |
rule-ai-context-engineering |
rule_tool_ai_context_engineering |
all | Use when an agent session is getting expensive, slow or worse at its job. Covers the context window as a budget, why adding files degrades answers, the levels of delegation from autocomplete to autonomous, compaction and handoff, pointing at evidence instead of pasting it, and what actually consumes a usage limit. |
rule-ai-evals |
rule_tool_ai_evals |
all | Use when building or auditing evals for an AI feature. Covers error analysis before writing any eval, binary LLM-as-judge design, judge calibration against human labels with TPR and TNR, RAG evaluation, synthetic test inputs, and running evals in CI. |
rule-ai-prompting |
rule_tool_ai_prompting |
all | Use when working with an AI coding agent, and when teaching someone to. Covers what a prompt needs, context engineering, the mistakes that waste the most tokens, when NOT to let AI write the code, and how to keep learning while using it. |
backend
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-backend |
rule_tool_backend |
all | Use when designing or building a backend service to route to the right runtime, protocol, or hardening skill. Covers REST, GraphQL, Express, Fastify, NestJS, Hono, the Node runtime, and the security and worker boundaries. |
rule-backend-express |
rule_tool_backend_express |
all | Use when building Express.js 5+ applications. Covers middleware patterns, error handling, routing, security headers, and production deployment. |
rule-backend-fastify |
rule_tool_backend_fastify |
all | Use when building Fastify 5+ applications. Covers plugins, hooks, schema validation, serialization, and high-throughput API optimization. |
rule-backend-graphql |
rule_tool_backend_graphql |
node, api, graphql | Use when designing, implementing, securing, or operating GraphQL APIs. Covers schema-first contracts, resolver boundaries, N+1 prevention, query abuse controls, caching, and error contracts. |
rule-backend-hono |
rule_tool_backend_hono |
all | Use when building Hono 4+ edge-compatible APIs. Covers middleware, Zod validation, RPC-style type sharing, and multi-runtime deployment. |
rule-backend-nestjs |
rule_tool_backend_nestjs |
all | Use when building NestJS 10+ applications. Covers modular architecture, decorators, dependency injection, guards, interceptors, GraphQL, and microservices. |
rule-backend-node |
rule_tool_backend_node |
node, api | Use when scaffolding or hardening a Node.js backend. Covers project structure, required libraries, quality gates, and the patterns that break under real traffic: blocking the event loop, unbounded Promise.all, buffering payloads, in-memory state, backpressure, missing timeouts, and fire-and-forget work. |
rule-backend-security |
rule_tool_backend_security |
node, api | Use when securing a backend or reviewing authentication. Covers environment variables, Docker images, dependency audits, security headers, rate limiting, CORS, secrets, input validation, and the authentication lifecycle: JWT verification, session revocation, logout, password reset, remembered devices, step-up auth, and CSRF. |
rule-backend-workers |
rule_tool_backend_workers |
node, worker-threads | Offload CPU-bound JavaScript to worker_threads, pools, and cluster. Covers the event loop model, libuv thread pool, piscina, clustering, and the decision framework for async vs workers vs cluster. |
data
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-data |
rule_tool_data |
all | Use when working with databases to route to the correct database skill. Covers PostgreSQL, MySQL, MongoDB, SQLite, DuckDB, and IndexedDB. |
rule-data-duckdb |
rule_tool_data_duckdb |
all | Use when working with DuckDB for analytical queries and embedded OLAP. Covers SQL, Parquet/CSV import, window functions, and performance optimization. |
rule-data-indexed-db |
rule_tool_data_indexed_db |
all | Use when using IndexedDB in the browser for client-side storage. Covers object stores, indexes, transactions, cursors, and versioning. |
rule-data-mongodb |
rule_tool_data_mongodb |
all | Use when working with MongoDB 7+. Covers schema design, CRUD operations, aggregation pipeline, indexing, sharding, replication, and Mongoose patterns. |
rule-data-mysql |
rule_tool_data_mysql |
all | Use when working with MySQL 8+ or MariaDB 11+. Covers DDL scripts, InnoDB tuning, indexing, replication, query optimization, and production maintenance. |
rule-data-postgresql |
rule_tool_data_postgresql |
all | Use when working with PostgreSQL 16+. Covers DDL scripts, indexing, performance tuning, replication, partitioning, connection pooling, JSONB, and full-text search. |
rule-data-sql |
rule_tool_data_sql |
all | Use when writing SQL queries or designing relational database schemas. Covers table design, indexing, DDL scripts, transactions, and database-agnostic best practices. |
rule-data-sqlite |
rule_tool_data_sqlite |
all | Use when working with SQLite for embedded databases. Covers DDL scripts, query optimization, JSON functions, WAL mode, and production usage patterns. |
rule-data-validation |
rule_tool_data_validation |
all | Use when validating international business data. Covers email, phone, VAT, tax IDs, postal codes, and national identification numbers for EU, UK, and US. |
devops
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-devops |
rule_tool_devops |
all | Use when setting up CI/CD, Docker, testing, or production reliability infrastructure to route to the correct DevOps skill. Covers pipelines, containers, observability, and version management. |
rule-devops-deploy-preview |
rule_tool_devops_deploy_preview |
all | Use when every merge request must get its own ephemeral preview environment. Covers GitLab review apps on DigitalOcean App Platform: DOCR image build, App Spec template, dynamic environment URL, and automatic teardown on merge. |
rule-devops-docker |
rule_tool_devops_docker |
all | Use when creating or maintaining Docker configuration. Covers Dockerfiles, docker-compose.yml, .dockerignore, multi-stage builds, and production readiness. |
rule-devops-observability |
rule_tool_devops_observability |
all | Use when defining production observability, SLOs, logging, metrics, tracing, alerts, incident response, or rollback verification. Covers measurable service health without prescribing a vendor, and tracing an AI agent: spans per tool call, a token ledger, and cost per session. |
rule-devops-testing |
rule_tool_devops_testing |
all | Use when writing unit or integration tests with Vitest. Covers test configuration, mocking, endpoint testing, component testing, and debugging failures. |
frontend
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-frontend |
rule_tool_frontend |
all | Use when building frontend UIs to route to the correct framework skill. Covers React, Vue, Angular, Svelte, SolidJS, Astro, and meta-frameworks. |
rule-frontend-angular |
rule_tool_frontend_angular |
angular | Use when building Angular standalone components. Follows rule-mcp principles: zero CSS classes, semantic HTML, barrel file tree, data-part selectors. |
rule-frontend-react |
rule_tool_frontend_react |
react | Use when building React 18+ functional components. Follows rule-mcp principles: zero CSS classes, semantic HTML, barrel file tree, data-part selectors. |
rule-frontend-solidjs |
rule_tool_frontend_solidjs |
solidjs | Use when building SolidJS applications with fine-grained reactivity. Follows rule-mcp principles: zero CSS classes, semantic HTML, Signals, barrel file tree. |
rule-frontend-svelte |
rule_tool_frontend_svelte |
svelte | Use when building Svelte 5 applications with runes API. Follows rule-mcp principles: zero CSS classes, semantic HTML, $state/$derived, barrel file tree. |
rule-frontend-vue |
rule_tool_frontend_vue |
vue | Use when building Vue 3 Composition API components. Follows rule-mcp principles: zero CSS classes, semantic HTML, barrel file tree, data-part selectors. |
rule-frontend-workers |
rule_tool_frontend_workers |
all | Use when browser JavaScript blocks the main thread. Covers Web Workers, worker pools, transferables, SharedArrayBuffer, OffscreenCanvas, scheduler.yield, and INP/LoAF measurement. |
meta
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-meta |
rule_tool_meta |
astro, next, nuxt, remix | Use when routing a meta-framework request to the correct rule-mcp skill: Astro, Next.js, Nuxt or Remix. Acts as the dispatcher for the meta-framework set, the way rule-mcp dispatches the whole ecosystem. |
rule-meta-astro |
rule_tool_meta_astro |
astro | Use when building Astro islands-architecture sites. Supports zero CSS classes, semantic HTML, partial hydration, and integration with UI frameworks. |
rule-meta-next |
rule_tool_meta_next |
next, react | Use when building Next.js applications. Covers App Router, Server Components, SSR/SSG/ISR, API routes, middleware, and Vercel deployment. |
rule-meta-nuxt |
rule_tool_meta_nuxt |
nuxt, vue | Use when building Nuxt.js applications. Covers file-based routing, SSR/SSG, server routes, auto-imports, Nitro engine, and modules ecosystem. |
rule-meta-remix |
rule_tool_meta_remix |
remix, react | Use when building Remix or React Router applications. Covers nested routing, loaders/actions, SSR, progressive enhancement, and sessions. |
platform
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-platform |
rule_tool_platform |
all | Use when building platform-specific projects to route to the correct platform skill. Covers desktop, mobile (Expo), library authoring, and web conventions. |
rule-platform-auth |
rule_tool_platform_auth |
auth, sessions, jwt, oauth, passkeys | Choose the right authentication strategy for a web app in 2026. Covers server-side sessions vs JWTs, OAuth 2.0/2.1 + OIDC, passkeys/WebAuthn, managed providers, CSRF/XSS hardening, token storage, revocation, and a decision matrix by app archetype. |
rule-platform-desktop |
rule_tool_platform_desktop |
electron, desktop | Use when building desktop applications with Electron. Covers main/preload/IPC, native APIs, window management, packaging, and auto-update. |
rule-platform-library |
rule_tool_platform_library |
all | Use when developing reusable npm packages. Covers pnpm structure, public API design, TypeScript exports, dual CJS/ESM, and semantic versioning. |
rule-platform-web |
rule_tool_platform_web |
all | Use when building browser-based web applications. Covers bundling, routing, progressive enhancement, performance budgets, WCAG 2.2 AA, and CDN deployment. |
process
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-process |
rule_tool_process |
all | Use when following development methodologies to route to the correct process skill. Covers ADRs, BMAD, code review, documentation, feature workflow, session handoff and handon, and prose/prompt compression via rule_tool_compress. |
rule-process-adr |
rule_tool_process_adr |
all | Use when recording architecture decisions. Covers auto-numbered ADRs with Nygard template, searchable index, and chronological ordering. |
rule-process-ai |
rule_tool_process_ai |
all | Use when planning how AI fits the delivery lifecycle rather than a single task, or when writing anything a reader will see. Covers the artifact chain from intent to incident, plan before code, the scope contract and the over-engineering catalog, English with American spelling and ASCII punctuation, and the phrasing that reads as machine-written. |
rule-process-bmad |
rule_tool_process_bmad |
all | Use when following the BMad structured delivery method. Covers 4-phase workflow (analysis, planning, solution, implementation) with agent-guided execution. |
rule-process-cargo-release |
rule_tool_process_cargo_release |
cargo, github-actions | "Set up a secure release process for a Rust crate: publish to crates.io through Trusted Publishing, keep the API token out of the workflow, dry-run before the irreversible upload. Use for any request to publish a crate, release to crates.io, harden a cargo publish pipeline, or migrate a token-based release to OIDC." |
rule-process-changelog |
rule_tool_process_changelog |
all | Use when a project needs a CHANGELOG, when deciding where changelog entries come from, or when one has drifted from the commits. Covers generating it from conventional commits, which commit types earn an entry, and why the release tag is the moment to build it rather than the commit hook. |
rule-process-code-review |
rule_tool_process_code_review |
all | Use when preparing, conducting, or improving a pull or merge request review. Covers review readiness, risk-based review, constructive feedback, approval gates, and follow-up ownership. |
rule-process-npm-release |
rule_tool_process_npm_release |
npm, github-actions | "Set up a secure release process for an npm package to protect it from supply chain attacks. Use for any request to create and publish a new npm package, secure npm publishing or releasing, set up npm Trusted Publishing, provenance, or Staged Publishing, harden a release workflow." |
rule-process-readme |
rule_tool_process_readme |
markdown, readme | 'Write or improve a README.md for an open source project. Use this for any request to create, rewrite, review, or polish a README, project description, or "getting started" docs for a library, framework, or tool, or to make an open source project more popular or attractive to users. Do NOT use for internal/private repo docs, API reference generation, or CHANGELOG/CONTRIBUTING files.' |
rule-process-tdd |
rule_tool_process_tdd |
all | Use when developing test-first (red-green-refactor) or when writing tests: unit tests via TDD, accessibility tests with Playwright + axe-core, or test setup for a project. Covers failing-test-first discipline, choosing what to cover, assertion quality, and closing the loop with rule_tool_check. |
rule-process-uv-release |
rule_tool_process_uv_release |
uv, github-actions | "Set up a secure release process for a Python package managed with uv: build with uv, publish to PyPI through Trusted Publishing, keep no API token in a workflow. Use for any request to publish a Python package, release to PyPI, harden a uv publish pipeline, or migrate an NPM-style or twine-based release to OIDC." |
styleguide
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-styleguide |
rule_tool_styleguide |
all | Style guides index - entry point for all coding style, conventions, best practices, guidelines, naming, and formatting rules. Use when the prompt mentions styleguides, coding standards, best practices, guidelines, conventions, or code formatting. Routes to the correct sub-skill based on topic: HTML semantics, CSS architecture, JS/TS conventions, JSON structure, Markdown formatting, naming/file-tree, accessibility (WCAG/a11y), internationalization (i18n/l10n), or business validation. |
rule-styleguide-a11y |
rule_tool_styleguide_a11y |
all | WCAG 2.2 AA compliance framework integrating A11Y.md persistent context protocol. Covers AI Behavioral Contract, Compliance Profiles (Shield/Standard/Launchpad), severity model, POUR standards, semantic HTML, ARIA, keyboard navigation, color contrast, platform-native mapping, and Playwright + axe-core verification. |
rule-styleguide-baseline |
rule_tool_styleguide_baseline |
all | Use when deciding whether a platform feature is safe to use, or when writing guidance that recommends one. Covers the three Baseline states, what a fallback really costs, progressive enhancement with supports queries, and declaring the project's own support floor in prose and in browserslist. |
rule-styleguide-comments |
rule_tool_styleguide_comments |
all | Use when writing or reviewing code comments. Covers what a comment is for, the three kinds that should never be committed - commented-out code, code kept for future use, and change history - and what to write instead. |
rule-styleguide-configuration |
rule_tool_styleguide_configuration |
all | Use when setting up base project configuration files. Covers .gitignore, .editorconfig, .nvmrc, .env.example, README, LICENSE, and CONTRIBUTING. |
rule-styleguide-css |
rule_tool_styleguide_css |
all | Use when writing CSS following rule-mcp architecture. Covers data-part selectors, element selectors, cascade layers, custom properties, and responsive design. |
rule-styleguide-file-tree |
rule_tool_styleguide_file_tree |
all | Use when laying out a source tree: the underscore-barrel convention, where a component folder puts its index.js, which files carry the underscore prefix, and what a barrel must re-export. Covers the scan that finds the drift and the fix that repairs it. |
rule-styleguide-git |
rule_tool_styleguide_git |
all | Use whenever writing, preparing, or validating git commits and pushes. Enforces atomic Conventional Commits with a MANDATORY scope on every commit - no bare fix: allowed. |
rule-styleguide-html |
rule_tool_styleguide_html |
all | Use when writing semantic HTML following rule-mcp conventions. Covers the mandatory document boilerplate (doctype, charset, viewport, title, icons, canonical, Open Graph), semantic elements over div, document structure, accessibility, and element selection. |
rule-styleguide-i18n |
rule_tool_styleguide_i18n |
all | Use when a product ships in more than one language or region. Covers what to externalize and how to key it, plural and gender rules, locale-aware dates, numbers, currencies and units via Intl, right-to-left layout, and the concatenation habits that cannot be translated. |
rule-styleguide-javascript |
rule_tool_styleguide_javascript |
all | Use when writing JavaScript or TypeScript following rule-mcp conventions. Covers naming, functions, classes, async patterns, modern idioms (Set.has, for...of, node: protocol, replaceAll, flatMap), DOM manipulation, and custom elements. |
rule-styleguide-json |
rule_tool_styleguide_json |
all | Use when structuring JSON data or API responses. Covers property naming, date formats, numeric precision, schema patterns, and consistency. |
rule-styleguide-markdown |
rule_tool_styleguide_markdown |
all | Use when writing Markdown documentation following rule-mcp style. Covers headings, lists, code blocks, tables, links, and tone for technical docs. |
rule-styleguide-naming |
rule_tool_styleguide_naming |
all | Use when following rule-mcp naming conventions for files, folders, and exports. Covers PascalCase, camelCase, UPPER_SNAKE_CASE, barrel patterns, and directory layout. |
rule-styleguide-typescript |
rule_tool_styleguide_typescript |
all | Use when writing or reviewing TypeScript code, or configuring its compiler. Covers the anti-patterns that flag in review (any, as, enum, optional-chaining sprawl), the practices that hold up at scale (generics, never, readonly, self-documenting APIs), where types live, and the tsconfig, strict mode and path aliases. |
toolchain
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-toolchain |
rule_tool_toolchain |
all | Use when configuring build tools, linters, or package managers to route to the correct toolchain skill. Covers Vite, Rspack, Parcel, Biome, ESLint, pnpm, Turborepo, and Husky. |
rule-toolchain-biome |
rule_tool_toolchain_biome |
all | Use when configuring Biome linter and formatter. Covers zero-config setup, migration from ESLint + Prettier, rule customization, and CI integration. |
rule-toolchain-eslint |
rule_tool_toolchain_eslint |
all | Use when configuring ESLint for JavaScript/TypeScript projects. Covers ESLint 10 flat config, eslint-plugin-unicorn presets and high-value rules, type-aware linting with typescript-eslint, incremental adoption, and CI setup. |
rule-toolchain-husky |
rule_tool_toolchain_husky |
all | Use when setting up Git hooks with Husky. Covers commit hooks, pre-push validation, lint-staged, commitlint, and CI-friendly configuration. |
rule-toolchain-parcel |
rule_tool_toolchain_parcel |
all | Use when building applications with Parcel 2+ bundler. Covers zero-config setup, entry points, code splitting, image optimization, and production builds. |
rule-toolchain-pnpm |
rule_tool_toolchain_pnpm |
all | Use when managing packages with pnpm. Covers workspaces, caching strategies, CI optimization, monorepo patterns, and store management. |
rule-toolchain-rspack |
rule_tool_toolchain_rspack |
all | Use when configuring Rspack as build tool. Covers rspack.config.ts, CSS, bundle optimization, code splitting, type checking, and debugging. |
rule-toolchain-turborepo |
rule_tool_toolchain_turborepo |
all | Use when orchestrating monorepos with Turborepo. Covers pipeline configuration, caching, remote caching, task dependencies, and parallel builds. |
rule-toolchain-vite |
rule_tool_toolchain_vite |
all | Use when configuring Vite as build tool. Covers vite.config.ts, environment variables, build optimization, and production deployment. |
ui
| Skill | Tool | Frameworks | Description |
|---|---|---|---|
rule-ui |
rule_tool_ui |
all | Use when designing or implementing user interfaces to route to the correct UI skill. Covers design systems, component patterns, accessibility, and styling tactics. |
rule-ui-design-system |
rule_tool_ui_design_system |
all | Use when creating production-grade UI components and design systems. Covers component composition, interaction design, accessibility states, external CSS, and design critique of a generated interface one axis at a time. |