Request Correlation IDs
Follow one user action through every request, job, and downstream call.
What it adds
A single ID generated or accepted at the edge and carried through logs, background jobs, outbound calls, and error reports, so one user action can be reconstructed end to end.
What your agent is told to do
6
What your agent is told to do
6-
1
Generate a correlation ID at the entry point of every inbound request. If the caller supplied one, validate it before trusting it — bounded length, a restricted character set, no newlines — and generate a fresh one if it fails.
-
2
Store the ID in a context that follows the unit of work, not in a global variable. Concurrent requests must never share one.
-
3
Propagate it explicitly: attach it to every log line, enqueue it with every background job, send it as a header on every outbound HTTP call, and attach it to error-tracker reports.
-
4
Show the ID on user-facing error pages so a support ticket can be matched to the exact failure. Show only the ID — never the exception, the stack, or the internal service that failed.
-
5
Do NOT derive the ID from user data, session tokens, or sequential counters. It must be unguessable and it must reveal nothing about who the user is.
-
6
Field names, severity levels, and redaction rules are owned by Structured Logging; extend that schema with the correlation field rather than defining a second logging convention here.
Edge cases it handles
6
Edge cases it handles
6- A job that spawns further jobs must pass the ID down the chain, and a retry must reuse the original ID rather than minting a new one.
- Scheduled and cron-triggered work has no inbound request. Generate an ID at the start of the run so those events are still traceable.
- An untrusted inbound header must never be echoed back unvalidated — that is a header injection and log-forging path.
- Async work that outlives the request must not lose the context when the request completes.
- The ID must appear in the response headers so a client or proxy can record it without reading the page.
- Do not let a missing ID be an error. If context is unavailable for any reason, log with a placeholder and continue serving.
Definition of done
8
Definition of done
8- Every inbound request has a correlation ID, either validated from the caller or freshly generated.
- The ID appears on every log line produced during that request.
- Background jobs, retries, and outbound HTTP calls carry the same ID.
- Error-tracker reports are tagged with the ID and user-facing error pages display it.
- The ID is returned in a response header.
- IDs contain no user-identifying or sequential information.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
AI Cost Budgets
AI Cost Budgets
Cap what AI features are allowed to spend before the bill arrives.
What it does
Monetary spending limits on AI work, scoped by workspace, feature, and time period, enforced before a run starts.
How it works
- 1 Find every place the app calls a model and route all of them through one accounting point that records estimated and actual spend against a scope. A budget that only covers the chat feature is not a budget.
- 2 Estimate the cost of a run from the size of its input before dispatching it, and refuse anything that would exceed the remaining budget on its own.
- 3 Reserve the estimate against the budget when the run starts, then reconcile to the real usage figures when it finishes, releasing whatever was over-reserved.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-cost-budgets
Multi-Model Routing
Multi-Model Routing
Send each AI request to the right model using rules you can read and test.
What it does
A deterministic routing layer that picks a model per request from task type, context size, latency budget, and data sensitivity.
How it works
- 1 Express routing as explicit, ordered rules over inputs the app can measure: task type, estimated context size, latency budget, and the sensitivity classification of the data involved. A rule set that can be read line by line can be reviewed and tested.
- 2 Make routing deterministic. The same inputs must always produce the same route, so a bad output can be reproduced and a rule change can be evaluated. Randomised or load-based selection turns every incident into guesswork.
- 3 Classify data before routing and refuse to route restricted content to any destination not approved for it. This check is a hard block, not a preference, and it must run before the request is assembled.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/multi-model-routing
SEO Setup
SEO Setup
Make your app findable — titles, meta, Open Graph, sitemap, robots.
What it does
The baseline SEO and social-preview setup every public app should have, and most skip.
How it works
- 1 Give every public page a unique, descriptive title and meta description. Find the app's layout and add a mechanism for each page to set them.
- 2 Add Open Graph and Twitter Card tags so shared links render a preview instead of a bare URL.
- 3 Generate a sitemap.xml covering every public, indexable page, and a robots.txt pointing at it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/seo-setup
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.