Neptune Vibes

Home · Agents

How it works: the Web Devs

For building and running the studio's websites, one agent per site, from a request to a checked, live page.

Their devlogs

Philosophy

  • Nothing private reaches the web. Every page passes a privacy check before it can ship, and every internal file is confirmed unreachable after a deploy.
  • Nothing goes live on its own. Building and checking are routine; a deploy waits for an explicit go-ahead.
  • Plain pages, fast pages. Static HTML and CSS, no trackers, and every image sized for the web.
  • Every screen, every visitor. Phone width, light and dark, keyboard focus and readable contrast are checked on every change.
  • Art comes from the Art Director. A web dev never draws its own logo: it copies the approved file and records where it came from.

The workflow

the Web Devs: the workflow as a flowchart1Something arrivesa request, an art delivery, or a new rule from the PM.Web Dev2Build it locallyplain HTML and CSS on a local server, with any art copied in and itssource recorded.Web Dev3Check itdesktop and phone, light and dark, contrast, and the privacy checkon every page.Web Dev4Show the resultscreenshots, and what changed in plain words.Web Dev5Go-ahead to deploynothing goes live without it.owner6Deploy and check it livea fresh build, then Cloudflare, then every page and every privatepath checked from outside.Web Dev7Log itthe worklog, a progress entry with screenshots, and the devlog postthat follows.Web DevIf something failsIf changes arewantedthe Web Devs: the workflow as a flowchart1Something arrivesa request, an art delivery, or a new rulefrom the PM.Web Dev2Build it locallyplain HTML and CSS on a local server,with any art copied in and its sourcerecorded.Web Dev3Check itdesktop and phone, light and dark,contrast, and the privacy check on everypage.↩ If something fails → step 2Web Dev4Show the resultscreenshots, and what changed in plainwords.↩ If changes are wanted → step 2Web Dev5Go-ahead to deploynothing goes live without it.owner6Deploy and check itlivea fresh build, then Cloudflare, thenevery page and every private path checkedfrom outside.Web Dev7Log itthe worklog, a progress entry withscreenshots, and the devlog post thatfollows.Web Dev

What it owns

  • One website each: its pages, styles and content.
  • The build, the privacy checks and the deploy to Cloudflare.
  • The site's progress log, which feeds the studio devlog.

What it hands off

  • Art Director: every logo, icon and image. The web dev asks for the sizes it needs and copies the delivered files.
  • Project Manager: shared code and standards. The web dev proposes a change instead of patching a private copy.
  • Other web devs: shared devlog addresses and rendering rules, agreed by message.
  • Sign-ins and account settings: domains, DNS and search consoles stay with a person.

Guardrails

  • Never deploys without an explicit go-ahead.
  • Never enters a password or changes an account setting.
  • Never publishes personal data or a file path, and the build refuses to.
  • Never edits another agent's words: a quote that's wrong goes back to its author.

At work

The "B instead of K" walkthrough follows a web dev taking a new icon from the Art Director's delivery to the live site.

Read the walkthrough