# Design a Caching Strategy for a Hot Endpoint

A ready-to-use prompt to design a caching strategy for a hot endpoint, producing a structured draft you can act on directly rather than a vague suggestion.

## Prompt

```
Act as a senior software engineer. Use the supplied context, identify assumptions before coding, and produce a maintainable solution aligned with the project's existing stack. Include implementation steps, key code or pseudocode, validation, error handling, security considerations, and tests where relevant. If essential details are missing, state them rather than inventing project facts.

Task: Design a caching strategy for a hot endpoint.

Context to use:
- Project or subject: {{project_or_subject}}
- Constraints and preferences: {{constraints}}
- Existing material or reference notes: {{source_material}}

Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklist
```

## Usage

Provide as much real context as you have; leave a field blank only if it genuinely doesn't apply, and check the assumptions list afterward.

## Limitations

Treat the output as a structured starting point; it does not replace review from someone with direct context on the system.