Copy-paste the block below into any AI coding agent to take a project idea from vague concept to a polished portfolio piece you'd be proud to show.
Keywords: portfolio, side project, showcase, personal project, build in public
Help me build a portfolio-worthy project. I'll describe the idea; you help me
shape it into something scoped, real, and presentable - something I can
explain confidently and that demonstrates actual skill.
## Steps
1. **Shape the idea** - Turn my description into a concrete project: what it
does, who it's for, and the 1–3 things that make it interesting. Push back
on scope creep ("a full app with auth, payments, and notifications" is too
much) and suggest the smallest version that's still impressive.
2. **Decide the stack** - Propose a stack I actually can build and explain,
matching my stated skills. Favor boring, well-documented choices unless
the project specifically wants something novel. Ask if you're unsure what I
know.
3. **Make a roadmap** - Break it into milestones that each produce something
working and demonstrable: MVP first (core feature works), then polish,
then extras. Each milestone has a clear "done" definition and how I'll test
it.
4. **Build it with me** - Implement milestone by milestone using good
practices: git from day one (small commits), tests where they matter,
README that explains the project, and a working setup for someone to clone
and run.
5. **Make it presentable** - A README that sells it honestly: what it is, how
it works (with real screenshots/usage), the interesting technical decisions,
and what I'd do next. Help me write a short "about this project" blurb for
my portfolio/README that's specific and true.
## Verification
- [ ] The project was scoped down to the smallest version that is still impressive, and the cut is stated.
- [ ] The stack matches skills I actually have, so I can explain every choice.
- [ ] Every milestone has a clear "done" definition and a way I will test it.
- [ ] The repo clones and runs for a stranger, with small commits from the first day.
- [ ] The README shows real screenshots and only claims the code actually supports.
## Rules
- Keep me in the loop on decisions; don't silently build a different project
than we agreed.
- Prefer code I can understand and explain over clever code I'd fumble when
asked about it.
- No fake polish: no mock data pretending to be real, no claims the code
doesn't support.
- The goal is a project I can talk about confidently - if we add complexity,
make sure I can explain it.