@design-ai/cli 4.55.0

package/docs/WEBSITE-IMPROVEMENT.ko.md

@@ -0,0 +1,75 @@
+# Website Improvement Control Tower
+
+`website-improvement`는 기존 웹사이트 개선 작업을 준비하고 관리하는 로컬 컨트롤 타워입니다. 이 repo는 대상 사이트의 소스 코드를 포함하거나 수정하지 않고, 진단 구조, 체크리스트, MCP readiness, Codex/Claude용 프롬프트, handoff report를 관리합니다.
+
+## Web App
+
+정적 앱은 [`docs/website-console/index.html`](website-console/index.html)에 있습니다. 별도 build나 dependency 없이 브라우저에서 열 수 있고, 상태는 `localStorage`에 저장됩니다.
+
+첫 실제 회사 사이트 pilot은 [회사 웹사이트 Intake Template](COMPANY-WEBSITE-INTAKE-TEMPLATE.ko.md)을 채운 뒤, 대상 repo를 열기 전에 [회사 웹사이트 Dogfood Runbook](COMPANY-WEBSITE-DOGFOOD.ko.md)을 따릅니다.
+
+주요 섹션:
+
+| 섹션 | 역할 |
+|---|---|
+| Site Profile | 사이트 이름, live URL, repo/local path, Figma, brand notes, pages, user flows, viewport를 정리 |
+| Audit Checklist | visual design, UX flow, responsive, accessibility, performance, SEO, technical quality, runtime issues, content quality 점검 |
+| MCP Readiness Matrix | GitHub, Figma, Browser, DevTools, Deploy, Sentry, DB, CMS, 협업, 리서치 연결 필요도를 표시 |
+| Workflow Graph | workspace, profile, audit, MCP, task, prompt, handoff, bundle, target repo node와 deterministic edge를 시각화하고 graph JSON을 export |
+| Refactor Plan | finding을 실제 task, priority, Codex prompt, verification, risk로 변환 |
+| Prompt Generator | Codex/Claude에 넘길 8개 prompt template 생성 |
+| Handoff Report | 실행한 작업, 검증 결과, 남은 리스크, 다음 작업을 기록하고 Markdown report로 정리 |
+| Operator Runbook | `design-ai site <bundle-dir> --bundle-handoff --json` 결과를 import해 runbook metadata source pill, source-bundle provenance/detail review, copy-ready source-bundle source marker, source-bundle artifact-specific action label, revalidation gate JSON action label, source-bundle revalidation metadata badge와 badge row, warning, Markdown gate, source/diagnostic context를 보존하는 gate-only JSON copy/export/import, focused provenance import source refresh, exported compact source marker, Markdown source marker, source-aware empty runbook Markdown, provenance-only notice source marker, JSON gate reason metadata, focused source-bundle JSON import, provenance-only review state와 Markdown marker, guarded copy-ready strict source command, source-bundle Markdown/JSON copy/export, task/command provenance chip, stage metric, resettable action/evidence row filter, status index, evidence progress, copy-ready stage row, row-level Markdown copy/export와 line copy, guarded filtered/full Markdown export, guarded next-line copy action을 검토 |
+
+브라우저에서 기록한 `implementationEvidence`는 JSON export 뒤에도 유지됩니다. `design-ai site --json`은 evidence count를 보고하고, `--tasks`는 evidence block을 보존하며, `--report`와 `--bundle`은 실행 작업 / 검증 결과 / 남은 리스크 / 다음 작업을 handoff artifact에 반영합니다.
+
+## Boundary
+
+MVP에서 하지 않는 것:
+
+- 자동 crawling, Lighthouse, axe, visual diff, screenshot capture
+- MCP 직접 연결이나 외부 시스템 write
+- 대상 웹사이트 repo 코드 수정
+- backend API, auth, multi-user sync
+- embeddings, fine-tuning, background learning
+
+## CLI / Skill
+
+라우팅과 프롬프트 생성은 다음처럼 사용할 수 있습니다.
+
+```bash
+design-ai site --intake-template --out company-website-intake.md
+design-ai site --intake-template --language ko --out company-website-intake.ko.md
+design-ai site --from-intake company-website-intake.ko.md --out website-workspace.json
+design-ai site --from-intake company-website-intake.ko.md --next-actions --out website-next-actions.md
+design-ai site --from-intake company-website-intake.ko.md --bundle --out website-handoff-bundle
+design-ai route "improve website UX SEO performance" --json
+design-ai prompt "improve homepage conversion" --route website-improvement --json
+design-ai check examples/website-improvement-report.md --route website-improvement --strict
+design-ai site --sample --out website-workspace.json
+design-ai site website-workspace.json --tasks --out website-workspace.tasks.json
+design-ai site website-workspace.json --json
+design-ai site website-workspace.json --mcp-check --strict --json
+design-ai site website-workspace.json --mcp-check --probes --json
+design-ai site website-workspace.json --mcp-plan --out mcp-action-plan.md
+design-ai site website-workspace.json --next-actions --json
+design-ai site website-workspace.json --next-actions --out website-next-actions.md
+design-ai site website-workspace.json --graph --json --out website-workflow-graph.json
+design-ai site website-workspace.json --bundle --out website-handoff-bundle
+design-ai site website-handoff-bundle --bundle-check --strict --json
+design-ai site website-handoff-bundle --bundle-compare website-handoff-bundle.previous --strict --json
+design-ai site website-handoff-bundle --bundle-handoff --strict --json --out target-repo-handoff.json --force
+design-ai site website-handoff-bundle --bundle-handoff --strict --out target-repo-handoff.md
+design-ai site website-workspace.json --report --out website-handoff.md
+design-ai site website-workspace.json --prompts --out website-prompts.md
+design-ai site website-workspace.json --prompt codex-implementation --out codex-implementation.md
+design-ai site website-workspace.json --prompt codex-implementation --task task-accessibility --out task-accessibility.md
+```
+
+`design-ai site --intake-template --language ko`는 한국어 content를 생성하고, `design-ai site --intake-template`은 문서에 있는 blank 회사 사이트 intake Markdown form을 CLI에서 바로 생성합니다. `--json`을 붙이면 template metadata, privacy boundary, 추천 후속 command, Markdown content를 하나의 payload로 받을 수 있습니다. `design-ai site --from-intake company-website-intake.ko.md`는 작성 완료된 영어 또는 한국어 intake Markdown을 deterministic workspace JSON으로 변환하며 site profile, priority page, user flow, brand note, MCP readiness status, grounded initial audit finding을 보존합니다. `--next-actions [--json]`을 붙이면 `website-workspace.json` 저장부터 시작하는 local runbook을 만들고, `--bundle --out <dir>`을 붙이면 CLI field를 다시 입력하지 않고 filled intake에서 handoff bundle을 바로 생성합니다. `design-ai site --sample`은 파일 기반 workflow를 바로 시작할 수 있는 유효한 starter workspace JSON을 생성합니다. `design-ai site --prompt-list --json`은 선택 전에 사용 가능한 prompt template id를 나열합니다. `design-ai site --mcp-check --json`은 외부 MCP를 호출하지 않고 local MCP readiness evidence와 task/MCP gap을 점검하며, `--strict`를 붙이면 required readiness evidence 누락 시 실패 처리합니다. `--mcp-check` 또는 `--mcp-plan`에 `--probes`를 붙이면 GitHub, Figma, Browser smoke target, deployment provider reference를 read-only URL/path/tool-handoff probe로 확인합니다. Probe는 외부 MCP를 호출하거나 외부 시스템에 write하지 않습니다. `design-ai site --mcp-plan`은 같은 readiness 상태를 blocking item, warning, task/MCP alignment, 선택형 read-only probes, execution sequence, follow-up command가 포함된 action plan으로 변환합니다. 다른 agent, CI smoke, handoff script가 Markdown 대신 구조화된 `website-improvement-mcp-action-plan` payload를 필요로 할 때는 `--json`을 함께 사용합니다. `design-ai site --next-actions [--json]`는 validation issue, MCP readiness, task/MCP gap, top refactor task, handoff command를 target repo로 이동하기 전 prioritized local operator checklist로 정리합니다. 사람이 읽는 runbook checkpoint가 필요하면 `--json`을 빼고 `--out website-next-actions.md`를 붙입니다. `design-ai site --graph --json`은 workspace, site profile, audit, MCP readiness, refactor task, prompt template, handoff, bundle, target-repo node와 deterministic edge를 포함한 portable Website Improvement workflow graph를 생성합니다. 이 graph는 local/read-only artifact이며 static console도 브라우저 상태에서 같은 workflow를 렌더링할 수 있고, 별도 workflow runtime dependency를 추가하지 않습니다. `design-ai site --bundle --out <dir>`은 README, summary JSON, generated tasks workspace, MCP readiness JSON, MCP action plan, handoff report, prompt bundle, top-priority Codex implementation prompt를 포함한 local handoff package를 한 번에 생성합니다. `design-ai site <bundle-dir> --bundle-check --strict --json`은 target-repo handoff 전에 file manifest, JSON consistency, 재계산한 MCP readiness, 필수 Markdown anchor, `summary.json`에 기록된 SHA-256 checksum, `summary.json.checksums.bundleDigest` bundle identity를 확인해 generated package를 검증합니다. `design-ai site <bundle-dir> --bundle-compare <other-bundle-dir> --strict --json`은 두 handoff bundle의 bundle digest, file checksum, summary metadata를 비교해 archive 또는 재생성된 bundle이 같은지 확인합니다. `design-ai site <bundle-dir> --bundle-handoff --strict --json`은 검증된 handoff bundle을 bundle digest, bundle-check status, implementation prompt, operating rules, final response requirements가 포함된 target-repo Codex prompt로 변환합니다. JSON output을 `--out target-repo-handoff.json --force`로 저장한 뒤 Console sidebar의 import로 다시 불러오면 Report tab의 Operator Runbook에서 stage metric, status chip, evidence progress, copy-ready next line을 검토할 수 있습니다. `design-ai site --tasks`는 audit finding를 deterministic starter refactor task로 확장합니다. `design-ai site --prompt <template-id>`는 다른 도구에 붙여넣을 다음 Codex 또는 Claude instruction만 필요할 때 단일 prompt template을 export합니다. Implementation prompt에서는 `--task <id-or-number>`를 붙여 기본 top-priority task 대신 특정 refactor task를 지정할 수 있습니다. `design-ai site`는 Website Console에서 export한 JSON을 검증하고, audit/MCP/task readiness summary, prioritized next-action checklist, Markdown handoff report, Codex/Claude prompt bundle, structured MCP action plan, portable workflow graph, complete handoff bundle directory, target-repo handoff prompt를 생성합니다. 대상 웹사이트 repo를 수정하거나 외부 MCP를 호출하지 않습니다.
+
+Claude Code에서는 `/design-website-improvement` 명령이나 `website-improvement` skill을 사용할 수 있습니다.
+
+## Verification Notes
+
+최종 artifact는 target repo boundary, MCP readiness, refactor plan, verification method, accessibility/focus/contrast note, responsive note를 포함해야 합니다. 자동화되지 않은 Lighthouse, axe, crawling, 외부 write, model training을 완료된 기능처럼 쓰지 않아야 합니다.

