moai-design-craft

Ground UI design decisions in domain understanding before implementation.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/windysky/snake-game --skill moai-design-craft-windysky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-design-craft
Source: https://github.com/windysky/snake-game/tree/main/.claude/skills/moai-design-craft
Command: npx skills add https://github.com/windysky/snake-game --skill moai-design-craft-windysky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and preserves design intent by anchoring decisions in domain understanding before UI construction.

Core Features & Use Cases

  • Intent-First design direction: capture domain vocabulary and design intent before building UI.
  • Design memory integration: read and update .moai/design/system.md to preserve rationale across SPECs and iterations.
  • Post-build critique workflow: perform structured reviews (observe, diagnose, decide) to ensure alignment with intent.
  • Domain-to-copy alignment: ensures design directions are reflected in copy and UI semantics.

Quick Start

Provide a feature brief and let this skill generate a design direction and run a post-build critique.

Frequently Asked Questions about moai-design-craft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve design intent and rationale across UI iterations?

You can preserve design intent by reading and updating a project-wide design memory file at .moai/design/system.md, ensuring your domain vocabulary and UI rationale remain traceable across iterations.

What is an intent-first design direction workflow?

An intent-first design workflow captures domain vocabulary and establishes design intent before UI construction, anchoring subsequent interface decisions in domain understanding rather than arbitrary styling.

How do I run a structured design critique after building a UI?

You can run a post-build critique by executing /moai review --critique to perform a structured review that observes, diagnoses, and decides if the UI aligns with the original design intent.

Do I need a specific file structure to maintain design memory?

Yes, you need a project-wide design memory file located at .moai/design/system.md to preserve design rationale and ensure traceability across various SPECs and development iterations.

How do I align web copy with domain understanding and UI semantics?

You align web copy by establishing design directions that explicitly reflect domain vocabulary, ensuring the UI semantics and copy remain consistent with the captured design intent.

What's the best way to document domain vocabulary before UI implementation?

The best way is to capture domain vocabulary and design intent upfront in a centralized memory file, grounding your UI decisions in domain understanding before you begin implementation.