MEI Copiloto

From moodboard to design canon

This one skipped Figma. The client had already gathered a Pinterest moodboard pointing at a neo-brutalist direction, so instead of rebuilding that intent inside a design tool, I took the moodboard straight to approval and then wrote it down as code-adjacent truth: a DESIGN.md design canon, before a single component existed. Every rule in it became a constraint the build had to obey, not a suggestion to interpret later. A single purple reserved for the primary call to action and nothing else, a warm cream floor instead of white, zero gradients, zero shadows, and exactly two border-radius values for the entire interface. Writing the canon first meant the whole system fit in one person's head, which is what let the build move as fast as the brief demanded.

Narrative and microcopy

The audience here has their hands full and their attention split between a client in front of them and a phone in their pocket. Every section had to earn its place: problem stated before solution, four concrete pillars named plainly (agenda, reminders, money, the DAS deadline) instead of a generic features list, and nothing that would need walking back later: no invented testimonials, no fabricated client counts, no pricing pulled from thin air.