Intent-First design craft specialist covering design direction, domain vocabulary, design memory, and post-build critique. Use when establishing design intent or auditing code against design principles.
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.moai/archive/skills/v3.0/moai-design-craft/SKILL.mdIntent-First design philosophy integrated into MoAI workflows. Ensures design decisions flow from intent and domain understanding, not from visual impulse.
Intent-First: Before any visual or component decision, establish why — the domain, the user, the interaction contract, and the craft principles that apply.
The three craft operations:
| Operation | When | What It Does |
|---|---|---|
| Design Direction | At /moai plan (design keywords) | Domain exploration, intent capture, vocabulary alignment |
| Design Audit | At /moai review --design | Checks implementation against .moai/design/system.md |
| Design Critique | At /moai review --critique | Post-build craft review: observe, diagnose, rebuild decision |
modules/intent-first.md — Intent-First process: domain exploration, design direction, vocabularymodules/design-memory.md — .moai/design/system.md read/write protocolmodules/critique-workflow.md — Post-build critique: observe → diagnose → rebuild, hard rules and rejection criteriamodules/web-copy-craft.md — Web copy guidelines: anti-AI writing, headline formulas, CTA patterns, body copy rhythmWhen manager-spec detects design-relevant keywords, trigger Design Direction:
.moai/design/system.md (if it exists) for established vocabulary and intent.moai/design/system.mdWhen /moai review --design is invoked:
.moai/design/system.md for current design system rulesWhen /moai review --critique is invoked:
When expert-frontend or team-designer generates web pages, apply copy craft rules:
moai-domain-uiux — Design tokens, WCAG, accessibility (complementary, not overlapping)moai-design-tools — Figma/Pencil tool mechanics (complementary, not overlapping)moai-domain-frontend — Component implementation patternsVersion: 1.2.0 Last Updated: 2026-03-30
| Rationalization | Reality |
|---|---|
| "Design direction is just aesthetics, the code works the same" | Design intent drives user perception and brand consistency. Code without design direction produces generic, forgettable interfaces. |
| "I will figure out the design vocabulary during implementation" | Naming components without a design vocabulary produces inconsistent names. Establish vocabulary before building. |
| "Design memory is unnecessary, the design system is the reference" | Design systems define what to use. Design memory captures why decisions were made and what was rejected. |
| "Post-build critique is just a formality" | Critique reveals drift between intent and execution. Without it, the gap accumulates with each iteration. |
| "This is an internal tool, design does not matter" | Internal users have the same cognitive load as external users. Poor design increases training cost and error rates. |
modu-ai/moai-adk
1176c97
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.