메뉴
Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.
Use for UI components, design systems, atomic design, tokens, themes, hardcoded visuals, or missing design SSOT.
Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.
Use for visual PDFs: create, polish, export, verify decks, reports, proposals, one-pagers, or HTML-to-PDF.
Use for real UI E2E smoke/regression proof across web, Flutter, browser, Chrome, or device flows, with artifacts.
Interview one clear question before planning/building ideas, features, codebase maps, specs, UI flows, prototypes, or final plans.
| name | diagnosing-bugs |
| description | Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing. |
Use this before changing code when the failure is not already isolated.
Load references/workflow.md for the diagnosis loop.
Coordinate with nearby skills:
performance-rescue tootest-quality toosecurity-review too.Do not jump from symptom to patch. First build evidence that the proposed fix addresses the exact user-described failure.