Loading...
Loading...
Found 45 Skills
Turn vague ideas into a validated design/spec through structured brainstorming. Use before any creative work (new features, UI/components, behavior changes, refactors) and whenever a user asks to brainstorm, define requirements, propose approaches, or write a design doc.
Use when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to create implementation-ready design documents
Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says "set up my project context," "what platforms am I targeting," "configure HIG settings," or when starting a new Apple platform project. Also activates when other HIG skills need project context but none exists yet. This skill creates .claude/apple-design-context.md so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and hig-technologies can provide targeted advice without repetitive questions.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
Facilitates collaborative design exploration before implementation. Explores user intent, constraints, and requirements through structured dialogue, then produces an approved design document. Must be invoked when entering plan mode or planning any implementation. Triggers: brainstorm, design, plan, "let's think through," "how should we build."
Use when a project needs requirements or design clarification before creative work like features, components, or behavior changes.
Internal skill. Use cc10x-router for all development tasks.
Comet Phase 2: In-depth Design. Invoke with /comet-design. Produce Design Doc and delta spec through brainstorming.
Craft portfolio-ready case studies that tell the story of a design project.
General Technical Design Document Summarization Skill: Scan documents and diagrams in the current execution directory (Markdown, PlantUML/Mermaid, drawio, images, etc.), extract system objectives, module boundaries, core processes, sequences and states, and output structured technical design documents. Use this skill when users mention "technical design documents", "solution sorting", "summarize design based on existing documents", "summarize documents and diagrams in the directory", or "complete sequence diagrams/state diagrams".
Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.
Use when the user wants to bring UI designs into a project for a PRD requirement. Identifies the screens/states a requirement needs, helps the user generate them via Stitch or Claude Design (or import existing exports), and places HTML + screenshot pairs under docs/designs/<FR-N>-<slug>.{html,png} so implementation can reference them. Triggers on "import these designs", "add screens for FR-001", "set up the designs for this requirement", "vibe design this screen", "/designs FR-N".