Dot Design System Agent Context

When to use

Use this context for a new product screen or UI, a Dot UI implementation, or a Dot UI design/code review. It is a versioned snapshot of the package guidance, not a substitute for the consumer repository's product requirements.

Working contract

1. Read the brief and inspect the installed package public API before proposing an import, component, prop, token, or asset ID.
2. Read docs/dot-design-system/references/catalog.json, then select only the relevant versioned references by kind, path, and source: language for product decisions, foundations for visual and interaction rules, component contracts for real public APIs, patterns for multi-component flows, content for writing, and brand documents for approved expression. Read adoption for consumer setup and domain-contract for a proposed system change.
3. Start with a short design brief: user goal, completed learning loop and next direction, one primary action, the discovery/understanding/execution/recovery costs to reduce, selected components/tokens, responsive layout, required states, and open deviations.
4. Prefer existing primitives and compositions. Do not invent a public API, raw visual language, or unapproved asset. Propose a design-system change when the documented system is insufficient.
5. Verify semantic state cues, keyboard/focus behavior, labels and errors, reduced motion, and small/medium/wide layouts before handing off.

Apply Flexible by adapting density and structure without changing meaning; apply Link by preserving people, data, choices, and progress across surfaces; apply Glow only when it gives direction in a genuinely uncertain or meaningful moment. Keep one primary action dominant, use semantic tokens, and preserve context between list, detail, and edit. Use concise Korean that describes action results. Do not add product backend types, auth, routing, or data fetching to the design-system package.

Snapshot discipline

In a consumer repository, treat docs/dot-design-system/manifest.json as the local record of the installed @classum/dot-design-system version and source-document SHA-256 hashes. Run pnpm exec dot-ds agents check before a substantial screen task; run pnpm exec dot-ds agents sync when it reports drift. Do not edit managed snapshot files or managed sections in AGENTS.md and CLAUDE.md by hand.

In the Dot Design System package repository itself, the canonical docs/ files are the source and no consumer snapshot is expected at the repository root. Follow docs/domain-contract.md, docs/spec.md, and the package checks instead of running agents check against that root.