You're building the idea from your Week 4 launchpad. If your idea fits the scope below — build it. If it drifted over the week, trim it now, not on day four.
One week of part-time work. The test: your "done" definition has 3–5 checkable statements, and you can imagine reaching them by mid-week with polish time left. Cut features until that's true — a small finished thing beats a large abandoned one.
Pick the shape that matches your main track:
Web. A small working app or site with a real UI: a tool, a tracker, a landing with interactive parts. Figma → code (Week 1) if you have a design; a clean hand-defined layout if not.
Backend. An API with a few endpoints and a data layer. Required technique: a frontend for verification — after each endpoint, have the agent throw together a simple one-off page that calls it and shows the response. It's a verification tool, not production code: don't polish it, don't grow it. You see your API through a consumer's eyes, without Postman fuss.
Testing. Take an existing app (a classmate's capstone from a previous cohort, your main-track project, a small open-source app) and build its test suite: test cases first, then automated tests through the agent. The special discipline of this variant: agent-written tests get the strictest review of all — verify each one tests real behavior by breaking the thing it claims to cover.
CLAUDE.md (from the launchpad)..env ignored, clean history, no secrets anywhere.The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*
Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.