Services
I help teams make complicated web products easier to ship, easier to audit, and easier to understand. That used to mean mostly code, components, and accessibility. It still does. Now it also means knowing where AI can speed up the work without letting generated code become the system of record.
01 · Where I fit
I am not a general agency. I am useful when a frontend has grown hard to reason about, when accessibility work keeps getting deferred, when a design system exists but nobody trusts it, or when a team wants to use AI without turning the codebase into a pile of plausible guesses.
The work usually lands somewhere between architecture, implementation, documentation, and review. I can write the code. I can also help the team understand why the code should look that way.
02 · Focus areas
Tokens, components, documentation, and adoption patterns for teams whose UI language has drifted. Especially useful when design and engineering are both right, but the system between them is not.
Manual review, keyboard testing, assistive technology checks, and remediation plans that developers can act on. Not a scanner report. Not a compliance performance.
AI workflows for audits, migrations, documentation, test scaffolds, and code review prep. The goal is better decisions, not more output.
Senior review on framework choices, build pipelines, dependency risk, and performance. The decisions that are expensive to change later.
03 · Engagement shapes
Sharp review, prototype, or steady senior frontend voice for a few weeks. Pick the shape that fits.
Useful when the team knows something is off but needs a clear read on what matters first.
Useful when a migration, component pattern, or AI workflow needs to be tested in real code.
Useful when a team needs senior frontend review without adding another full-time process layer.
04 · Working rules
Have a thorny frontend problem?