moai-design-craft

Intent-first design craft grounds UI work in domain understanding and craft principles to establish clear design intent. It ensures reliable UI by maintaining a design system memory, capturing domain vocabulary, and enforcing critique cycles to guide domain-driven UI decisions.

To start a design direction, complete a domain exploration to clarify domain intent and vocabulary. Write the resulting design direction into the .moai/design/system.md file to anchor the next build and guide implementation decisions across the project.

Design memory records decisions, domain vocabulary, and rationale to guide future work and maintain consistency across projects. It ensures reliable UI by preserving the context and intent behind past design choices in a centralized system file.

A UI audit works by evaluating the built interface against the established design direction and domain vocabulary. It applies craft principles to check alignment with the original intent, generating actionable improvements for post-build critique cycles.

No, this approach requires maintaining a design system memory in .moai/design/system.md. The file captures domain vocabulary, records design decisions, and anchors the design direction needed to enforce critique cycles and guide domain-driven UI decisions.