Verification Checklist
Quality checks for bilingual structure, sources, and AI-ready design-system guidance.
This page defines how the handbook itself is verified. Design-system documentation is not a static artifact. It needs recurring correction as AI coding tools, design tools, and token standards change.
Automated Checks
Run these commands after handbook changes.
pnpm --filter handbook run check:design-systems-ai
pnpm --filter handbook run typecheckcheck:design-systems-ai verifies:
| Area | Rule |
|---|---|
| Page structure | Korean and English meta.json page order must match. |
| File coverage | Every registered .mdx page must exist in both locales. |
| Frontmatter | Every page must include title and description. |
| Link localization | English pages must use /en/books/design-systems-ai/ links, not /books/design-systems-ai/. |
| Verification coverage | This page must reference every primary chapter slug. |
Chapter Coverage
| slug | Review focus |
|---|---|
token-architecture | Confirm DTCG, Style Dictionary, and Tailwind CSS token guidance against current sources. |
component-spec | Confirm props, slots, states, variants, and accessibility contracts are machine-readable. |
accessibility | Confirm ARIA, keyboard, focus, and accessible-name rules are implementable. |
prompt-interface | Confirm prompt examples include component choice, forbidden patterns, and verification commands. |
design-md-interface | Confirm DESIGN.md communicates brand intent and visual rules clearly. |
agentic-design-control | Confirm screenshot review, Playwright checks, and agent feedback loops are explicit. |
workflow-strategies | Confirm design-to-code, code-to-design, and bidirectional workflows are not overstated. |
ds-evolution | Confirm AI-assisted refactoring, audits, and documentation expansion are operational. |
context-injection | Confirm AGENTS.md, CLAUDE.md, DESIGN.md, and MCP responsibilities are separated. |
consistency | Confirm grid, spacing, density, and responsive behavior are written as verifiable rules. |
interaction | Confirm feedback, motion tokens, loading, error, and empty states are covered. |
forms | Confirm validation, error copy, field composition, and accessibility are treated together. |
agent-ui-protocols | Confirm A2UI, AG-UI, MCP Apps, and similar claims match public documentation. |
generative-ui | Confirm runtime UI generation is constrained by schemas, registries, and guardrails. |
spatial-multimodal | Confirm spatial, voice, and multimodal rules connect back to design-system tokens. |
playbook | Confirm the 0 -> 1 sequence is small enough for teams to execute. |
migration | Confirm migration is incremental rather than a big-bang rewrite. |
governance | Confirm ownership, approval, review, and quality gates connect to docs and code. |
case-studies | Confirm examples are framed as reusable patterns and limits, not tool promotion. |
Source Refresh Rules
Check version and date before making status claims.
| Topic | Source rule |
|---|---|
| Design Tokens | Check the latest Design Tokens Format Module report and the DTCG site. |
| Style Dictionary | Check official Style Dictionary docs before claiming full 2025.10 DTCG support. |
| Tailwind CSS | Check official Tailwind docs for v4 @theme and theme variables. |
| Figma MCP | Check Figma developer docs and help center for remote/desktop MCP status and beta wording. |
| React | Check the official React release blog for React 19.x feature status. |
| MCP Apps | Check the Model Context Protocol blog before using proposal, extension, or production-ready wording. |
Manual Review
Automation protects structure, not judgment. For meaningful changes:
- Confirm the Korean and English pages make the same technical claims.
- Confirm English pages have enough context for global readers, not only literal translation.
- Check that "official", "GA", "stable", "beta", and "production-ready" match the cited source.
- Pair every AI workflow recommendation with validation loops, failure modes, and explicit constraints.