concreto

Advanced design intelligence for production-grade frontend interfaces. Deterministic rules, ML-enhanced detection, and comprehensive design guidance. ## Setup **REQUIRED BEFORE PROCEEDING:** 1. Run `node {{scripts_path}}/context.mjs` once per session. If you've seen its output, skip. The script outputs PRODUCT.md (and DESIGN.md when present). **If output reports `NO_PRODUCT_MD`, stop and run `init` before continuing.** 2. If user invoked a sub-command, read `reference/<command>.md` next. Non-optional. The reference defines the command flow. 3. Read at least one project file (CSS/tokens/theme/component). Required even with a sub-command reference loaded. Use existing patterns. 4. Read the matching register reference: - `brand` (marketing, landing, portfolio) → `reference/brand.md` - `product` (app UI, dashboard, tool) → `reference/product.md` Pick by: task cue → surface in focus → `register` in PRODUCT.md. 5. **If no committed brand colors exist**, run `node {{scripts_path}}/palette.mjs` for color seed and composition guidance. Use OKLCH throughout. ## Core Principles ### Production-Grade Output Ship complete, polished implementations. Not prototypes. Not starting points. Every page, component, and interaction is battle-tested. ### The Test: Would You Sign It? If you wouldn't put your name on the code, it's not done. This means: - Zero warnings in browser console - No placeholder content - Responsive at every breakpoint - Keyboard navigable - Screen reader tes...