AI Engine

Agent Teams

One team per build type, each with its charter and the specialists it actually has.

The teams

9 teams, 39 specialists. Each line names the agent, whether it is plain code or an AI call, the mode it starts in when that is not Lite, and what it does.

Web · 5

Web team

Turns a description into a validated Site Spec and the static site built from it.

  • web.architectCodeChooses the industry playbook, section order and page shape.
  • web.page-plannerCodeDecides whether the site is one page or many, and what each page holds.
  • web.auditorCodeScores structure, conversion, copy, SEO, a11y and mobile, and returns the fix for each issue.
  • web.copywriterAI callfrom EconomyRewrites weak marketing language without touching structure.
  • web.visual-reviewerBrowserfrom PowerLooks at the rendered page and reports what a person would notice.

Game · 13

Game team

Plans a playable 3D game, then proves it can actually be finished before publishing it.

  • game.architectCodeDetects the genre and plans the world, goal and win condition.
  • game.auditorCodeScores the spec and returns repair instructions for what it finds.
  • game.legibilityCodeChecks lit surfaces read against their background, and corrects them.
  • game.performanceCodeBudgets draw calls and triangles so the frame rate survives.
  • game2d.brieferCodeReads the request and settles the genre, subject and win condition the rest of the 2D build works to.
  • game2d.architectCodeTurns the brief into the scene, entity and loop structure the generator emits.
  • game2d.level-designerCodeLays out the tilemap, spawn points and difficulty curve for the genre.
  • game2d.systemsCodeSpecifies scoring, input handling and state transitions, so the artifact is a game rather than a scene.
  • game2d.physicsCodeSettles gravity, collision shapes and hitboxes — the 2D physics the genre needs to be playable.
  • game2d.runtimeBrowserLoads the emitted document in a real browser and reports whether it starts, draws and responds to input.
  • game2d.playtesterBrowserPlays the game — starts it, scores in it, waits for a run to end, then presses Restart — because everything the runtime probe checks is also true of a screensaver.
  • game2d.auditorCodeReads the emitted document for missing controls, absent scoring, blocked fetches and unreachable win states.
  • game.playtesterCodePlays it through to confirm the goal is reachable.

Mobile app · 2

Mobile app team

Plans an app's screens and navigation, then checks every tap leads somewhere.

  • mobile.architectCodeDetects the app type and plans its screens and navigation.
  • mobile.auditorCodeScores the spec and returns repair instructions, including dead-end screens.

Sheets · 4

Sheets team

Plans a workbook's sheets and formulas, then evaluates them to prove the numbers compute.

  • sheets.architectCodePlans the sheets, columns and the formulas that tie them together.
  • sheets.brieferCodeTurns the plan into the brief the model is given, so the build is asked for the sheets that were planned rather than a generic workbook.
  • sheets.testerBrowserEvaluates the workbook and reports formulas that error or disagree.
  • sheets.repairCodeWrites the repair brief from the checks that actually failed, so the second pass fixes those rather than guessing.

Data viz · 3

Data viz team

Reads a dataset, plans the dashboard it supports, and verifies every chart against the data.

  • dataviz.architectCodePlans which charts the dataset can honestly support, and their order.
  • dataviz.analystCodeFinds the movements in the data worth stating in the copy.
  • dataviz.verifierCodeChecks every plotted value against the source, so no chart invents a number.

Design · 3

Design team

Produces poster and social artefacts, and checks each one reads at a glance on its own canvas.

  • design.architectCodeDecides what is being designed and at what distance it is read, which fixes the aspect, the copy budget and the hierarchy.
  • design.auditorCodeChecks headline and bullet budgets against the poster's aspect, and that a layout carries what it promises.
  • design.repairCodeWrites the repair brief from the poster findings, so the second pass fixes what the audit caught rather than guessing.

Slides · 3

Slides team

Produces decks, and checks each slide can be read from the back of a room and carries what its layout needs.

  • slides.architectCodeReads the request to decide which kind of deck this is, then fixes its length, its slide order and its bullet budget before anything is written.
  • slides.auditorCodeChecks layout/payload agreement, bullet density, deck shape and layout variety.
  • slides.repairCodeWrites the repair brief from the deck findings — the slides that ran long or lost their point — so the second pass targets those.

Animation · 3

Animation team

Produces hand-coded motion pieces, and proves each one can actually run in the sandbox before it ships.

  • animation.architectCodeChooses the technique, the loop shape and the timing for the piece — a logo reveal resolves and holds, an ambient field must never appear to start.
  • animation.auditorCodeReads the emitted document for blocked external fetches, opaque-origin storage, absent motion and missing controls.
  • animation.repairCodeWrites the repair brief from the animation findings, so the second pass fixes the timing and motion the audit caught.

Documents · 3

Documents team

Produces long-form documents, and checks their structure, tables and readability.

  • document.architectCodeDecides which kind of document this is, and which sections it cannot ship without — and which would be wrong for it.
  • document.auditorCodeChecks table rows against their column count, heading structure, contents pages and paragraph length.
  • document.repairCodeWrites the repair brief from the document findings, so the second pass addresses the sections the audit flagged.