Prize Wheel Giveaway
Run a spin-the-wheel giveaway where each entrant gets one spin and a recorded prize.
What it adds
A giveaway with a wheel interface, one server-decided spin per entrant, and a durable record of every result.
What your agent is told to do
5
What your agent is told to do
5-
1
Decide the outcome on the server before the wheel starts turning. The request returns a prize, the animation lands on it, and the client is only ever playing back a result it was given.
-
2
Model prizes with explicit weights and optional stock counts, and let an operator edit them without a deploy. A giveaway whose odds live in code cannot be corrected once it is live.
-
3
Tie an entry to an account where the app has one, and where it does not, combine the strongest identifiers available and treat a single spin as the hard limit across all of them.
-
4
Record every spin through the app's existing Audit Log: who, when, which prize, the weights in force at that moment, and the request that produced it. Giveaways generate disputes and an unlogged spin cannot be defended.
-
5
Do not treat the animation as the source of truth. Reusing a wheel library that picks a random segment locally and reports it means a determined entrant can pick their own prize from the console.
Edge cases it handles
8
Edge cases it handles
8- Any outcome computed in the browser can be inspected and replayed until it produces the desired prize. The client must never hold the weights, the prize list with odds, or the random draw, only the label it is told to display.
- One spin per entrant has to hold across devices, browsers, and signed-out sessions. Enforce it with a uniqueness constraint on the entry record rather than a check-then-write, so two simultaneous requests cannot both pass the check.
- Limited prizes are over-awarded when stock is decremented after the prize is announced. Reserve the prize and decrement the count in the same transaction that decides the outcome, and fall back to the next eligible prize if the stock has just run out.
- Every spin needs a durable record before the result is shown, including spins where the response never reached the entrant. An entrant who claims they won something must be answerable from the log rather than from memory.
- A spinning wheel is exactly the animation that causes problems for motion-sensitive viewers. Honour the app's existing Reduced Motion Support by showing the result directly, with no rotation and no flashing, and make that path equally celebratory rather than a degraded consolation.
- The connection can drop between the outcome being decided and the wheel finishing. Persist the result first so reloading the page shows the prize already won rather than offering a second spin or losing the first one.
- Prizes and giveaways attract automated entry. Apply the app's existing Rate Limiting, and require whatever identity verification the app already has before an entry counts.
- A wheel with a losing segment must say so plainly when it lands there. Ambiguity about whether a spin was a loss or a failure is the single most common source of giveaway complaints.
Definition of done
9
Definition of done
9- Prize outcomes are decided server-side and the client receives only the result to display.
- Each entrant can spin exactly once, enforced by a database constraint across devices and sessions.
- Limited prizes cannot be awarded beyond their stock, even under concurrent spins.
- Every spin is written to the audit log with the prize, the entrant, and the weights in force.
- Prize weights and stock are editable by an operator without a deploy.
- Reduced-motion viewers get the result without rotation or flashing.
- A dropped connection after the outcome shows the prize already won rather than granting a second spin.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Poll Widget
Poll Widget
Ask a one-question poll anywhere in the app and show the results as soon as someone votes.
What it does
An embeddable single-question poll with a vote control and a results view revealed after voting.
How it works
- 1 Keep it to one question with a small set of options. The moment it grows a second question it is a survey and belongs in the survey feature instead.
- 2 Record the vote on the server and return the updated tallies in the same response, so the results the voter sees are the real counts rather than an optimistic local guess that may disagree after a refresh.
- 3 Hold voting open to signed-out visitors if the poll is public, and identify them well enough to prevent casual repeat voting without demanding an account for a single click.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/poll-widget
Announcement Bar
Announcement Bar
Put a timed message across the top of the site without shipping a deploy.
What it does
An operator-configured, dismissible strip at the top of public pages, with scheduling and a link.
How it works
- 1 Extend the existing Service Incident Banner rather than adding a second bar. It already handles scheduling, targeting, dismissal, and severity; this is a marketing-styled variant of the same component, and two independent bars will eventually stack on top of each other.
- 2 Let an operator set the message, an optional link, background and text colours, and a start and end time from an admin screen. Requiring a deploy to run a weekend promotion means it goes live late.
- 3 Insert the bar into the document flow so it pushes fixed headers and sticky navigation down. Overlaying it on top of the header hides navigation on exactly the pages people arrived on.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/announcement-bar
Discussion Forum
Discussion Forum
Give users a public place to ask questions and answer each other.
What it does
Topic boards containing user-created threads with replies, moderation controls, and permalinks.
How it works
- 1 Ship boards, threads, replies, and a single level of nesting. Resist arbitrary-depth reply trees, reputation scores, badges, and private subforums until people are actually posting; each of those is a feature in its own right.
- 2 Reuse Comments and Mentions for the reply composer, mention parsing, and content rendering rather than writing a second editor with its own escaping rules.
- 3 Route reported and held posts into the existing Moderation Queue and reuse AI Text Content Moderation and Content Reporting if present. Do not build a forum-specific moderation inbox alongside the one the app already has.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/discussion-forum
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.