AI Workflow

How a change gets made

1. TriageA read-only agent classifies the task, names the files it touches, checks them against the path rules and picks the agent that should do the work.
2. GateA hook blocks every edit until triage has run in that session. Reading code and read-only commands pass freely.
3. Plan on recordBefore touching a file, the agent writes its plan in a decision log: the strongest alternative it rejected, the assumption the plan rests on, and what would prove it wrong.
4. Build and verifyIt implements, then runs the build and the type check and fetches the static HTML. The results go into the same log.
5. ReviewBefore a push, a hook suggests a review command that checks the whole branch. It only passes with zero high-severity findings.

Agents

• TriageRoutes every task. Never edits.
• FeaturesPages, components, styles and site content.
• DebuggingBugs and build failures, down to the root cause.
• TestsWrites and runs tests. Never touches source code.
• DependenciesPackage upgrades. Always asks me first.
• SecurityAudits for secrets, XSS and unsafe links. Never edits.

Agents for APIs, databases and CI are parked, ready to come back when a project needs them. Each one has a clear area, and an agent hands off instead of crossing into another one's area.

Rules the AI can't skip

• RestrictedSecrets, deploy and build config. The agent stops and asks me before writing.
• Review requiredThe page head and the content schema. The agent proceeds but flags the change.
• ForbiddenBuild output, generated files and the lockfile. Never written by hand.
• DestructiveAnything that can't be undone pauses for my confirmation, wherever it happens.

Why it matters for clients

• The AI follows the project's rules, not its own defaults, so the code stays consistent.
• Every decision has a written reason, so a reviewer can see why, not just what.
• It can't touch secrets, deploy config or dependencies without my explicit OK.

Built for agents to read, too

Every page on this site has a Markdown version, and an llms.txt indexes them, so assistants like Claude can read the portfolio directly.

llms.txtThis page in Markdown