Loading...
Loading...
Found 23 Skills
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.
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".
YC office hours skill. Used by founders for product diagnostic with six forcing questions, premise challenges, alternatives, and a design doc. Use when the user wants founder coaching, startup strategy feedback, or a mock office-hours conversation.
Extract a complete design system from an existing website or screenshot into a DESIGN.md file. Analyses colours, typography, component styles, spacing, and atmosphere through browser automation and HTML inspection. Produces a semantic design system document optimised for consistent page generation. Triggers: 'extract design system', 'design system', 'create DESIGN.md', 'analyse the design', 'what design does this site use', 'extract styles from', 'reverse engineer the design'.
Manage structured change proposals for design documents with PR-like review experience. Use /intent-changes start <file> to begin, /intent-changes propose to suggest changes, /intent-changes accept/reject to decide, /intent-changes finalize to apply.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
Use when a project needs requirements or design clarification before creative work like features, components, or behavior changes.
Use when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to create implementation-ready design documents
This skill should be used when users need to generate detailed, structured prompts for creating UI/UX prototypes. Trigger when users request help with "create a prototype prompt", "design a mobile app", "generate UI specifications", or need comprehensive design documentation for web/mobile applications. Works with multiple design systems including WeChat Work, iOS Native, Material Design, and Ant Design Mobile.
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.
Convert a /spec:brainstorm session into a structured design document saved under docs/designs.