moai-design-craft

To anchor design decisions to user intent, you translate domain exploration into explicit vocabulary and persist decisions into a memory file for cross-SPEC consistency. This prevents premature visuals and misalignment across teams.

Design memory persists decisions and domain vocabulary in a system.md file for cross-SPEC consistency. It ensures design direction traces back to user goals, maintaining frontend design consistency across planning and implementation.

To run a structured design critique, you review the implementation against the original design intent and domain vocabulary. This post-build critique workflow guides you to patch or rebuild components as needed.

Intent-first design direction requires prior domain exploration to translate into explicit design intent and vocabulary. Without it, anchoring decisions to user goals and domain concepts lacks the necessary foundation.

The best way to capture domain vocabulary is to summarize the design intent and domain concepts, then persist them into a dedicated design memory file. This supports audits and critique throughout the development lifecycle.

Implementation misaligns with planning intent when design decisions are not anchored to user goals and domain vocabulary. Capturing vocabulary and persisting decisions in design memory prevents this drift across teams.