Loading...
Loading...
Found 3,104 Skills
1. Requirement Gathering
Patterns for writing clear, consistent API field descriptions including types, constraints, examples, and edge cases.
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Pasa el paso 3 de borrador a automático, después de mostrarte los números que dicen si conviene.
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.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Read an academic paper together in three passes of increasing depth — a bird's-eye profile, an interactive close reading, and a line-by-line derivation or reproduction — using this directory as a reading workspace that remembers you and your papers across sessions. Give it PDF paths or a title, arXiv ID, or DOI.