Total 37,942 skills
Showing 12 of 37942 skills
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.
Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"
UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report
Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder
Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
Use this skill when the user wants to purchase a virtual debit card using crypto, create a prepaid card via x402 protocol, check virtual card status, or set up an EVM wallet for card payments. Trigger on: "buy a card", "get a virtual card", "create card", "card status", "setup wallet for card", or any intent involving purchasing virtual Visa/Mastercard with cryptocurrency.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.