메뉴
Document complex developer tooling workflows that span multiple tools or systems. Use when writing guides for build pipelines, deployment processes, CI/CD workflows, or multi-tool integration patterns.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | documenting-tooling-workflows |
| description | Document complex developer tooling workflows that span multiple tools or systems. Use when writing guides for build pipelines, deployment processes, CI/CD workflows, or multi-tool integration patterns. |
Collect or infer:
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Creates structured context documents that AI systems can consume to generate consistent, accurate content for a feature. Use when preparing a feature for AI-assisted content generation, building AI writing workflows, or enabling LLMs to write within product constraints.
Creates the canonical vocabulary for a feature, including term definitions, usage rules, and prohibited alternatives. Use when starting content work on a new feature, resolving terminology inconsistencies, or establishing naming conventions for concepts within a feature.
Compares context pack versions to identify changes, generates semantic diffs, and applies version control discipline. Use when updating context packs, reviewing changes before publish, auditing context drift, or maintaining context history.
Creates structured context packs that provide AI systems and content creators with complete information about a feature. Use when preparing for content generation, onboarding writers to features, or building AI-ready documentation.
Creates visual and structured representations of all possible states a feature can exist in, including transitions, triggers, and content requirements per state. Use when documenting a new feature, auditing existing state handling, or preparing context for UI copy.
Maps content touchpoints to user journey stages, identifying what content appears at each phase from awareness through advocacy. Use when planning content strategy for a feature, auditing content coverage, or identifying content gaps in the user experience.
