ROLE

Design Lead

TIMELINE

2025–2026
3 months

CLIENT

Stackit

TOOLS

Figma · Rive

IMPACT

40 component sets
14 complete user flows
Rive animation system

DESIGN SYSTEM

RIVE

FIGMA

PREDICTION MARKETS PLATFORM

A design system developers could execute with confidence

A design system developers could execute with confidence

Building a complete design system for a prediction markets platform. 40 component sets, 14 user flows, and a custom Rive animation system built for speed and developer confidence.

THE CHALLENGE

A complete design system from scratch, in 3 months

A complete design system from scratch, in 3 months

Stackit needed a full design system from scratch. The platform had to handle complex prediction markets while staying intuitive for casual sports fans. Every component needed to cover real-world states, sizes, and edge cases before a single screen was assembled.

THE APPROACH

Design system as product

Design system as product

I built components first, screens second. Each component was documented with states and usage guidelines before being assembled into user flows. This gave developers complete specifications upfront instead of discovering edge cases mid-build.

The system included 40 component sets with 154 total variants. Buttons alone had 72 variants covering state, size, and context. The documentation took longer upfront but cut back-and-forth during implementation.

THE SYSTEM

Components first, screens second

Components first, screens second

3 months

Rapid delivery from concept to build

Zero design debt

Components defined before assembly

Fast execution

Clear specs enabled first-time builds

THE IMPACT

Fast execution, clear handoff

Fast execution, clear handoff

0

Component sets

0+

Total variations

0

Complete flows

Built entire UI system with specs so precise developers executed QUICKLY AND CONFIDENTLY. I'd work with him again without hesitation.

— Georges Rahbani

Engineering Director, Stackit

REFLECTION

A component isn't finished until a developer can build it with confidence

A component isn't finished until a developer can build it with confidence

Documenting every component state before development removed 90% of the clarification questions. When Georges and his team built the platform, they had answers for edge cases before they hit them. The system anticipated those questions instead of reacting to them.

This isn't about perfect designs. It's about complete documentation. Developers can build confidently when specs cover disabled, empty, loading, and error states, not just the happy path.

© 2026 Jorge Godoy

© 2026 Jorge Godoy

© 2026 Jorge Godoy