How to use Cursor to build a courtroom card game

Victor Da Luz built a two-player courtroom card game for a hackathon using Cursor custom modes while learning Godot. He divided the work among a requirements interviewer, architect, planner, developer, reviewer and technical writer, giving each mode different tools and output files.

The initial roles produced requirements, a system design and an implementation plan. The ongoing loop became simpler: the planner proposed work, the developer implemented it and the reviewer inspected changes. When the reviewer kept failing to run git diff, Da Luz discovered that he had omitted terminal access and corrected its permissions. He also narrowed review scope to changes rather than entire files.

The result was a functional game with basic visuals and documentation, but development required repeated human intervention. One card-effect change broke the turn system; review caught it only after failed test runs. Another refactor removed buttons. UI requests were especially unreliable because the developer had no visual design to follow.

Da Luz manually repaired misunderstood layouts and tested the game. The useful account is a concrete role-and-tool workflow plus its failure points: a review agent could catch missing preconditions and logic bugs, while neither specialized roles nor a large plan eliminated the need to play and inspect the interface.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Personal blog · Victor Da Luz