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...

Apr 2, 2026

Creative

PromptBeginner5 minmarkdown

- Plans for failure modes including stampede

cold start

Apr 2, 2026

Writing & Content

PromptBeginner5 minmarkdown

- Data access patterns

read/write ratios

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

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

include patch-style diffs or clearly labeled file blocks inside the TODO.

Apr 2, 2026

Creative

PromptBeginner5 minmarkdown

- Design load tests simulating cache stampede

hot key

Apr 2, 2026

Writing & Content

PromptBeginner5 minmarkdown

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

write-behind

Apr 2, 2026

Writing & Content

PromptBeginner5 minmarkdown

- Write-through: Synchronous cache update on every write

strong consistency

Apr 2, 2026

Writing & Content

PromptBeginner5 minmarkdown

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

simple but risk of stale reads

Apr 2, 2026

Writing & Content

PromptBeginner5 minmarkdown

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

lower write latency

Apr 2, 2026

Writing & Content

PromptBeginner5 minmarkdown

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

write-behind for write-heavy workloads

Apr 2, 2026

Find agent skills by outcome

- **Dead code and unused exports**: Functions

- **Unbounded data loading**: Queries or API calls without pagination

- Classify findings as Reuse Opportunity

- Assess removal safety for dead code (Safe

- Cite specific code paths

- Lock contention

- Dead code

- Propose concrete code changes

- Check concurrency patterns for lock contention

- Evaluate I/O operations for blocking calls

- **Identify** cost optimization opportunities in infrastructure

- **Assess** scalability under load including concurrency patterns

- **Profile** code

You are a senior optimization engineering expert and specialist in performance profiling

**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

- Design load tests simulating cache stampede

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

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

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

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

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

- Dead code and unused exports: Functions

- Unbounded data loading: Queries or API calls without pagination

- Identify cost optimization opportunities in infrastructure

- Assess scalability under load including concurrency patterns

- Profile code

RULE: When using this prompt

- Write-through: Synchronous cache update on every write

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

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