A guided build environment for first-time developers

Build real software.
From idea to verified code.

YourDev turns a rough idea into a bounded plan: four milestones, a few files each, a definition of done, and the exact prompt to hand your AI coding agent. Then it checks each step before you move on.

Break down an ideaInspect output blueprint
phased milestones per idea
4
files to touch in each step
≤3
minutes per milestone, at most
~90
first prompt, ready to paste
1
blueprint / habit-trackerStep 3 in progress
The idea, as typed
“A habit tracker that reminds me every day and gives me a badge when I hit a 7-day streak.”
  1. 01 (verified)Habit data model
  2. 02 (verified)Habit row UI
  3. 03 (current)Save between visits
  4. 04 (up next)Streaks & badges

Save habits between visits

~60 min · 2 files
hooks/useHabits.tslib/storage.ts
Definition of done: try ticking these off
1 of 3 checks passing

Devi, your mentor
Run it on localhost first. I’ll check your work against this list before step 4 unlocks.

01The beginner’s gap

A beginner has an idea. Where does it go?

Opening Cursor or Claude with a messy brainstorm usually ends the same way. The difference isn’t the agent. It’s the size of what you ask it to do.

The blank prompt approach compared with the YourDev method
The blank prompt trapThe YourDev method
What you ask for“Build me a full app.”One slice: a typed habit model and a single row on screen. Nothing else yet.
What the agent returns800 lines of unverified code across 14 new files, with missing dependencies.Two or three files you can read in one sitting, scoped to about 90 minutes.
How you check itYou hope it runs, then get stuck on line 12.A written definition of done, tested on localhost and reviewed by your mentor.
OutcomeOverwhelm, broken builds, abandoned ideas.Working software, step-by-step confidence.

Never ask an agent to build an entire app at once. Build one small verifiable slice, test it on localhost, commit it, and only then move to the next.

The golden rule for agent pair programming

02How it works

From raw concept to working software.

  1. Paste your raw idea

    Drop your messy brainstorm into the console. No formatting or architecture buzzwords needed. Write like you think: stream of consciousness, bullets, or run-on sentences.

    in
    A paragraph, in your own words
    out
    Three or four intake questions

  2. Get an execution blueprint

    The coach analyses your intent and produces a phased roadmap, immediate next actions, a tailored tech stack, the foundations to learn first, and your first agent prompt.

    in
    Your idea and your answers
    out
    A blueprint with four milestones

  3. Copy. Paste. Build.

    Copy clean, agent-ready Markdown with explicit instructions into Cursor, Claude, or Copilot and begin Phase 1. Submit your work at each milestone for review.

    in
    One milestone at a time
    out
    Verified, working code

03Live console

Break down your idea. Right here.

Describe what you want to build. Answer a few intake questions if you like, and get a blueprint you can start on today.

yourdev / consoleBuild it · Understand it · Verify it
Or start from a sample:

04The output specification

Six parts. One roadmap you can actually follow.

Every generated blueprint is structured so you can build milestone by milestone with continuous verification, avoiding hallucination and scope drift.

  1. Visual execution tree

    Four sequential milestones from data contracts to polish. Each one lists the exact files to create, verified docs, and an agent prompt.

  2. Per-step mentor review

    Submit your code or test logs at each milestone for an immediate critique, approval checks, and guidance on what to fix.

  3. Failure modes and traps

    Guards against the beginner traps specific to your project: manifest permissions, hydration mismatches, premature auth.

  4. Calibrated tech stack

    A deliberately small set of frameworks and tools, each with a plain-English reason and the trade-off you are accepting.

  5. Single-step and master prompts

    Copy a milestone-specific prompt or the full blueprint prompt directly into Cursor, Claude, or Copilot.

  6. Progress that stays put

    Your session, choices, and reviews are saved in this browser, so a reload never costs you your place.

05Your mentor

Stuck between steps? Ask Devi.

Devi, the YourDev mentor, holding a tablet showing code

A patient pair programmer who has read your blueprint.

Devi sits beside every milestone. Ask why a step comes first, paste an error you don’t understand, or have your work checked before you continue.

  • Knows your project. Answers with your stack, your active milestone, and the files it asks you to create.
  • Reviews before you move on. Checks submitted code and logs against the step’s definition of done.
  • Keeps working offline. Falls back to built-in guidance when the AI service is unavailable.
  • Never runs anything. Replies are inert Markdown. You stay in control of your code.