Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or to...
Guide for creating effective subagents (custom agents). Use when users want to create a new subagent that can be dispatched via Task tool for autonomous work. Covers frontmatter fields (name, description, tools...
Generate database schema from feature descriptions. User doesn't see SQL. Use when: features require data persistence. Triggers: internal use only.
Generate CRUD API endpoints automatically. User doesn't see routes. Use when: features need backend logic. Triggers: internal use only.
Build browser extensions with Manifest V3, content scripts, and service workers. Use when: creating Chrome extension, Firefox addon, browser plugin. Triggers: "extension", "browser extension", "chrome extension...
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion
Use when about to claim work is complete or fixed - requires running verification commands and confirming output before making any success claims
Modern Python backend stack: FastAPI, SQLAlchemy 2.0, Pydantic v2, uv, ruff. Use when: building Python APIs, async services, or working with Python backend code. Triggers: "fastapi", "python backend", "sqlalche...
Write failing test first, then minimal code to pass. Red-Green-Refactor cycle. Use when: implementing features, fixing bugs, refactoring code. Triggers: "implement", "add feature", "fix bug", "tdd", "test first...
Use when encountering any bug, test failure, or unexpected behavior - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before atte...
Infrastructure as Code with Terraform - modules, state management, and best practices.
Query optimization, partitioning, clustering, and warehouse tuning.
Build command-line tools with argument parsing, subcommands, and nice UX. Use when: creating CLI, terminal app, command-line utility. Triggers: "cli", "command line", "terminal", "clap", "typer", "commander".
Infrastructure security, CIS benchmarks, and vulnerability scanning.
Automatically generate and run tests after each code change. Use when: any code is generated or modified in the pipeline. Triggers: internal use only.
Modern Node.js backend stack: NestJS/Hono, Drizzle ORM, Vitest, TypeScript. Use when: building Node.js APIs, TypeScript backends, or serverless functions. Triggers: "nestjs", "node backend", "express", "hono",...
Gather user design preferences before building UI. Use when: starting a project with visual interface (Web App, Mobile, Browser Extension). Triggers: "design preferences", "visual style", "choose theme", "desig...
Essential testing patterns for any project. Use when: writing tests, setting up testing, or fixing test issues. Triggers: "test", "testing", "unit test", "write tests".
Help and documentation for Idea to MVP plugin. Use when: user asks about building MVPs, vibe coding, or available commands. Triggers: "help", "what can you do", "mvp help", "how to build".
Dimensional modeling, normalization, and schema design for analytics.
Observability stack with Prometheus, Grafana, and alerting.
Protect repositories from accidental secret commits. Essential when working with AI agents. Use when: setting up new project, adding pre-commit hooks, scanning for secrets, fixing leaked credentials. Triggers:...
Generate UI components from natural language descriptions. Use when: user asks for a page, component, or UI element. Triggers: "create page", "add component", "show form", "make button", "страница", "компонент"...
Validates beads issues after creation. Checks dependencies, PRD mapping, order. Use when: after creating issues in project-init, before TDD loop. Triggers: "validate beads", "check issues", "verify tasks".
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.