How I build
The stack, the skill library, and the repo discipline behind the work
Why this page exists
The work shipped here is built with the same AI workflows that would show up in a customer engagement. This page is the honest tour: what runs the site, what runs the skills behind it, and what the repo discipline looks like so the IP compounds instead of decaying.
The stack
Next.js 16, React 19, Tailwind 4, Vercel hosting, Resend for transactional mail. Claude Code as the primary build agent. GitHub Copilot in the loop for inline drafting. Anthropic Console as the frontier toolchain item on the horizon. Power BI and Tableau in the analyst stack—used as an AI-augmented analyst, not a bench-deep specialist.
The skill library
10+ shipped skills that compound across engagements rather than evaporating after one. The resume-tailoring skill is one public example—the same skill that retargeted this site for the role on the table right now. The rest are proprietary methodology, but they share a common shape: constraints up front, evaluation built in, reusable structure over one-off output.
The repo discipline
Constraints-first repo architecture. Four canonical constraint files (brand, workflow, architecture, content) sit upstream of every page-level decision, so the AI agent doing the work has the same context the human does. Backlog entries live in spec format (Trigger / Work / Why / Tradeoffs / Run when / How) so future sessions can pick them up cold.
Three worked examples
When this section is fleshed out, three concrete walkthroughs will land: a skill that retargeted this site for a specific role, a constraints sync that kept the brand coherent across a repo split, and an end-to-end capture-synthesize-ship chain that moved an observation from voice memo to published artifact. Humans stay in the loop for the judgment calls; agents handle the surface area.
- Resume-tailoring skill: how the skill behind this site's current framing actually works.
- Constraints-first repo split: keeping brand and workflow coherent when the codebase grows.
- Capture → synthesize → ship: Fathom → Claude → Copilot, with humans in the loop.
Built with this approach
The artifacts on the Work page are produced through the same stack, skill library, and repo discipline described here.
See the work