prompt-caching-strategy

Topics in the source

• Prompt Caching Strategy
• When to Activate
• How It Works
• Preserve a stable prefix
• Preserve user and workspace boundaries
• Provider Requirements and Usage Evidence
• Cost Comparison Calculator
• Examples

Arrange reusable prompt content to improve cache reuse, then measure input cost and latency. Savings depend on model, platform, cache eligibility, writes, retention, reuse and output volume. Runtime cache hits and savings for this skill are unmeasured; the examples below validate arithmetic without provider calls. Use for repeated API requests that share authorized instructions, tools or reference material. First identify the exact provider endpoint, model, service tier and caching mode. Consult its current documentation before selecting rates, minimum prefix length or retention. Caching does not reduce context-window use. Keep reusable instructions, tool schemas and examples stable; place changing questions, timestamps and retrieved results after that content where the API allows. Respect the provider's serialization order: Claude uses tools, system, then messages. Matching prefixes need identical content, including tool schemas and relevant request settings. A changed prefix can prevent reuse from that point. A dynamic suffix may itself be cached later if reused unchanged. Choose only relevant context. Padding prompts or broadening access just to meet an eligibility threshold nee

This is an excerpt. Refer to the complete source and its current requirements.