moai-design-craft

Establishes design intent, domain vocabulary, and post-build critique workflows for UI development.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/yekinya/moai-novel --skill moai-design-craft-yekinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-design-craft
Source: https://github.com/yekinya/moai-novel/tree/main/moai-novel/.claude/skills/moai-design-craft
Command: npx skills add https://github.com/yekinya/moai-novel --skill moai-design-craft-yekinya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend work often jumps straight to visual decisions without a clear statement of purpose, producing generic interfaces, inconsistent component naming, and AI-sounding web copy. This Skill anchors design decisions in documented intent and audits built interfaces against that intent. ## Core Features & Use Cases - Design Direction: Runs domain exploration, captures a 1-3 sentence design intent, and defines 3-5 domain vocabulary terms before any UI is built. - Design Memory: Reads and writes .moai/design/system.md so design intent, vocabulary, and anti-patterns persist across sessions and SPECs. - Design Audit & Critique: Checks implementations against the design system via /moai review --design and runs an observe-diagnose-decide critique via /moai review --critique, classifying drift as cosmetic, structural, or intent-level. - Web Copy Craft: Applies five headline formulas, sentence-rhythm variation, filler-phrase elimination, and verb-first CTA rules to all visible page text. - Use Case: When planning a new landing page SPEC, trigger Design Direction to record intent and vocabulary in .moai/design/system.md, then after implementation run a critique to detect drift and decide whether to patch or rebuild. ## Quick Start Ask the agent to run design direction for your new feature SPEC so it explores the domain, writes a design intent statement, and saves the vocabulary to .moai/design/system.md.

Frequently Asked Questions about moai-design-craft

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

FAQPage Schema
How do I define design intent before building a UI?

Run the Design Direction process: explore the user context, audit the mental model, and define the interaction contract. Then write a 1-3 sentence Design Direction statement covering user intent, design intent, and one craft principle, and save it to .moai/design/system.md.

How to audit frontend code against a design system?

Invoke /moai review --design to read .moai/design/system.md, scan UI components against its rules, and report violations with file:line references. For deeper review, /moai review --critique runs an observe-diagnose-decide pass classifying drift as cosmetic, structural, or intent-level.

What is the difference between design audit and design critique?

Design audit checks implementation against the rules stored in .moai/design/system.md and suggests minimal fixes. Design critique evaluates the built interface against the original intent through observation and diagnosis, deciding whether to patch or rebuild.

How do I write web copy that does not sound AI-generated?

Use the five headline formulas (Number Anchor, Reversal, Direct Question, Empathy Hook, Declaration), vary sentence rhythm so no three consecutive sentences share a structure, replace vague intensifiers with specific facts, and make CTAs verb-first and outcome-oriented.

When should design direction not be triggered?

Skip it for minor modifications to existing components that already follow established vocabulary. It is intended for new user-facing flows, consequential decisions, unfamiliar domains, or features where copy and labels are part of the design.