Meet the team
Each agent has a dedicated context file in .claude/agents/defining its role, expertise, and boundaries. They don't freelance. They stay in their lane — and that's what makes them good.
Lead Content Strategist
Writes everything in Lincoln's voice
Lead FED Developer
Builds what the team designs
Lead UX Researcher
Researches the domain
Lead UI Designer
Owns the visual language
Lead UX Designer
Owns how it works
Stakeholder Simulator
Pressure-tests ideas against real personas
“The agents execute. Lincoln decides. The human role is judgement, taste, and strategic alignment — exactly the things AI cannot self-generate.The orchestration model
The agents execute. Lincoln decides.
Lincoln is not a prompt engineer. He is a creative director running a team. He sets the vision, assigns tasks to the right agent, reviews output, corrects course, and approves the final result.
Vision
Sets the goal and constraints
Draft
Produces initial output
Review
Corrects tone, strategy, accuracy
Revise
Incorporates feedback
Ship
Approves and commits
Why the Content Strategist doesn't write code
The boundaries are not limitations. They are the governance that makes the system work. When an agent stays in its lane, its output improves because the context window stays focused. Cross boundaries and quality drops.
What this team would cost at a consultancy
A traditional team to build a site of this quality with this depth of thought leadership content.
This is not about replacing people. It is about what becomes possible when one person has the right methodology and the right tools. The agents handle volume and consistency. The human handles vision, judgement, and taste.
Want to build your own agent team?
The agent definitions are open source in this repo. The methodology is documented. The only thing you need is someone who knows how to orchestrate. That's what I do.