Prompting Guide

Each supported model family has its own guide. Identify the family that will run the instructions, read that guide, and follow its routing to its own references and template. Do not preload the other guides.

The target is the model that will execute the prompt, not the model doing the editing. Take it from the request, a model ID in the integration or configuration, a model field in the agent or skill definition, or the host's documented default. Ask only when it cannot be determined and the answer changes the advice.

For a Codex Goal mode or Claude Code /goal prompt, whether to explain, draft, review, translate between the two harnesses, or activate one, read the Goal mode guide together with the target family's guide. It carries the goal contract, the harness differences that change how a goal is written or judged, and the activation rules.

When an artifact will run on more than one family, such as a skill shared by Claude Code and Codex, apply each family's guide to that family's behavior and keep the clauses distinguishable. When migrating from one family to another, follow the target family's guide; the source family's guide only helps identify scaffolding written for the old model.

Keep Families Separate

Do not port guidance between families without measurement. The model lines changed in different directions, and effort level names do not mean the same amount of thinking across models. A clause, effort setting, or workaround that one guide recommends is evidence about that family only. The Fable and Opus guides share some Anthropic runtime facts; when maintaining one of them, update the other as listed in Opus source notes.

A model outside these families has no guide here. Say so and work from that model's official prompting documentation rather than borrowing a family guide's model-specific clauses.