#E3F2FDCASE STUDY
Magnetita Design System
From a visual library to a more consistent language for Foregon products.
FOUNDATIONS
Color, typography, grid, and spacing as shared decisions.
67 paint styles · 17 text styles · 3 effect styles · 2 grid styles
FEEDBACK COLORS
#BBDEFB#64B5F6#007AD9#1976D2#0D47A1#E1F5FE#B3E5FC#4FC3F7#1AD3FF#039BE5#01579B#FFF8E1#FFECB3#FFD54F#FFC107#FFA000#FF6F00#E0F7FA#B2EBF2#4DD0E1#00BCD4#0097A7#006064#B71C1C#D32F2F#F44336#E57373#FFCDD2#FFEBEE#1B5E20#388E3C#4CAF50#81C784#C8E6C9#E8F5E9NEUTRAL COLORS
#1D1D1D#3D3D3D#5C5C5C#707070#DBDBDB#F3F3F3#FFFFFFPRIMARY COLORS
#020653#00298F#0055B8#007AD9#1AD3FF#C4F6FF#E8FDFFGRADIENTS
BACKGROUND COLORS
#FFFFFF#FAFCFF#F3F3F3#707070#3D3D3DPREMIUM COLOR
#2C1B08#533516#7A4E25#A16733#FEB705#FED293#FEECC7Typography
Outfit — 17 text styles · Desktop + Mobile · heading + body
Desktop / H1Magnetita Design System40px · BoldDesktop / H2Magnetita Design System32px · BoldDesktop / H3Magnetita Design System28px · BoldDesktop / H4Magnetita Design System24px · BoldDesktop / H5Magnetita Design System20px · BoldMobile / H1Magnetita Design System24px · BoldMobile / H2Magnetita Design System20px · BoldMobile / H3Magnetita Design System16px · BoldCorpo de textoMagnetita Design System24px · RegularCorpo de texto — BoldMagnetita Design System24px · BoldCorpo de texto 1Magnetita Design System20px · RegularCorpo de texto 1 — BoldMagnetita Design System20px · BoldCorpo de texto 2Magnetita Design System16px · RegularCorpo de texto 2 — SemiBoldMagnetita Design System16px · SemiBoldBotãoMagnetita Design System14px · ExtraBoldSobrancelhaMagnetita Design System14px · BoldDescriçãoMagnetita Design System14px · RegularLEGACY × V2
The change went beyond appearance
A real comparison between Legacy and V2 components. The elements below represent instances from the Magnetita file.
LEGACY
Inconsistent naming
- No defined states
- No component set
V2
Component Set
51 variants · Type, State, Icon
V2 — FORM / INPUT
8 variants · Type × State × Filled
V2 — FORM / SWITCH
8 variants · On · Off · Hover · Focus · Disabled
COMPONENT GALLERY
Component Gallery
The real building blocks behind Foregon products, grouped by their role in the system.
ACTIONS
Buttons · 51 variants with Type, State, Icon
FORMS
Input · Switch · Radio · Selection controls
NAVIGATION
Pagination · Chevron · Chip
FEEDBACK & UTILITY
Badge · Tooltip · Pop over · Notification · Loader · QA status
DATA & SCORE
Score · Badge score · Numerals
PRODUCT & BRAND
Product · Avatar · Logo
COMPONENT SPOTLIGHT
Button / Primary
51 variants · Type (Primary, Card, Account, Loan, Link) × State (Normal, Hover, Focus, Disabled, Loading) × Icon
TYPE
STATE
ICON
COMPONENT ARCHITECTURE
Atom → Molecule → Organism
ATOM
Buttons, Inputs, Switch, Radio, Badge, Tooltip, Loader
MOLECULE
Score Card, Status Card, Pop over, Navigation
ORGANISM
Carousels, Headers, Product Cards, Navigation, Complete screens
SYSTEM ARCHITECTURE
Core × Team × Lab
A separation of responsibilities across shared, squad-specific, and experimental components.
💙 CORE
440 components · 56 component setsCentralized governance. Used by Score, Cards, Loans, and Digital Account.
TEAM
234 components · 45 component setsAutonomy within standards for squad-specific needs.
🧪 LAB
Protected sandboxToken explorations, evolution proposals, and concept tests not yet formalized.
TOKEN MODEL
Token Model
An exploration of a semantic language for visual decisions.
primarias/500#0055B8action/primarybutton/background/defaultprimarias/300#1AD3FFaction/secondarybutton/background/hoverprimarias/700#020653text/primaryheading/colorneutras/900#1D1D1Dtext/defaultbody/colorneutras/100#F3F3F3surface/secondarycard/backgrounddanger/500#F44336feedback/errorinput/border/errorSuccess/500#4CAF50feedback/successbadge/background/successAviso/500#FFC107feedback/warningalert/background/warningROADMAP
Evolution Roadmap
Nov 2023 – Mar 2024 · 5 phases
- 01
Audit
Component inventory, inconsistency mapping, and usage analysis across products.
- 02
Foundations
Color, typography, grid, and spacing became shared decisions: 67 paint styles and 17 text styles.
- 03
Core Rebuild
Atomic reconstruction from Atom to Molecule to Organism: 440 components and 56 component sets.
- 04
Team / Lab
Core, Team, and Lab were separated to balance autonomy and governance.
- 05
Documentation
Guidelines, usage patterns, and an In Memoriam deprecation model.
DEPRECATION MODEL
Deprecation Model
How components are retired without breaking products in production.
DEPRECATED
Deprecation tag, visual warning, and documented replacement.
IN MEMORIAM
Transition page, notified teams, and a migration period.
LIXO
Removed from active use and kept as a historical reference.
Components found in ‘In memoriam / Lixo’:
Ícone/Rounded/MenuÍcone/Rounded/FecharÍcone/Rounded/BuscaÍcone/Rounded/SetaBotão/Selection ControlBotão/Navegação/ChipBotão/Navegação/Item de listaBotão/Avaliação/CurtirGOVERNANCE
Documentation & Governance
- 01–03
Discovery
Need · Exploration · System Review
- 04–05
Build
Design + Engineering · Documentation
- 06–07
Ship
Release · Adoption
- 08–09
Evolve
Feedback · Iteration
DOCUMENTATION
Per-component guidelines, anatomy, props, variants, and do/don't living alongside the Figma component.
GOVERNANCE
Open contribution with review, proposals through Lab, consistency checks before promotion to Core, and semantic versioning.
MY CONTRIBUTION
My Contribution
SYSTEM STRATEGY
I helped define the Core / Team / Lab architecture and separate shared and squad-specific responsibilities.
COMPONENT EVOLUTION
I contributed to the Legacy-to-V2 evolution, atomic restructuring, and variant properties.
DESIGN QUALITY
I worked with the team on visual states, basic accessibility, and consistency across products.
PRODUCT ALIGNMENT
I helped align the needs of Score, Cards, Loans, and Digital Account with the system.
DOCUMENTATION
I contributed to component guidelines and the In Memoriam / Lixo deprecation model.
2026 REVIEW / RECONSTRUCTED
What I would do differently today
- 01
TOKENS FIRST
Start with Figma Variables from day one: Primitive → Semantic → Component.
- 02
DOCUMENTATION AS A PRODUCT
Apply the same design thinking used for interfaces to guidelines.
- 03
GOVERNANCE BEFORE COMPONENTS
Define contribution, review, and evolution before the library fragments.
- 04
DESIGN × CODE PARITY
Keep naming, props, and component tokens closer across Figma and code.
- 05
NATIVE ACCESSIBILITY
Make contrast, focus, target sizes, and keyboard navigation creation requirements.
- 06
ADOPTION METRICS
Track instance coverage, detach rate, and onboarding time.
REFLECTION
Final reflections
A system is not a collection of components. It is a shared mental model.
The hardest part is not building it — it is driving adoption.
Consistency is a political decision, not only a visual one.
Documentation no one reads is not documentation.
A Design System matures when it stops organizing only components and starts organizing decisions.
Jhonatan Rafael — Product Designer
2023 – 2024 · RECONSTRUCTION 2026

