메뉴
Use when investigating, fixing, or improving an existing codebase — any task where refactoring temptation, scope creep, or architectural drift could exceed what was actually asked.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Process raw-extracted JSON files from PDF book extractions into clean, well-structured markdown. Use this skill whenever a user uploads a raw-extracted.json (or similar JSON with metadata and chunks arrays) from a PDF text extraction pipeline, or when they mention cleaning up, formatting, structuring, or organizing extracted book text. Also trigger when the user mentions OCR output, pypdf extraction, book chapters, or converting messy PDF extractions into readable markdown. This skill handles books with varying extraction quality — from clean text to garbled OCR — and adapts its approach accordingly.
This skill should be used when the user invokes /code-documentation, or asks to "write/generate/audit/update documentation", "write a README", "document this API or codebase", "write a tutorial / how-to / runbook", "write user help docs", "generate docstrings", "write an ADR or RFC", "create a changelog", "produce llms.txt or AGENTS.md", or "turn these docs into a doc site". Produces first-class documentation for any audience (end users, API consumers, contributors, operators, evaluators, AI agents) across all four Diátaxis modes, for the full lifecycle — authoring, generating from a codebase, auditing, and maintaining. Emits publish-ready Markdown or structured content for Docusaurus, MkDocs, Sphinx, Starlight, Mintlify, or Volume.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.
Use when the user wants to brainstorm blog topics, generate or score article ideas, review/approve content ideas, track article status, or manage editorial planning — including mentions of "content calendar", "editorial calendar", "blog ideas", "article pipeline", "content backlog", or "publishing schedule".
Checklist for auditing architecture contracts in a develop-by-contract environment. Covers the failure modes most commonly found during contract review: status drift, AI-invented decisions, cross-contract fact drift, stale feature references, missing state specs, and business policy gaps.
Use when analyzing, auditing, reviewing, or explaining a codebase, system, or project state — whenever written claims could mix observed fact with interpretation.
| name | scope-and-direction-guardrails |
| description | Use when investigating, fixing, or improving an existing codebase — any task where refactoring temptation, scope creep, or architectural drift could exceed what was actually asked. |
This skill enforces constraints on project direction, scope, and refactoring behaviour.
It exists to prevent unintended architectural drift and “agent heroics.”
This skill applies whenever an agent:
Agents MUST NOT:
If direction change seems warranted, the agent MUST:
Refactors are NOT the default solution.
Allowed:
Forbidden:
If work is identified that:
The agent MUST:
This skill exists to protect:
Agents are collaborators, not saviours.
