Explore

Find agent skills by outcome

23,927 skills indexed with the new KISS metadata standard.

Showing 24 of 23,927Categories: Data & Insights, Data, Writing & Content, Coding & Debugging, Creative, Openclaw

RULE: When using this prompt

you must create a file named `TODO_caching-architect.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wk...

Find agent skills by outcome

**RULE:** When using this prompt

- Plans for failure modes including stampede

- Data access patterns

Write all proposed caching architecture designs and any code snippets to `TODO_caching-architect.md` only. Do not create any other files. If specific files should be created or edited

- Leverage Redis data structures (Sorted Sets

- Set TTLs based on data change frequency: seconds for real-time data

- Avoid embedding volatile data (timestamps

- [ ] Memory sizing accounts for peak load

- [ ] Cache hit rates meet target thresholds (typically >90% for hot data

- Design load tests simulating cache stampede

- Map each data entity to its invalidation strategy (write-through

- **Cache-aside (lazy loading)**: Application manages cache reads and writes explicitly

- **Write-behind (write-back)**: Asynchronous batch writes to backing store

- **Event-driven invalidation**: Publish cache invalidation events on data changes

- **Write-through**: Synchronous cache update on every write

- **Distributed caching**: Redis clusters for shared state

- **Database caching**: Query result caching

- Calculate cache memory requirements based on data size

- Select invalidation patterns per data type: write-through for critical data

- **Select optimal caching technologies** based on use case requirements

- Identify hot data sets

- Design from the outside in: CDN layer

- **Ensure data consistency** by designing invalidation workflows

- **Implement cache invalidation patterns** including write-through

RULE: When using this prompt

- Cache-aside (lazy loading): Application manages cache reads and writes explicitly

- Write-behind (write-back): Asynchronous batch writes to backing store

- Event-driven invalidation: Publish cache invalidation events on data changes

- Write-through: Synchronous cache update on every write

- Distributed caching: Redis clusters for shared state

- Database caching: Query result caching

- Select optimal caching technologies based on use case requirements

- Ensure data consistency by designing invalidation workflows

- Implement cache invalidation patterns including write-through