Loading...
Loading...
Found 693 Skills
Transform raw brain dumps (dictated freestyle) into structured implementation artifacts. Use when user has messy ideas, scattered thoughts, or dictated stream-of-consciousness about something they want to build. Produces contracts and implementation specs written to ./docs/ideation/{project-name}/.
Creates Source-of-Truth docs (Project Brief, Decisions, Glossary) for new app ideas. Use at the very start of a project to lock scope, stack, and terminology. Essential for preventing drift in downstream PRD, UI/UX, and Architecture phases.
Use when an agent needs to write user stories for a project
Research, discuss, and write specs. Use this when creating or refining specs.
Use when you need to generate "page list → function points → business processes → business rules" with evidence from frontend code, and the project has non-unique routing entries, complex dynamic routes/permissions/backend menus, and the team is prone to making assumptions or missing evidence chains.
Use BEFORE brainstorming — when the user wants to capture WHAT a feature should do as Gherkin scenarios. Trigger when the user says "I need to build X", "let's spec this out", "what should this feature do?", or wants to formally capture a new edge case or bug as a BDD scenario.
Эксперт по OpenAPI документации. Используй для создания Swagger спецификаций, API schemas и автогенерации документации.
Prototype Design Skill
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
Analyzes raw requirements into visual specs and generates artifacts. Invoke when user runs /vspec:new for analysis or /vspec:verify for models and prototypes.
Loads the full ***plain language reference into context: syntax, section types (definitions, implementation reqs, test reqs, functional specs, acceptance tests), concept notation, frontmatter (import/requires/required_concepts/exported_concepts), templates, linked resources, module model, and authoring best practices. Use whenever authoring, editing, reviewing, or debugging .plain files, or before invoking any other skill that reads or writes .plain content.