dux-agent-mayasura

DESIGN.md authoring translates your product intent into a coherent, single-source visual contract that acts as a durable source of truth. You generate it by asking the Mayasura agent to author or update the file based on your product requirements.

Intent-based routing automatically dispatches your requests to the correct workflow for DESIGN.md authoring, linting, screen generation, or prototype creation. It interprets your product intent and eliminates manually juggling separate tools and formats.

You lint a DESIGN.md file by requesting it from the Mayasura agent, which applies persona-driven design guardrails using persistent facts and predefined principles. This enforces accessibility and consistency standards across your visual system outputs.

Yes, you can generate screens and marketing prototypes by asking the Mayasura agent to build them. It routes your request using your DESIGN.md as the visual contract to ensure all executable outputs and marketing sites remain visually consistent.

Config-aware execution requires loading module and dux configuration, including the DESIGN.md location and output folder, to apply the correct project paths. This setup is required to accurately route requests into the correct registered workflows.

Using a single DESIGN.md for prototyping limits outputs to the visual rules defined within that file. If your product intent requires divergent visual systems, maintaining a single-source visual contract may restrict creative flexibility across screens.