package/docs/WEBSITE-IMPROVEMENT.md

@@ -0,0 +1,89 @@
+# Website Improvement Console
+
+The Website Improvement Console is a local control tower for improving an existing website without storing that site's source code in this repository.
+
+Open the MVP app:
+
+[Open Website Improvement Console](website-console/index.html)
+
+For the first real company-site pilot, complete the [Company Website Intake Template](COMPANY-WEBSITE-INTAKE-TEMPLATE.md), then follow the [Company Website Dogfood Runbook](COMPANY-WEBSITE-DOGFOOD.md) before opening the target repository.
+
+## What It Does
+
+- Tracks a Site Profile with live URL, target repo reference, Figma link, pages, user flows, platform notes, and viewport coverage.
+- Manages an Audit Pipeline across visual design, UX flow, responsive QA, accessibility, performance, SEO, technical quality, runtime issues, and content quality.
+- Classifies MCP readiness as `required`, `optional`, `unused`, or `unavailable`.
+- Converts audit findings into starter refactor tasks with impact, effort, priority, MCP recommendations, Codex prompts, verification steps, and risks.
+- Renders a local Workflow Graph with workspace, profile, audit, MCP, task, prompt, handoff, bundle, and target-repo nodes plus deterministic edge rows.
+- Generates prompts for Codex implementation work, Claude design review, competitor research, copy critique, visual QA, deployment verification, and final handoff.
+- Tracks executed work, verification results, remaining risks, and next actions after target-repo implementation.
+- Imports `design-ai site <bundle-dir> --bundle-handoff --json` output as an Operator Runbook in the Report tab, including runbook metadata source pills, source-bundle provenance/detail review, copy-ready source-bundle source markers, source-bundle artifact-specific action labels, revalidation gate JSON action labels, source-bundle revalidation metadata badges, badge rows, warnings, Markdown gates, source/diagnostic-context-preserving gate-only JSON copy/export/import, focused provenance import source refresh, exported compact source markers, Markdown source markers, source-aware empty runbook Markdown, provenance-only notice source markers, JSON gate reason metadata, focused source-bundle JSON import, provenance-only review state and Markdown markers, guarded copy-ready strict source commands, source-bundle Markdown/JSON copy/export, task/command provenance chips, stage metrics, resettable action/evidence row filters, status indexes, evidence progress, copy-ready stage rows, row-level Markdown copy/export and line copy, guarded filtered-row Markdown copy/export, full Markdown export, and guarded next-line copy actions.
+- Drafts a Markdown handoff report that includes before/after status, implementation evidence, verification evidence, and follow-up work.
+- Preserves handoff evidence when exported JSON is processed by `design-ai site --report`, `--tasks`, or `--bundle`.
+- Packages target-repo execution checklist guidance so implementation prompts require repo confirmation, architecture inspection, focused task scope, quality gates, and evidence recording.
+
+## Boundaries
+
+The console does not crawl pages, run Lighthouse, run axe, capture screenshots, call external AI APIs, connect directly to MCP tools, or modify target website repos. It stores state in browser `localStorage` and supports JSON export/import so the same workspace can be moved later to a server-backed store.
+
+Actual code changes happen in the target website repository. Use the generated Codex prompts there, then paste verification evidence back into the handoff report.
+
+## MVP Workflow
+
+1. Fill or import a Site Profile.
+2. Review the Audit Checklist and record findings.
+3. Set the MCP Readiness Matrix so prompts include realistic tool assumptions.
+4. Review the Workflow Graph to confirm audit, MCP, task, prompt, and handoff dependencies.
+5. Generate starter refactor tasks from findings.
+6. Copy a Codex or Claude prompt and run it in the right tool.
+7. After generating a bundle handoff JSON, import it back into the console to review the Operator Runbook before moving into the target repo.
+8. Record executed work, verification results, remaining risks, and next actions in the Handoff Report tab.
+9. Export the handoff report after implementation and verification.
+
+## CLI Export Workflow
+
+Use `design-ai site` when a Website Improvement Console JSON export needs to leave the browser and become an operator artifact:
+
+```bash
+design-ai site --intake-template --out company-website-intake.md
+design-ai site --intake-template --language ko --out company-website-intake.ko.md
+design-ai site --from-intake company-website-intake.ko.md --out website-workspace.json
+cat company-website-intake.ko.md | design-ai site --from-intake --stdin --out website-workspace.json --force
+design-ai site --from-intake company-website-intake.ko.md --next-actions --out website-next-actions.md
+cat company-website-intake.ko.md | design-ai site --from-intake --stdin --next-actions --out website-next-actions.md --force
+design-ai site --from-intake company-website-intake.ko.md --tasks --out website-workspace.tasks.json
+cat company-website-intake.ko.md | design-ai site --from-intake --stdin --tasks --out website-workspace.tasks.json --force
+design-ai site --from-intake company-website-intake.ko.md --bundle --tasks --out website-handoff-bundle
+cat company-website-intake.ko.md | design-ai site --from-intake --stdin --bundle --tasks --out website-handoff-bundle
+design-ai site --init --name "Company marketing site" --live-url https://example.com --repo-url https://github.com/acme/site --page / --page /pricing --flow "Visitor compares plans and starts signup" --out website-workspace.json
+design-ai site --init --name "Company marketing site" --live-url https://example.com --repo-url https://github.com/acme/site --next-actions --out website-next-actions.md
+design-ai site --init --name "Company marketing site" --live-url https://example.com --repo-url https://github.com/acme/site --bundle --out website-handoff-bundle
+design-ai site --sample --out website-workspace.json
+design-ai site website-workspace.json --tasks --out website-workspace.tasks.json
+design-ai site website-workspace.json --json
+design-ai site website-workspace.json --mcp-check --strict --json
+design-ai site website-workspace.json --mcp-check --probes --json
+design-ai site website-workspace.json --mcp-plan --out mcp-action-plan.md
+design-ai site website-workspace.json --next-actions --json
+design-ai site website-workspace.json --next-actions --out website-next-actions.md
+design-ai site website-workspace.json --graph --json --out website-workflow-graph.json
+design-ai site website-workspace.json --bundle --out website-handoff-bundle
+design-ai site website-handoff-bundle --bundle-check --strict --json
+design-ai site website-handoff-bundle --bundle-compare website-handoff-bundle.previous --strict --json
+design-ai site website-handoff-bundle --bundle-handoff --strict --json --out target-repo-handoff.json --force
+design-ai site website-handoff-bundle --bundle-handoff --strict --out target-repo-handoff.md
+design-ai site website-handoff-bundle --bundle-handoff --task task-accessibility --strict --out target-repo-task-accessibility-handoff.md
+design-ai site website-workspace.json --report --out website-handoff.md
+design-ai site website-workspace.json --prompts --out website-prompts.md
+design-ai site website-workspace.json --prompt codex-implementation --out codex-implementation.md
+design-ai site website-workspace.json --prompt codex-implementation --task task-accessibility --out task-accessibility.md
+cat website-workspace.json | design-ai site --stdin --strict --json
+```
+
+`design-ai site --intake-template --language ko` emits Korean content, and `design-ai site --intake-template` emits the same blank company-site intake Markdown form linked from the docs, so operators can create `company-website-intake.md` before project details are ready for `--init`. Add `--json` when another wrapper needs template metadata, privacy boundaries, recommended follow-up commands, and the Markdown content in one payload. `design-ai site --from-intake company-website-intake.ko.md` converts a filled English or Korean intake Markdown file into deterministic workspace JSON, preserving site profile fields, priority pages, user flows, brand notes, MCP readiness statuses, and grounded initial audit findings. Use `design-ai site --from-intake --stdin` when the filled intake comes from a secure note, generated Markdown stream, or another local tool; stdin supports JSON stdout, `--out` workspace persistence, `--next-actions`, `--tasks`, and `--bundle --tasks --out <dir>` with the same local/no-target-repo boundary. Add `--next-actions [--json]` to get a local runbook that starts by saving `website-workspace.json`; add `--tasks --out website-workspace.tasks.json` when the intake already contains initial audit findings and you want the first deterministic refactor tasks without an intermediate workspace command. Add `--bundle --tasks --out <dir>` to create the task-ready handoff bundle directly from the filled intake without retyping CLI fields. `design-ai site --init` creates the same real-project intake workspace from CLI fields, including site profile, default checklist notes, derived MCP readiness, default implementation evidence arrays, and no starter refactor tasks until audit findings exist. Add `--next-actions [--json]` to the same init command when you want a local operator runbook before saving or handing off the workspace; that runbook starts with the exact `site --init ... --out website-workspace.json` command and then lists the MCP check, task generation, handoff report, and bundle commands against `website-workspace.json`. Add `--bundle --out <dir>` to the same init command when you want a one-shot company dogfood handoff kit directly from project intake fields; it writes the same local bundle artifacts as the workspace-based bundle flow and still does not mutate the target website repo. Use `--sample` when you want the canned Korean SaaS fixture instead. `design-ai site --prompt-list --json` lists the available prompt template ids before you choose one. `design-ai site --mcp-check --json` checks local MCP readiness evidence and task/MCP gaps without calling external MCPs; add `--strict` to fail when required readiness evidence is missing. Add `--probes` to `--mcp-check` or `--mcp-plan` when you want read-only URL/path/tool-handoff probes for GitHub, Figma, Browser smoke targets, and deployment provider references; probes do not call external MCPs or write to any outside system. `design-ai site --mcp-plan` turns the same readiness state into an action plan with blocking items, warnings, task/MCP alignment, optional read-only probes, execution sequence, and follow-up commands; add `--json` when another agent, CI smoke, or handoff script needs the structured `website-improvement-mcp-action-plan` payload instead of Markdown. `design-ai site --next-actions [--json]` distills validation issues, MCP readiness, read-only MCP probe readiness and probe counts, task/MCP gaps, top refactor tasks, and handoff commands into a prioritized local operator checklist before you move into the target repo; omit `--json` and add `--out website-next-actions.md` when you want a Markdown runbook checkpoint. `design-ai site --graph --json` exports a portable Website Improvement workflow graph with workspace, site profile, audit, MCP readiness, refactor task, prompt template, handoff, bundle, and target-repo nodes plus deterministic edges; the graph is local/read-only and the static console can render the same workflow from browser state without adding a workflow runtime dependency. `design-ai site --bundle --out <dir>` writes a complete local handoff package with a README, summary JSON, generated tasks workspace, MCP readiness JSON, read-only MCP probe JSON, MCP action plan, handoff report, prompt bundle, and top-priority Codex implementation prompt. The bundle README and `summary.json.handoff` explain strict-ready state, recommended handoff command, strict command, draft command, verification command, target-repo execution checklist, and the boundary between planning-only draft prompts and implementation-authority strict prompts. `design-ai site <bundle-dir> --bundle-check --strict --json` validates the generated package before target-repo handoff by checking the file manifest, JSON consistency, recomputed MCP readiness and probe readiness, required Markdown anchors, `summary.json.handoff.executionChecklist`, SHA-256 checksums recorded in `summary.json`, and `summary.json.checksums.bundleDigest` bundle identity. `design-ai site <bundle-dir> --bundle-compare <other-bundle-dir> --strict --json` compares two valid handoff bundles by bundle digest, file checksums, and summary metadata so operators can confirm whether an archived or regenerated bundle is identical before using it in a target repo. `design-ai site <bundle-dir> --bundle-handoff --strict --json` turns a verified handoff bundle into a target-repo Codex prompt that carries the bundle digest, bundle-check status, MCP probe status, MCP probe counts, implementation prompt, operating rules, target-repo execution checklist, and final response requirements plus an “Available Bundle Tasks” catalog with task numbers, ids, priority, impact, effort, pages, recommended MCPs, and copy-ready strict handoff commands; JSON output exposes the top-priority bundled task as `bundle.defaultTask` and the actual prompt target as `bundle.effectiveTask`, each with `handoffOutFile`, `handoffCommand`, and `strictHandoffCommand`; add `--task <id-or-number>` to regenerate that handoff prompt for a specific task from `website-workspace.tasks.json` while preserving verified bundle metadata and adding the selected task's own `handoffOutFile`, `handoffCommand`, and `strictHandoffCommand` to JSON `bundle.selectedTask`; `bundle.effectiveTask` then switches to that selected task. Save the JSON output with `--out target-repo-handoff.json --force` and import it through the console sidebar when you want the Report tab to show the Operator Runbook with stage metrics, status chips, evidence progress, and copy-ready next-line actions before entering the target repo. `design-ai site --tasks` expands audit findings into deterministic starter refactor tasks. `design-ai site --prompt <template-id>` exports one prompt template when you want to paste only the next Codex or Claude instruction into another tool. For implementation prompts, add `--task <id-or-number>` to target a specific refactor task instead of the default top-priority task. The command validates the local workspace schema, summarizes audit/MCP/task/probe readiness and probe counts, and generates prioritized next-action checklists, Markdown handoff reports, prompt bundles, structured MCP action plans, portable workflow graphs, complete handoff bundle directories, or target-repo handoff prompts. It still does not modify the target website repo or call external MCPs.
+
+When a workspace JSON includes `implementationEvidence`, the CLI keeps it local and deterministic: `--json` reports evidence counts, `--tasks` preserves the evidence block, `--report` renders the evidence sections, and `--bundle` stores the same evidence in `website-workspace.tasks.json`, `website-handoff.md`, and `summary.json`.
+
+## Accessibility And Responsive Notes
+
+The app is desktop-first because the primary user is an operator planning website improvements, but controls remain usable on mobile. Interactive controls are keyboard reachable, focus-visible, and use text labels. Status and priority values are not represented by color alone; each status is printed as text.

