Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Interactively guides the documentation of arc42 Section 12 (Glossary). Scans other sections for undefined terms, asks about domain vocabulary and ambiguous terminology, and generates a structured glossary with consistent preferred terms. Iterates until the user is satisfied.
Use when a business transaction spans multiple services or aggregates and no distributed-transaction primitive is available — phrases like "saga pattern", "distributed transaction", "compensating action", "choreographed saga", "orchestrated saga", "process manager", "should we use a saga here", "how do we roll back across services". Defines a saga as a sequence of local transactions tied together by compensating actions, with two implementation styles (choreography and orchestration).
Use when discussing object-oriented design principles or component-level structure — phrases like "SOLID", "Single Responsibility", "Open-Closed", "Liskov Substitution", "Interface Segregation", "Dependency Inversion", "SRP", "OCP", "LSP", "ISP", "DIP". Defines the five SOLID principles, with the honest caveats Uncle Bob's original treatment glosses over and the cases where they shouldn't be applied dogmatically.
Design Azure cloud architectures from requirements and generate High-Level Design (HLD) documentation with service selection, patterns, cost estimates, and WAF alignment. Use this when asked to design or architect Azure solutions.
Generate an ARCHITECTURE.md file for a codebase following matklad's principles. Use when asked to "write an architecture doc", "create ARCHITECTURE.md", "document the architecture", "explain the codebase structure", "write a codemap", or when onboarding contributors to a project. Based on https://matklad.github.io/2021/02/06/ARCHITECTURE.md.html and modeled after rust-analyzer's architecture doc.
This skill should be used when the user asks to "编译 ArkWeb", "build ArkWeb", "执行 ArkWeb 编译", "验证 ArkWeb 构建", "排查 ArkWeb build.log", "分析 ArkWeb 编译失败", or mentions build_arkweb.sh, src/out/<product>/build.log, ArkWeb native or browser build targets, or incremental ArkWeb build verification. Handles command selection, incremental build execution, success verification, and build.log-first failure diagnosis for ArkWeb projects.
Use when the user wants to stress-test a plan, design, migration, or architectural decision before building or committing; de-risk a major decision; examine design tradeoffs; assess whether a product or feature is worth building (problem evidence, demand test, go/no-go); or says “grill me.” It then interviews the user relentlessly, one question at a time, with a recommended answer for each, exploring the codebase before asking until every branch of the decision tree is resolved and there is shared understanding.
Production-tested setup for AutoAnimate (@formkit/auto-animate), a zero-config drop-in library that automatically adds smooth transitions when DOM elements are added, removed, or moved, at about 3 KB gzipped with no dependencies and built-in prefers-reduced-motion support. Covers the useAutoAnimate React hook, its stable-key and always-rendered-parent requirements, and SSR-safe usage. Use when animating dynamic lists, filter and sort interfaces, accordions, toast notifications, or form validation messages without writing animation code, when working in Vite + React + Tailwind, when deploying to Cloudflare Workers Static Assets, or when hitting SSR errors from animation libraries. For gestures, scroll-linked effects, or complex sequences, use the motion skill instead.
Manage an engineering backlog for humans and AI agents: classify issues, improve issue quality, sync PR state, and label safe tickets for agent execution. Use when GitHub Issues, GitHub Projects, Linear, or an explicit local backlog path is the source of truth.
A collection of concrete rewrite patterns for migrating baserCMS 4 (based on CakePHP 2) plugin internals to baserCMS 5 (based on CakePHP 5): Controller/Table/Entity/View/Helper/forms/Vue and JS. Refer to this when fixing plugin screen, model, template, and frontend display errors one by one, such as “migrate plugins from 4 to 5,” “move admin_ methods to Controller/Admin,” “move public $belongsTo/$hasMany to initialize(),” “ClassRegistry/TableRegistry,” “convert find(all/first/list, array) to the query builder,” “replace $this->Model (null) with fetchTable,” “pluralize getControlSource,” “replace $this->Form with BcAdminForm and control(),” “search form searches/ → search/,” “FormHelper::create string model → null,” “FormHelper::year()/month()/domId() removed,” “Time::format ICU patterns,” “Number::format/Text::truncate do not allow null,” “array conditions no longer auto-add IN; null uses IS,” “change Vue/JS admin URL to $.bcUtil.adminBaseUrl and rebuild with webpack,” “$this->data / $View->request trigger incorrect helper loading,” “MissingTableClassException / MissingHelperException / No context provider found,” “external libraries bundled via App::import in Vendor (such as leafo/scssphp) were not ported to version 5 and their functionality is broken,” and “PHP 8 incompatibilities in old bundled libraries, such as removed each() and invalid regex escapes.” This skill focuses on detecting and converting version 4 idioms; for the authoritative version 5 patterns, see basercms5-plugin-development. For the full site-wide version 4-to-5 migration process (installation/DB migration/theme and plugin conversion/Git practices), see basercms4-to-5-upgrade; for theme (mainly templates) migration, see basercms-theme-4-to-5-upgrade; for plugin migration from 5.2 to 5.3, see basercms-plugin-5x-update; for issues caused by CakePHP itself, see cakephp-migration; for issues caused by PHP itself, see php-migration; for running tests, see basercms-unittest; when migrating plugins that add custom fields to blogs and similar to bc-custom-content, see the basercms5-custom-content-development skill
A recipe collection for baserCMS-specific breaking changes, deprecations, and test infrastructure handling when migrating baserCMS plugins from the 5.2 series to the 5.3 series (based on PHP 8.5 / CakePHP 5.2.x, in development). Refer to this when migrating the plugin itself or its test infrastructure, e.g. "make the plugin compatible with 5.3", "baserCMS 5.3 migration", "PluginCollection::create(): $config null given", "Plugin named X is already loaded (integration test)", "BcApp.testAppPluginsToLoad", "plugins.php null → []", "Class BcCcFile\... not found (sub-plugin not loaded)", "Cannot set a node''s parent as itself (TreeBehavior + Content fixture)", "validateUnique(): Argument #2 not passed (double loading of vendor CakePHP)", "MissingTemplateException error500.php masks the test's true cause", "deprecation of the BcFile constructor/delete() path argument". This is a skill for a minor update within the same major version (5.2→5.3); for the major upgrade from baserCMS 4 to 5 (a full rewrite from CakePHP 2 to 5), refer to basercms-plugin-4-to-5-upgrade. For issues caused by PHP itself refer to php-migration, for issues caused by CakePHP itself refer to cakephp-migration, and for test execution steps refer to the basercms-unittest skill. When handling a new baserCMS version, append it to this document by version.
A collection of development rules for baserCMS 4 series (based on CakePHP 2.10) + jQuery projects. Refer to this when checking the coding policy, directory structure, naming conventions, logging/error handling, treatment of read-only files, and server constraints for baserCMS 4 series projects, e.g. "develop with baserCMS 4", "fix a 4 series plugin", "write CakePHP 2 series code", "Controller/Model/View under app/Plugin", "theme Elements/Layouts", "using BcBaserHelper/BcFormHelper/BcHtmlHelper", "output logs with CakeLog", "no core hacks in lib/Baser and lib/Cake". For baserCMS 5 series development refer to basercms5-development, and for 4→5 upgrades refer to the basercms4-to-5-upgrade skill.
A collection of rules and patterns AI agents should follow when upgrading or migrating baserCMS 4 (based on CakePHP 2) code and sites to baserCMS 5 (based on CakePHP 5). Covers the full 4-to-5 upgrade process, including “migrate from baserCMS 4 to 5,” “upgrade from version 4 to 5,” “migrate data with BcDbMigrator,” “convert themes/plugins with BcAddonMigrator,” “rewrite CakePHP 2 → CakePHP 5,” “move admin_ prefixed methods to Controller/Admin,” “convert config/setting.php and config.php to return arrays,” “remove init.php and create PluginClass,” “generate migration_snapshot,” “site_configs theme → sites theme,” “standard migration flow/order,” “enable plugins directly in the DB,” “apply themes directly in the DB,” “convert request->data/query/params to getters,” “remove File/Folder classes,” “ClassRegistry → TableRegistry,” “FrozenTime → DateTime,” and “FixtureManager → FixtureFactory.” For specific rewrites of plugin internals (Controller/Table/Entity/View/Helper/forms/Vue/JS), see basercms-plugin-4-to-5-upgrade; for theme migration (mainly templates), see basercms-theme-4-to-5-upgrade; for plugin migration from 5.2 to 5.3, see basercms-plugin-5x-update; for changes caused by CakePHP itself, see cakephp-migration; for changes caused by PHP itself, see php-migration; for running tests, see the basercms-unittest skill. For correct baserCMS 5 code as the source of truth for development, see basercms5-plugin-development / basercms5-theme-development.
Base skill defining shared rules for baserCMS 5 (CakePHP 5.0.5 series) and jQuery projects: environment, directory structure, naming conventions, logging and error handling, prohibition on core hacks, and server constraints. Refer to it to check shared policies and constraints for version 5 projects, such as “develop with baserCMS 5,” “check the structure and conventions of a version 5 project,” “placement under htdocs/plugins,” “logging with CakeLog,” and “no core hacks in htdocs/vendor/baserproject or cakephp.” For implementation patterns for plugin development and modification (Table/Entity, controllers, admin forms, events, Vue/JS, etc.), basercms5-plugin-development is authoritative; for theme development and modification (layout/element, widgets, mail form templates, assets), basercms5-theme-development is authoritative. For baserCMS 4 development, see basercms4-development; for upgrading from 4 to 5, see basercms4-to-5-upgrade
Apply comprehensive bash scripting standards including main function pattern, usage documentation, argument parsing, dependency checking, and error handling. Triggers when creating/editing .sh files, bash scripts, or discussing shell scripting, deployment scripts, automation tasks, or bash conventions.
Supplies the project-specific conventions, architecture, and contribution guidelines for the better-chatbot open-source AI chat platform (github.com/cgoinglove/better-chatbot; Next.js 15, Vercel AI SDK 5, Better Auth, Drizzle ORM, PostgreSQL). Covers the API architecture, the three-tier tool system (MCP, Workflow, Default), server action validators and the safe() wrapper, database repository patterns, compound component design, DAG workflow builder internals, Playwright E2E test setup, and principles such as progressive enhancement, defensive programming, and streaming-first, plus templates for adding tools, API routes, and repositories. Use when working in the better-chatbot repository, contributing features or fixes, adding API routes or database queries, implementing tools and workflows, building UI components, or integrating multiple AI providers.
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.
Creates and amends product specification markdown — PRD, FRD, TRD, user story, and UI specs (flow, screen structure, view states) — with consistent layout and frontmatter. Use only when the user names this skill (`/building-product-specifications`, `$building-product-specifications`, or "building-product-specifications"), or references a spec file under a marked docs root (`@docs/prd.md`, `@docs/features/checkout/frd.md`) — no code implementation
Builds robust Python MCP (Model Context Protocol) servers with FastMCP—covering tool design, error contracts, event-loop-safe blocking work, subprocess/CLI wrapping, single-file vs. packaged distribution, global-state-free testing, and prompt-injection awareness. Use when writing an MCP server, exposing a tool or CLI to an LLM client, debugging tool registration or packaging, or testing MCP tools.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Chinese commit and changelog configuration reference—Chinese adaptations of Conventional Commits, Chinese templates for commitlint/husky/commitizen, and Chinese conventional-changelog configuration. Invoke only when the user explicitly uses /chinese-commit-conventions; do not trigger automatically based on context.
Browser automation and testing using chrome-devtools MCP server. Use when automating web browsers, taking screenshots, inspecting console logs, monitoring network requests, testing responsive layouts, collecting performance metrics, or debugging web applications. Critical for visual testing workflows and browser-based automation tasks.
Google quantum computing framework. Use when targeting Google Quantum AI hardware, designing noise-aware circuits, or running quantum characterization experiments. Best for Google hardware, noise modeling, and low-level circuit design. For IBM hardware use qiskit; for quantum ML with autodiff use pennylane; for physics simulations use qutip.
Update, upgrade, or migrate an existing CKEditor 5 integration to the latest or a specific version. Use it to bump the editor version, apply the breaking changes between two versions, move off a legacy installation method (predefined builds, webpack source imports, DLL builds, the old CDN), or fix errors that an update or mismatched CKEditor package versions caused. Do not use it to add CKEditor 5 to a new project, to write custom plugins, for downgrades, or for CKEditor 4.
Language-agnostic skill for authoring and reviewing code with low cognitive complexity, readability, and long-term maintainability. Covers guard clauses, single-responsibility functions, type-driven design (illegal states unrepresentable, branded primitives, discriminated unions), schema-first validation, single source of truth for union metadata, functional core + imperative shell, idempotency, and neighbour-pattern symmetry. Pairs with `tdd` for new code (rules apply in GREEN/REFACTOR). Stack-specific extensions live under `rules/stacks/<stack>/` (React, Next.js today; drop a subdirectory for any other language or framework). Use during PR review, after writing new code, in TDD GREEN/REFACTOR, or when asked to "improve quality", "make this readable", "reduce complexity", "deduplicate", "clean this up", or "/code-quality".
Analyzes Rails code quality, architecture, and patterns without modifying code. Use when the user wants a code review, quality analysis, architecture audit, or when user mentions review, audit, code quality, anti-patterns, or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist agents), writing new tests (use rspec-agent), or generating new features.
Explore codebases efficiently with code2prompt, using sem-backed entity maps and grouped source reads to reduce agent round trips. Use when understanding an unfamiliar repository, locating implementations, gathering context for changes or reviews, or installing code2prompt
Technical architecture guide for building a multi-purpose consent preference center. Covers per-purpose granularity, easy withdrawal under Article 7(3), version history, audit trails, and IAB Transparency and Consent Framework v2.2 integration. Includes database schema, API design, and UI component specifications.
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.