1 min lesson
Use a repository they recognize
Explain why a legacy repository provides stronger evidence than a clean scaffold.
Step 1 of 2
Use a repository they recognizeThe repository sets the context
A fresh Next.js scaffold does not represent most enterprise work. Use a repository with constraints the audience knows, such as a 15-year Java monolith, a large Spring service, a slow build or an unreliable integration test. A credible demo shows how Cursor behaves under those conditions.
A real legacy repository. Use a fork of their repository after security review, or a faithful public example if that is not possible.
Include patterns their engineers recognize, such as large classes, missing tests or unclear module boundaries.
Their ticketing system, their CI, their PR template.
A todo app, a fresh scaffold or another clean sample that avoids their constraints.
A repository prepared in secret to make the agent look perfect.
Anything the audience cannot relate to its own work.
"I want to use a repository that reflects your work. Let us open an older service with the same constraints your engineers handle each day."
Do not prepare the repository in secret to hide likely failures. Experienced engineers will question a run that looks unrealistically clean.
If you cannot get their repository in time, say so and use the closest public equivalent. Never pretend it is theirs.