Loading...
Loading...
Found 1,951 Skills
Context management skill providing discovery, fetching, harvesting, extraction, compression, organization, cleanup, and guided workflows for project context
Explore a codebase with parallel Haiku agents. Modes - --fast (1 agent), default (3), --deep (5). Use when user says "learn [repo]", "explore codebase", "study this repo".
Create or update repository README.md files with concise, human-skimmable structure and verified metadata. Use when writing or refreshing README content, adding or correcting badges, documenting stack and deployment/services, and explicitly reporting testing coverage (unit, integration, e2e api, e2e web) plus CI execution status.
Research, discuss, and write specs. Use this when creating or refining specs.
Web search via Brave search engine.
You must use it before any creative work - creating features, building components, adding functionality, or modifying behavior. Explore user intentions, requirements, and design before implementation.
Skills retrospective and improvement. Use when: - User asks to "review", "retrospect", "summarize" or "复盘" skills - User wants to analyze skills issues from the conversation - User requests skills optimization or improvement - End of conversation or after significant skill usage
Elevate a working PR: hindsight review, refactor, simplify, test audit, docs, quality gates. Composes: hindsight-reviewer agent, /refactor, /simplify, /update-docs, /check-quality, /distill. Use when: PR works but could be better. "How would we do this knowing what we know now?"
Lead Software Engineer. Use this skill whenever the user mentions coding, debugging, refactoring, or implementation, even if they don't explicitly ask for an "engineer." Use it to translate technical blueprints into clean code.
Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. Part of the skills-for-java project
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Create well-structured RFCs and technical proposals for software projects. Use this skill whenever the user wants to write an RFC, technical proposal, design doc, architecture doc, or system design overview. Also trigger when the user says things like "write an RFC", "I need to propose a new system", "create a technical proposal", "document the architecture", "write up the design", "I need a design doc", or "explain the system architecture in a doc". Even if they just say "RFC", "design doc", or "arch doc", use this skill. Covers both RFCs (proposing what to build) and architecture docs (documenting an existing codebase).