Hi, I'm Simon. I build scalable Design Systems and React platforms that make teams ship faster & more consistently.

Extended and enhanced workflow with Claude Code.
Integrating AI into real development workflows — not as a gimmick, but with the same strict precision I apply to design systems. I work extensively with Claude Code to accelerate development, from scaffolding components to refactoring entire modules. Beyond generation, I use AI as a critical reviewer: auditing code for accessibility gaps, inconsistent naming conventions, code conventions, design token usage, and optimization opportunities. The value isn't in replacing thinking — it's in getting honest, tireless feedback that improves the output.

On my own design system, Ashlar, Claude Code runs nightly routines with the skills and conventions I wrote, and I review every change before it is merged.

Scalable design systems are built to enhance team collaboration, efficiency, and consistency.
By focusing on essential elements such as design tokens, typography, spacing, color, and theming, alongside robust component architecture and clear documentation, these systems effectively eliminate UI drift. I work by governance, adoption, and versioned releases—built to scale across multiple teams.

High-quality user interfaces are built on modern React platforms, such as Next.js.
Most often delivered through a Design System. Design patterns address real product complexities such as routing, performance, accessibility, and component-driven development, resulting in a flexible frontend foundation that is easy to extend and maintain across teams.

The use of TypeScript ensures a reliable, scalable shared codebase.
Through strict typing and predictable component contracts, this approach significantly improves developer experience, enabling faster feature delivery with fewer issues—especially in collaborative environments where multiple teams work in a shared codebase.

Predictable state is the foundation of a stable UI and data flow.
Whether the right answer is local component state, a lightweight Zustand store, or Redux Toolkit in a large codebase, the choice follows the problem — not the trend. Clear boundaries between client state, server state, and URL state keep applications maintainable as they scale. It differs per project and use case; the solution is always tailored to the problem.

Testing is part of the workflow, so teams can move fast without introducing UI drift.
Unit tests cover component logic, variants, and shared utilities to keep behavior predictable. Integration tests validate real user flows. Visual testing catches layout shifts, spacing/typography changes, theming issues, and responsive breakpoints. Regression testing protects what’s already in production—especially during refactors and migrations.

Bridging the gap between design and engineering
I work closely with design teams to ensure that design systems and React platforms are built to meet real product needs. This leads to practical systems that enhance usability. Implementing shared naming conventions and comprehensive documentation fosters alignment with team workflows. Removing that unintentional “design drift” and focusing on a Design System that inspires trust among designers, encourages adoption among developers, and adapts seamlessly as product teams evolve.