Same words, same content. One follows a system, one doesn't. That's the whole session in one slide.
Your design system
Four commitments. Every screen obeys them.
TypeONE font pairing
Color
ONE palette, 3-4 colors max
FeelingONE adjective
SpacingONE rule, the same gap every time
This is not decoration. It's a system: decide once, apply everywhere.
Copy this prompt · run it in the build block
Generate 3 directions, then pick like a founder
My product: [thesis]. My user: [person]. Generate 3 genuinely different visual directions: font pairing, 4-color palette, one adjective, one spacing rule for each. Make them MORE different if two feel the same.
Two minutes to pick. Decide, commit, move. Debating longer than that costs more than a wrong pick.
The consistency prompt
One system. Every screen. No exceptions.
Here is our design system: [font pairing], [palette], [adjective], [spacing rule]. Apply it across EVERY screen of the app. Nothing gets its own style. Show me before/after.
You did one line of this on Day 1, a design schema card like “make it look like airbnb.com.” Today it becomes a system, not a one-liner.
Exercise · Build your design system FOLLOW ALONG · laptops open
TEAM. Style card, then run the prompt.
10:00
1Fill in your style card: one font pairing, one palette (3-4 colors), one adjective, one spacing rule.
2Paste the consistency prompt into Kimi Code with your four answers filled in.
3Run it. Screenshot before and after, post both to the TEAM FOLDER.
10:00
Style card + before/after → TEAM FOLDER. Next: the build block applies it for real.
Exit ticket
Leave with ·Your design system + before/after screenshots.
Decided ·The look, locked. Every screen obeys it now.
Bring next ·13:45 build block: apply the system while you build the next features off your build order. Redeploy so your live URL shows the new look.