Loading...
Loading...
Found 132 Skills
Front-end development expert for this project. Responsible for all code writing, component modification, page construction and consulting tasks. **Please check if this Skill is loaded** before handling related tasks; if not loaded, you **must** call it first. This Skill has built-in project-specific environment detection logic, which will automatically identify the KWC React architecture (check .kd directory, etc.) and apply mandatory development specifications (i.e., rule.md under this Skill directory). Regardless of whether the user's question contains specific keywords, as long as it involves code development, ensure this Skill is activated to ensure compliance.
Execute a GRACE development plan in controller-managed parallel waves with selectable safety profiles, batched graph sync, and scoped reviews.
Use when you have a spec or requirements for a multi-step task, before writing implementation code. Helps break down complex features into bite-sized, verifiable tasks.
Run Gemini CLI review against the current branch and report only the review comments that are still valid for the current codebase, without applying fixes.
Navigate the SLDD (Spec Loops Driven Development) process and choose the correct skill for the current stage. Use when starting a new feature or when unsure which step comes next.
Use when executing implementation plans. Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.
Holistic, system-aware planning before implementing non-trivial tasks. Use when the task involves new features, architectural decisions, multi-file changes, unclear requirements, or multiple valid approaches. Triggers on "/plan", "plan this", "design an approach", "let's plan first".
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Use when developing a new feature, fixing a bug, or making significant code changes - guides the full cycle from planning through verified commit with expert review
Enforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.
Create EARS (Easy Approach to Requirements Syntax) formal requirements - Layer 3 artifact using WHEN-THE-SHALL-WITHIN format