6,477 件 ・ 関連度順
概要と使いどころ
[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Idea to PBI workflow for turning an idea — or a raw product vision/problem — into prioritized PBIs and stories (single-PBI deep mode, or multi-opportunity discovery mode).
日本語の概要は準備中です。原文の説明を表示しています。
[Category] Use when defining the standard skill description pattern.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Review Current Changes workflow for review, fix, and re-review recursively until all issues resolved.
日本語の概要は準備中です。原文の説明を表示しています。
[Git] Use when you need to create isolated git worktree for parallel development.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Seed Test Data workflow for idempotent QC happy-path seeders.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when you need to run /workflow-review-changes repeatedly in an outer convergence loop until a complete whole-workflow run applies zero fixes — recursive re-review of a fixed scope (branch-diff + current changes) until a clean no-op pass.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Integration Test Green workflow — drive an integration-test suite to fully green with a bounded convergence loop: verify the whole system (or the named target), adjudicate every failure with /debug-investigate + /integration-test-review before any edit, fix at the owning layer, /changes-review each round's fix diff, re-verify from scratch, then sync spec TCs, the integration-test reference doc, and feature docs.
日本語の概要は準備中です。原文の説明を表示しています。
[Frontend] Use when designing beautiful or aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.
日本語の概要は準備中です。原文の説明を表示しています。
[Utilities] Use when you need to restore workflow context from checkpoint after session loss.
日本語の概要は準備中です。原文の説明を表示しています。
[Investigation] Use when about to author a new Feature Spec from an idea — investigate all existing Feature Specs AND related code logic first to surface related/overlapping/affected specs, missing features, missing test cases/user stories, system unknowns, and the invariant landscape, before any spec is drafted.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use to validate a spec artifact's decisions with the user across three contexts — a freshly-authored Feature Spec (idea-to-spec), an existing canonical spec before PBI decomposition (spec-to-pbi), or a refined idea + §8 test-specs (idea-to-pbi deep mode). Detects the context, walks every applicable validation category, and runs an exhaustive but budget-bounded blocking clarification gate so every non-obvious or conflicting decision is confirmed before the artifact drives downstream work.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Big Feature workflow for large or ambiguous research-driven feature work.
日本語の概要は準備中です。原文の説明を表示しています。
[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).
日本語の概要は準備中です。原文の説明を表示しています。
[Architecture] Use when scaffolding reusable OOP/SOLID project foundations before feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.
日本語の概要は準備中です。原文の説明を表示しています。
[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.
日本語の概要は準備中です。原文の説明を表示しています。
[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.
日本語の概要は準備中です。原文の説明を表示しています。
[Skill Management] Use when shared protocol checklists change and need propagation across skills.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Bug Fix workflow for systematic debugging with root cause investigation, fix, and verification.
日本語の概要は準備中です。原文の説明を表示しています。
[Utilities] Use when you need to review recent changes and wrap up the work.
日本語の概要は準備中です。原文の説明を表示しています。
[General] Use when building 3D web apps with ThreeJS and related WebGL or WebGPU examples.
日本語の概要は準備中です。原文の説明を表示しています。