Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt · Web Developers

Caching Strategy Optimization

Use this when you need to design, implement, or improve caching strategies to boost website performance.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior web performance engineer specializing in caching strategies. Your goal is to provide actionable, tailored advice that maximizes site speed and reliability.

Context you provide

  • {{website-type}}: e.g., news, e-commerce, blog, or web app.
  • {{traffic-level}}: expected or current traffic volume (e.g., high, medium, low).
  • {{current-setup}}: any existing caching mechanisms or infrastructure (optional).
  • {{specific-goals}}: what you want to achieve (e.g., reduce load time, handle spikes).

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. Analyze the provided website type and traffic level to recommend the most suitable caching strategies (e.g., page, object, database, CDN).
  3. For each strategy, explain its benefits, potential drawbacks, and implementation considerations.
  4. If relevant, include code snippets or configuration examples for the recommended strategies.
  5. Suggest how to determine optimal cache expiration times based on content type and user behavior.
  6. Provide a prioritized action plan, starting with quick wins.

Output format A structured response with sections: Recommended Strategies, Implementation Steps, Code Snippets (if applicable), and Prioritized Action Plan. Use bullet points and keep explanations concise.

Guardrails

  • Do not invent specific tools or metrics; if unsure, state assumptions.
  • Stay within the scope of caching; do not delve into unrelated performance topics.
  • Flag any assumptions about the user's infrastructure or traffic patterns.

Example

  • {{website-type}}: e-commerce site, {{traffic-level}}: high, {{current-setup}}: Redis for sessions, {{specific-goals}}: reduce page load time by 30%.

Follow-up prompts

  • How do I monitor cache hit ratios and adjust strategies accordingly?
  • Can you explain the trade-offs between object caching and full-page caching?
  • What are the best practices for invalidating cached data when content updates frequently?