package/docs/announcements/README.md

@@ -0,0 +1,56 @@
+# Launch kit
+
+Ready-to-post announcement drafts for design-ai v4.0.0 launch. **Drafts only** — review before posting; tailor as needed.
+
+## What's here
+
+| File | Channel | Language | Length |
+|---|---|---|---|
+| [`press-kit.md`](press-kit.md) | Reusable assets (one-liner / stats / FAQ) | EN + KO | — |
+| [`okky-post.ko.md`](https://github.com/sungjin9288/design-ai/blob/main/docs/announcements/okky-post.ko.md) | OKKY (okky.kr) | KO long-form | ~600 words |
+| [`hashnode-post.ko.md`](https://github.com/sungjin9288/design-ai/blob/main/docs/announcements/hashnode-post.ko.md) | hashnode.com (KR tag) | KO blog | ~800 words |
+| [`dev-to-korea.md`](dev-to-korea.md) | dev.to (#korea + #design tags) | EN + bilingual examples | ~600 words |
+| [`show-hn.md`](show-hn.md) | Hacker News Show HN | EN concise | ~150 words title+body |
+| [`twitter-thread.md`](twitter-thread.md) | X / Twitter | EN + KO threads | 6-8 tweets each |
+| [`reddit-r-korea.md`](reddit-r-korea.md) | r/korea / r/programming | EN + KO versions | ~300 words |
+
+## Posting order (suggested)
+
+1. **Tag v4.0.0 + verify CI publish**. Wait for `npm view @design-ai/cli version` to show `4.0.0`.
+2. **Show HN** (Tuesday-Thursday 8-10am PT — best HN window).
+3. **dev.to** (same day or +1).
+4. **OKKY post** + **hashnode** (Korean morning, KST 9-11am).
+5. **Twitter threads** (EN + KO) staggered by 2 hours.
+6. **Reddit** (r/programming, then r/korea) — wait 24h after HN to avoid duplicate-feel.
+
+## Tracking
+
+After posting, log in `docs/announcements/posted.md` (created at first post):
+- Channel + URL.
+- Posted at (timestamp + timezone).
+- 24h metrics (upvotes, comments, click-through if known).
+- 7-day metrics.
+
+## Don't
+
+- **Don't post all on the same day.** Staggered = sustained visibility; same-day = burst then silence.
+- **Don't translate KR content via auto-translate.** Drafts are written in natural Korean; auto-translation breaks tone.
+- **Don't post before npm publish.** Adopters see the link, try `npx`, fail. Tag → verify → then announce.
+- **Don't oversell.** "Senior product designer" is the tagline; "replaces designers" is not.
+
+## Tone
+
+| Channel | Voice |
+|---|---|
+| Show HN | Engineer-to-engineer, low-key, factual |
+| dev.to | Technical blog, code-heavy |
+| OKKY | 한국 개발자 톤, 해요체, 구체적 use case 중심 |
+| hashnode KR | 기술 블로그, 해요체, 코드 + 그림 |
+| Twitter/X | Hook-first, scannable |
+| Reddit | Modest, ask-don't-tell, link to repo |
+
+## Cross-reference
+
+- [`CHANGELOG.md`](../../CHANGELOG.md) — full v4.0.0 release notes
+- [`docs/SESSION-LOG.md`](../SESSION-LOG.md) — v2.0 → v4.0 narrative for press
+- [`docs/RELEASE-CHECKLIST.md`](../RELEASE-CHECKLIST.md) — post-tag steps

package/docs/announcements/dev-to-korea.md

@@ -0,0 +1,206 @@
+# dev.to post draft
+
+Target: <https://dev.to/new>. Tags: `#korea`, `#ai`, `#design`, `#claude`, `#opensource`.
+
+## Title
+
+```
+design-ai v4.0: turn any AI coding agent into a senior product designer (with Korean market depth)
+```
+
+Alt titles:
+- `Building a model-agnostic design knowledge base for Claude Code, Codex CLI, Cursor`
+- `Why I built a design system corpus that works in 5 different AI tools`
+
+## Cover image
+
+1280×720 — same template as hashnode (logo + stats card + install command).
+
+## Body
+
+```markdown
+After 32 phases over the last few months, my open-source design knowledge
+base — `design-ai` — hit v4.0 stable last week. Sharing the architectural
+choices that shaped it, since a few of them go against common AI-tooling
+conventions.
+
+```bash
+npx @design-ai/cli install
+```
+
+GitHub: https://github.com/sungjin9288/design-ai · License: MIT
+
+## What design-ai is
+
+A hand-curated design knowledge base that turns any AI coding agent into
+a senior product designer. It plugs into:
+
+- **Claude Code** — skills + commands + review agents
+- **Codex CLI** — `AGENTS.md` convention
+- **Cursor** — `.cursorrules`
+- **Aider** — `--read` flag
+- **VS Code** — sidebar extension (vendor-neutral, pairs with Copilot Chat / Cursor / Continue)
+- **Plain prompts** — concatenate as system prompt for any LLM
+
+Contains 91 knowledge files, 160 worked examples, 19 skills with
+playbooks, 15 slash commands, 4 review agents, and 5 integration
+walkthroughs (each in English and Korean).
+
+## Three architectural choices
+
+### 1. Markdown is the source of truth, not vendor-specific skill files
+
+Most AI design tools encode their content as Claude-specific skills,
+Cursor-specific rules, or vendor templates. That locks adopters in.
+
+design-ai uses plain markdown + JSON. The Claude Code skill system is
+just one ergonomic surface on top — `SKILL.md` is `PLAYBOOK.md` with
+frontmatter wrapping. Same content works in Codex via `AGENTS.md`, in
+Cursor via `.cursorrules`, in Aider via `--read`, in VS Code via the
+sidebar extension, or as raw system prompt.
+
+Trade-off: lose some Claude-specific ergonomics (e.g., automatic skill
+invocation). Gain: portability across the entire AI tooling ecosystem.
+
+### 2. Korean market is a first-class citizen, not a footnote
+
+Most Western design system documentation treats non-English markets as
+"localization concerns" — typography fallbacks, RTL, currency formatting.
+design-ai treats Korean conventions as deep domain knowledge:
+
+- **Payments**: Toss / KakaoPay / NaverPay decision tree, 본인인증
+  (PASS / NICE / KCB) integration, 청약철회 disclosure, 표시광고법.
+- **Typography**: Pretendard primary, fallback chain, 한글 optical
+  adjustments.
+- **Voice/chatbot**: 해요체 vs 합쇼체 register branching, Bixby /
+  Clova / NUGU / Kakao i platform conventions.
+- **Game UI**: 확률 표시 (mandatory probability disclosure), GRAC
+  ratings, PC bang usability.
+- **Video**: KFDA / KFTC ad disclosure, 자막 conventions.
+- **Print**: 명함 90×50, 분리배출 표시 (recycling marks), KFDA / KATS
+  regulatory.
+
+Foundational docs (`README`, `QUICKSTART`, `AGENTS`, `DISTRIBUTION`,
+`USING`, `CONTRIBUTING`, `ARCHITECTURE`) all have Korean equivalents.
+5 integration walkthroughs translated. Audit script
+(`korean-copy-check.py`) catches machine-translation artifacts.
+
+### 3. Distribution before mass content
+
+When the corpus was at ~30% component coverage, the temptation was to
+push to 70% before doing anything else. Instead, I built distribution:
+
+- npm CLI (`@design-ai/cli`)
+- Homebrew formula
+- Public mkdocs-material doc site (with English + Korean)
+- Claude Code plugin manifest
+- VS Code extension
+
+A 30% corpus that adopters can install in one command beats a 70%
+corpus locked in a private repo. Coverage push to 55% happened after
+distribution was solid.
+
+## v2.0 → v4.0 in numbers
+
+| Surface | v2.0 | v4.0 |
+|---|---|---|
+| Knowledge files | 55 | 91 |
+| Worked examples | 83 | 160 |
+| Skills | 12 | 19 |
+| Slash commands | 8 | 15 |
+| Component coverage | ~24% | 55.3% |
+| Distribution channels | 1 | 4 |
+| Integration walkthroughs | 0 | 5 (EN + KO) |
+| Site languages | 0 | 2 |
+| CI audits | 4 | 6 |
+
+## 6 audits gating CI
+
+Every PR must pass:
+
+1. `frontmatter-check.py` — YAML validity + version field shape
+2. `link-check.py` — 360+ internal links resolve
+3. `korean-copy-check.py` — Korean voice / register / typography
+4. `check-coverage.py` — component coverage diff
+5. `integration-check.py` — walkthrough completeness
+6. `stale-check.py` — knowledge freshness (>12mo = CI failure)
+
+Audit count grew from 4 → 6 over the project. Each new audit prevented
+a regression class:
+
+- `korean-copy-check` (v3.0) — auto-translation artifacts
+- `integration-check` (v3.4) — walkthroughs missing required sections
+- `stale-check` (v3.12) — content rotting under stable version pin
+
+## Try it
+
+```bash
+# Quickest
+npx @design-ai/cli install
+
+# Or git clone
+git clone https://github.com/sungjin9288/design-ai
+cd design-ai && ./install.sh
+
+# Or Homebrew (macOS)
+brew tap sungjin9288/design-ai
+brew install design-ai
+```
+
+After installing, in Claude Code:
+
+```
+/design-palette-from-brand
+> Brand: Korean B2B SaaS, calm professional voice, primary blue.
+```
+
+In Codex CLI:
+
+```bash
+cd /path/to/design-ai
+codex "Generate a color palette for a Korean fintech app"
+```
+
+In Cursor: drop `docs/integrations/cursor-walkthrough.md` into your
+chat or follow the walkthrough.
+
+## What's next (4.x roadmap)
+
+- VS Code marketplace publish (1.0.0)
+- Coverage push 55% → 70%
+- Semantic search index (Algolia / Typesense)
+- Component spec extractor v2 (TypeScript AST parsing)
+- Quarterly stability re-review ritual (operationalized via stale-check)
+
+## Feedback welcome
+
+- GitHub Issues for bugs / feature requests / Korean convention
+  additions.
+- Korean translation / content contributions welcome — see
+  [`docs/CONTRIBUTING.ko.md`](https://github.com/sungjin9288/design-ai/blob/main/docs/CONTRIBUTING.ko.md).
+- Especially curious about: Cursor + Figma workflows, B2B SaaS team
+  adoption patterns, non-Korean fintech market additions.
+
+Thanks for reading.
+
+— [@sungjin9288](https://github.com/sungjin)
+```
+
+## Posting tips
+
+- **Best time**: Tuesday-Thursday 9-11am PT — dev.to algorithm
+  weighs early engagement.
+- **Reading time**: ~6 min (dev.to surfaces this).
+- **Cover image**: matters a lot for click-through; see press-kit.md
+  for spec.
+- **Reply within 30min** to first comments — boosts thread visibility.
+- **Cross-post**: dev.to → hashnode (set canonical URL) is OK; same
+  text but different audiences.
+
+## Don't
+
+- Don't use auto-translation banners ("originally in Korean") —
+  the post is written in English directly.
+- Don't tag `#javascript` or `#react` aggressively — those tags
+  drown out smaller-tag visibility.
+- Don't post both dev.to and hashnode same hour. Stagger by 24h.