Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compact the current conversation into a handoff document for another agent to pick up.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' to run the full shape-then-build flow, or 'teach' for design context setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to resolve an in-progress git merge/rebase conflict.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Teach the user a new skill or concept, within this workspace.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stop. That last message did not land — re-pitch it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize BMad project configuration and load config variables. Use when any skill needs module-specific configuration values, or when setting up a new BMad project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scrum master for sprint planning and story preparation. Use when the user asks to talk to Bob or requests the scrum master.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.