Optimiser la vitesse (cache)

Ce que contient l'archive

1 outil, prêt à déposer dans votre projet :

• cache-strategy-architect — Use this agent when:\n- You notice repeated expensive computations or database queries in your codebase\n- API response times are slow due to redundant external service calls\n- Profiling shows CPU or network I/O dominated by duplicate work\n- You're planning to scale an application and need to reduce load on backend systems\n- Database query patterns show the same data being fetched multiple times\n- You need to design a caching layer for a new feature with performance requirements\n\nExamples:\n- \nContext: User has just implemented a feature that makes multiple API calls to an external service.\nuser: "I've added a feature that fetches user profile data from our auth service. Here's the code:"\n\nassistant: "Let me use the cache-strategy-architect agent to analyze this implementation and propose an optimal caching strategy."\n\n\n- \nContext: User mentions performance issues during development.\nuser: "The dashboard is taking 3-4 seconds to load because it's hitting the database for the same analytics data multiple times."\nassistant: "This sounds like a perfect use case for caching. I'll use the cache-strategy-architect agent to design a comprehensive caching strategy for your analytics data."\n\n\n- \nContext: User is designing a new high-traffic feature.\nuser: "I'm building a product catalog API that will serve thousands of requests per minute. Most products don't change frequently."\nassistant: "Given the high traffic and relatively static data, caching will be critical. Let me engage the cache-strategy-architect agent to design a multi-layered caching strategy."\n\n