- Usage types are now Web / SW (general mode, viewer mode) / OrgChart / mixed. Shared AI_GUIDE step 1 asks for the SW mode only when the request or the project setting (HMDesign 사용 유형: SW 일반 | SW 뷰어) leaves it open; examples B0/B1/B2 cover "HMDesign SW로 화면을 만들어 주세요", general and viewer. - Missing-component handling in three steps (reuse in the chosen type/mode -> build with that mode's tokens -> HMDesign-consistent style, reported as "AI 구성 값 — 디자인 확인 필요"), plus SW general/viewer separation rules. - sw/ai: AI_USAGE §0 mode selection, catalog §8 lists all 33 SWViewer* exports, DESIGN_RULES §11 viewer tokens, PATTERNS 7 viewer composition; examples B/F marked as general mode. ui/ai and org-chart/ai aligned with the new types. - AGENTS_SNIPPET, AGENTS.md and MAINTAINING updated; copies synced. - scripts/ai-docs.mjs: shared-copy check ignores CRLF/LF (core.autocrlf=true checks out packages/sw as LF and the rest as CRLF). - Verification record updated (code samples typechecked, built and rendered).
@hm-design/ui
React 19 UI components and the HM default theme. Published entrypoints contain ESM JavaScript and TypeScript declarations.
import { Button, Input } from "@hm-design/ui"
import { applyRuntimeTheme, resetRuntimeTheme } from "@hm-design/ui/theme"
With Tailwind CSS 4, import these styles in order in the application's CSS entrypoint:
@import "tailwindcss";
@import "@hm-design/ui/tailwind.css";
@import "@hm-design/ui/theme.css";
Process this entrypoint with the application's Tailwind CSS 4 integration. The package registers its compiled component classes as Tailwind sources and includes the required shadcn CSS without installing the shadcn CLI. React and React DOM are peer dependencies and are not bundled.
The default theme, Noto Sans KR font and its OFL license are included. External theme JSON and a Theme CDN are optional and are not included in this package. The runtime theme API remains available from @hm-design/ui/theme.
For Dashboard work status colors, explicitly load the optional status stylesheet after the theme:
@import "tailwindcss";
@import "@hm-design/ui/tailwind.css";
@import "@hm-design/ui/theme.css";
@import "@hm-design/ui/dashboard-status.css";
The status stylesheet defines only --hm-dashboard-status-active, --hm-dashboard-status-hold, --hm-dashboard-status-done and --hm-dashboard-status-issue. It does not automatically style Badge, buttons or data-status attributes. Consumers must map these variables to their existing component styles; the repository's docs/patterns/dashboard-layout.md shows the Badge mapping. done resolves the existing white palette token in each :root / [data-hm-theme] scope. The other colors preserve the approved Dashboard values and are not additional Runtime Theme tokens.
From the HMDesignSystem repository, run npm run build -w @hm-design/ui. npm pack runs this build automatically. Only dist/, ai/, this README and the package manifest are packed; source and Storybook files are excluded.
AI coding tools
AI coding tools should read ai/AI_GUIDE.md first (shared HMDesign entry point: choose Web / SW / OrgChart / mixed, then reuse → props → composition → minimal custom). Web-specific rules: ai/AI_USAGE.md, ai/COMPONENT_CATALOG.md, ai/DESIGN_RULES.md, ai/COMPOSITION_PATTERNS.md. To make a consumer project pick them up automatically, copy ai/AGENTS_SNIPPET.md into its root AGENTS.md (see AI_GUIDE.md §9).