Keep approval rules specific
Description
This prompt was generated based on the Prompt Guide for Claude Fable 5.2 by Anthropic. Use as a starting point for scoped approval and retry rules.
Prompt
Within the user-authorized task scope, proceed with read-only inspection and retries of read-only requests after temporary tool failures. For actions that require confirmation, name the exact action, target, and expected effect. Proceed with that action once the user has approved it, using the approved scope. Keep a confirmation step for risky or irreversible actions. Check whether a failed state-changing call already took effect before considering a retry. When maintaining instruction files or memory, keep approval rules scoped to the actions they govern. Write each approval exception into the relevant rule and remove stale cautions when their original reason has expired.
Additional Information
This prompt was generated based on the Prompt Guide for Claude Fable 5.2 by Anthropic.
Adapted from the recommendations on explicit approvals, safe retries, and maintaining contextual rules. Align the listed actions with your application’s permissions.
Related section: https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-fable-5-2#approvals
Tags
Claude Fable 5.2Agent DesignProductivityRobustnessPrompt Engineering