@design-ai/cli 4.63.0 → 4.64.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "design-ai",
-  "version": "4.63.0",
+  "version": "4.64.0",
   "description": "Senior product designer for any AI coding agent. 20 skills, 17 commands, 4 review agents covering UI/UX, website improvement, design systems, motion, illustration, print, video, game UI, conversational, and spatial design. Korean market depth.",
   "author": {
     "name": "Sungjin Park",

package/CHANGELOG.md

@@ -2,6 +2,34 @@
 
 User-facing release notes for design-ai. Versions follow semver.
 
+## v4.64.0 — Route coverage sweep: marketing-page route and 18-class routing (2026-07)
+
+Generalizes the two dogfood rounds' converged finding — route-table coverage is the recurring gap class — into one systematic batch. Eighteen common task classes were probed through `route()`; thirteen were low/misrouted/zero-match despite the knowledge corpus already covering nearly every one of them (a pricing-page brief scored 0 with `pricing-page-design.md` sitting in the corpus). All fixed in one pass; evidence tables in `docs/ROUTE-COVERAGE-SWEEP.md`. Additive and backward-compatible.
+
+### Added
+- **`marketing-page` route** — consolidates three previously zero/misrouted marketing-surface classes (landing page, pricing page, email template) with five dedicated knowledge files curated (`landing-hero-design`, `landing-page-patterns`, `pricing-page-design`, `email-design`, `brand-identity`) and check requirements for conversion/CTA evidence, visual hierarchy, and responsive/email-client behavior.
+- **`examples/marketing-page-saas-landing.md`** (examples now 224) — the route's worked example (developer-tool SaaS landing: 히어로, 기능 소개, 가격, 후기, CTA 배치, 한국형 신뢰 요소).
+
+### Changed
+- **`dashboard-design`** gains chart/data-viz and permissions vocabulary (차트, 데이터 시각화, 시계열, 범례, 권한, 역할 관리 + English forms) and three more curated knowledge files (`chart-types`, `chart-color-encoding`, `realtime-data`) — data-viz and RBAC-admin briefs move from score 0 to `[medium]`.
+- **`flow-design`** gains nine interaction classes' vocabulary (체크아웃, 알림 센터, 계정 관리, 프로필 수정, 회원 탈퇴, 업로드, 드래그 앤 드롭, 댓글, 멘션, 공유 권한, 코치마크, 투어, 필터, 정렬, 무한 스크롤, 내비게이션, 하단 탭, 다단계, 임시저장, 유효성 검증 + English forms). A multi-step form brief now intentionally routes to `flow-design` instead of `component-spec`.
+- Post-fix probe: **all 18 classes land on their target routes at medium+ confidence** where the brief vocabulary allows; the previously-correct classes are unchanged; no keyword hijacks (verified programmatically against every route's keyword set); route eval 6/6; both dogfood briefs keep their routes.
+
+### Verified
+- All 8 audits passed.
+- `npm run release:check`.
+- `npm run release:metadata`.
+- `git diff --check`.
+- Route eval 6/6; example-qa 22/22 routes; 18-class before/after probe recorded in `docs/ROUTE-COVERAGE-SWEEP.md`.
+- Main-branch GitHub Actions (`Design-AI audit`, `Deploy doc site`) passed for the constituent commits.
+
+### Versions
+- `package.json` + `.claude-plugin/plugin.json`: 4.63.0 → 4.64.0.
+- `vscode-extension/package.json`: remains 0.4.1.
+
+### What this enables
+- The route table now covers the common product-design task space end to end: any of the 18 probed classes — from checkout flows to RBAC admin screens to pricing pages — reaches purpose-matched curation, checklists, and checks instead of falling through to design-system scaffolding.
+
 ## v4.63.0 — Dogfood round 2: dashboard-design route and flow-design keyword depth (2026-07)
 
 The dogfood loop's second turn, run immediately after v4.62.0 on fresh briefs. It first verified the v4.62 fixes live (flow briefs route to `flow-design`, recall selections are 100% design corpus, `pack` trims to the character boundary), then probed three new task classes and shipped what the weakest one surfaced. Evidence trail in `docs/DOGFOOD-DASHBOARD-FINDINGS.md`. All additive and backward-compatible.

package/README.ko.md

@@ -3,7 +3,7 @@
 [![Audit](https://img.shields.io/badge/audit-passing-brightgreen)](https://github.com/sungjin9288/design-ai/actions/workflows/audit.yml)
 [![Docs](https://img.shields.io/badge/docs-live-indigo)](https://sungjin9288.github.io/design-ai/ko/)
 [![Knowledge files](https://img.shields.io/badge/knowledge-95-blue)](knowledge/PRINCIPLES.md)
-[![Examples](https://img.shields.io/badge/examples-223-blue)](examples/README.md)
+[![Examples](https://img.shields.io/badge/examples-224-blue)](examples/README.md)
 [![Skills](https://img.shields.io/badge/skills-20-blue)](skills/README.md)
 
 > 🇰🇷 한국어 / [🇺🇸 English](https://github.com/sungjin9288/design-ai/blob/main/README.md)
@@ -12,7 +12,7 @@
 
 > **모델이 아니에요. 파인튜닝도 아니에요.** 디자인 전문 지식을 구조화한 코퍼스 + 에이전트가 바로 실행할 수 있는 지시문이에요. 범용 LLM을 이번 세션에서만큼은 시니어 디자이너로 바꿔주는 셈이에요.
 
-> **배포 상태, 2026-07-06 확인:** 로컬 `npm run release:check`는 통과했고, GitHub Pages 문서는 live 상태이며, GitHub Release `v4.62.0`과 npm `@design-ai/cli@4.62.0`(`latest`) publish가 provenance와 함께 확인됐어요. 이번 릴리스는 도그푸드 루프를 마감했어요 — `flow-design` 라우트, trust & safety 코퍼스 파일과 워크드 예제, recall 주입의 `docs/` 제외(디자인 지식 전용), `pack` UTF-8 바이트 예산 픽스, Agent SDK 워크스루(영/한). live `npm run registry:smoke`가 published `@design-ai/cli@4.62.0`에 대해 깨끗이 통과했어요(retrieval 표면과 route enrichment 포함). Homebrew formula는 `v4.62.0`에 pinning되어 있고, VS Code Marketplace에는 `sungjin.design-ai-vscode@0.4.1`이 공개되어 있어요. 자세한 내용은 [`docs/external-status.md`](docs/external-status.md)를 확인하세요.
+> **배포 상태, 2026-07-07 확인:** 로컬 `npm run release:check`는 통과했고, GitHub Pages 문서는 live 상태이며, GitHub Release `v4.63.0`과 npm `@design-ai/cli@4.63.0`(`latest`) publish가 provenance와 함께 확인됐어요. 이번 릴리스는 도그푸드 루프 2회전이에요 — 데이터 밀집 화면 클래스를 위한 `dashboard-design` 라우트(금액 표기·테이블 접근성·밀도 check 요건)와 정산 워크드 예제, 그리고 `flow-design` 키워드 심화(한글 스텝 플로우 어휘 + 상태 설계 복합어, illustration 라우트와 양방향 검증). live `npm run registry:smoke`가 published `@design-ai/cli@4.63.0`에 대해 깨끗이 통과했어요(retrieval 표면과 route enrichment 포함). Homebrew formula는 `v4.63.0`에 pinning되어 있고, VS Code Marketplace에는 `sungjin.design-ai-vscode@0.4.1`이 공개되어 있어요. 자세한 내용은 [`docs/external-status.md`](docs/external-status.md)를 확인하세요.
 
 ## 한눈에 보는 커버리지
 
@@ -172,7 +172,7 @@ design-ai는 한국 시장을 1순위로 만들어졌고, 글로벌 시장 패
 
 ## 상태
 
-전체 단계 로그는 [`docs/ROADMAP.md`](docs/ROADMAP.md), 현재 완료 범위는 [`docs/PRODUCT-READINESS.md`](docs/PRODUCT-READINESS.md)에서 확인하세요. 현재 **v4.62.0**: 도그푸드 루프 마감(`flow-design` 라우트, trust & safety 코퍼스, 디자인 지식 전용 recall, `pack` 바이트 예산 보장, SDK 워크스루), ranked-search eval 체크포인트(`search --eval`), Agent SDK(`@design-ai/cli/sdk`) — TypeScript 선언 + opt-in `learn.*` 로컬 쓰기 네임스페이스, public npm publish, provenance-backed GitHub Actions release, public registry smoke, Website Console MCP readiness, workspace learning restore/eval coverage, handoff bundle verification, 90%+ component coverage가 완료됐어요.
+전체 단계 로그는 [`docs/ROADMAP.md`](docs/ROADMAP.md), 현재 완료 범위는 [`docs/PRODUCT-READINESS.md`](docs/PRODUCT-READINESS.md)에서 확인하세요. 현재 **v4.63.0**: 도그푸드 루프 2회전(`flow-design`+`dashboard-design` 라우트, trust & safety 코퍼스, 디자인 지식 전용 recall, `pack` 바이트 예산 보장, SDK 워크스루), ranked-search eval 체크포인트(`search --eval`), Agent SDK(`@design-ai/cli/sdk`) — TypeScript 선언 + opt-in `learn.*` 로컬 쓰기 네임스페이스, public npm publish, provenance-backed GitHub Actions release, public registry smoke, Website Console MCP readiness, workspace learning restore/eval coverage, handoff bundle verification, 90%+ component coverage가 완료됐어요.
 
 핵심 디자인 컨설팅 워크플로우는 로컬 릴리스 기준으로 준비되어 있어요. 웹사이트 개선 컨트롤 타워는 zero-dependency static Web App과 `website-improvement` route/skill/command로 제공되고, Site Profile, audit checklist, MCP readiness, refactor prompt, handoff evidence tracking, bundle export/verify/repair를 한 번에 다뤄요. 로컬 학습 선호도는 `design-ai learn`으로 관리해요 — profile bootstrap, feedback 캡처, 읽기 전용 signal registry, 반복 QA 신호에서 만드는 skill 제안, 그리고 backup/restore/curate/audit까지 전부 로컬에서만 동작하는 opt-in 기능이에요. AI 모델 학습이나 fine-tuning은 여전히 현재 배포 범위 밖이에요.
 

package/README.md

@@ -3,7 +3,7 @@
 [![Audit](https://img.shields.io/badge/audit-passing-brightgreen)](https://github.com/sungjin9288/design-ai/actions/workflows/audit.yml)
 [![Docs](https://img.shields.io/badge/docs-live-indigo)](https://sungjin9288.github.io/design-ai/)
 [![Knowledge files](https://img.shields.io/badge/knowledge-95-blue)](knowledge/PRINCIPLES.md)
-[![Examples](https://img.shields.io/badge/examples-223-blue)](examples/README.md)
+[![Examples](https://img.shields.io/badge/examples-224-blue)](examples/README.md)
 [![Skills](https://img.shields.io/badge/skills-20-blue)](skills/README.md)
 
 > 🇺🇸 English / [🇰🇷 한국어](https://github.com/sungjin9288/design-ai/blob/main/README.ko.md)
@@ -12,7 +12,7 @@ A model-agnostic design knowledge base + skill system. Drop it in front of any A
 
 > **Not a model. Not a fine-tune.** A structured corpus of design expertise + agent-ready instructions that turn a general-purpose LLM into an expert.
 
-> **Distribution status, checked 2026-07-06:** local `npm run release:check` passes, GitHub Pages docs are live, GitHub Release `v4.62.0` is published, `@design-ai/cli@4.62.0` is public on npm (`latest`) with provenance, and the live `npm run registry:smoke` passes cleanly against `@design-ai/cli@4.62.0`. The Homebrew formula is pinned to `v4.62.0`, and `sungjin.design-ai-vscode@0.4.1` is public on the VS Code Marketplace. See [`docs/external-status.md`](docs/external-status.md).
+> **Distribution status, checked 2026-07-07:** local `npm run release:check` passes, GitHub Pages docs are live, GitHub Release `v4.63.0` is published, `@design-ai/cli@4.63.0` is public on npm (`latest`) with provenance, and the live `npm run registry:smoke` passes cleanly against `@design-ai/cli@4.63.0`. The Homebrew formula is pinned to `v4.63.0`, and `sungjin.design-ai-vscode@0.4.1` is public on the VS Code Marketplace. See [`docs/external-status.md`](docs/external-status.md).
 
 ## Coverage at a glance
 
@@ -214,7 +214,7 @@ Refresh refs/ on demand: `./tools/extractors/run-all.sh`.
 
 ## Status
 
-See [`docs/ROADMAP.md`](docs/ROADMAP.md) for the full phase log and [`docs/PRODUCT-READINESS.md`](docs/PRODUCT-READINESS.md) for the current completion boundary. Currently at **v4.62.0**: the closed dogfood loop (`flow-design` route, trust & safety corpus, design-knowledge-only recall, `pack` byte-budget guarantee, SDK walkthrough), the ranked-search eval checkpoint (`search --eval`), the Agent SDK (`@design-ai/cli/sdk`) with shipped TypeScript types and the opt-in `learn.*` local-write namespace, public npm publish, provenance-backed GitHub Actions release, public registry smoke, Website Console MCP readiness, workspace learning restore/eval coverage, handoff bundle verification, and 90%+ component coverage are complete.
+See [`docs/ROADMAP.md`](docs/ROADMAP.md) for the full phase log and [`docs/PRODUCT-READINESS.md`](docs/PRODUCT-READINESS.md) for the current completion boundary. Currently at **v4.63.0**: two dogfood-loop turns (`flow-design` + `dashboard-design` routes, trust & safety corpus, design-knowledge-only recall, `pack` byte-budget guarantee, SDK walkthrough), the ranked-search eval checkpoint (`search --eval`), the Agent SDK (`@design-ai/cli/sdk`) with shipped TypeScript types and the opt-in `learn.*` local-write namespace, public npm publish, provenance-backed GitHub Actions release, public registry smoke, Website Console MCP readiness, workspace learning restore/eval coverage, handoff bundle verification, and 90%+ component coverage are complete.
 
 Core design consulting workflows are locally release-ready. The website improvement control tower ships as a zero-dependency static Web App plus a `website-improvement` route/skill/command, covering Site Profiles, audit checklists, MCP readiness, refactor prompts, handoff evidence tracking, and bundle export/verify/repair. Local learning preferences are available through `design-ai learn` — profile bootstrap, feedback capture, a read-only signals registry, skill-proposal generation from repeated QA signals, and full backup/restore/curate/audit tooling, all local-only and opt-in. AI model training or fine-tuning remains outside the shipped scope.
 

package/cli/lib/check.mjs

@@ -417,6 +417,32 @@ const ROUTE_REQUIREMENTS = {
       ],
     },
   ],
+  "marketing-page": [
+    {
+      id: "marketing-conversion",
+      title: "Conversion and CTA evidence",
+      required: [
+        { label: "call to action", patterns: [/\bcta\b|\bcall.to.action\b/i, /전환|버튼 문구|행동 유도/] },
+        { label: "conversion reasoning", patterns: [/\bconversion\b/i, /전환율|전환/] },
+      ],
+    },
+    {
+      id: "marketing-visual-hierarchy",
+      title: "Visual hierarchy and fold coverage",
+      required: [
+        { label: "hierarchy or hero", patterns: [/\bhierarchy\b|\bhero\b/i, /위계|히어로/] },
+        { label: "fold or scroll order", patterns: [/\babove the fold\b/i, /폴드|스크롤 순서/] },
+      ],
+    },
+    {
+      id: "marketing-responsive-email",
+      title: "Responsive and email-client behavior coverage",
+      required: [
+        { label: "responsive or mobile", patterns: [/\bresponsive\b/i, /반응형|모바일/] },
+        { label: "email client behavior", patterns: [/\bemail client\b/i, /이메일 클라이언트|다크모드 대응/] },
+      ],
+    },
+  ],
 };
 
 function routeRequirementResult(routeId, requirement, text) {

package/cli/lib/examples.mjs

@@ -33,6 +33,7 @@ const ROUTE_EXAMPLE_QUERIES = {
   "stability-review": "dogfood findings release",
   "flow-design": "flow report block moderation onboarding",
   "dashboard-design": "dashboard settlement admin data table KPI",
+  "marketing-page": "landing hero pricing email template saas",
 };
 
 const ROUTE_CATEGORY_BOOSTS = {
@@ -57,6 +58,7 @@ const CANONICAL_ROUTE_EXAMPLES = {
   "slide-deck": ["examples/slide-deck-example.md"],
   "flow-design": ["examples/flow-design-report-block.md"],
   "dashboard-design": ["examples/dashboard-design-settlement.md"],
+  "marketing-page": ["examples/marketing-page-saas-landing.md"],
 };
 
 export function parseExamplesArgs(args) {

package/cli/lib/route.mjs

@@ -311,6 +311,26 @@ export const ROUTES = [
       // states-design brief outscores illustration's bare `빈 상태` hit. Kept compound
       // (not bare `상태`/`에러`/`빈`) to avoid hijacking other routes' bare terms.
       "에러 상태", "빈 상태 화면", "상태 설계", "검색 결과 없음", "empty state", "error state",
+      // Phase 768 (docs/ROUTE-COVERAGE-SWEEP.md): nine interaction-flow sweep classes
+      // (checkout, notifications, account, file-upload, collaboration, product-tour,
+      // search-filter, navigation, long-form) were zero/low/misrouted despite curated
+      // knowledge (search-ux.md, mobile-navigation.md, information-architecture.md,
+      // settings-page.md) reaching them through recall. `product tour` is kept as a
+      // compound even though it substring-contains design-from-brief's bare `product`,
+      // because the extra flow-design keyword hits on the same brief (온보딩, 투어,
+      // 코치마크) outweigh design-from-brief's single hit.
+      "체크아웃", "알림 센터", "계정 관리", "프로필 수정", "회원 탈퇴", "업로드", "드래그 앤 드롭",
+      "댓글", "멘션", "공유 권한", "코치마크", "투어", "필터", "정렬", "무한 스크롤",
+      "내비게이션", "하단 탭", "다단계",
+      "checkout", "notification center", "account management", "file upload", "drag and drop",
+      "comment thread", "mention", "coachmark", "product tour", "infinite scroll", "bottom tab",
+      "multi-step",
+      // Sweep long-form class (docs/ROUTE-COVERAGE-SWEEP.md): a multi-step form brief
+      // ("다단계 입력... 임시저장... 유효성 검증") tied against component-spec's bare
+      // `입력`/`폼` hits without these two. `임시저장` (save-draft) and `유효성 검증`
+      // (validation timing) are flow-specific signals distinct from a static
+      // component contract, and neither collides with any other route's keywords.
+      "임시저장", "유효성 검증",
     ],
   },
   {
@@ -336,6 +356,38 @@ export const ROUTES = [
       "대시보드", "정산", "매출 화면", "지표", "어드민", "백오피스", "데이터 테이블",
       "정산 내역", "KPI",
       "dashboard", "admin panel", "back-office", "back office", "analytics screen", "data table",
+      // Phase 768 (docs/ROUTE-COVERAGE-SWEEP.md): data-viz and rbac-admin sweep classes
+      // matched zero route keywords despite dedicated knowledge (chart-types.md,
+      // chart-color-encoding.md, realtime-data.md) already existing. Bare `chart` is
+      // safe (no other route claims it); `permissions matrix`/`role management` are
+      // compound so they don't hijack shorter generic terms from other routes.
+      "차트", "데이터 시각화", "시계열", "범례", "권한 관리", "역할 관리", "권한",
+      "chart", "data visualization", "time series", "legend", "permissions matrix", "role management",
+    ],
+  },
+  {
+    id: "marketing-page",
+    label: "Marketing page & campaign surface design",
+    command: null,
+    skills: ["skills/design-critique/SKILL.md", "skills/handoff-spec/SKILL.md"],
+    agents: ["agents/a11y-reviewer.md", "agents/design-critic.md"],
+    knowledge: [
+      "knowledge/patterns/landing-hero-design.md",
+      "knowledge/patterns/landing-page-patterns.md",
+      "knowledge/patterns/pricing-page-design.md",
+      "knowledge/patterns/email-design.md",
+      "knowledge/patterns/brand-identity.md",
+    ],
+    keywords: [
+      // Phase 768 (docs/ROUTE-COVERAGE-SWEEP.md): landing, pricing-page, and
+      // email-template sweep classes were zero-match or misrouted (landing fell
+      // through to handoff-spec via bare `개발자`; email-template misrouted to
+      // palette-from-brand via bare `다크모드`) despite dedicated knowledge files
+      // already existing. `랜딩 페이지` is compound because `website-improvement` owns
+      // bare `랜딩`; `히어로`/`히어로 섹션` are safe (no other route claims them).
+      "랜딩 페이지", "히어로", "히어로 섹션", "가격 페이지", "플랜 비교", "이메일 템플릿",
+      "CTA", "전환율",
+      "landing page", "pricing page", "hero section", "email template", "campaign page",
     ],
   },
 ];

package/docs/ROADMAP.md

@@ -1,5 +1,42 @@
 # Roadmap
 
+## Phase 769 — Route Coverage Sweep Release (v4.64.0) ✓ ready
+
+Ships the Phase 768 route-coverage sweep as an npm version: the `marketing-page` route with its worked example, the `dashboard-design` chart/permissions enrichment, and the `flow-design` nine-class keyword batch — 18/18 probed task classes now land on target routes at medium+ confidence. Additive and backward-compatible.
+
+### Verified
+- All 8 audits passed.
+- `npm run release:check` (unit tests, strict audits, whitespace, package contents, release metadata, release self-tests, packed-tarball smoke).
+- `npm run release:metadata`.
+- `git diff --check`.
+- Route eval 6/6; example-qa 22/22 routes; 18-class before/after probe in [ROUTE-COVERAGE-SWEEP.md](ROUTE-COVERAGE-SWEEP.md).
+- Main-branch GitHub Actions (`Design-AI audit`, `Deploy doc site`) passed for the constituent commits.
+
+### Versions
+- `package.json` + `.claude-plugin/plugin.json`: 4.63.0 → 4.64.0.
+- `vscode-extension/package.json`: remains 0.4.1.
+
+### What this enables
+- npm users get route coverage across the common product-design task space: marketing surfaces, data screens, and interaction flows all reach purpose-matched curation and checks instead of the design-system fallback.
+
+### What's still ahead
+- A future dogfood on browse/IA briefs to decide whether search/navigation deserve a dedicated route beyond flow-design keywords.
+- Next planning window per [NEXT-SURFACE-DECISION.md](NEXT-SURFACE-DECISION.md).
+
+## Phase 768 — Route coverage sweep (implemented, unreleased)
+
+Generalizes the two dogfood rounds' converged finding (route-table coverage is the recurring gap class) into one systematic batch: 18 common task classes probed through `route()`, 13 found low/misrouted/zero-match, all fixed at once. Full sweep tables and fix evidence in [ROUTE-COVERAGE-SWEEP.md](ROUTE-COVERAGE-SWEEP.md).
+
+### Delivered
+- [x] 18-class sweep probe at v4.63.0: 13 gaps, with the defining pattern that the knowledge corpus already covered nearly every weak class (pricing-page had dedicated knowledge yet scored 0) — the route table simply didn't connect briefs to it.
+- [x] New `marketing-page` route (`command: null`) consolidating landing/pricing/email-template: five dedicated knowledge files curated, conversion/hierarchy/responsive-email check requirements, `examples/marketing-page-saas-landing.md` at example-qa 12/12 (routes now 22/22).
+- [x] `dashboard-design` enrichment: chart/data-viz and permissions/role keywords (incl. bare `권한` for middle-dot forms like "권한·역할 관리") + `chart-types`, `chart-color-encoding`, `realtime-data` knowledge — data-viz and rbac-admin move from score 0 to medium.
+- [x] `flow-design` keyword batch for nine interaction classes (checkout, notifications, account, file-upload, collaboration, product-tour, search-filter, navigation, long-form incl. 임시저장/유효성 검증 tie-breakers) — keywords only; browse/IA knowledge reaches briefs via recall, with a dedicated route noted as the follow-up if dogfood shows curation mismatch.
+- [x] Post-fix probe: 18/18 classes land on target routes at medium+ where vocabulary allows; the previously-correct classes unchanged; no keyword hijacks (programmatically verified against every route's keyword set); route eval 6/6; both dogfood briefs keep their routes.
+
+### Remaining
+- [ ] Release: bundle into the next npm version.
+
 ## Phase 767 — Dogfood Round 2 Release (v4.63.0) ✓ ready
 
 Ships the dogfood loop's second turn (Phase 766) as an npm version: the `dashboard-design` route with data-screen check requirements and the settlement worked example, plus the `flow-design` Korean step-flow and states-design keyword depth verified in both directions. Additive and backward-compatible; route eval 6/6 and representative-brief routing unchanged.

package/docs/ROUTE-COVERAGE-SWEEP.md

@@ -0,0 +1,65 @@
+# Route coverage sweep (Phase 768)
+
+Two dogfood rounds converged on one recurring gap class: route-table coverage ([DOGFOOD-SDK-FINDINGS.md](DOGFOOD-SDK-FINDINGS.md), [DOGFOOD-DASHBOARD-FINDINGS.md](DOGFOOD-DASHBOARD-FINDINGS.md)). Instead of a third one-class round, this sweep enumerates 18 common product-design task classes, probes them all through `route()` in one batch, and fixes every gap at once.
+
+## Sweep results (2026-07-07, at v4.63.0)
+
+| Class | Routed to | Verdict |
+|---|---|---|
+| settings, a11y-audit, dark-mode, brand-identity | flow-design / design-review / design-from-brief / palette-from-brand, all `[medium]` | ✅ correct |
+| long-form (다단계 보험 가입 폼) | component-spec `[medium] 2` | ⚠️ marginal — a multi-step form flow fits flow-design better than a component spec |
+| checkout | design-from-brief `[low] 1` (flow-design 2nd at 1) | ❌ `체크아웃` not in any keyword set (`결제 플로우` doesn't substring-match "결제 체크아웃 플로우") |
+| notifications | flow-design `[low] 1` | ⚠️ right route, weak match (알림 센터 vocabulary missing) |
+| account | design-from-brief `[low] 1` | ❌ 계정 관리/프로필 수정/회원 탈퇴 unmatched |
+| file-upload | design-review `[low] 1` | ❌ 업로드/드래그 앤 드롭 unmatched |
+| collaboration | design-review `[low] 1` | ❌ 댓글/멘션/공유 권한 unmatched |
+| product-tour | flow-design `[low] 1` | ⚠️ right route, weak (코치마크/투어 missing) |
+| search-filter | design-review `[low] 1` | ❌ 필터/정렬/패싯 unmatched — despite `search-ux.md`, `list-and-feed.md` existing |
+| navigation | design-from-brief `[low] 1` | ❌ 내비게이션/하단 탭 unmatched — despite `mobile-navigation.md`, `information-architecture.md` existing |
+| data-viz | design-from-brief `[low] 0` | ❌ zero match — despite `chart-types.md`, `chart-color-encoding.md`, `realtime-data.md` existing |
+| rbac-admin | design-from-brief `[low] 0` | ❌ zero match — admin-permissions class |
+| landing | handoff-spec `[low] 1` (via `개발자`!) | ❌ misroute — despite `landing-hero-design.md`, `landing-page-patterns.md` existing |
+| pricing-page | design-from-brief `[low] 0` | ❌ zero match — despite `pricing-page-design.md` existing |
+| email-template | palette-from-brand `[low] 1` (via `다크모드`) | ❌ misroute — despite `email-design.md` existing |
+
+Pattern: the knowledge corpus already covers nearly every weak class — the route table simply doesn't connect briefs to it. 13 of 18 classes were low/misrouted/zero-match.
+
+## Fix plan (one batch)
+
+1. **New route `marketing-page`** — consolidates three zero/misrouted classes (landing, pricing-page, email-template) that share a marketing-surface character and have five dedicated knowledge files (`landing-hero-design`, `landing-page-patterns`, `pricing-page-design`, `email-design`, `brand-identity`). Keywords: 랜딩 페이지, 히어로, 가격 페이지, 플랜 비교, 이메일 템플릿, CTA + English forms. Check requirements: conversion/CTA evidence, visual-hierarchy evidence, responsive/email-client behavior. Worked example required (example-qa).
+   - _Done (2026-07-07): added `marketing-page` route in `cli/lib/route.mjs` (command: null, `skills/design-critique`, `skills/handoff-spec`, `agents/a11y-reviewer`, `agents/design-critic`, the five curated knowledge files above), `ROUTE_REQUIREMENTS["marketing-page"]` in `cli/lib/check.mjs` (conversion/CTA, visual-hierarchy/fold, responsive/email-client), worked example `examples/marketing-page-saas-landing.md` (12/12 on `check --route marketing-page`), wired into `cli/lib/examples.mjs` (`ROUTE_EXAMPLE_QUERIES` + `CANONICAL_ROUTE_EXAMPLES`) and `examples/README.md`. `tools/audit/smoke_assertions.py` `EXPECTED_ROUTE_CATALOG_IDS` += `marketing-page`. README/README.ko examples badge 223 → 224._
+2. **`dashboard-design` enrichment** — data-viz and rbac-admin are data-screen/admin classes: add 차트, 데이터 시각화, 시계열, 범례, 권한 관리, 역할 관리 (+ English) keywords, and add `chart-types.md`, `chart-color-encoding.md`, `realtime-data.md` to the curated knowledge.
+   - _Done (2026-07-07): keywords added in `cli/lib/route.mjs` (plus bare `권한`, needed because the rbac-admin brief uses a middle-dot form "권한·역할 관리" that the space-separated compound `권한 관리` doesn't substring-match). The three knowledge files were added to `dashboard-design.knowledge`._
+3. **`flow-design` keyword batch** — nine interaction classes (checkout, notifications, account, file-upload, collaboration, product-tour, search-filter, navigation, long-form): 체크아웃, 알림 센터, 계정 관리, 프로필 수정, 회원 탈퇴, 업로드, 드래그 앤 드롭, 댓글, 멘션, 공유 권한, 코치마크, 투어, 필터, 정렬, 무한 스크롤, 내비게이션, 하단 탭, 다단계 (+ English). Keywords only — the curated knowledge list stays at its current size; `search-ux`/`mobile-navigation`/`information-architecture`/`settings-page` reach these briefs through recall. If a future dogfood shows curation mismatch for browse/IA briefs, a dedicated route is the follow-up.
+   - _Done (2026-07-07): all listed keywords added to `flow-design.keywords` in `cli/lib/route.mjs`, verified collision-free against every other route's keyword set. Two extra keywords beyond the plan's literal list were needed to actually tip the long-form class over to flow-design (see Post-fix probe note below): `임시저장` and `유효성 검증`, both collision-free._
+
+Regression gates: route eval checkpoint stays all-pass; the well-routed five stay put; both prior dogfood briefs keep their routes/confidence; every existing route's representative brief unchanged; all 18 sweep briefs re-probed with the target outcomes recorded below.
+
+## Post-fix probe
+
+Re-probed with the same 18 briefs via `sweep.mjs` after the fix batch above landed:
+
+| Class | Routed to | Outcome |
+|---|---|---|
+| search-filter | flow-design `[medium] 3` (필터, 정렬, 무한 스크롤) | ✅ fixed — was design-review `[low] 1` |
+| checkout | flow-design `[medium] 2` (플로우, 체크아웃) | ✅ fixed — was design-from-brief `[low] 1` |
+| settings | flow-design `[medium] 2` (설정 화면, 알림 설정) | ✅ unchanged (already correct pre-fix) |
+| landing | marketing-page `[medium] 3` (랜딩 페이지, 히어로, CTA) | ✅ fixed — was handoff-spec `[low] 1` misroute |
+| long-form | flow-design `[medium] 3` (다단계, 임시저장, 유효성 검증) | ✅ fixed (intended move) — was component-spec `[medium] 2` |
+| notifications | flow-design `[medium] 2` (알림 설정, 알림 센터) | ✅ fixed — was flow-design `[low] 1` (weak match) |
+| account | flow-design `[medium] 3` (계정 관리, 프로필 수정, 회원 탈퇴) | ✅ fixed — was design-from-brief `[low] 1` |
+| data-viz | dashboard-design `[medium] 3` (차트, 시계열, 범례) | ✅ fixed — was design-from-brief `[low] 0` (zero match) |
+| navigation | flow-design `[medium] 2` (내비게이션, 하단 탭) | ✅ fixed — was design-from-brief `[low] 1` |
+| rbac-admin | dashboard-design `[medium] 2` (역할 관리, 권한) | ✅ fixed — was design-from-brief `[low] 0` (zero match) |
+| file-upload | flow-design `[medium] 2` (업로드, 드래그 앤 드롭) | ✅ fixed — was design-review `[low] 1` |
+| collaboration | flow-design `[medium] 3` (댓글, 멘션, 공유 권한) | ✅ fixed — was design-review `[low] 1` |
+| pricing-page | marketing-page `[medium] 2` (가격 페이지, 플랜 비교) | ✅ fixed — was design-from-brief `[low] 0` (zero match) |
+| email-template | marketing-page `[medium] 2` (이메일 템플릿, CTA) | ✅ fixed — was palette-from-brand `[low] 1` misroute |
+| a11y-audit | design-review `[medium] 2` (감사, 접근성) | ✅ unchanged (already correct pre-fix) |
+| dark-mode | design-from-brief `[medium] 2` (디자인 시스템, 토큰) | ✅ unchanged (already correct pre-fix) |
+| brand-identity | palette-from-brand `[medium] 2` (컬러, 팔레트) | ✅ unchanged (already correct pre-fix) |
+| product-tour | flow-design `[medium] 3` (온보딩, 코치마크, 투어) | ✅ fixed — was flow-design `[low] 1` (weak match) |
+
+All 18 classes land on their target route at medium+ confidence. Zero regressions on the five previously-✅ classes. `long-form` completed its intended move from `component-spec` to `flow-design`.
+
+Regression gates re-run after the fix, all green: route eval checkpoint (`--eval --strict`, 6/6 pass); both dogfood briefs (report/block → flow-design `[high] 4`; settlement → dashboard-design `[medium] 2`); representative briefs for design-system, component, palette, website, motion, illustration all unchanged; `npm test` (586/586); `npm run audit` (8/8, example-qa 22/22 routes and 22/22 examples); `npm run release:metadata`; `npm run package:smoke`; `npm run registry:smoke:self-test`; `npm run ci:local`.

package/docs/external-status.md

@@ -1,29 +1,29 @@
 # External Publication Status
 
-> Checked: 2026-07-06
+> Checked: 2026-07-07
 > Scope: npm registry, GitHub Pages, Homebrew tap, VS Code Marketplace, Claude/Codex MCP
 
 ## Summary
 
-npm is publicly published at `@design-ai/cli@4.62.0` (npm dist-tag `latest` = `4.62.0`); publish run from tag `v4.62.0` succeeded with provenance and all pre-publish gates green. This release ships the closed dogfood loop: the `flow-design` route, the trust & safety corpus file and worked example, the recall-injection exclusion of `docs/` (design-knowledge-only recall), the `pack` UTF-8 byte-budget fix, and the Agent SDK walkthrough (en/ko). The live `npm run registry:smoke` passes cleanly against published `@design-ai/cli@4.62.0` ("Registry smoke passed"), covering the retrieval surfaces (index/ranked/embeddings/recall) and route enrichment. GitHub Release `v4.62.0` is published, and the Homebrew tap formula points at the `v4.62.0` release source tarball with a verified SHA-256. The VS Code extension `sungjin.design-ai-vscode` remains published at `0.4.1`. GitHub Pages docs are publicly reachable.
+npm is publicly published at `@design-ai/cli@4.63.0` (npm dist-tag `latest` = `4.63.0`); publish run from tag `v4.63.0` succeeded with provenance and all pre-publish gates green. This release ships the dogfood loop's second turn: the `dashboard-design` route (data-dense screen class with money-format/table-a11y/density check requirements) with its settlement worked example, and `flow-design` keyword depth (Korean step-flow vocabulary + states-design compounds, verified in both directions against the illustration route). The live `npm run registry:smoke` passes cleanly against published `@design-ai/cli@4.63.0` ("Registry smoke passed"), covering the retrieval surfaces (index/ranked/embeddings/recall) and route enrichment. GitHub Release `v4.63.0` is published, and the Homebrew tap formula points at the `v4.63.0` release source tarball with a verified SHA-256. The VS Code extension `sungjin.design-ai-vscode` remains published at `0.4.1`. GitHub Pages docs are publicly reachable.
 
 ## Results
 
 | Surface | Checked target | Result | Evidence |
 |---|---|---|---|
-| npm registry | `@design-ai/cli` | Published latest is `4.62.0` (tag `v4.62.0`, provenance). Pre-publish packed-tarball smoke (incl. SDK import + `learn.remember` write) and live `npm run registry:smoke` both pass for `@design-ai/cli@4.62.0`. | `npm view @design-ai/cli version` → `4.62.0`; live registry smoke "Registry smoke passed" |
+| npm registry | `@design-ai/cli` | Published latest is `4.63.0` (tag `v4.63.0`, provenance). Pre-publish packed-tarball smoke (incl. SDK import + `learn.remember` write) and live `npm run registry:smoke` both pass for `@design-ai/cli@4.63.0`. | `npm view @design-ai/cli version` → `4.63.0`; live registry smoke "Registry smoke passed" |
 | GitHub Pages | `https://sungjin9288.github.io/design-ai/` | Published and reachable: HTTP `200`, design-ai MkDocs page rendered | `evidence/cli-logs/github-pages-status.log` |
-| Homebrew tap | `Formula/design-ai.rb` | Formula pinned to `v4.62.0` release source tarball with SHA-256 `bb56b461359b4d94b5f2dd99d8f068364290d0b52469c75599725bd1ca78659f` (recomputed from the published tag tarball) | `Formula/design-ai.rb` |
+| Homebrew tap | `Formula/design-ai.rb` | Formula pinned to `v4.63.0` release source tarball with SHA-256 `024a720cfe1a18a1b77751232818f01d9a2826fac4772865b889bd3d91ce1ae8` (recomputed from the published tag tarball) | `Formula/design-ai.rb` |
 | VS Code Marketplace | `sungjin.design-ai-vscode` | Published: run `28431571256` published `v0.4.1`, and the Marketplace Gallery API returned visible version `0.4.1` on 2026-07-02. | `evidence/cli-logs/vscode-marketplace-status.log`, `evidence/cli-logs/vscode-marketplace-secret-status.log`, `evidence/cli-logs/vscode-extension-vsce-package.log`, `evidence/cli-logs/vscode-publish-workflow-status.log` |
-| GitHub Release | `v4.62.0` | Published for tag `v4.62.0` at commit `751c84d` | `gh release view v4.62.0` |
-| MCP server | `@design-ai/cli@4.62.0` / local clone | Public npm `design-ai-mcp` responds to initialize and tools/list with 10 tools; local Codex and Claude Code both report `design-ai` MCP as configured and connected. | `evidence/cli-logs/npm-registry-smoke.log`, `evidence/cli-logs/design-ai-mcp-client-status.log` |
+| GitHub Release | `v4.63.0` | Published for tag `v4.63.0` at commit `d6ce680` | `gh release view v4.63.0` |
+| MCP server | `@design-ai/cli@4.63.0` / local clone | Public npm `design-ai-mcp` responds to initialize and tools/list with 10 tools; local Codex and Claude Code both report `design-ai` MCP as configured and connected. | `evidence/cli-logs/npm-registry-smoke.log`, `evidence/cli-logs/design-ai-mcp-client-status.log` |
 
 ## Interpretation
 
 - The repository is locally release-ready based on `npm run release:check`.
 - GitHub Pages docs can now be described as publicly deployed.
-- Public npm install can now be described as published and smoke-tested at `4.62.0`.
-- Homebrew tap install can now be described as pinned to the `v4.62.0` release tarball; full tap audit/install/test remains a maintainer-side verification step because this Homebrew version rejects path-based `brew audit Formula/...` calls.
+- Public npm install can now be described as published and smoke-tested at `4.63.0`.
+- Homebrew tap install can now be described as pinned to the `v4.63.0` release tarball; full tap audit/install/test remains a maintainer-side verification step because this Homebrew version rejects path-based `brew audit Formula/...` calls.
 - VS Code Marketplace can now be described as published and publicly reachable at version `0.4.1`.
 - Claude Code and Codex can now be described as locally connected to the clone-backed `design-ai` MCP server, while public npm users can verify the published `design-ai-mcp` entrypoint from a clean working directory.
 
@@ -32,12 +32,12 @@ npm is publicly published at `@design-ai/cli@4.62.0` (npm dist-tag `latest` = `4
 ```bash
 npm view @design-ai/cli version name time.modified dist-tags --json
 curl -sS -L -o /tmp/design-ai-pages.html -w 'http_code=%{http_code}\nurl_effective=%{url_effective}\n' https://sungjin9288.github.io/design-ai/
-curl -sL https://github.com/sungjin9288/design-ai/archive/refs/tags/v4.62.0.tar.gz | shasum -a 256
+curl -sL https://github.com/sungjin9288/design-ai/archive/refs/tags/v4.63.0.tar.gz | shasum -a 256
 ruby -c Formula/design-ai.rb
 brew style Formula/design-ai.rb
-gh release view v4.62.0 --repo sungjin9288/design-ai --json tagName,isDraft,isPrerelease,publishedAt,name,url,assets
+gh release view v4.63.0 --repo sungjin9288/design-ai --json tagName,isDraft,isPrerelease,publishedAt,name,url,assets
 gh run view 28569283984 --repo sungjin9288/design-ai --json status,conclusion,name,url,createdAt,updatedAt
-npm exec --yes --package=@design-ai/cli@4.62.0 -- design-ai-mcp
+npm exec --yes --package=@design-ai/cli@4.63.0 -- design-ai-mcp
 codex mcp get design-ai
 claude mcp list
 curl -sS -H 'Content-Type: application/json' \

package/examples/README.md

@@ -247,6 +247,12 @@ Worked outputs from each skill — what "good" looks like. Use as reference when
 | --- | --- | --- |
 | [dashboard-design-settlement.md](dashboard-design-settlement.md) | `design-critique` / `handoff-spec` (`dashboard-design` route) | Seller settlement dashboard. KPI strip + table-first layout, Korean amount/number formatting, table accessibility (caption, header scope, aria-sort), density + responsive degradation, export/alert edge cases. |
 
+### Marketing page & campaign surface specs
+
+| File | Skill | Demonstrates |
+| --- | --- | --- |
+| [marketing-page-saas-landing.md](marketing-page-saas-landing.md) | `design-critique` / `handoff-spec` (`marketing-page` route) | Developer-tool SaaS landing page. Hero archetype selection, above-the-fold section sequencing, pricing plan comparison, Korean trust/CTA copy, email-client-safe responsive behavior. |
+
 ### End-to-end deliverables
 
 | File | Skill | Demonstrates |

package/examples/marketing-page-saas-landing.md

@@ -0,0 +1,97 @@
+<!-- hand-written -->
+# Worked example: developer-tool SaaS landing page design
+
+> Generated by the `marketing-page` route (`skills/design-critique`, `skills/handoff-spec`). Demonstrates the canonical marketing-surface spec format — hero archetype selection, section sequence with above-the-fold reasoning, pricing/plan comparison, testimonial trust elements, CTA copy strategy, and email-client-safe responsive behavior. Adapted from the sweep brief in [`docs/ROUTE-COVERAGE-SWEEP.md`](../docs/ROUTE-COVERAGE-SWEEP.md) (Phase 768, `landing` class).
+
+**Brief**: 개발자 도구 SaaS 랜딩 페이지 설계 — 히어로, 기능 소개, 가격, 후기, CTA 배치.
+
+Cite [`knowledge/patterns/landing-hero-design.md`](../knowledge/patterns/landing-hero-design.md) (hero archetype selection and 5-second comprehension test), [`knowledge/patterns/landing-page-patterns.md`](../knowledge/patterns/landing-page-patterns.md) (section sequencing and above-the-fold structure), [`knowledge/patterns/pricing-page-design.md`](../knowledge/patterns/pricing-page-design.md) (plan comparison and toggle patterns), [`knowledge/patterns/email-design.md`](../knowledge/patterns/email-design.md) (email-client-safe markup for the trial-confirmation follow-up), and [`knowledge/patterns/brand-identity.md`](../knowledge/patterns/brand-identity.md) (voice and color-token consistency across the surface) as the grounding for this spec.
+
+---
+
+```markdown
+# 개발자 도구 SaaS 랜딩 페이지 스펙
+
+> 근거: knowledge/patterns/landing-hero-design.md, knowledge/patterns/landing-page-patterns.md,
+> knowledge/patterns/pricing-page-design.md, knowledge/patterns/email-design.md,
+> knowledge/patterns/brand-identity.md, knowledge/PRINCIPLES.md
+
+## 1. 히어로 섹션 (Above the fold)
+
+- **아키타입 선택**: 텍스트 주도형(text-led) 히어로. 개발자 도구는 스크린샷보다 "무엇을, 왜, 어떻게"를 5초 안에 전달하는 문장이 전환에 더 크게 기여한다(시각 주도형은 별도 기능 섹션에서 다룬다).
+- **헤드라인**: "배포 파이프라인, 코드 3줄로 끝내세요" — 문제(느린 배포)와 해결(3줄 설정)을 동시에 전달. 서브헤드라인은 대상 독자(백엔드 팀)를 명시.
+- **CTA 배치**: Primary CTA "무료로 시작하기"(신용카드 불필요 명시) + Secondary "라이브 데모 보기". 위계: Primary는 브랜드 accent 색 + 굵은 버튼 문구, Secondary는 outline 스타일로 시각적 종속 관계를 명확히 한다.
+- **스크롤 순서(위계)**: 히어로 → 신뢰 로고 스트립(사용 중인 기업 로고, 폴드 바로 아래) → 기능 3종 → 후기 → 가격 → 최종 CTA. 폴드 위(above the fold)에는 헤드라인·서브헤드·CTA·최소 1개 시각 자료만 배치하고 기능 나열은 폴드 아래로 미룬다.
+- 히어로 시각 자료는 실제 터미널/대시보드 스크린샷 또는 코드 스니펫 애니메이션(자동재생 무음, 3초 루프)을 사용하고, 정적 이미지로도 동일 정보를 전달하는 대체 텍스트를 제공한다.
+
+## 2. 기능 소개 섹션
+
+- 3열 그리드(데스크톱), 각 카드: 아이콘 + 소제목(동사형, 예: "자동으로 롤백하세요") + 1문장 설명 + "더 알아보기" 텍스트 링크.
+- 기능 카드의 시각 위계는 아이콘 > 소제목 > 설명 순으로, 소제목이 헤드라인보다 한 단계 작은 타이포 스케일을 사용해 히어로와의 종속 관계를 유지한다.
+- 각 기능 카드는 실제 제품 스크린샷을 근거로 하며, 추상 일러스트로 대체하지 않는다(개발자 대상 제품은 실물 UI가 신뢰를 만든다).
+
+## 3. 가격 페이지 섹션
+
+- 3단 플랜 비교: Free / Pro / Enterprise. 월/연 토글 기본값은 연간(할인율 뱃지 "2개월 무료" 병기), 토글 전환 시 가격 숫자만 즉시 갱신되고 페이지 스크롤 위치는 유지된다.
+- Pro 플랜 카드는 "가장 인기" 뱃지 + 테두리 강조로 시각 위계를 부여하되, 나머지 플랜과 동일한 카드 구조(기능 체크리스트, CTA 버튼)를 유지한다.
+- Enterprise 플랜의 CTA는 가격 대신 "영업팀에 문의하기"로 대체하고, 클릭 시 문의 폼 모달을 연다(신용카드 입력 흐름과 분리).
+- 플랜별 기능 체크리스트는 표 형태로 정렬해 스캔 가능하게 하고, 각 행에 툴팁으로 기능 설명을 보강한다. FAQ 아코디언을 가격 표 바로 아래 배치.
+
+## 4. 후기 및 신뢰 요소 (한국형 신뢰 신호)
+
+- 후기 카드 3~4개: 실명 대신 "직책 + 회사명"(예: "백엔드 리드, OO테크") 표기 — 개인정보 노출 최소화와 신뢰 확보를 병행. 실제 도입 기업 로고 병기.
+- **한국형 신뢰 요소**: 사업자 정보(상호, 대표자, 사업자등록번호, 통신판매업 신고번호)를 푸터에 명시하고, 결제 수단 아이콘(카카오페이, 토스페이, 카드사 로고)을 가격 섹션 하단에 노출해 결제 신뢰를 보강한다.
+- 정량 지표 스트립("설치 도구 12,000개 팀 사용 중", "평균 배포 시간 40% 단축")을 후기 섹션 상단에 배치해 정성 후기 전에 정량 신뢰를 먼저 전달한다.
+- 후기 인용문은 자동 캐러셀로 넘기지 않고 정적 그리드로 고정한다 — 자동 전환 캐러셀은 후기를 끝까지 읽기 전에 사라져 신뢰 신호로서의 가치를 잃는다.
+
+## 5. CTA 문구 전략과 전환율
+
+- **한국형 CTA 문구**: "무료로 시작하기"(행동 유도 + 무비용 강조), "지금 데모 예약하기"(긴급성), "영업팀에 문의하기"(Enterprise). 영어 원문 그대로("Get Started", "Sign Up")를 직역하지 않고 한국 사용자에게 익숙한 행동 유도 어휘를 사용한다.
+- 전환율을 높이기 위해 Primary CTA는 페이지당 반복 배치(히어로, 기능 섹션 하단, 가격 섹션, 최종 CTA 섹션) — 단, 같은 문구를 반복하지 않고 맥락별로 변주한다("무료로 시작하기" → "지금 무료로 시작하기" → "5분 만에 시작하기").
+- 최종 CTA 섹션은 배경색을 전환해(라이트 배경 페이지 중간에 브랜드 accent 배경) 스크롤 종료 지점에서 재진입 지점임을 시각적으로 신호한다.
+- 신규 가입 완료 후 발송되는 트라이얼 확인 이메일은 CTA 버튼을 bulletproof 버튼(VML + padding 기반, 이미지 배경 아님)으로 구현해 Outlook 데스크톱에서도 클릭 가능한 버튼으로 렌더링되도록 한다.
+
+## 6. 반응형 동작과 이메일 클라이언트 대응
+
+- **Desktop (1280px+)**: 히어로 텍스트/시각 50-50 분할, 기능 3열 그리드, 가격 3단 나란히 배치.
+- **Tablet (768–1024px)**: 히어로는 텍스트 우선 단일 컬럼 + 시각 자료 아래 배치, 기능 2열 그리드, 가격 3단 유지하되 카드 폭 축소.
+- **Mobile (360–430px)**: 모든 섹션 단일 컬럼 스택. 가격 플랜은 세로 스와이프 캐러셀로 전환하되 Pro 플랜이 기본 노출 카드가 되도록 스냅한다. Primary CTA는 하단 고정(sticky) 바로 전환해 스크롤 중에도 항상 접근 가능하게 한다.
+- **이메일 클라이언트 대응**: 트라이얼 확인 이메일은 600px 고정폭 테이블 기반 레이아웃(div/flexbox 미사용), 다크모드 대응(투명 배경 로고 SVG 대신 PNG + 명시적 배경색 지정으로 Gmail/Outlook 다크모드에서 반전 깨짐 방지), Outlook에서 CSS `background-image` 미지원을 고려해 배경색을 fallback으로 반드시 지정한다.
+
+## 접근성
+
+- CTA 버튼은 색상 대비 최소 **4.5:1 contrast ratio**(WCAG AA)를 확보하며, accent 배경 위 버튼 텍스트도 동일 기준을 적용한다.
+- 모든 CTA와 링크는 키보드 Tab 순회로 도달 가능해야 하며, 포커스 상태는 `focus-visible` 아웃라인으로 명시한다. 가격 토글(월/연)은 `role="switch"` + `aria-checked`로 마크업.
+- 히어로 배경 영상/애니메이션은 `prefers-reduced-motion` 대응 정적 대체 이미지를 제공하고, 자동재생 콘텐츠에는 일시정지 컨트롤을 노출한다.
+- 스크린 리더: 신뢰 로고 스트립과 후기 회사 로고는 `alt` 텍스트로 회사명을 명시하고, 순수 장식 아이콘은 `aria-hidden="true"` 처리한다.
+- 가격 표는 `<caption>`과 `scope="col"` 헤더를 사용해 스크린 리더 사용자도 플랜별 기능을 표로 탐색할 수 있게 한다.
+
+## Don't
+
+- Don't: 폴드 위에 기능 목록까지 욱여넣지 않는다 — 헤드라인·서브헤드·CTA·시각 자료 이상은 스크롤 아래로 미룬다.
+- Don't: 가격 토글 전환 시 페이지를 스크롤 상단으로 리셋하지 않는다 — 사용자의 비교 흐름을 끊는다.
+- Don't: 후기를 자동 캐러셀로 빠르게 넘기지 않는다 — 신뢰 신호를 읽기도 전에 사라진다.
+- Don't: CTA 문구를 페이지 전체에서 동일하게 반복하지 않는다 — 맥락별 변주 없는 반복은 클릭 유인 효과가 떨어진다.
+- Avoid: 트라이얼 이메일에 이미지 배경 버튼을 사용하는 것 — Outlook 데스크톱에서 배경 이미지가 렌더링되지 않아 버튼이 사라진다.
+```
+
+---
+
+## Why this is a good marketing-page example
+
+- **Conversion/CTA evidence is explicit and layered** — CTA 배치 위계(Primary/Secondary), 반복 배치 전략, 맥락별 문구 변주, 전환율 근거, matching `route --check marketing-page`'s conversion requirement.
+- **Visual hierarchy is concrete** — hero archetype selection, above-the-fold section sequencing (폴드/스크롤 순서), typographic subordination between headline/subhead/feature titles, matching the visual-hierarchy requirement.
+- **Responsive and email-client behavior are both covered** — three breakpoints for the page itself, plus a dedicated email-client section (bulletproof buttons, 다크모드 대응, Outlook background-image fallback), matching the responsive/email-client requirement.
+- **Grounding is load-bearing** — every section traces back to `landing-hero-design.md`, `landing-page-patterns.md`, `pricing-page-design.md`, or `email-design.md`, cited in the header.
+- **Korean specifics are concrete, not decorative** — 한국형 CTA 문구 rationale, 사업자 정보 신뢰 요소, 카카오페이/토스페이 결제 아이콘, 고객 후기 신뢰 요소 (직책+회사명 표기, 정량 지표 선행 배치).
+- **Accessibility is concrete** — explicit 4.5:1 contrast ratio, `focus-visible`, `prefers-reduced-motion`, `aria-hidden`, table `<caption>`/`scope="col"` for the pricing table.
+- **A Don't section closes the spec** — five concrete anti-patterns, each tied back to a rule stated earlier.
+
+## Cross-reference
+
+- [`knowledge/patterns/landing-hero-design.md`](../knowledge/patterns/landing-hero-design.md) — hero archetype selection and 5-second comprehension test
+- [`knowledge/patterns/landing-page-patterns.md`](../knowledge/patterns/landing-page-patterns.md) — section sequencing and above-the-fold structure
+- [`knowledge/patterns/pricing-page-design.md`](../knowledge/patterns/pricing-page-design.md) — plan comparison, toggle, and FAQ patterns reused above
+- [`knowledge/patterns/email-design.md`](../knowledge/patterns/email-design.md) — bulletproof button and dark-mode-safe email markup for the trial-confirmation flow
+- [`knowledge/patterns/brand-identity.md`](../knowledge/patterns/brand-identity.md) — voice and token consistency guidance applied to CTA copy and color accents
+- [`docs/ROUTE-COVERAGE-SWEEP.md`](../docs/ROUTE-COVERAGE-SWEEP.md) — the sweep (Phase 768, `landing` class) this example is adapted from

package/knowledge/COVERAGE.md

@@ -1,7 +1,7 @@
 <!-- generated by tools/audit/check-coverage.py — do not hand-edit -->
 ---
 title: Design-AI coverage report
-generated_at: 2026-07-06
+generated_at: 2026-07-07
 ---
 
 # Coverage report
@@ -14,7 +14,7 @@ generated_at: 2026-07-06
 | --- | --- | --- |
 | Knowledge files | 95 | 80 hand-written + 15 generated |
 | Skills (PLAYBOOK + SKILL) | 20 | 20 with verification phase |
-| Worked examples | 223 | |
+| Worked examples | 224 | |
 | Extractors | 12 | |
 | Canonical components | 200 | indexed across Ant / MUI / shadcn |
 | Components with worked spec | 181 | **90.5% spec coverage** (16 via parent/alias specs) |
@@ -49,7 +49,7 @@ generated_at: 2026-07-06
 
 | File | Lines | Type | Title |
 | --- | --- | --- | --- |
-| [knowledge/COVERAGE.md](../knowledge/COVERAGE.md) | 746 | generated | Coverage report |
+| [knowledge/COVERAGE.md](../knowledge/COVERAGE.md) | 747 | generated | Coverage report |
 | [knowledge/PRINCIPLES.md](../knowledge/PRINCIPLES.md) | 108 | hand-written | Design-AI principles |
 
 #### a11y
@@ -476,6 +476,7 @@ generated_at: 2026-07-06
 | [examples/dogfood-korean-fintech-system.md](../examples/dogfood-korean-fintech-system.md) | 433 | Dogfood: Korean fintech mobile app — design system bootstrap |
 | [examples/email-transactional-example.md](../examples/email-transactional-example.md) | 259 | Worked example: transactional email (Korean fintech) |
 | [examples/flow-design-report-block.md](../examples/flow-design-report-block.md) | 141 | Worked example: report & block flow design |
+| [examples/marketing-page-saas-landing.md](../examples/marketing-page-saas-landing.md) | 97 | Worked example: developer-tool SaaS landing page design |
 | [examples/palette-saas-violet.md](../examples/palette-saas-violet.md) | 235 | Palette: B2B SaaS — violet primary |
 | [examples/print-business-card-spec.md](../examples/print-business-card-spec.md) | 205 | Print spec: business card (Korean 명함, premium tier) |
 | [examples/print-packaging-spec.md](../examples/print-packaging-spec.md) | 285 | Print spec: folding carton (Korean cosmetics, mid-tier) |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@design-ai/cli",
-  "version": "4.63.0",
+  "version": "4.64.0",
   "description": "Senior product designer for any AI coding agent. Installs design-ai (20 skills, 17 commands, 4 agents) into Claude Code globally. Korean market depth plus website improvement control tower.",
   "bin": {
     "design-ai": "cli/bin/design-ai.mjs",

package/tools/audit/smoke_assertions.py

@@ -690,6 +690,7 @@ EXPECTED_ROUTE_CATALOG_IDS = (
     "stability-review",
     "flow-design",
     "dashboard-design",
+    "marketing-page",
 )
 EXPECTED_PROMPT_SLASH_COMMAND = "/design-component-spec"
 EXPECTED_PROMPT_QUALITY_COMMAND = "design-ai check output.md --route component-spec --strict"