Components, styles, foundations.
The canonical reference for building Leadjr screens. This microsite keeps the system navigable: start with foundations, then move into tokens, type, components, patterns, states, rules, and the Cabana conversion contract.
One system, split into smaller working rooms.
The design system should be easy to consult while building. Each section owns one kind of decision so new components can be added without turning the reference into a single long document.
The product rules before the pixels.
Purpose, tone, structure, and constraints for anything that should feel like Leadjr.
Black ink, warm paper, rare signal.
Color, spacing, radii, shadows, and motion decisions that keep the system serious and source-aware.
Serif headlines, mechanical labels.
Typefaces, type scale, weights, and rendered specimens for every step in the system.
Lucide, used sparingly.
The approved icon set with sizes, weights, and copy-paste imports. Add nothing decorative.
Reusable pieces with live specimens.
Primitive UI surfaces and documented component behavior for building Leadjr screens.
Repeatable layouts for real work.
Task-shaped templates for briefs, references, review queues, and detail pages.
State through structure first.
Status language that stays calm instead of turning the record into dashboard confetti.
The checklist before a page ships.
Fast QA rules that protect the system from generic SaaS drift and responsive breakage.
Cabana anatomy, Leadjr judgment.
The conversion contract for adding components without importing another system's language.