Put DealCraft in your codebase
One file teaches a coding agent the whole integration: where the game goes, which key belongs in a page and which never does, and how to take a reward code at checkout without burning it on an abandoned cart.
Install it
The skill is one markdown file served from this domain. Fetch it into whatever your agent reads, and it has the contract instead of guessing at it.
Claude Code
Drops it into the project skills folder, where it loads on any DealCraft task.
Codex
Appends it to AGENTS.md, which Codex already reads on every run.
Any other agent
Fetch it and put it wherever that tool keeps project instructions.
What it teaches
Written from the failures we actually see, not from a feature list.
The pop-up, per framework
Including why a plain script tag inside a React component runs on the first load and never again, which is the most common broken install.
Taking a code at checkout
Check at the cart, mark used after the payment is captured, and a request id so your own retry is safe while a second till still is not.
Verifying a webhook
Against the raw body, with the rotation overlap, because a re-serialised JSON body produces different bytes and never matches.
What a per-person cap really means
Anonymous play counts browsers, so a cleared cookie earns another play. If the promise has to hold, the skill says which mode to pick.
The mistakes that happen
A secret key in a NEXT_PUBLIC variable, a test key in a page, granting an entitlement from a postMessage, embedding before listing the site.
Four ways in
Rising order of effort. Every one of them ends with the server having decided the outcome before any animation ran.
Website pop-up
The game opens over your own pages, on rules you set in the dashboard.
one script tag
Inline embed
The game sits inside a page rather than opening over it.
one iframe
Public link or QR
Send it, print it, open it on a tablet. Every visit starts a new play.
no code
API
Your own accounts, your own checkout, your own per-person guarantee.
two HTTP calls