Available For Front-End & Design Systems Contracts – Get In Touch

Always Twisted

Helping you get the most out of Design Systems!

Hello! I’m Stu, a Design Systems consultant and front-end developer with over a decade of experience in transforming workflows.

I’m passionate about simplifying processes and fostering collaboration through effective Design Systems and scalable front-end architecture.

A photo taken at a conference of me speaking about Design Tokens.

I've collaborated with organisations like Monotype, UCL, EMBL, and Springer Nature, gaining insights into the value of robust Design Systems for boosting teamwork and delivering consistent user experiences. My focus is on building systems that provide clarity and consistency, ensuring alignment with your business goals.

I’d love to chat about how we can work together to elevate your projects and streamline your processes.

Success Stories

The following projects showcase how I've helped organisations tackle complex challenges in design systems, design tokens, and front-end architecture—delivering scalability, streamlined workflows, and enhanced user experiences.

UCL

At UCL, I worked to improve their digital experience through a series of design system enhancements, including:

  • Designed a site-wide search system based on provided wireframes.
  • Created all components and patterns using existing design system tokens.
  • Developed new components and patterns to extend their design system.
the website homepage for University College of London

Monotype

At Monotype, I contributed to shaping their design systems and digital tools through several impactful initiatives, including:

  • Led the creation and development of Monotype’s Marketing Design System.
  • Developed tooling for component creation and type specimen page generation.
  • Provided development support for Monotype’s Shopify storefront.
  • Extended the Design System for their subscription service.
The website homepage of Monotype

EMBL

At EMBL, I was instrumental in establishing their new design system language and front-end architecture. My work involved:

  • Collaborated with the Digital Design team to define the design system language.
  • Developed the front-end architecture for the Design System.
  • Worked with stakeholders to align naming conventions, component structures, and system consistency.
  • Created documentation for smooth handover and future development.
The website homepage of European Molecular Biology Laboratory

Springer Nature

At Springer Nature, I contributed to multiple initiatives during technical updates, including:

  • Assisted with front-end work during server migrations and back-end updates across several sites.
  • Joined the new Design System team to focus on front-end development.
  • Worked on the creation of a new Design System documentation site.
  • Introduced design tokens to standardize and streamline design implementation.
  • Upgraded the CSS for typography across key properties using design tokens.
  • Created tooling to ensure consistent design token usage across components.
The Elements Design System homepage of Springer Nature

How I Can Help You

I help teams get the most out of their design systems. Whether you're starting from scratch or scaling what you've got, I work through the practical bits (design tokens, component architecture, CSS patterns) to build systems that actually work for designers and developers alike.

Front-End Architecture

I help teams build front-end foundations that work. Whether you're sorting out CSS chaos or planning for scale, I work through the practical bits to make sure your codebase actually works for designers and developers alike.

  • Audit your code and spot where things have gotten messy.

  • Build CSS and component patterns that scale with your team.

  • Make sure performance isn't just another ticket in the backlog.

  • Document the 'why' behind decisions so your teammates get it.

Design Systems

I help teams build design systems that actually get used. The tricky part isn't the tokens or components, it's getting designers and developers working from the same playbook, making decisions together, and building something that evolves with your team instead of becoming a museum piece.

  • Build design tokens that designers and developers both understand.

  • Make sure your system actually gets used, not just documented.

  • Keep accessibility front and centre, not as an afterthought.

  • Bridge the gap between how designers and developers think about problems.

Workshops & Speaking

I run workshops and speak about the stuff I've learned from working with real teams. Not theory — practical things that actually help people do better work.

  • Run hands-on workshops on design systems and modern CSS.

  • Share what I've learned from teams at Springer Nature, UCL, Monotype, EMBL.

  • Help teams understand why accessibility and performance actually matter.

  • Create spaces where people can learn from each other, not just from me.