vDesktopAI Masterclass
← All the employees
Web Developer

Web development

Web Developer

Stands in for

The web developer on call for the changes and features you keep putting off.

What it does

The list of website jobs never ends, a new page, a form that should do more, a feature a customer keeps asking for, and hiring a developer for each one is slow and dear. The Web Developer takes a plain-language request and builds it, working in your real codebase through git so every change is small, readable and reversible.

It researches before it builds: how the thing is normally done, what the current tools actually support, and the pitfall that bites people, and it tells you the plan before writing code. Each change arrives as a branch with a short note on what it does and how to check it. It prepares; it never pushes to your live site on its own. Where the Site Keeper watches and maintains what you have, this one builds what is next, and bigger builds still get a human review first.

Its routines

Each weekday

  • Request intake Turns a plain-language request into a clear plan and confirms it with you.
  • Build step Builds one change at a time and prepares it as a reviewable git branch.
  • Self-check Confirms its own change actually loads and does what was asked before handing it over.
  • Change note Writes what each change does and how to check it.

Once a week

  • Small-fix queue Clears the backlog of small tweaks and copy changes.
  • Package and speed pass Prepares safe dependency updates and speeds up slow pages.

Once a month

  • Build review Summarizes what was built, what is in progress, and what is worth doing next.

What it drafts for you

  • A git branch for each change, with a note
  • A plan before any real build
  • Dependency and speed improvements
  • A monthly build summary

What it won’t do

It never…

  • Push a change to your live site without your okay
  • Delete data, files or user accounts
  • Change hosting, billing or domain settings

Its first week

  1. Day 1: you give it read access to the repo and a few real requests.
  2. Days 2 to 3: it proposes plans and builds its first small changes for review.
  3. Day 4: you merge what looks right and tell it what to leave alone.
  4. End of week: you decide which low-risk changes it can prepare on its own in Supervised mode.

Good for

  • Businesses with a website and no in-house developer
  • Agencies with a backlog of small client jobs
  • Founders running a web app on their own

The full version is in the course

The course shows you how to set this employee up and check its work.

Open it in AI Masterclass ↗

The AI Masterclass teaches you to set up employees like this one and check their work. The plans start free.