Usage Limits
Cap what free accounts can do — visibly and fairly.
What it adds
Per-plan usage limits, enforced server-side, with the user always able to see where they stand.
What your agent is told to do
4
What your agent is told to do
4-
1
Define limits per plan in one place. Do not scatter magic numbers through the codebase.
-
2
Enforce on the server at the point of creation. A client-side check is decoration.
-
3
Show current usage BEFORE the user hits the wall — surprise limits feel like a bug.
-
4
When a limit is hit, explain it and link to the upgrade.
Edge cases it handles
4
Edge cases it handles
4- Counting must be race-safe — two simultaneous requests must not both slip past the last slot.
- Deleting a record must free up its slot, if that's the intended behaviour. Decide, then be consistent.
- A downgrade that puts a user over the limit must be handled explicitly: keep the data readable, block new writes.
- Limits must reset predictably (per month? rolling window?) and be documented.
Definition of done
7
Definition of done
7- Limits are defined in one place and enforced server-side.
- Concurrent requests cannot exceed the limit.
- Usage is visible before the limit is reached.
- Hitting the limit explains it and offers an upgrade.
- Over-limit users after a downgrade keep read access but cannot create.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Upgrade Modal
Upgrade Modal
Sell the upgrade at the exact moment someone wants it.
What it does
A focused upsell that appears when a free user reaches for a paid capability.
How it works
- 1 Trigger it at the point of intent — when they click the locked thing — not on a timer or on page load.
- 2 Name the specific feature they just tried to use. A generic pricing modal converts far worse.
- 3 State the price plainly and give one button to upgrade.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/upgrade-modal
Billing Portal
Billing Portal
Let people manage their own subscription.
What it does
A billing area where users can see their plan, change payment method, get invoices, and cancel.
How it works
- 1 Use the payment provider's hosted billing portal if it has one. Do not rebuild card management — it's a PCI liability you don't need.
- 2 Show the current plan, renewal date, and payment method on your own account page.
- 3 Make cancelling possible without emailing support. Dark patterns here generate chargebacks.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/billing-portal
Feature Gating
Feature Gating
Lock premium features behind a plan — without wrecking the free experience.
What it does
A consistent way to gate features by plan, and to sell the upgrade at the moment of intent.
How it works
- 1 Find where plan/subscription state already lives on the user. Do not invent a second source of truth.
- 2 Enforce every gate SERVER-SIDE. Hiding a button is not a gate, it is a hint — assume the user will call the endpoint directly.
- 3 Add one reusable client-side gate component for the UI affordance.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feature-gating
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.