Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Aptos blockchain and Move language expert. Covers Move programming (abilities, generics, resources), Aptos framework modules, smart contract development, token standards (Coin, Fungible Asset, Digital Asset), object model, gas optimization, and dApp integration. Triggers on Aptos, Move language, Move smart contract, Aptos blockchain, abilities, generics, resources, fungible asset, digital asset.
Validates cross-section ID consistency in arc42 documentation that follows this toolkit's conventions. Checks toolkit IF-xx interface IDs (Section 3↔Section 5), building block deployment coverage (Section 5↔Section 7), Q42 quality tag traceability (Section 1↔Section 10), toolkit ADR risk references (Section 9↔Section 11), and aspirational scenario linkage (Section 10↔Section 11). Runs the automated linter script when available, or applies rules manually when not.
Interactively guides the documentation of arc42 Section 4 (Solution Strategy). Asks about technology choices, decomposition approach, and how quality goals are achieved before generating a concise strategy summary. Iterates until the user is satisfied.
Interactively guides the documentation of arc42 Section 8 (Crosscutting Concepts). Asks about domain model, security, persistence, error handling, and observability before generating only the concepts that are architecturally significant. Iterates until the user is satisfied.
Use when recording an architectural decision so future maintainers know why—phrases like "ADR", "architecture decision record", "why did we pick X", "lightweight architecture documentation", "decision log", "should this be an ADR", "tribal knowledge", "we chose this two years ago and now nobody remembers why". Defines an ADR as a short, structured document capturing what was decided, why, alternatives considered, and consequences—written at the time of the decision and kept in the repo
Use when protecting a service from a degraded or failing dependency—phrases like "circuit breaker", "bulkhead", "retry policy", "exponential backoff", "fail fast", "fallback", "cascade failure", "open/closed/half-open state", "resilience4j", "Polly", "Hystrix". Defines the circuit breaker pattern and related failure-isolation tools (bulkhead, retry-with-backoff, timeout, fallback)
Use when separating read and write models — phrases like "CQRS", "Command Query Responsibility Segregation", "read model vs write model", "denormalized read side", "materialized view", "different scaling for reads and writes", "command bus", "query bus", "should we use CQRS here". Defines CQRS as keeping reads and writes on separate models, with picking criteria that resist over-application.
Use when designing a system around asynchronous events—phrases like "event-driven architecture", "EDA", "event broker", "Kafka", "publish-subscribe at scale", "event-first design", "choreography vs orchestration", "event broker vs message queue", "broker topology vs mediator topology". Defines event-driven as a macro architectural style where components emit and react to events, not direct calls
Use when persisting state as a sequence of events—phrases like "event sourcing", "event store", "append-only log of facts", "replay events to rebuild state", "audit log as source of truth", "temporal queries", "snapshot", "should we event-source this aggregate". Defines event sourcing as storing the history of what happened as the canonical state, with current state derived by replay
Use when enforcing architectural characteristics through automation — phrases like "architecture fitness function", "evolutionary architecture", "architecture tests", "ArchUnit", "dependency rules in CI", "automated architecture checks", "guardrails", "drift detection". Defines fitness functions as automated checks that verify architectural characteristics on every change, catching drift before it accumulates.
Use when picking a software architecture style or pattern for a system — phrases like "what architecture should we use", "monolith vs microservices", "should we go event-driven", "is this a CQRS situation", "do we need a saga here", "should we use hexagonal architecture", "what's the right architectural style for this problem". Diagnostic mode that routes a stated problem to the relevant architecture skill or rules patterns out.
Use when discussing layered architecture (n-tier) — phrases like "layered architecture", "n-tier", "presentation / business / persistence layers", "should we go layered", "leaky layer", "sinkhole anti-pattern", "open vs closed layers". Defines the layered style with its strict top-down dependency rule, the open/closed layer concept, and the most common failure modes.
Use when designing or reviewing a microservices architecture — phrases like "microservices", "should we split this service", "service boundaries", "bounded context per service", "API gateway", "backend for frontend", "BFF", "service mesh", "microservices vs monolith", "database per service", "data ownership". Defines microservices as independently deployable services aligned with business capabilities — and the discipline of resisting the style until the monolith proves inadequate.
Use when migrating a legacy system incrementally — phrases like "strangler fig", "strangler pattern", "incremental migration", "monolith to microservices", "rewrite without big bang", "replace legacy in place", "facade in front of the legacy system", "anticorruption layer". Defines Fowler's Strangler Fig as the migration discipline of gradually replacing legacy functionality behind a stable facade, never doing a big-bang rewrite.
Establish the architecture for Next.js 15+ applications using the Scope Rule and Screaming Architecture. Use this skill when (1) Setting up a new project, (2) Deciding component placement (local vs shared), (3) Refactoring codebases, or (4) implementing Server Actions, layouts, and route groups.
Execute architectural refactoring from an assessment document with deterministic, chunked operations and aggressive verification at every step. Use when you have an architectural assessment, clean architecture review, refactoring recommendations, or seam-ripper output and need to actually perform the refactoring safely. Also use when asked to "refactor based on this assessment", "execute these architectural recommendations", "fix architectural drift", "refactor in chunks", or any request to systematically restructure a codebase according to a plan. Designed specifically to prevent the kind of agent drift that causes architectural problems in the first place.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.
Ask what would be lost from the plan if this session ended now — decisions about the system made in conversation and never written down — drive each to a home or an approved forget, then answer honestly whether anything would have to be decided again.
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.
This skill should be used when the user asks to "find a class", "search for symbol", "find usages", "find implementations", "search codebase", "find file", "class hierarchy", "find callers", "module dependencies", "unused dependencies", "project map", "project conventions", "project structure", "what frameworks", "what architecture", "find Perl subs", "Perl exports", "find Python class", "Go struct", "Go interface", "find React component", "find TypeScript interface", "find Rust struct", "find Ruby class", "find C# controller", "find Dart class", "find Flutter widget", "find mixin", "find Scala trait", "find case class", "find object", "find PHP class", "find Laravel model", "find PHP trait", or needs fast code search in Android/Kotlin/Java, iOS/Swift/ObjC, Dart/Flutter, TypeScript/JavaScript, Rust, Ruby, C#, Scala, PHP, Perl, Python, Go, C++, or Protocol Buffers projects. Also triggered by mentions of "ast-index" CLI tool.
Astro content-focused web framework. Covers islands architecture, content collections, and multi-framework support. Use when building content-heavy or static websites. USE WHEN: user mentions "Astro", asks about "islands architecture", "content collections", "Astro components", "client directives", "Astro.glob", "static site generation with Astro", "multi-framework in Astro" DO NOT USE FOR: Next.js - use `nextjs-app-router` instead; Nuxt - use `nuxt3` instead; SvelteKit - use `sveltekit` instead; Gatsby - use Astro as modern alternative; pure React/Vue/Svelte - use respective framework skills
Structure asyncio code: task management, cancellation, rate limiting, blocking calls kept off the event loop. TRIGGER WHEN: building async APIs, concurrent or I/O-bound systems needing non-blocking operations, or choosing between asyncio, threading and multiprocessing.
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.
Map Delphi classes to a relational database using TMS Aurelius ORM attributes. Use when the user asks to create entity classes, add Aurelius mapping to existing classes, fix or review mapping attributes, explain how a class is mapped, or work with associations, inheritance, automapping, nullable fields, blobs, or composite identifiers. Triggers on requests like "create Aurelius entities for...", "map this class to Aurelius", "add ORM mapping", "fix the mapping on this class", "how do I map a one-to-many in Aurelius".
Save, load, update, delete, merge, and navigate entity objects using TMS Aurelius ORM (TObjectManager). Use when the user asks how to persist or retrieve data with Aurelius, manage object lifetime, work with associations or collections at runtime, handle transactions, use cached updates, or control concurrency. Does NOT cover query DSL or criteria/projections (those are in a separate skill). Triggers on requests like "save an entity with Aurelius", "load a customer from the database", "add items to a collection", "how do I update an object", "flush changes", "delete a record with Aurelius", "merge a transient object", "how do transactions work in Aurelius", "batch updates Aurelius".
Author or upgrade Model Advisor checks for Simulink and System Composer models. Covers the full lifecycle: guideline authoring, check specification, Model Advisor check implementation, and qualification testing. Use when creating new checks (edit-time, standard batch, config-parameter, auto-fix), converting legacy StyleOne/StyleTwo/StyleThree checks to modern DetailStyle, creating a guideline for modeling, enforcing a modeling rule, or testing/qualifying a check. Triggers on any modeling constraint (e.g., "blocks shall...", "signals must match...", "parameters shall be set to...").
Background job processing patterns including job queues, scheduled jobs, worker pools, and retry strategies. Use when implementing async processing, job queues, workers, task queues, async tasks, delayed jobs, recurring jobs, scheduled tasks, ETL pipelines, data processing, ML training jobs, Celery, Bull, Sidekiq, Resque, cron jobs, retry logic, dead letter queues, DLQ, at-least-once delivery, exactly-once delivery, job monitoring, or worker management.
Research-grounded, read-only audit that validates a repository's codebase, architecture, and business logic against real-world knowledge from authoritative sources (arxiv, PubMed, Google Scholar, JSTOR, OpenAlex, Crossref, Semantic Scholar) plus standards bodies (NIST, IETF/RFC, OWASP, ISO, sector regulators). Use when you want an audit that flags algorithms, architectural choices, or business rules violating established norms, standards, or best practices — e.g. 'is our APR calculation correct per lending norms?', 'does our crypto follow NIST?', 'is this consensus approach sound?' — each finding tied to a real, fetched citation. Extracts falsifiable claims across algo/arch/biz layers, routes each to the right source class, verifies against fetched evidence, and adversarially refutes before reporting; emits a severity-graded cited report with UNCONFIRMED for anything ungrounded. Not a linter, SAST, or CVE scanner — it reasons about norms, not syntax.
A workflow and scripts for end-to-end handling of baserCMS repository security advisories (including GHSA and triage): list advisories, verify findings, fix issues individually, create private forks/branches/PRs, and verify locally. Use for requests such as “check security advisories,” “verify triaged vulnerabilities,” “create a fork and PR for each advisory,” or “bundle vulnerability fixes into pull requests.” Covers relying on local verification (/code-review・basercms-unittest) because Copilot/GHA cannot be used on advisory forks, retries while waiting for pushed changes to appear, splitting hunks in shared files, and common conflict resolution when syncing with base.
Java Layered Architecture Design Pattern — A complete implementation guide for the classic five-layer architecture using Spring Boot + MyBatis-Plus. Suitable for bootstrapping new Java projects, refactoring existing architectures, establishing team development standards, and database migration scenarios.
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or Auto render modes; designing component hierarchies and state. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
In-depth technical blog writing. Not a content generator, but a tool for expressing opinions. Forces forming a judgment → Chinese and English versions → mermaid/architecture diagrams first → SEO + FAQ + distribution. Trigger words: 写博客, 写文章, blog, 介绍新工具, 参考这个链接写, 整理资料成文. Use this skill when the user needs to: (1) write a technical blog (2) organize materials/write an in-depth piece referencing a URL (3) introduce a new tool/technology (4) produce a technical article with architecture/flow diagrams
This skill should be used when the user asks about Bootstrap 5 getting started, Bootstrap installation, Bootstrap CDN setup, Bootstrap npm installation, Bootstrap Bun installation, Bootstrap project setup, Bootstrap starter template, Bootstrap browser support, Bootstrap version compatibility, Bootstrap RTL support, Bootstrap Vite setup, Bootstrap Parcel setup, Bootstrap Webpack setup, Bootstrap Rails setup, Bootstrap Rails 8 integration, Bootstrap importmaps Rails, Bootstrap cssbundling-rails, Bootstrap Propshaft setup, Bootstrap dartsass-rails, Bootstrap Turbo integration, Bootstrap Stimulus controllers, Bootstrap Hotwire, Rails form helpers Bootstrap, Bootstrap Icons Rails, bootstrap gem Ruby, Bootstrap accessibility, Bootstrap WCAG compliance, Bootstrap screen reader support, Bootstrap visually-hidden class, Bootstrap reduced motion, Bootstrap RFS, Bootstrap responsive font sizes, Bootstrap fluid typography, Bootstrap download, Bootstrap file structure, Bootstrap contents, Bootstrap CSS variables, Bootstrap ES modules, Bootstrap best practices, or needs help setting up a new Bootstrap project.
Use this skill when implementing BoxLang filesystem watchers: watcherNew/watcherStart/watcherStop lifecycle BIFs, WatcherInstance APIs, event payload handling, recursive directory monitoring, debounce/throttle/atomicWrites tuning, errorThreshold auto-stop behavior, and listener patterns (closure, struct, class, class name string).
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Celery async task dispatch and management skill with cross-platform deployment support (Windows/Linux/macOS). Provides automatic configuration of an isolated skill environment, command execution tasks, delayed scheduling, and task monitoring. Use cases: (1) executing commands or scripts asynchronously, (2) delayed or scheduled task execution, (3) task queue management and monitoring, (4) distributed task processing. Built-in cross-platform compatibility handling automatically detects the system type and adapts the configuration. **Three required services**: Redis/Memurai, Celery Worker, and Flower monitoring are all required, and any that is not running should be started automatically. **AI assistant auto-starts services**: before dispatching a task, it automatically checks for and starts any service that is not running, with no manual user intervention. Requires Redis/Memurai (Windows) to be installed first.
Extracts HTTP/HTTPS request and response data from Charles Proxy session files (.chlsj format), including URLs, methods, status codes, headers, request bodies, and response bodies. Use when analyzing captured network traffic from Charles Proxy debug sessions, inspecting API calls, debugging HTTP requests, or examining proxy logs.
Configuration reference for domestic Git platforms—SSH/HTTPS/credentials/CI integration differences and mirror synchronization for Gitee, Coding.net, 极狐 GitLab, and CNB. Invoke only when the user explicitly says /chinese-git-workflow; do not trigger automatically based on context.
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.