메뉴
Guardrails for debugging and troubleshooting. Auto-loaded when Droid encounters errors, test failures, or build issues. Prevents context drift and tech stack swaps during error recovery.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | troubleshooting-guardrails |
| description | Guardrails for debugging and troubleshooting. Auto-loaded when Droid encounters errors, test failures, or build issues. Prevents context drift and tech stack swaps during error recovery. |
| user-invocable | false |
When you encounter an error, build failure, or test failure, follow this protocol BEFORE proposing any fix:
The fix MUST:
NEVER do any of these to fix a bug:
any)try/catch that swallows errors silentlyIf you cannot fix the issue within these bounds after 2 attempts:
Records architectural and implementation decisions. Use when a significant technical decision is made, a spec is modified, or an approach changes during implementation. Creates numbered decision records in .factory/decisions/.
Generates structured requirements using EARS (Easy Approach to Requirements Syntax) notation. Use when the user is planning a feature, entering spec mode, or asking for requirements. Produces user stories with testable acceptance criteria.
Technology stack constraints and approved libraries. Auto-loaded when Droid is making technology choices, adding dependencies, or proposing architectural changes. Defines what frameworks, libraries, and patterns are allowed.