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

Always Twisted

I help teams with design systems, front-end architecture, and building and maintaining front-end codebases.

Design Systems

Design systems are how teams ship faster without duplicating work. I help build systems that live in product code, not just Figma or documentation. We define design tokens, component libraries, governance, and handoff processes that actually work.

  • Strategy and audit of existing design tokens and component architecture.

  • Create design token workflows for colour, typography, spacing, and theming.

  • Build and document component libraries with accessibility standards.

  • Set up contribution and governance so teams maintain the system over time.

Front-End Architecture

Codebases drift. CSS becomes inconsistent, patterns fracture, performance slips. I help teams untangle this by defining clear architecture, naming conventions, and folder structure. Result: faster shipping, fewer regressions, teams moving independently.

  • Audit CSS architecture, component patterns, and performance.

  • Define scalable CSS conventions and folder structure.

  • Build accessible, maintainable components teams can reuse.

  • Document decisions so teams understand the 'why' and can evolve the system.

Front-End Services

I build production front-ends for websites and products—HTML, CSS, JavaScript, responsive templates. I also do front-end archaeology: auditing legacy codebases, identifying load-bearing code versus cruft, and refactoring safely without breaking user experience.

  • Build accessible, production-ready components and page templates.

  • Implement responsive layouts and patterns that work across devices.

  • Audit legacy code to understand technical debt and browser hacks.

  • Refactor and modernise with clear plans that reduce risk.

Workshops & Speaking

I run workshops and speak on design systems, design tokens, component architecture, and modern CSS—based on real work with teams at Springer Nature, UCL, Monotype, and EMBL. Sessions are practical and tailored so people leave with approaches they can use immediately.

  • Deliver workshops on design tokens, design systems, and component architecture.

  • Speak on front-end architecture, accessibility, and performance.

  • Share lessons from real team contexts and help teams solve their challenges.

  • Provide follow-up coaching so momentum carries past the session.

If any of these resonate with what you're working on, let's talk about how I can help.