Capability
Depth, against a stated benchmark
Bands rather than percentages. A self-assigned 98% asserts nothing; a defined band is a claim that can be interrogated in an interview — which is the point.
Technical depth
Architecture
- Frontend ArchitectureExpert
- NX MonorepoExpert
- Design SystemsExpert
- SSR / HydrationExpert
- Multi-tenant & Multi-locale PlatformsExpert
- Micro-frontendsAdvanced
- System DesignAdvanced
Core Frontend
- React.jsExpert
- Next.js 15Expert
- ZustandExpert
- React QueryAdvanced
- Vue.js / Nuxt.jsAdvanced
- ReduxAdvanced
- React Hook FormAdvanced
- Tailwind CSSAdvanced
- Material UIAdvanced
- StorybookAdvanced
AI & Agents
- MCP Server DesignExpert
- Agentic WorkflowsExpert
- Claude Code Skills & HooksExpert
- LLM GuardrailsAdvanced
- Prompt EngineeringAdvanced
- Anthropic SDKAdvanced
- RAG / GroundingAdvanced
- Model EvaluationWorking
Graphics & Motion
- Canvas / 2D RenderingExpert
- Three.js InteropAdvanced
- Real-time Sync (WebSockets)Advanced
- Animation & Motion SystemsAdvanced
- Parallax & Scroll ChoreographyAdvanced
- SVGAdvanced
Languages
- TypeScriptExpert
- JavaScript (ES6+)Expert
- HTML5 / CSS3 / SASSExpert
Platform & Quality
- ViteExpert
- Git / GitHubExpert
- Jest / React Testing LibraryExpert
- WCAG 2.1 AA AccessibilityExpert
- Performance OptimizationExpert
- CI/CD PipelinesAdvanced
- WebpackAdvanced
- DockerWorking
- AWSWorking
APIs & Backend
- REST API DesignExpert
- GraphQLAdvanced
- Node.jsAdvanced
- Express.jsAdvanced
- MongoDBWorking
- Firebase / SupabaseWorking
- Expert
- Production-proven at scale, with architectural responsibility
- Advanced
- Shipped features and reviewed others' work
- Working
- Used in real projects, not a primary focus
Fig. — Five things, each with the proof attached.
Text alternative: “The Part Underneath”14s
Five domains, each with a diagram that a selection bracket walks through, naming each part as it lands. A cross-section strip along the bottom gains a layer per domain and keeps that domain's headline number.
Architecture. An NX monorepo core feeding five brand shells across twelve locales; a GraphQL proxy holds the credentials server-side and React Query SSR hydrates. Design systems. Atoms, molecules and organisms assembling in three linked tiers — built from scratch, twice, cutting delivery time 20% across the team.
Performance. Three bars shrinking against their original length: −45% application load, −30% build time, +40% faster partner onboarding. Accessibility.A focus ring walking a form, and the site's own accent on white measuring 5.18:1 — WCAG 2.1 AA as a build constraint, not a cleanup pass.
The AI layer. A model, a guarded MCP server and a system, with typed calls flowing both ways: 2 MCP servers, 4 agents running unattended, 12+ custom skills. It closes on Nobody sees it. Everybody stands on it.
How the work gets led
Practices with evidence behind them, not adjectives.
- Solution Design & Architectural Planning
- Design Review
- Technical Mentoring
- Cross-team API Contract Definition
- Written Technical Documents / RFCs
- Stakeholder Communication
- Agile / Scrum
On keeping current
Technology turns over fast, but judgement compounds. I invest in the parts that transfer — how systems fail, how teams adopt change, how to tell a constraint from a preference — and pick up the frameworks as the work demands them.
The full decision records behind these are on the work page.