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

Mar 28, 2026

General

PromptBeginner5 minmarkdown

- Include specific

actionable information rather than vague disclaimers

Mar 28, 2026

General

PromptBeginner5 minmarkdown

- [ ] Page routes (`/terms`

`/privacy`

Mar 28, 2026

General

PromptBeginner5 minmarkdown

- [ ] Footer

cookie banner

Mar 28, 2026

General

PromptBeginner5 minmarkdown

- [ ] All documents include effective date

version number

Mar 28, 2026

Find agent skills by outcome

- Document cache key schema with namespaces

- **High availability**: Redis Sentinel or Cluster mode

- **Hot key mitigation**: Local caching of hot keys

- **Cache stampede prevention**: Mutex locks

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

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

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

- **Application-level caching**: In-process caches (e.g.

- **CDN caching**: Static assets

### 5. Monitoring

- Implement cache hit rate monitoring

- Plan for cache stampede prevention using locking

- Configure eviction policies (LRU

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

- Select appropriate caching technologies (Redis

- **Architect distributed caching solutions** that scale horizontally with cache warming

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

- **Optimize cache hit rates** through strategic cache placement

- Are living documents with versioning

**RULE:** When using this prompt

- Include specific

- [ ] Page routes (`/terms`

- [ ] Footer

- [ ] All documents include effective date

- High availability: Redis Sentinel or Cluster mode

- Hot key mitigation: Local caching of hot keys

- Cache stampede prevention: Mutex locks

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

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

- Write-through: Synchronous cache update on every write

- Application-level caching: In-process caches (e.g.

- CDN caching: Static assets

- Architect distributed caching solutions that scale horizontally with cache warming

- Implement cache invalidation patterns including write-through

- Optimize cache hit rates through strategic cache placement

RULE: When using this prompt