Loading...
Loading...
Found 749 Skills
Arc's UI design system. Use when building interfaces inspired by Arc's aesthetic - light mode, Inter font, 4px grid.
Update AGENTS.md and agent_docs/ following best practices. Use when modifying agent guidelines, adding new documentation, or restructuring agent instructions.
Core BDD concepts, philosophy, and the Three Amigos practice
Create outcome spec (overview, decisions, steps, edge cases). Use $ARGUMENTS as spec topic if provided.
Add an implementation requirement to the ***implementation reqs*** section of a ***plain spec file. Use when the user wants to add non-functional requirements like technology choices, architectural constraints, coding standards, data formats, error handling strategies, or any HOW-to-build guidance to a .plain file.
Supabase's UI design system. Use when building interfaces inspired by Supabase's aesthetic - dark mode, Inter font, 4px grid.
Deep interview process to transform vague ideas into detailed specs. Works for technical and non-technical users.
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Focuses on reviewing, maintaining, and generating project documentation (located in the docs/ directory).
Write or update a single-feature PRD (`Type: feat`/`fix`/`chore`) with scope, user stories, and acceptance criteria. Triggers: plan prd, write feature spec, define acceptance criteria, update prd.
Railway's UI design system. Use when building interfaces inspired by Railway's aesthetic - dark mode, Inter font, 4px grid.
Weather/current-conditions verification workflow. Use when user asks for weather, temperature, forecast, rain/snow/wind, typhoon alerts, air quality, or other time-sensitive local conditions. Requires location + source links + local update/publish time; NEVER fabricate.