GitHubWhat they did
For a Hacktoberfest mini app challenge, the author, who runs court operations and does not write code, wanted a tip calculator that shows every amount in both US dollars and Mexican pesos. They asked Claude to write a build prompt from a two-sentence idea, revised it twice, then pasted it into Cursor. The spec fixed everything up front: one HTML file with no framework, a manual exchange rate field, tip buttons and a split count, input validation that never shows NaN, exact brand colours and fonts, a README, and a final instruction to add no extra features. It also told Cursor to run git, create a public repo with the gh CLI, push and enable GitHub Pages, then report both links.
How it went
Cursor did it in one pass with no redirection: first ask at 8:25, a single commit at 8:32, the Pages site live at 8:33, and the math held when the author checked it by hand. Their Cursor credits ran out right after, so Claude reviewed the 424-line file instead and found three issues: a fractional number of people was accepted, results were not announced to screen readers, and one CSS rule could never match. The first two were fixed in a two-line second commit. The only miss the author noted from Cursor was a README with em dashes.
Worth knowing
The author credits the spec more than the tool: most of the eight minutes went into writing the prompt, and the line forbidding extra features did the most work. A tip calculator is small enough for one spec to cover every decision; they say they have not yet tested whether this holds for anything with state or a backend. The exchange rate is typed in by hand, not fetched.
