Loading...
Loading...
Found 3,123 Skills
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.
Produce a "production-ready, replica-grade" UI/UX R&D specification document package (directory isomorphic skeleton, common foundation, component/page contracts, coverage mapping, index and worklog) from the product PRD. Suitable for scenarios where PRDs need to be converted into front-end replicable specification documents, UI/UX R&D specifications, interface contracts and acceptance criteria; not recommended for requests that only require visual inspiration/pure UI appreciation or direct code implementation.
Run a complete repository-native, spec-anchored development loop inspired by DeepSeek Harness. Use for feature development, bug fixes, simplification, architecture, process, or testing work that changes behavior, contracts, structure, test strategy, durable formats, or decision rationale; when asked to write, review, continue, implement, reject, supersede, archive, or verify a spec/Agent Note/RFC/ADR; or when code, tests, current-state docs, and decision rationale must converge in one change. Also use for read-only spec-to-code drift checks. Do not create a spec for a purely mechanical local edit that changes none of those things.
Lists decisions done during the session.
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.