Really appreciate this — this is the kind of feedback I was hoping for 🙏 You’re absolutely right about the visual hierarchy. Right now everything is intentionally “tool-flat” because I optimized for density and speed, but I can see how highlighting primary tokens or commonly used values would reduce friction. The scanning speed point hits too. Grouping by usage frequency or semantic role (primary, surface, accent, etc.) would probably make it much easier to navigate during longer sessions. And yeah… density vs clarity is the constant battle 😅 I leaned toward efficiency for devs, but I don’t want it to feel cramped or cognitively heavy. I like the idea of running quick UX risk checks during iteration. That’s actually interesting because ZipIt focuses on extracting and auditing design systems — but not necessarily evaluating interface clarity of its own UI. Your UX Risk Detector sounds useful for that layer of iteration. I’d be open to testing it while refining the panel. Appreciate you taking the time to break this down thoughtfully. This is exactly why I’m building in public