Skip to content

Portfolio

Monnie Hammill

Nike Design Systems · design engineer

Nike Design Systems

Five years of design systems, documentation, accessibility, motion, and design-to-code work across Nike’s Enterprise Design System (EDS) and Podium—React + TypeScript surfaces teams used day to day.

Most of this lives behind VPN/Okta, so there are no live links here. I lead with what I contributed, how I think about systems work, and why it matters; after that, representative full-page captures from internal docs—a small sample of pages, not the whole catalog.

  • Senior Design System Engineer
  • React + TypeScript
  • Accessibility
  • Design Tokens
  • Motion Systems
  • Documentation UX
  • Figma-to-Code

My contribution

Themes from my time with design, engineering, and program partners.

Built and documented reusable React + TypeScript primitives and interaction patterns.

Partnered with designers to reduce drift between Figma specs and production implementation.

Contributed to documentation systems that helped teams self-serve component usage, accessibility guidance, and design token decisions.

Supported EDS → Podium adoption through migration resources, office hours, and engineering support.

Architected motion token and utility-class documentation with prefers-reduced-motion support.

Helped build MCP-backed design system tooling exposing tokens, component APIs, and system context for engineers and AI-assisted workflows.

How I approach design systems

Make the right path easy

Defaults, scaffolding, and docs should steer teams toward consistent patterns without blocking reasonable exceptions.

Treat documentation as product

Clear information architecture, predictable examples, and maintainable content reduce slack pings and rework.

Build accessible defaults

Semantics, keyboard flows, focus, and motion preferences belong in the system—not as one-off fixes downstream.

Close the gap between design intent and production UI

Shared language around tokens, components, and motion keeps design tools and shipped interfaces aligned.

Why it matters

The strongest systems aren’t only component libraries—they’re infrastructure: clear APIs, accessible defaults, consistent visuals, documentation teams trust, and adoption support so product teams ship better interfaces faster.

Contact

View resume Connect on LinkedIn Email me

Image preview