Atlas — Design System
Figma · Tokens · 94 components
Designing interfaces with the rigor of engineering.
Shipping them with the taste of a designer.
I'm James — ten years building product surfaces for early-stage teams from Austin, TX. Consulting on the hard parts. Selling the parts you can reuse.
Signature ⟶ The Architecture Blueprint
Hover the component. Watch it come apart.
Every interface I ship has four legible layers underneath. Move your cursor to see them.
<Card>
<Card.Header title="Monthly revenue" badge="+12.4%" />
<Card.Metric value="$48,210" trend="up" />
<Card.Sparkline data={series} stroke="--fg" />
</Card>--radius: 12px--space-4: 16px--fg: #ffffff--surface: #1a1a1a
Monthly revenue+12.4%
$48,210
idle — hover to inspect
04 layers
Marketplace ⟶ 02
Latest resources
Files I built for client work, then polished for resale. Lifetime updates.
$148
Slate Mockup Pack
Figma · 12 scenes
What I do ⟶ 03
Three practices, one engineering mindset
01 — Product strategy
Decide what to build before pixels move.
Two-week sprints with founders to pressure-test the product, cut scope by roughly 40%, and ship the surface that actually moves the metric. No deck theater.
Discovery sprintsPricing & packagingRoadmap pruning
02 — UI architecture
Component graphs your engineers can actually read.
Typed primitives, predictable state, zero one-off cards.
03 — Design systems
Tokens, primitives, and the docs that keep them honest.
Built in Figma, shipped to code in the same week.
Framer templates ⟶ 04
Sites you can publish this week
Hand-built in Framer. CMS-ready. Tested at every breakpoint.
Meridian
Portfolio · Framer
Strata
SaaS · Framer
Counter
Agency · Framer
Worked with ⟶ 05
Linear'21–'25
Vercel'21–'25
Ramp'21–'25
Notion'21–'25
Arc'21–'25
Mercury'21–'25
Pitch'21–'25
Cash App'21–'25
Around 94% of engagements end with a system the in-house team keeps building on without me. That's the bar.