메뉴
Use when generating or maintaining codebase documentation. Divio framework.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | codebase-documentation |
| description | Use when generating or maintaining codebase documentation. Divio framework. |
∀ codebase analysis tasks. ∀ documentation tasks.
| Type | Purpose | Audience | Style |
|---|---|---|---|
| Tutorial | Learning-oriented | New dev | Step-by-step, "do this, then this" |
| How-to | Task-oriented | Working dev | "To achieve X, do Y" |
| Reference | Information-oriented | Any dev | Accurate, complete, terse |
| Explanation | Understanding-oriented | Curious dev | Discursive, "why" focused |
| File | Focus | Content |
|---|---|---|
| STACK.md | Technology | Languages, frameworks, tools, versions, rationale |
| ARCHITECTURE.md | Structure | Patterns, layers, boundaries, data flow |
| CONCERNS.md | Cross-cutting | Tech debt, security, fragile areas, missing coverage |
| CONVENTIONS.md | Standards | Naming, file structure, commit format, review process |
project docs directory (e.g., docs/)Use when making git commits. Conventional commit format and rules.
Use when running security review on a diff/PR/file. Research-vs-Reporting discipline, three-tier confidence gate, attacker-controllable taxonomy.
Use when invoking plannotator for approval review of generated .tff-cc milestone artifacts (plan, verification, spec).
Use when starting design or discovery work. MUST use before any creative work.
Use when the user wants to report a bug, file an issue, or send feedback about tff-cc. Triggers on phrases like 'report issue', 'file a bug', 'tff-cc broke', 'something is wrong with tff-cc', 'open an issue', '/report-issue'.
Use when creating, refining, or composing skills. Evidence-driven pattern analysis.