Loading...
Loading...
Found 8 Skills
New Feature Design Exploration Process. Used when users have vague ideas for new features or modules. Through the structured process of "Requirements Convergence → Technical Research → ASCII Batch Exploration → HTML Design Draft → Full State Coverage → Requirements Summary", deliverable design reference documents are generated from vague ideas, serving as input for the PRD phase.
Generate visual design proposal catalogues for existing projects. Use when: - User wants to explore design directions before implementation - Redesigning or refreshing an existing interface - Starting /aesthetic or /polish without clear direction - User says "explore designs", "show me options", "design directions" Keywords: design catalogue, proposals, visual exploration, aesthetic directions, DNA
Export .pen design to React/Tailwind code. Does ONE thing well. Input: .pen frame ID or file path Output: React component code + Tailwind config Use when: design-exploration or user needs implementation code from a finalized Pencil design.
Render DNA codes to Pencil .pen frames. Does ONE thing well. Input: DNA code + component type (hero, card, form, etc.) Output: .pen frame ID + screenshot Use when: design-exploration or other orchestrators need to render visual proposals using Pencil MCP backend.
Unified brand discovery that outputs brand.yaml. Merges brand-builder (voice/audience) + design-exploration (visual direction) into one flow. Run once per project to establish brand identity.
Collaborative design exploration that refines ideas into validated specs through iterative questioning. Use before any creative work including creating features, building components, adding functionality, or modifying behavior.
Design exploration with parallel agents. Use when brainstorming ideas, exploring solutions, or comparing alternatives.
Socratic discovery and design exploration before planning. Activates when starting non-trivial work — asks clarifying questions, explores alternatives and tradeoffs, produces a design document for approval. Pulls context from Linear issue description, linked docs, and existing CLAUDE.md learnings. Simple bugs and fixes skip this automatically.