Tech stack

How I plug into your team

Most stack pages prove someone owns a Figma licence. This one shows where I join, what I hand over, and which of your existing tools I'm already working in.

How the work moves

Five stages, one continuous handoff

I join wherever your product already is. Point at a stage to light up the tools I use there.

  1. 01

    Discover

    Understand the users, the constraints, and what actually needs building.

    • User Research
    • Information Architecture

    12 tools

  2. 02

    Design

    Turn the problem into interfaces, patterns, and a system that scales.

    • Design Systems
    • Design Tokens

    15 tools

  3. 03

    Prototype

    Make it real enough to test before anyone commits engineering time.

    • Prototyping
    • Motion Design

    8 tools

  4. 04

    Build

    Ship production front-end code, not a handoff document.

    • Component Libraries
    • Responsive Design

    29 tools

  5. 05

    Ship

    Review, QA, accessibility, and a deploy your team can own after I leave.

    • Accessibility (WCAG)

    12 tools

Runs through every stage
  • AI Workflows
  • Prompt Engineering

The inventory

Tools I already work in

Whatever your team runs on, it's probably here. The named tools open a note on how I use them.

Design

  • Design, Prototype. Design systems, specs, and the file your engineers actually open.
  • Prototype. High-fidelity interactive prototypes and live marketing sites.
  • FigJam
  • Illustrator
  • Photoshop

AI

  • Discover, Design, Build. Research synthesis, product thinking, and production code review.
  • Prototype, Build. AI-assisted coding for rapid feature development.
  • ChatGPT
  • Gemini
  • GitHub Copilot
  • MCP Servers
  • Perplexity

Engineering

  • Prototype, Build. The component layer most product teams are already standardised on.
  • Build, Ship. App-router production builds, server components, and routing.
  • Build. Typed components that survive contact with an engineering team.
  • Astro
  • JavaScript
  • HTML
  • CSS
  • Tailwind CSS
  • shadcn/ui
  • Node.js

Mobile

  • Prototype, Build. Native iOS interfaces built the way Apple platform teams build them.
  • Swift
  • Xcode
  • iOS
  • Android

Infrastructure

  • Build, Ship. Branches, PRs, and reviews in the repo your team already uses.
  • Ship. Preview deploys on every PR, so stakeholders review the real thing.
  • Git
  • Netlify
  • npm
  • pnpm
  • AWS
  • Google Cloud

Data

  • PostgreSQL
  • Supabase
  • Firebase

Collaboration

  • Discover, Design, Build, Ship. Where I stay reachable — async updates, not status meetings.
  • Notion
  • Zoom
  • Google Meet
  • Microsoft Teams
  • Confluence
  • Google Docs

Project management

  • Design, Build, Ship. Where design work lands as tickets your team already tracks.
  • Jira
  • Trello
  • Asana