メニュー
Generates CLI error messages and defines exit code conventions. Use when writing stderr output, defining exit codes, creating error message templates, or designing error recovery guidance for command-line tools.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | writing-cli-errors-and-exit-codes |
| description | Generates CLI error messages and defines exit code conventions. Use when writing stderr output, defining exit codes, creating error message templates, or designing error recovery guidance for command-line tools. |
Collect or infer:
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Low freedom
CLI errors occur across operational states:
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.
