Idea to production
Prompting as a skill
Debugging with the agent
Security essentials
Practice
Assignment
Back to Track
Deliverable: one feature taken through the complete flow — idea to reviewed PR.
Use your Week 1 project or your main-track project.
- Define done (posted in Practice #5) — one or two checkable sentences.
- Prompt with the template. Goal / Context / Boundaries / Done when — for the skeleton and for each fill-in step.
- Build through the stages. Skeleton → fill-in (small diffs) → polish → tests (cases first, then code; break something to verify a test catches it).
- Security pass before pushing:
.env gitignored, no secrets in the diff or history, every command you approved — one you could explain.
- PR with the honest description (Week 2 format), plus one new section: a debugging note — what broke during the week and how you got out (rollback? fresh session? better error context?). If nothing broke, say so — and say what you'd have done.
- Get it reviewed — a separate review chat, a classmate, or a mentor — and respond in small commits.
You are done with Week 3 when
- [ ] Your PR matches the "done" definition you posted at the start — no more, no less.
- [ ] Every prompt in your main thread had goal, context, boundaries, and done-when.
- [ ] Your tests catch a deliberately introduced break.
- [ ]
.env is ignored, history is clean, and you can explain every command you approved.
- [ ] Your PR includes the debugging note.
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.