How this was actually built
Real conversations, real failures, real corrections. The Branch + Burn reality behind the polished output.
Explore →The InfrastructureCLAUDE.md, annotated
The single file that governs six agents. This is what machine-readable culture looks like.
Explore →The FormatAgent-readable components
What a component looks like when the primary reader is an AI agent — and why JSON beats Markdown.
Explore →The PluginFigJam to Narrative
A working Figma plugin that extracts ideation boards into structured markdown. The I→N pipeline as a shipped artefact.
Explore →The DeliveryWhat I ship with Claude
Six workflows — each a full I<N>C cycle. From app audits to plugin development, this is what one person with the right methodology delivers.
Explore →This site is the case study.
Most portfolios describe work. This one demonstrates it. The same methodology I use with clients — I<N>C, agentic design systems, machine-readable context — is the methodology that built every page you're reading.
One person. Six agents. A single CLAUDE.md file encoding brand, voice, architecture, and design system rules. The agents don't freelance. They operate within a governed system — just like engineers on a well-run product team.
The system pages make that invisible infrastructure visible. Not as a technical exercise — as proof that the methodology works at the smallest possible scale, with the highest possible transparency.
“My portfolio demonstrates the system that my portfolio describes.Recursive proof of the I<N>C framework