Quoted by complexity
CI/CD & quality-gate setup
One deterministic rule set - format, lint, types, tests, coverage, security - that runs identically in the editor, before push and in CI. Ratcheted so legacy code can adopt it on day one.
For AI agents: a documentation index is available at /llms.txt. Every page also has a Markdown version at its URL plus .md.
← What I do
~/what-i-do/dx
Developer Experience
Developers are fastest when the right thing is also the easy thing. I look for the friction that quietly eats a team’s week (slow feedback, flaky setup, manual steps) and remove it with tooling, not more documentation.
01What I can do for you
Quoted by complexity
AI-assisted development enablement
Get real leverage from coding agents without the chaos: skills, hooks and a gate the agent can’t quietly weaken, plus workflows from ticket to reviewable PR.
02How I work
Feedback in seconds, not in CI
The same checks run in the editor, before push and in CI, so problems surface while the code is still in your head, not twenty minutes later.
Seen in: Foundry →
One command to a working setup
Pinned toolchains and reproducible environments end "works on my machine". A new developer should be productive on day one.
Seen in: Foundry →
Remove steps instead of documenting them
Scaffolding, CLI tools and previews beat a wiki page listing twelve manual steps nobody reads.
Seen in: Email Template Preview →
Ask where the time goes first
Before picking tools I watch how the team actually works. The biggest win is often not the one anyone asked for.
Conventions live in the tooling
If a rule matters, a check enforces it: architecture tests, import boundaries, duplication limits. Review time goes to design, not to repeating the style guide.
Seen in: DevInsight → · Foundry →
Errors that tell you the fix
A failing check names exactly which rule broke and where, so a person or an agent can fix it without going digging.
Seen in: Leash →
A flaky check is a broken check
A test that fails at random teaches everyone to ignore red. It gets fixed or removed, never retried until green.
03What I’ve built
Foundry
A polyglot engineering gate for AI-assisted development
- GitHub Actions
- mise
- Python
- POSIX shell
Leash
Keeps a coding agent to the project rules no linter can check
- TypeScript
- Node.js
- Jev
- Claude Code hooks
Email Template Preview
Preview transactional emails with real order data, rendered like Gmail would
- PHP
- Shopware 6
- Symfony
- Vue
DevInsight
GitHub activity turned into an evidence-based portfolio
- C#
- .NET 10
- ASP.NET Core
- EF Core
doppelscan
A syntax-aware duplicate code finder that hands an agent the helper to extract
- Rust
- tree-sitter
- rayon
- MCP
04Writing
A quality gate for a codebase nobody dares touch - a one-week plan
How to add linting, tests and security scanning to a legacy repository without a cleanup sprint, a red build on day one, or a revolt.
One rule set, three placements
Why I stopped treating CI and "AI coding standards" as two separate things - and what Foundry does instead.