スキルを探す

[Utilities] Use when you need to review recent changes and wrap up the work.

日本語の概要は準備中です。原文の説明を表示しています。

[Git] Use when creating release notes from git history.

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.

日本語の概要は準備中です。原文の説明を表示しています。

[Dev Data] Use when you need to implement or enhance test data seeders that simulate QC happy-path scenarios via application-layer commands. Flag: --mode=review reviews a target seeder (or the current changes / current work-context result) against every universal seed-data rule AND the project-specific seeder conventions — read-only, evidence-backed PASS/FAIL.

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when you need to run quality gate checklist.

日本語の概要は準備中です。原文の説明を表示しています。

[AI & Tools] Use when you need to apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification.

日本語の概要は準備中です。原文の説明を表示しています。

[Planning] Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.

日本語の概要は準備中です。原文の説明を表示しています。

[Project Management] Use when converting ideas to PBIs, validating problem hypotheses, adding acceptance criteria, or refining requirements.

日本語の概要は準備中です。原文の説明を表示しています。

[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs written before code.

日本語の概要は準備中です。原文の説明を表示しています。

[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.

日本語の概要は準備中です。原文の説明を表示しています。

[Testing] Use when you need individual page/component testing with Python Playwright scripts.

日本語の概要は準備中です。原文の説明を表示しています。

[Process] Use when the developer wants something explained or taught, or wants to know HOW TO REVIEW a change — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS delivers a teacher-and-coach review guide, high level first then detail: what was done, a VISUAL MAP (system flowchart, domain ERD, sequence diagrams), the user stories and business rules with their REAL test-case IDs, a REVIEW PATH naming which files to open first and in what order with an exit criterion per stage, the technical concepts needed to follow it, how it works, why THIS solution, every alternative option with pros/cons, the trade-offs accepted, the blast radius, HOW TO TEST AND DEMO the change, the developer's decision levers, and written challenge prompts that provoke the reader to pressure-test the work. Works at ANY scope — from one line of code to the whole project: it SIZES the target into a scope tier, DECOMPOSES a large one into understanding groups, BREAKS the work into tasks before the first deep read, and ACCUMULATES the report group by group on disk so a huge explanation stays complete instead of thinning out. Writes the full report to a single combined markdown file (plans/reports/understand-*.md) that opens with a detailed summary section — or delivers it in full in chat when Step 3 finds no git-ignored directory for it — and always summarizes it in chat. Regardless of coding level. Never interrogates, never quizzes, never blocks.

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when you need to combine /why-review + /fix in a recursive loop — each round runs /why-review to find validated findings then /fix to resolve them, then loops again over the CHANGED target until a fresh full /why-review produces zero findings (nothing left to fix).

日本語の概要は準備中です。原文の説明を表示しています。

[General] Use when building 3D web apps with ThreeJS and related WebGL or WebGPU examples.

日本語の概要は準備中です。原文の説明を表示しています。

[Process] Use when you need to end the active workflow and clear state.

日本語の概要は準備中です。原文の説明を表示しています。

[Testing] Use when you need to run tests locally and analyze the summary report.

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when reviewing UI/frontend changes for long-content overflow, responsive multi-screen layout (flex-wrap / row-to-column on small devices), flex-vs-fixed sizing, z-index discipline, SCSS/BEM styling quality, and async UI states & feedback (loading indicator, error surface, empty state).

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

[Utilities] Use when you need to restore workflow context from checkpoint after session loss.

日本語の概要は準備中です。原文の説明を表示しています。

[Documentation] Use when (re)generating the DERIVED technical spec view over code + tests, or reporting canonical §8 TC/test-code drift. A GENERATOR — it projects code + tests into a regenerable per-component view and NEVER authors business content. Modes generate|audit|sync. Per-mode procedure lives in references/{author,sync}.md.

日本語の概要は準備中です。原文の説明を表示しています。

[Skill Management] Use when shared protocol checklists change and need propagation across skills.

日本語の概要は準備中です。原文の説明を表示しています。

[Content] Use when you need to build marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.

日本語の概要は準備中です。原文の説明を表示しています。

[Architecture] Use when you need to research, analyze, and compare tech stack options as a solution architect.

日本語の概要は準備中です。原文の説明を表示しています。