Loading...
Loading...
Found 58 Skills
Check whether a design is complete enough to move into implementation planning. Use when a design appears mostly done and needs a final readiness review for missing branches, weak assumptions, unresolved risks, failure handling, validation gaps, or non-functional omissions. Trigger before invoking writing-plans or when the user asks whether the current design is ready to implement. Do not use as a general design-document audit for external docs or as a replacement for initial design work.
Create maintainable Mermaid diagrams for software documentation, including flowcharts, sequence, class, ER, C4, state, git, gantt, and chart diagrams. Trigger when structure, relationships, sequencing, or architecture would be clearer visually, especially for persistent README, wiki, PR, or design-document diagrams. Verify the target renderer and Mermaid version before using version-sensitive syntax.
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
Use when starting any feature, project, or design work. Guides collaborative design refinement through incremental questioning before any code is written.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and task lists. Triggers: "kiro", ".kiro/specs/", "feature spec", "需求文档", "设计文档", "实现计划".
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.
Use when writing a proposal, RFC, design document, spec, or migration plan - anything that argues for a change, records a design, or asks readers for input on one. Encodes the proposal skeleton, the Why & What decision box, and the completeness checks. Use whenever a change needs arguing or scoping in writing, even if the user just says "write up the approach".
Phase 1 of the feature workflow — Draft a design document for the new feature, which serves 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-layer 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.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
Create complete web pages with production-grade frontend design AND auto-generated images. Use this skill when the user asks to build websites, landing pages, dashboards, or any web interfaces that need images. This skill combines frontend design expertise with automatic AI image generation to create fully functional, visually stunning web pages with all images included. Generates creative, polished HTML/CSS/JS code with AI-generated images that match the aesthetic direction.