Update Log
Change history and next improvement candidates for the AI-era design systems handbook.
2026-05-17
English support was added and the bilingual verification baseline was formalized.
| Area | Change |
|---|---|
| English edition | Added the en/design-systems-ai book structure and 19 primary chapters. |
| Home listing | Registered the English title and description for the handbook home surface. |
| Verification | Added check:design-systems-ai for ko/en page order, file coverage, frontmatter, and English link localization. |
| Operations pages | Added verification and updates pages to both Korean and English editions. |
| Source correction | Adjusted Style Dictionary v5 and Figma MCP wording to match official documentation more conservatively. |
| English depth | Expanded prompt-interface, component-spec, agentic-design-control, context-injection, and case-studies. |
Operating Rules
- Korean and English editions keep the same structure.
- Adding a chapter requires updating both locale
meta.jsonfiles, both.mdxfiles, andverificationcoverage. - Current AI tooling should distinguish "available", "beta", "proposal", "official extension", and "production-ready" based on sources.
- Tool lists should resolve into design-system operating rules, not stay as trend inventory.
Next Improvement Candidates
| Candidate | Why it matters |
|---|---|
| Per-chapter agent prompt packs | Agents need short task instructions they can reuse directly. |
| Design token migration examples | DTCG, Style Dictionary, and Tailwind v4 mapping deserves concrete conversion examples. |
| Visual QA playbook | Playwright screenshots, accessibility checks, and design review rubrics should become one repeatable loop. |
| Case-study source notes | Material, Fluent, Figma, shadcn/ui, and Radix examples can carry tighter official-source links. |