Each model does the job it is best at.
A coding agent handles code, a fast model handles research and review, and the strongest model is kept for planning and judgement.
How I use AI to build and maintain this portfolio. One model plans and checks, specialist helpers each do one job, and I decide what gets published.
The team
Plans the work, hands out jobs, checks every result and reports back to me.
hands jobs to
Writes the code.
Looks things up.
Checks for mistakes.
Writes the words.
Example
Adding a new case study page, from request to live site.
Works out what a new case study page needs and which files it touches.
Pulls the project notes and shows how existing case pages are built.
Receives a full written brief and writes the page code.
Runs the site checks and lists anything that is broken or unclear.
Opus fixes what was flagged and reports back. I read it before it goes live.
A coding agent handles code, a fast model handles research and review, and the strongest model is kept for planning and judgement.
Every change Codex makes is checked by a separate reviewer before it is committed, the way a second analyst would check a model.
Helpers that do not depend on each other work side by side, so a task takes the time of its slowest step rather than the sum of them all.
The rules the team follows are written down in the repository, and nothing reaches the live site without passing the build checks and my review.
What this does not claim
The models write code and drafts when asked. I choose what to build, read changes before they are published, and the ownership of each case study is stated on its own page. When this page launched in October 2026, Codex was not yet connected, so Opus built it directly with my approval.