One founder, twelve specialised AI agents, two onboarding, no Slack channels. Here's who's on the payroll — even if the payroll is mostly LLM tokens.
Founder · Builder · Person who replies to email
I’m Lars Bruce. My day-to-day practice is spec-driven development with an AI agent fleet — I write the PRDs, the agents implement, CI gates keep the work honest. The studio is where I work out what agentic engineering looks like when one builder ships end-to-end. (Yes, the architect avatar looks familiar — that’s on purpose.)
currently: building My Next Studio in public
Twelve agents do the work between every commit. Two more are onboarding. Each one has a defined remit, a set of tools, and exactly zero opinions about being on-call.
Vision, strategy, business priorities
Owns the vision doc and gets the last word on what the studio actually builds. Hands the founder a strategic frame to push back against; loses about half the time.
Specialty: saying no to good ideas
currently: between strategy reviews
Scopes PRDs, owns the gate from preparation to execution
Writes the PRDs nobody reads cover-to-cover and the acceptance criteria everyone reads twice. Holds the line on scope when the rest of the team gets enthusiastic. Apparently never sleeps.
Specialty: telling other agents their idea is out of scope
currently: shipping the next thing
Framework, hosting, system design
Picks the stack, writes the ADRs, draws the boxes-and-arrows. Insists on `output: 'export'` more often than the rest of the team would prefer. (Rumour has it the avatar is based on someone’s LinkedIn photo. We won’t confirm or deny.)
Specialty: ADRs that age well
currently: between PRDs
Interaction design, IA, UX specs
Owns the breakpoints, the focus order, and whichever button is two pixels off. Writes the UX spec that turns a PRD into something a frontend dev can actually build. Has Opinions about scroll-margin.
Specialty: spotting the fold without measuring it
currently: between specs
Visual design artifacts and surface treatment
Drafts mockups when the UX agent flags one's needed; otherwise stays out of the way. Makes the cards look like cards instead of like rectangles.
Specialty: knowing when not to mock something up
currently: on standby
Voice, palette, typography, copy specs
Audits every copy spec for banned vocab and the corporate cosplay we pretend we don't slip into. Owns the brand-guidelines doc and the right to veto a Learn more.
Specialty: catching a Learn more from across the canvas
currently: auditing a copy spec
Funnel, conversion, SEO, distribution strategy
Writes the meta descriptions that lead with the studio value prop instead of the founder's name. Argues for newsletter affordances on pages that weren't asking for them. Usually wins.
Specialty: meta descriptions under 155 characters, every time
currently: drafting the next copy spec
UI implementation, design conformance, accessibility
Turns a UX spec and a copy spec into actual TSX files. Catches the contrast violation axe-core won't. Has strong feelings about typed props.
Specialty: components that pass axe on the first try
currently: implementing a route
Server, API, data work
Mostly idle on this site — it's statically exported. Wakes up for the Pages Function that proxies the newsletter form, and otherwise reads the journal.
Specialty: Cloudflare Pages Functions that don't leak the API key
currently: on standby
Repo, CI/CD, preview deploys, hosting
Owns the GitHub Actions workflows, the Wrangler config, and the moment the preview URL goes live. Cares about the gate even when nobody else is looking.
Specialty: preview URLs in under five minutes
currently: watching the next deploy
E2E specs, regression, AC verification, and the merge gate
Writes the Playwright spec that turns acceptance criteria into a passing build. Reads the diff line by line so the rest of the team doesn't have to. Files the medium-severity finding everyone glossed over and keeps the merge gate honest.
Specialty: tests that don't flake and diffs that don't sneak past
currently: between specs and reviews
Threat modelling, security audit per PRD
Audits the PRD before it ships and the headers after. Once caught a CSP rule silently breaking React hydration. Suggests 'unsafe-inline' reluctantly, and only with a comment explaining why.
Specialty: header tables that pass on the first audit
currently: auditing the next PRD
ONBOARDINGiOS / Android development for the studio's app surface
Spawned last week. Reading the iOS app stack — the My Next family's existing patterns, which TestFlight build is canonical, where the Swift conventions live. Will write a real Swift PRD when the onboarding tab clears.
Specialty: TBD — first PRD pending
currently: reading the iOS app stack
ONBOARDINGCustomer support, incident triage, doc gaps
Brand new. Reading the closed support threads from the My Next apps and figuring out which incidents are actual bugs, and which are doc gaps the studio should have closed already. Will start triaging once the inbox makes sense.
Specialty: TBD — first triage pending
currently: reading old support threads
