Grimblaz/agent-orchestra - 2페이지

bdd-scenarios

Structured Given/When/Then scenario authoring with ID traceability and CE Gate coverage gap detection. Use when writing or reviewing BDD scenarios in Agent Orchestra, classifying scenarios as [auto]/[manual], managing scenario ID lifecycle, extracting…

원문 언어: 영어

oversized-skill

test skill

원문 언어: 판별 불가

skill-a

---

원문 언어: 영어

some-skill

a test skill with no table of contents

원문 언어: 영어

documentation-finalization

Documentation finalization workflow for accuracy, cleanup, and design-doc maintenance. Use when updating implementation-facing docs, synchronizing design documents with shipped behavior, or removing obsolete documentation. DO NOT USE FOR: formal specification…

원문 언어: 영어

browser-canvas-testing

VS Code native browser tool behavior for canvas-based games (Phaser 3, etc.). Use when interacting with HTML canvas elements, clicking game objects, verifying canvas state via browser tools, or when `clickElement` fails on canvas. DO NOT USE FOR: React…

원문 언어: 영어

ui-iteration

Reusable screenshot-driven UI polish workflow for iterative visual refinement. Use when improving layout, hierarchy, spacing, feedback, or Tailwind-based presentation through repeated review-and-adjust passes. DO NOT USE FOR: functional bug fixing,…

원문 언어: 영어

process-analysis

Reusable retrospective and process-analysis methodology for workflow reviews. Use when analyzing execution timelines, plan adherence, documentation conflicts, workflow efficiency, or skill-usage gaps after work completes. DO NOT USE FOR: CE Gate Track 2…

원문 언어: 영어

process-retrospective

Formalized skeleton for the process-retrospective frame port. Use when #348 ships the live producer and replaces this skeleton. DO NOT USE FOR: any current PR — applies-when is 'never' until #348 ships. See trigger-deferred-to and trigger-deferred-since below.

원문 언어: 영어

brainstorming

Structured Socratic questioning for exploring ideas and solutions. Use when exploring new features, evaluating approaches, or thinking through complex decisions. DO NOT USE FOR: architecture evaluation or SOLID analysis (use software-architecture), UI…

원문 언어: 영어

frontend-design

Guide for creating distinctive UI designs that avoid generic templates. Use when designing new UI components, screens, or evaluating designs for uniqueness and purpose. DO NOT USE FOR: architecture decisions or SOLID evaluation (use software-architecture),…

원문 언어: 영어

guidance-measurement

Guidance-complexity measurement tooling and usage notes. Use when running or maintaining the guidance measurement script and related deterministic analysis assets for issue #360. DO NOT USE FOR: changing D10 ceiling rules or prompt-facing guidance policy,…

원문 언어: 영어

process-troubleshooting

Five-scenario workflow troubleshooting guide for diagnosing and fixing common orchestration failure patterns. Use when diagnosing premature implementation, agent confusion, validation gaps, documentation conflicts, or terminal stalls during a workflow…

원문 언어: 영어

property-based-testing

Incremental rollout policy for property-based testing that preserves readable example-based tests while adding invariant-focused randomized verification. Use when adding randomized testing, validating input ranges, or verifying mathematical properties. DO NOT…

원문 언어: 영어

software-architecture

Clean Architecture, SOLID principles, and architectural decision guidance. Use when evaluating layer boundaries, dependency flow, design contract violations, or ADR-level decisions. DO NOT USE FOR: open-ended idea exploration (use brainstorming), UI component…

원문 언어: 영어

specification-authoring

Structured authoring guidance for formal specification documents. Use when drafting machine-readable requirements, filling the repository specification template, or refining interfaces and acceptance criteria into a self-contained spec. DO NOT USE FOR:…

원문 언어: 영어

systematic-debugging

4-phase debugging process (Observe, Hypothesize, Test, Fix) for complex issues. Use when debugging fails, investigating flaky tests, tracking root causes, or facing mysterious bugs. DO NOT USE FOR: writing new tests (use test-driven-development), React…

원문 언어: 영어

ui-testing

Resilient React component testing strategies focusing on user behavior. Use when writing or reviewing component-level React tests, fixing flaky component tests, or establishing React testing patterns. DO NOT USE FOR: Playwright E2E tests (use webapp-testing),…

원문 언어: 영어

webapp-testing

Playwright end-to-end testing guidance for web apps, with practical patterns and setup steps. Use when creating or improving browser-based E2E coverage, test stability, and CI execution. DO NOT USE FOR: React component tests (use ui-testing), canvas game…

원문 언어: 영어