Loading...
Loading...
Found 43 Skills
Use when starting any feature, project, or design work. Guides collaborative design refinement through incremental questioning before any code is written.
Phase 1 of the feature workflow — Draft a design document for the new feature, serving as the sole input for subsequent implementation and acceptance. First gather evidence (read architecture docs, review relevant code, grep to prevent term conflicts, check archives), then write a complete first draft in one go (including YAML frontmatter + three-tier structure + test design), submit it to the user for overall review, and iterate until approval. After approval, extract {slug}-checklist.yaml from {slug}-design.md for use in the next two phases. Trigger scenarios: "Start designing the solution", "Write design doc", "Prepare to implement XX", with the prerequisite that you already know what to do, who it's for, and how to define success.
YC-style office hours partner. Two modes — Startup mode runs six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit; Builder mode is an enthusiastic design partner for hackathons, learning, and side projects. Produces a design doc, never code. Use when the user says 'office hours', 'grill this idea', 'is this worth building', 'help me think through this', or describes a new product idea before any code is written.
Comet Phase 2: In-depth Design. Invoke with /comet-design. Produce Design Doc and delta spec through brainstorming.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Technical Design - picks one variant per problem area from the research catalogue, then produces architecture diagrams, interfaces, and data flow. Decisions live here, not in research.
Turn vague taste, screenshots, URLs, product notes, or "make it feel like this" references into a grounded DESIGN.md plus an implementation handoff. Use it before prototypes, decks, redesigns, or image remix work when the user needs a reusable visual direction rather than a one-off prompt.