Loading...
Loading...
Found 2,094 Skills
Trim a spec, ADR set, or design doc down to what a builder needs, without losing a fact. TRIGGER when: user says a spec is 'too long' or 'bloated'; user asks what to remove from it, or wants it cut to 'just what we need to build'.
Writes a clear design for a proposed feature or system change. Use when important product or technical choices must be settled before coding. Covers behavior, interfaces, failures, risks, acceptance criteria, and tests. Use architecture when the repository needs current ARCHITECTURE.md.
Read at the start of every session, before any other skill, and again after any compaction, model change, resume, or handoff. Routes the work to the right skill in this collection and holds one person's decisions rather than a recommendation: where generated files go, which skill wins when two match, which borrowed collections are trusted, where the ceremony is not wanted, and what the portable skills deliberately leave open. Machine-specific on purpose. Not a summary of the other skills, and not a substitute for reading the one that matched.
Patterns for writing clear, consistent API field descriptions including types, constraints, examples, and edge cases.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
One-time setup that maps direct competitors, alternatives, and category substitutes for the current project from the codebase, user input, and external research, then writes a root COMPETITORS.md. Use when the user invokes $setup-competitors-md, says "setup competitors", "create COMPETITORS.md", "competitive landscape", or asks to document rivals and differentiation for the project.