Iverson Dantas

A few people here asked how Ilse deals with bigger design systems. So far I talked about one direction: Ilse reads your tokens and components, writes a DESIGN.md, and your agent stops inventing new buttons.

The next release adds the other direction: what's already in your code and should become part of the system.

Open the new Consistency tab and Ilse reads the screen you're on:

• Look-alikes: four links with the same classes pasted by hand, which look like one piece but aren't a component. Ilse groups them and names what's off, like "1 differs in padding".

• Off the system: a DS component overridden with a className, a hand-written copy of a variant, a color outside your tokens, a font or size off the scale.

• Agent review: your own agent reads that screen's code once and adds what rules can't catch.

• Fixes show on the page before anything is sent, the same way the panel works. "Make it a component" turns a group of look-alikes into a note for your agent, with your tokens. Ignore something once and Ilse remembers it for the whole project.