optimize-claude-fable-5-prompts

Optimize Claude Fable 5 Prompts

Turn rough ideas and existing prompt stacks into copy-ready prompts for Claude Fable 5. Preserve the user's intent and hard constraints, clarify genuinely blocking gaps, and keep the result no more elaborate than the task requires.

Use the official basis

Read references/official-guidance.md when model-specific rationale, API-setting guidance, migration details, or long-context patterns are relevant. Treat its URLs as canonical sources and its prose as a dated working summary. Fetch the live Anthropic pages before making claims about current model IDs, parameters, availability, limits, or pricing.

Use the official model name Claude Fable 5. Treat Fabel as a likely spelling variant when it appears in a prompt-optimization request, unless context indicates a different product.

Follow the workflow

1. Capture the prompt contract

Identify the following from the user's message, pasted prompt, or referenced file:

• the user-visible outcome and why it matters;
• the inputs, source material, and context Claude will receive;
• hard constraints, facts, policies, and values to preserve;
• the required output, audience, language, and level of detail;
• tools, evidence, or verification needed for success;
• whether Claude should assess, recommend, draft, implement, or take external action;
• authorized actions and actions that require approval;
• stopping and fallback behavior when a dependency is unavailable.

Treat these as diagnostic dimensions, not mandatory prompt sections. Keep a simple rewriting prompt simple.

If the user supplies a layered prompt stack, preserve the separation between system, developer, user, and tool-description content. Do not silently move instructions between trust levels.

2. Apply the clarity gate

Ask a question only when the missing or conflicting information is blocking: two reasonable answers would produce materially different prompts, outputs, permissions, evidence, or success criteria.