shkim4
0086d66a94
- AI_GUIDE stage 5 "Header 전용 스타일의 적용 범위": header-only styles stay in the header (SW SWHeader / SWProcessHeader / SWViewerHeader, Web GNB / LNBMobileHeader / DashboardHeader); no header CSS or tokens on body UI, no global overrides, layout-only joins, package-shared tokens unchanged, whole-screen use only on explicit request. Synced to the 4 package copies; referenced from stage 6, SW and Web AI_USAGE §3 - SWProcessHeader: with documentTitle "" the file name keeps #AEDBCC on hover and a default cursor (root data-document-untitled). The button, focus and onDocumentClick are kept; a real file name keeps the yellow hover and pointer. Visual vs. click difference recorded as a UX item - Step enablement documented as implemented: only an explicit disabled (step, group, process, header) turns steps off; project / file state never does; selection is activeStepId + onStepSelect (also for host previous / next); no activeStepId and empty groups described - Regression check tests/process-header-states.check.mjs (15/15); typecheck:sw, build:sw, check:ai-docs pass; public-api keeps its 3 existing failures, none new
@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).