The "agent starts from zero" problem Marque addresses is one of the most frustrating aspects of working with AI coding agents at scale. Every new conversation, the agent has no memory of your color palette, your spacing system, your component patterns, or the reasoning behind your design decisions. You end up spending 30% of every prompt re-establishing context that should be ambient.

Moving design identity to the infrastructure level rather than the prompt level is the right architectural instinct. When `get_design_context_for()` is a first-class call the agent makes before writing any component, the design system becomes a constraint the agent generates within rather than a suggestion it can ignore.

This maps directly to the Agile Vibe Coding Manifesto's principle that "architecture guides and constrains generation." The manifesto's argument is that system-level constraints — including design systems, API contracts, and architectural conventions — should be explicit inputs to generation rather than things developers have to re-inject into every prompt.

The "marque improve" drift detection loop is clever: https://agilevibecoding.org