메뉴
Quality enforcement rules — no fallbacks, no false positives, no patch work, script everything. Use when reviewing code, verifying fixes, or ensuring code quality.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | quality-guards |
| description | Quality enforcement rules — no fallbacks, no false positives, no patch work, script everything. Use when reviewing code, verifying fixes, or ensuring code quality. |
Never claim "fixed", "working", or "done" without ALL verification steps:
Anti-patterns: trusting HTTP status codes, saying "should be working" without proof, declaring "code loaded" as "feature working".
The user has deficits in long-term memory. Script everything:
make status is the reliable information device.env.{dev,prod} and ./deployment scriptsThe orchestrator (and any agent acting on behalf of the user) NEVER approves destructive operations autonomously. Destructive operations include:
| Category | Examples |
|---|---|
| Docker | docker system prune, docker volume prune, docker rm -f |
| Filesystem | rm -rf, rm -r on data directories, bulk deletes |
| Git | git push --force, git reset --hard, git clean -f |
| Database | DROP TABLE, TRUNCATE, cache clear on production |
When a subagent or process requests a destructive operation:
This applies even during autonomous operation. Destructive = user decision.
Master index of all available skills for development workflows. Use when needing guidance on which skill to apply or when starting work on any project.
Master index of all available skills for development workflows. Use when needing guidance on which skill to apply or when starting work on any project.
Autonomous work mode — never ask user to run commands, never stand by, always take next action. Use when working independently on tasks.
Claude Code setup and configuration reference. Skills, commands, hooks, MCP servers, CLI, and permissions.
Code audit, cleanup, refactoring, API minimization, test review, examples, and project evaluation. Use when reviewing code quality or preparing for release.
Core development philosophy including development cycles, naming conventions, architectural decisions, and multi-agent workflows. Use when establishing project foundations or making architectural decisions.