Plan Your First Coding Portfolio Project in 1-3 Hour Milestones

Get one portfolio project matched to your goal and skills, split into 1-3 hour milestones, each with one new concept and a clear 'done when' check.

You getProject pitch, table and up to 3 stretch goals

Prompt

Prompt
Act as a senior developer who mentors beginners through their first portfolio project.

Help me plan one portfolio project I can finish. First ask me these questions in one numbered message, then wait for my answers:
1. What is the project for (first job, freelance work, a tool I need)?
2. What languages and tools have I used, and what have I built?
3. How many hours a week can I spend, and by when?
4. Any topic or problem I care about?

Rules:
- Pick one project that fits my goal and skills, and say in one line why an employer would care.
- Split it into 8-14 milestones, each 1-3 hours of work at my level.
- Each milestone teaches exactly one new concept, and you name it.
- Each milestone has a 'Done when' check I can verify in under 2 minutes, like a page loading or a test passing.
- Milestone 1 ends with something running; the last one is deployment plus a README.

Output format:
1. Project pitch (2-3 sentences) and tech stack
2. Table: #, Milestone, Hours, New concept, Done when
3. Up to 3 stretch goals
4. Where I'm likely to get stuck and what to search for

End with one line on the assumptions you made about my skill level.

Example output

At a glanceRun Log milestones by hours11 milestones, about 20.5 hours total at 6 hours a week
  • 1. Repo and Vite setup: 1.5 h
  • 2. Add-run form: 1.5 h
  • 3. Render runs list: 2 h
  • 4. Save to localStorage: 1.5 h
  • 5. Pace per run: 1.5 h
  • 6. Test pace function: 2 h
  • 7. Delete and edit: 2 h
  • 8. Weekly totals: 2 h

Example for: a self-taught learner aiming for a junior front-end job, knows HTML, CSS and basic JavaScript, 6 hours a week, enjoys running.

1. Project pitch

Run Log is a browser app to record runs, see pace per run and track weekly distance on a chart. It shows an employer you can manage state, persist data, write tests and ship a working app.

Stack: HTML, CSS, vanilla JavaScript, Vite, Vitest, Chart.js, Netlify.

2. Milestones

#MilestoneHoursNew conceptDone when
1Set up repo and Vite project with a Run Log heading1.5Git + Vite dev serverPage loads on localhost and first commit is on GitHub
2Build the add-run form (date, distance, time)1.5Form submit eventsSubmitting prints the three values in the console
3Store runs in an array and render a list2Rendering from stateAdding 3 runs shows 3 list items
4Save runs to the browser1.5localStorage + JSONRuns are still there after a refresh
5Calculate pace per run1.5Pure functions5 km in 27:30 shows 5:30 /km
6Test the pace function2Unit tests with Vitestnpm test shows 4 passing tests
7Delete and edit a run2Event delegationA deleted run stays gone after refresh
8Weekly totals summary2Array reduce and date groupingThis week's km matches your manual sum
9Bar chart of the last 6 weeks2.5Using a third-party libraryChart shows 6 bars with correct totals
10Mobile layout and accessibility pass2Media queries + form labelsLighthouse accessibility score is 90 or higher
11Deploy and write the README2Netlify deploymentLive URL works on your phone; README has a screenshot and setup steps

Total: about 20.5 hours, roughly 3.5 weeks at 6 hours a week.

3. Stretch goals

  • Filter runs by month
  • Export runs as a CSV file
  • Set a weekly distance goal with a progress bar

4. Where you'll likely get stuck

  • Grouping by week (milestone 8): search "JavaScript get ISO week number from date".
  • List not updating after delete (milestone 7): search "re-render list after array change vanilla JS".
  • Time input parsing (milestone 5): search "convert mm:ss string to seconds JavaScript".

Assumption: you can write functions and loops but have not used a build tool, tests or deployment before.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Capping milestones at 1-3 hours keeps each step finishable in one sitting, which stops beginners stalling on vague tasks.
  • One named concept per milestone turns the project into a learning path, so you know what skill each step adds.
  • The 2-minute 'Done when' check gives a clear finish line, so you never wonder whether a step is really complete.

Use when you know some basics but keep stalling on big projects. Paste into ChatGPT, Claude or Gemini, then answer its four questions about your goal, skills, weekly hours and interests.

Common edits

  • Name a specific stack, such as React or Python with Flask, if you need practice in it for job listings.
  • Ask for 6 milestones instead of 8-14 for a smaller weekend project.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Coding