shkim4
3a5e29f2fa
Integrate the SW home (logo) menu into SWHeader for SW general mode only. SW viewer mode code and stories are unchanged. - Resolve conflicts: keep both sw-home-menu and sw-viewer exports; renumber AI docs (catalog viewer 8->9, patterns home menu 7->8, design rules home menu 11->12) - SWHeader: start the home menu after the file name when it sits inside controls, so the file name stays visible - AI guides: mark home menu as general-mode only; forbid it in viewer mode (AI_USAGE, catalog, design rules, patterns, VIEWER.md, AI_GUIDE) - Tests: ignore wildcard identifiers in ai-docs check; update expected Storybook SW titles (SW/Tool removed, SW/Viewer added) - Add merge QA report docs/sw/sw-home-menu-merge-2026-10-19.md
@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).