@mieweb/ui 0.11.0-dev.17 → 0.11.0-dev.18

package/agent/README.md

@@ -1,20 +1,193 @@
-# agent/ — AI Agent Rules Shipped with @mieweb/ui
+# agent/ — AI Agent Team Shipped with @mieweb/ui
 
-Rules that teach AI coding agents (Copilot, Claude Code, Cursor, Codex, …) to
-use `@mieweb/ui` components — most importantly, **DataVis NITRO for all
-tables** — instead of inventing their own UI.
+Rules and agents that teach AI coding agents (Copilot, Claude Code, Cursor,
+Codex, …) to use `@mieweb/ui` components — most importantly, **DataVis NITRO
+for all tables** — instead of inventing their own UI.
 
-Agents don't read files inside `node_modules`, so consumers install the rules
+Agents don't read files inside `node_modules`, so consumers install everything
 into their repo with:
 
 ```bash
 npx @mieweb/ui init-agent
 ```
 
+This directory is growing from a single instructions file into the **MIE UI
+Design Agent team** — an orchestrator plus specialist subagents and skills —
+per epic [#545](https://github.com/mieweb/ui/issues/545). This README is the
+governing spec: later tickets cite it instead of re-deciding.
+
+## Files
+
 | File                                                   | Purpose                                                                                                                                                                                                                                                     |
 | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [mieweb-ui.instructions.md](mieweb-ui.instructions.md) | The rules template. Copied verbatim to the consumer's `.github/instructions/` (VS Code Copilot auto-applies it via the `applyTo` frontmatter) and embedded, minus frontmatter, in a marked block in the consumer's `AGENTS.md` (the cross-tool convention). |
-| [init-agent.mjs](init-agent.mjs)                       | The `mieweb-ui` bin. Idempotent — rerun after upgrading `@mieweb/ui` to refresh both targets.                                                                                                                                                               |
+| [init-agent.mjs](init-agent.mjs)                       | The `mieweb-ui` bin. Idempotent — rerun after upgrading `@mieweb/ui` to refresh all targets. `--experimental-agents` additionally installs the agent team below.                                                                                            |
+| [agents/](agents/)                                     | Agent templates: `mieweb-ui-design` (orchestrator) + `mieweb-ui-styling`. Installed to the consumer's `.github/agents/` behind `--experimental-agents`.                                                                                                     |
+| [skills/](skills/)                                     | Skill templates: `mieweb-ui-catalog`, `mieweb-ui-tokens`, `mieweb-ui-icons` (generated — `pnpm agent:skills`, never hand-edit) + `mieweb-ui-brands` (hand-written). Installed to `.github/skills/` behind `--experimental-agents`.                          |
+| `evals/` _(Phase 2+)_                                  | Golden-question eval sets per specialist; the regression harness for agent knowledge.                                                                                                                                                                       |
 
 Rule content is sourced from [lessons/component-policy.md](../lessons/component-policy.md);
 keep the two in sync when policy changes.
+
+## Governing rules
+
+Decided in [#545](https://github.com/mieweb/ui/issues/545) (design principles +
+execution decisions). Summarized here as the citable spec.
+
+1. **Persona-or-facts test.** A domain earns an _agent seat_ only if it needs a
+   persona and workflow (audit procedure, diagnostic method, judgment). If it
+   only needs _facts_, it's a `SKILL.md`. Taxonomy buckets ("primitives",
+   "complex components") are not domains.
+2. **Agents = behavior, skills = facts.** Deep reference material lives in
+   skills loaded on demand, never inlined into agent prompts.
+3. **Thin orchestrator owns selection.** The orchestrator answers component
+   selection/usage itself from the catalog skill and routes everything else
+   (see routing spec below). It is not a pure switchboard.
+4. **Auditors are read-only.** Audit-persona agents (A11y, i18n/RTL,
+   Migration/Compliance) get no edit tools; they produce a report plus an
+   "Apply Fixes" handoff. Fixer personas (Styling & Theming) may edit.
+5. **Single source of truth.** Shipped files are synced from `lessons/`
+   (canonical prose) or generated from source (tokens from the Tailwind preset,
+   catalog from exports + `src/catalog/*.mdx`). No third drifting copy.
+6. **Promotion rule.** Knowledge starts as a skill on the orchestrator; it is
+   promoted to an agent seat only when dogfooding/routing data shows demand for
+   a dedicated workflow.
+7. **Consumer team vs maintainer team.** `agent/` templates ship to consumers.
+   Maintainer agents (PR checks, release, story authoring) live in this repo's
+   `.github/agents/` and are never shipped.
+8. **Tool-agnostic distribution.** VS Code/Copilot gets `.agent.md` +
+   `SKILL.md`; tools without native subagents get the `AGENTS.md` marked block
+   extended with an agent roster that references the installed files by path.
+9. **Experimental gating.** Until the epic completes, agents/skills/roster
+   install **only** with `init-agent --experimental-agents`. The default run
+   stays byte-identical to today's behavior (instructions file + `AGENTS.md`
+   block). The default flips on in P5.2
+   ([#607](https://github.com/mieweb/ui/issues/607)) — the official launch.
+
+## Naming & layout
+
+- Every shipped artifact is prefixed **`mieweb-ui-`** so consumer repos can
+  distinguish managed files from their own at a glance.
+- Template layout in this repo → installed location in the consumer:
+
+| Template (this repo)                     | Installed (consumer repo)                                                 |
+| ---------------------------------------- | ------------------------------------------------------------------------- |
+| `agent/mieweb-ui.instructions.md`        | `.github/instructions/mieweb-ui.instructions.md`                          |
+| `agent/agents/mieweb-ui-<name>.agent.md` | `.github/agents/mieweb-ui-<name>.agent.md`                                |
+| `agent/skills/mieweb-ui-<name>/SKILL.md` | `.github/skills/mieweb-ui-<name>/SKILL.md`                                |
+| _(embedded block)_                       | `AGENTS.md` between `<!-- mieweb-ui:begin -->` / `<!-- mieweb-ui:end -->` |
+
+- Agent display names: `MIE UI <Domain> Agent` (e.g. `MIE UI Styling Agent`);
+  the orchestrator is `MIE UI Design Agent`.
+- Generated skills are produced by `scripts/` generators into `agent/skills/`
+  at build time and committed, so the installer stays a dumb file copier.
+
+## Managed-file markers
+
+Every **newly shipped** whole-file artifact (agents, skills) carries a managed
+marker so reruns can refresh safely:
+
+```
+<!-- mieweb-ui:managed @mieweb/ui@X.Y.Z -->
+```
+
+- **Scope:** marker-based refresh applies to `--experimental-agents` artifacts
+  only. The two legacy targets keep their existing behavior unchanged (rule
+  9's byte-identical guarantee): `.github/instructions/mieweb-ui.instructions.md`
+  is overwritten verbatim on every run (as today), and `AGENTS.md` uses its own
+  `begin`/`end` block markers.
+- **Placement:** first line of the file body — immediately after the YAML
+  frontmatter block if present, otherwise line 1. (Frontmatter must stay at
+  byte 0 for VS Code to parse it.)
+- **Refresh rules (idempotent rerun):**
+  - Target file exists **with** marker → overwrite with the new template
+    (marker version updated).
+  - Target file exists **without** marker → **skip and warn**: it's
+    user-created; never clobber it.
+  - Template removed in a newer release but installed file still present →
+    **report, never delete**.
+  - `AGENTS.md`: only the content between the `begin`/`end` markers is
+    replaced; everything outside is untouched.
+
+## `.agent.md` frontmatter baseline
+
+All shipped agents conform to:
+
+```yaml
+---
+name: MIE UI <Domain> Agent
+description: <one sentence: domain + when to invoke; this is the routing surface>
+tools: [<minimal set for the persona>]
+# auditors:        ['search', 'codebase', 'fetch'] — no edit/terminal tools
+# fixers:          add 'editFiles'
+# diagnosticians:  add 'runInTerminal' only if the workflow runs commands
+handoffs: # where useful — auditors always include an "Apply Fixes" handoff
+  - label: Apply Fixes
+    agent: agent
+    prompt: Apply the fixes identified above.
+    send: false
+---
+```
+
+- **No pinned `model:`** — agents must be model-agnostic.
+- **`description` is the routing surface**: it must state the domain and the
+  invoke-when, because orchestrators and humans both select on it.
+- **Tools are the persona contract**: read-only auditors cannot hold edit
+  tools (governing rule 4).
+
+### Audit: existing `.github/agents/style.agent.md` vs baseline
+
+| Check            | Status | Notes                                                                                                                                                  |
+| ---------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| No pinned model  | ❌     | Pins `model: Claude Sonnet 4` — remove when evolved in P1.5 (#599)                                                                                     |
+| Minimal tools    | ⚠️     | Holds `editFiles` + `runInTerminal` + `terminalLastCommand`; Styling is a fixer so `editFiles` stays, terminal tools drop unless a workflow needs them |
+| Handoffs pattern | ✅     | "Apply Fixes" handoff is the team-wide template                                                                                                        |
+| Naming           | ❌     | `Style Agent` → `MIE UI Styling Agent`, file → `mieweb-ui-styling.agent.md` (P1.5)                                                                     |
+| Facts in skills  | ❌     | Inlines token tables — dedupe into the generated tokens skill (P1.2, #600)                                                                             |
+
+The original `.github/agents/style.agent.md` stays in place (maintainer use)
+until P1.5 ships its consumer replacement.
+
+## Orchestrator routing spec
+
+The orchestrator (`MIE UI Design Agent`) answers **directly** from the catalog
+skill: component selection ("Card or Panel?", "which table component?" —
+propose DataVis NITRO first per Rule 1 of
+[mieweb-ui.instructions.md](mieweb-ui.instructions.md); `Table` only for its
+documented static-rows exception), basic props/variants/composition usage,
+high-level architecture (headless vs styled, preset vs TW4 `@source`), and
+"where do I find X".
+
+Everything else is delegated per this table (final domain boundaries):
+
+| Question is about…                                 | Delegate to            |
+| -------------------------------------------------- | ---------------------- |
+| install / peer deps / preset / safelist / @source  | MIE UI Install Agent   |
+| tokens, CSS vars, Tailwind classes, brands, dark   | MIE UI Styling Agent   |
+| ARIA, keyboard nav, screen readers, contrast       | MIE UI A11y Agent      |
+| translations, locale bundles, Intl formats, RTL    | MIE UI i18n Agent      |
+| migrating code to @mieweb/ui, raw-HTML compliance  | MIE UI Migration Agent |
+| DataVis NITRO, eSheet, grids, virtualization       | MIE UI Grids Agent     |
+| charts, maps, globes, sparklines, report templates | MIE UI DataVis Agent   |
+| ViewSet, dashboards, panels, app shell layout      | MIE UI Views Agent     |
+| SuperChat, Inbox, AI messages, media conversation  | MIE UI SuperChat Agent |
+| rich text editors, Kerebron, Markdown              | MIE UI Rich Text Agent |
+
+**Tie-breakers for ambiguous cases:**
+
+- _Selection vs depth:_ "which component" is always the orchestrator, even for
+  grid/chart components; the specialist owns configuration, APIs, and
+  debugging of the chosen component.
+- _Styling a specialist's component:_ generic token/Tailwind/brand questions →
+  Styling Agent; component-specific theming APIs (e.g. NITRO theme config) →
+  that component's specialist.
+- _Cross-cutting audits win:_ a11y/i18n questions route to those auditors no
+  matter which component they concern.
+- _Multi-domain:_ consult each relevant specialist, synthesize one answer,
+  attribute which specialist produced which part.
+- _No fit / unsure:_ say so and point at the catalog/Storybook — never
+  improvise an answer outside the roster.
+
+Until a specialist ships (phases land incrementally), its row is absent from
+the installed roster and the orchestrator answers from the catalog skill or
+defers to docs.

package/agent/agents/mieweb-ui-design.agent.md

@@ -0,0 +1,71 @@
+---
+name: MIE UI Design Agent
+description: Orchestrator for the @mieweb/ui design system — answers component selection and usage questions ("which component for X?", props, variants, composition) from the catalog skill and routes deeper domain work to MIE UI specialist agents. Invoke for any @mieweb/ui design, component, or UI-building question when no more specific MIE UI agent obviously fits.
+tools: ['search', 'codebase', 'fetch', 'agent']
+handoffs:
+  - label: Styling & theming
+    agent: MIE UI Styling Agent
+    prompt: Handle the styling/theming question above (tokens, Tailwind classes, brands, dark mode) and apply fixes where asked.
+    send: false
+---
+
+# MIE UI Design Agent (orchestrator)
+
+You are the entry point for all `@mieweb/ui` design-system questions. You are a
+**thin orchestrator**: you own component _selection and basic usage_ yourself,
+and you delegate domain depth to specialists. You never edit files — propose
+changes or hand off.
+
+## Answer directly (your own domain)
+
+Ground every answer in the installed skills — `mieweb-ui-catalog` (inventory,
+entry points, per-family selection guidance and its `selection-guidance.md`
+comparison tables) and `mieweb-ui-icons` (icon aliases and conventions):
+
+- **Component selection** — "which component for X?", "Card or Panel?". Read
+  the family's policy and "Which one?" table before answering. For any table,
+  grid, or tabular view, **propose DataVis NITRO first** (Rule 1 of the
+  installed `mieweb-ui.instructions.md`); `Table` only for its documented
+  static-rows exception. `AGGrid` is deprecated — never suggest it.
+- **Basic usage** — props, variants, sizes, composition slots, import entry
+  points.
+- **Icon questions** — which Lucide alias exists, sizing, icon accessibility.
+- **High-level architecture** — headless modules vs styled components, Tailwind
+  preset vs TW4 `@source`, where to find something in the Storybook
+  (https://ui.mieweb.org).
+
+## Route to specialists
+
+| Question is about…                               | Delegate to          |
+| ------------------------------------------------ | -------------------- |
+| tokens, CSS vars, Tailwind classes, brands, dark | MIE UI Styling Agent |
+
+More specialists (Install, A11y, i18n, Migration, Grids, DataVis, Views,
+SuperChat, Rich Text) land in later phases; until one ships, answer its domain
+from the skills and the component docs, or defer (below).
+
+**Tie-breakers:**
+
+- _Delegation mechanics:_ for multi-domain answers, invoke the specialist as a
+  subagent (the `agent` tool) and fold its result into your synthesis; use the
+  handoff instead when the user should continue the conversation with the
+  specialist. Delegate only to installed MIE UI agents.- _Selection vs depth:_ "which component" is always yours, even for grid/chart
+  components; the specialist owns configuration, APIs, and debugging of the
+  chosen component.
+- _Styling a specialist's component:_ generic token/Tailwind/brand questions go
+  to the Styling Agent; component-specific theming APIs stay with that
+  component's specialist (or with you while none exists).
+- _Cross-cutting audits win:_ a11y/i18n questions route to those auditors once
+  they ship, no matter which component they concern.
+
+## Rules
+
+1. **Never invent APIs.** Only cite components, props, and entry points you can
+   verify in the skills or the Storybook docs. If you cannot verify, say so.
+2. **Multi-domain questions:** consult each relevant specialist or skill,
+   synthesize one answer, and attribute which source produced which part.
+3. **No fit / unsure:** admit it and point at the catalog skill or
+   https://ui.mieweb.org — never improvise outside the roster.
+4. The installed `mieweb-ui.instructions.md` rules are non-negotiable; your
+   answers must comply with them (NITRO-first, ButtonGroup, tokens-not-hardcoded
+   colors, lucide-react icons, a11y, i18n/RTL).

package/agent/agents/mieweb-ui-styling.agent.md

@@ -0,0 +1,83 @@
+---
+name: MIE UI Styling Agent
+description: Styling & theming specialist for the @mieweb/ui design system — design tokens, Tailwind classes, CSS variables, brands and brand switching, dark mode, and motion/animation. Invoke to audit components for branding compliance, fix hardcoded colors/radius, apply or create a brand, debug dark mode, or wire up motion.
+tools: ['search', 'codebase', 'fetch', 'editFiles']
+handoffs:
+  - label: Apply Fixes
+    agent: agent
+    prompt: Apply the styling fixes identified above to the codebase.
+    send: false
+---
+
+# MIE UI Styling Agent
+
+You are the styling and theming specialist for the **@mieweb/ui** design
+system. You audit and fix token, brand, dark-mode, and motion usage. You are a
+**fixer**: you may edit files when asked to fix, but always report findings
+first.
+
+## Your sources of truth (never inline-duplicate them)
+
+- **`mieweb-ui-tokens` skill** — every color scale, semantic token, radius,
+  typography, shadow, and animation class, with the CSS variable and default
+  each resolves to, plus the dark-mode model and TW3-safelist/TW4-`@source`
+  setup. Consult it before naming any token.
+- **`mieweb-ui-brands` skill** — available brands, applying/switching brands,
+  the create-a-new-brand procedure, and the brand-CSS-without-base-stylesheet
+  pitfall.
+- The installed `mieweb-ui.instructions.md` — Rules 5–7 (variants not
+  className hacks, never hardcode colors, theme through the brand system) are
+  the policy you enforce.
+
+## What to flag in an audit
+
+1. **Hardcoded palette colors** — `bg-blue-500`, `text-violet-600`, hex values,
+   `style={{ color: … }}`, gradients with raw colors. Fix: `primary-*`,
+   `secondary-*`, `neutral-*`, or a semantic token (`bg-background`,
+   `text-muted-foreground`, `border-border`).
+2. **Raw status colors** — `bg-green-*`/`bg-amber-*`/`bg-red-*` for state. Fix:
+   the `success` / `warning` / `destructive` / `info` scales.
+3. **Arbitrary radius** — `rounded-[20px]` and friends. Fix: the mapped
+   `rounded-sm|md|lg|xl|2xl` brand tokens (`rounded-full` is fine for
+   circles/pills).
+4. **Variant imitation** — utility classes restyling a component to mimic an
+   existing `variant`/`size` prop (Rule 5). Fix: use the prop.
+5. **Global CSS** — element-selector overrides or resets (Rule 7). Fix:
+   component-scoped styles.
+6. **Physical direction classes** — `ml-*`/`pl-*`/`left-*`/`text-left` in new
+   code; prefer logical `ms-*`/`ps-*`/`start-*`/`text-start` (RTL rule). Flag
+   it, and route deeper i18n/RTL audits to that specialist once it ships.
+7. **Hand-rolled animation** — bespoke keyframes or transition soup where a
+   library `animate-*` class or motion preset exists.
+
+## Motion (absorbed domain)
+
+- Baseline micro-animations are CSS: the `animate-*` classes in the tokens
+  skill (fade, slide, shimmer, scale — with `*-rtl` variants).
+- Rich motion is **opt-in** via `@mieweb/ui/motion`: wrap the app in
+  `MotionProvider`; components opted in upgrade automatically. `Animated`,
+  `AnimatedPresence`, `useMotionRuntime`, and `motionPresets` build custom
+  sequences. An app that never imports the entry never bundles the `motion`
+  library — do not import it anywhere else.
+- Respect `prefers-reduced-motion`; `MotionProvider` handles it — another
+  reason not to hand-roll.
+
+## Audit output format
+
+### 🔍 Audit results for `<scope>`
+
+| File | Line | Issue | Current | Recommended |
+| ---- | ---- | ----- | ------- | ----------- |
+
+Then a short summary (what passes, what fails, counts). Offer the **Apply
+Fixes** handoff — or fix directly when the user asked you to fix.
+
+## Rules
+
+1. Verify every token you recommend against the tokens skill — never invent
+   token names.
+2. Brand work follows the brands skill procedure exactly; remind users that
+   brand assets are trademarked (see `BRAND_GUIDELINES.md`).
+3. Component selection questions ("which component?") belong to the MIE UI
+   Design Agent — redirect rather than guess.
+4. Keep fixes minimal and behavior-preserving; one concern per fix.

package/agent/init-agent.mjs

@@ -8,15 +8,29 @@
  *  2. A marked block in `AGENTS.md` — read by Claude Code, Cursor, Codex,
  *     and other agents that follow the AGENTS.md convention.
  *
- * Idempotent: rerun after upgrading @mieweb/ui to refresh both targets.
+ * With `--experimental-agents` (epic #545, until P5.2 flips the default):
+ *  3. The MIE UI agent team — `.github/agents/mieweb-ui-*.agent.md` and
+ *     the `.github/skills/mieweb-ui-*` dirs, each stamped with a managed
+ *     marker so reruns refresh them, plus an agent-roster section in the
+ *     `AGENTS.md` block for tools without native subagent support.
+ *
+ * Idempotent: rerun after upgrading @mieweb/ui to refresh all targets.
+ * Managed-marker rules are specified in agent/README.md.
  */
-import { readFileSync, writeFileSync, mkdirSync, existsSync } from 'node:fs';
+import {
+  readFileSync,
+  writeFileSync,
+  mkdirSync,
+  existsSync,
+  readdirSync,
+} from 'node:fs';
 import { dirname, join, resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
 
 const command = process.argv[2];
+const experimentalAgents = process.argv.includes('--experimental-agents');
 if (command !== 'init-agent') {
-  console.log('Usage: npx @mieweb/ui init-agent');
+  console.log('Usage: npx @mieweb/ui init-agent [--experimental-agents]');
   process.exit(command ? 1 : 0);
 }
 
@@ -32,12 +46,131 @@ mkdirSync(instructionsDir, { recursive: true });
 writeFileSync(instructionsPath, template);
 console.log(`✔ wrote .github/instructions/mieweb-ui.instructions.md`);
 
-// --- 2. AGENTS.md marked block ------------------------------------------
+// --- 2. Agent team (only with --experimental-agents) --------------------
+const MARKER_PREFIX = '<!-- mieweb-ui:managed ';
+const marker = `${MARKER_PREFIX}@mieweb/ui@${pkg.version} -->`;
+// Marker goes on the first body line — after frontmatter if present.
+const withMarker = (content) => {
+  const fm = content.match(/^---\n[\s\S]*?\n---\n/);
+  return fm
+    ? `${fm[0]}${marker}\n${content.slice(fm[0].length)}`
+    : `${marker}\n${content}`;
+};
+const isManaged = (path) => readFileSync(path, 'utf8').includes(MARKER_PREFIX);
+const frontmatterField = (content, field) =>
+  content.match(new RegExp(`^${field}:\\s*(.+)$`, 'm'))?.[1].trim();
+const warnUserFile = (label) =>
+  console.warn(
+    `⚠ skipped ${label} — exists without a managed marker (user-created); not overwritten`
+  );
+const warnOrphan = (label) =>
+  console.warn(
+    `⚠ ${label} is installed but no longer shipped by @mieweb/ui — remove manually if unwanted`
+  );
+
+let roster = '';
+if (experimentalAgents) {
+  const agentLines = [];
+  const skillLines = [];
+
+  // Agents: file granularity.
+  const agentsTemplateDir = join(here, 'agents');
+  const agentTemplates = readdirSync(agentsTemplateDir)
+    .filter((f) => f.endsWith('.agent.md'))
+    .sort();
+  const destAgentsDir = join(targetRoot, '.github', 'agents');
+  for (const file of agentTemplates) {
+    const content = readFileSync(join(agentsTemplateDir, file), 'utf8');
+    const dest = join(destAgentsDir, file);
+    if (existsSync(dest) && !isManaged(dest)) {
+      warnUserFile(`.github/agents/${file}`);
+    } else {
+      mkdirSync(destAgentsDir, { recursive: true });
+      writeFileSync(dest, withMarker(content));
+      console.log(`✔ wrote .github/agents/${file}`);
+    }
+    agentLines.push(
+      `- **${frontmatterField(content, 'name')}** (\`.github/agents/${file}\`): ${frontmatterField(content, 'description')}`
+    );
+  }
+
+  // Skills: per-file refresh rules, same as agents — a managed SKILL.md must
+  // not authorize clobbering an unmarked (user-created) companion file.
+  const skillsTemplateDir = join(here, 'skills');
+  const skillTemplates = readdirSync(skillsTemplateDir, {
+    withFileTypes: true,
+  })
+    .filter((d) => d.isDirectory())
+    .map((d) => d.name)
+    .sort();
+  const destSkillsDir = join(targetRoot, '.github', 'skills');
+  for (const dir of skillTemplates) {
+    const srcDir = join(skillsTemplateDir, dir);
+    const skillContent = readFileSync(join(srcDir, 'SKILL.md'), 'utf8');
+    let wrote = false;
+    for (const f of readdirSync(srcDir).sort()) {
+      const content = readFileSync(join(srcDir, f), 'utf8');
+      const dest = join(destSkillsDir, dir, f);
+      if (existsSync(dest) && !(f.endsWith('.md') && isManaged(dest))) {
+        warnUserFile(`.github/skills/${dir}/${f}`);
+        continue;
+      }
+      mkdirSync(join(destSkillsDir, dir), { recursive: true });
+      writeFileSync(dest, f.endsWith('.md') ? withMarker(content) : content);
+      wrote = true;
+    }
+    if (wrote) console.log(`✔ wrote .github/skills/${dir}/`);
+    skillLines.push(
+      `- \`${dir}\` (\`.github/skills/${dir}/SKILL.md\`): ${frontmatterField(skillContent, 'description')}`
+    );
+  }
+
+  // Report (never delete) installed mieweb-ui-* artifacts we no longer ship.
+  if (existsSync(destAgentsDir)) {
+    for (const f of readdirSync(destAgentsDir)) {
+      if (
+        f.startsWith('mieweb-ui-') &&
+        f.endsWith('.agent.md') &&
+        !agentTemplates.includes(f)
+      )
+        warnOrphan(`.github/agents/${f}`);
+    }
+  }
+  if (existsSync(destSkillsDir)) {
+    for (const d of readdirSync(destSkillsDir)) {
+      if (d.startsWith('mieweb-ui-') && !skillTemplates.includes(d))
+        warnOrphan(`.github/skills/${d}/`);
+    }
+  }
+
+  roster = [
+    '',
+    '',
+    '## MIE UI agent team (experimental)',
+    '',
+    'Installed by `npx @mieweb/ui init-agent --experimental-agents`. Tools with',
+    'native agent support (VS Code Copilot) discover these automatically; other',
+    'tools should read the files below and adopt the matching persona. Start with',
+    'the **MIE UI Design Agent** for any @mieweb/ui question.',
+    '',
+    '### Agents',
+    '',
+    ...agentLines,
+    '',
+    '### Skills',
+    '',
+    ...skillLines,
+  ].join('\n');
+}
+
+// --- 3. AGENTS.md marked block ------------------------------------------
 const BEGIN = '<!-- mieweb-ui:begin -->';
 const END = '<!-- mieweb-ui:end -->';
-// Same rules, minus the VS Code-specific frontmatter.
+// Same rules, minus the VS Code-specific frontmatter. The roster rides inside
+// the block so AGENTS.md-only tools see the team too (empty when flagless —
+// the default run stays byte-identical to the pre-team behavior).
 const body = template.replace(/^---\n[\s\S]*?\n---\n+/, '');
-const block = `${BEGIN}\n${body.trimEnd()}\n${END}`;
+const block = `${BEGIN}\n${body.trimEnd()}${roster}\n${END}`;
 
 const agentsPath = join(targetRoot, 'AGENTS.md');
 if (!existsSync(agentsPath)) {

package/agent/mieweb-ui.instructions.md

@@ -275,3 +275,21 @@ export default function App() {
 Privacy: conversation content stays between the user and Ozwell and is never
 relayed to the host page. The host receives only the tool calls it declares,
 lifecycle/error events, and any data the user explicitly shares (opt-in).
+
+## Rule 17: Icons come from lucide-react
+
+- **Every icon comes from `lucide-react`** — either a `*Icon` convenience re-export from `@mieweb/ui` (`HomeIcon`, `SearchIcon`, `TrashIcon`, …) or a direct `lucide-react` import for the full set.
+- **Never hand-roll an `<svg>` icon and never add another icon library** (Font Awesome, Heroicons, Material Icons, …) — `@fortawesome/*` is ESLint-blocked in the library for this reason, and mixed icon sets break visual consistency.
+- Sizing: `h-4 w-4` (16px) is the default inline size; `h-5 w-5` for emphasis, `h-3.5 w-3.5` in dense UI. Lucide's `size={16}` prop is equivalent.
+- Icon-only controls need an `aria-label` (Rules 2 and 9); purely decorative icons get `aria-hidden="true"`.
+- For dynamic icon props, type them as `LucideIcon` (re-exported from `@mieweb/ui`).
+
+```tsx
+// ✅ Convenience re-exports, or the full set directly
+import { SearchIcon, TrashIcon } from '@mieweb/ui';
+import { Stethoscope } from 'lucide-react';
+
+// ❌ Hand-rolled or foreign icons
+// <svg viewBox="0 0 24 24"><path d="..." /></svg>
+// import { faTrash } from '@fortawesome/free-solid-svg-icons';
+```

package/agent/skills/mieweb-ui-brands/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: mieweb-ui-brands
+description: Brand theming for @mieweb/ui — available brands, switching brands at build or runtime, the dark-mode model, and the step-by-step procedure for creating a new brand. USE WHEN applying a brand to an app, switching themes, debugging brand colors not applying, or adding a brand for a new product.
+---
+
+# @mieweb/ui brands
+
+A brand is a set of `--mieweb-*` CSS variable overrides. Components never change per brand — they read tokens via the Tailwind preset (see the `mieweb-ui-tokens` skill for every token). Brand names, logos, and assets are trademarks of Medical Informatics Engineering — see `BRAND_GUIDELINES.md`; they are not covered by the code license.
+
+## Available brands
+
+`bluehive`, `ccme`, `default`, `enterprise-health`, `mieweb`, `ozwell`, `waggleline`, `webchart` — each has a `BrandConfig` in `src/brands/<name>.ts`, and all except `default` ship a committed CSS file exported as `@mieweb/ui/brands/<name>.css`.
+
+## Applying a brand
+
+**Static (most apps)** — import the brand CSS once:
+
+```ts
+import '@mieweb/ui/styles.css'; // or init.css — REQUIRED, see pitfall below
+import '@mieweb/ui/brands/bluehive.css';
+```
+
+Tailwind 4 consumers: keep both imports plain (unlayered), in that order. Do **not** wrap only the brand CSS in `layer(theme)` — the base stylesheet's `:root` defaults are unlayered, and unlayered declarations beat layered ones, so a layered brand's overrides would silently lose and the brand would not apply.
+
+**Runtime switching** — generate CSS from a brand config and inject it:
+
+```ts
+import { brands, generateBrandCSS } from '@mieweb/ui/brands';
+
+const config = await brands['waggleline']();
+styleEl.textContent = generateBrandCSS(config);
+```
+
+`createBrandPreset(config)` / `generateTailwindTheme(config)` exist for build-time Tailwind integration of a single brand.
+
+## Dark mode
+
+Each brand CSS defines light-mode semantic tokens on `:root` and dark-mode overrides under `[data-theme='dark'], .dark`. Toggling dark mode = adding/removing the `.dark` class or `data-theme="dark"` attribute on an ancestor (usually `<html>`). Components already carry their `dark:` variants; never write brand- or mode-specific component code.
+
+## Pitfall: brand CSS alone is not a theme
+
+Brand CSS files emit only the **primary scale + semantic tokens**. The other scales (`neutral`, `secondary`, `destructive`, …) get their defaults from the library's base stylesheet. If an app imports a brand CSS **without** `@mieweb/ui/styles.css` (or `init.css`), those scales resolve to nothing and classes like `dark:bg-neutral-900` render transparent. Always load the base stylesheet first.
+
+## Creating a new brand
+
+1. **Config** — add `src/brands/<name>.ts` exporting a `BrandConfig` (`name`, `displayName`, `colors`, `typography`, `borderRadius`, `boxShadow`). Only the `primary` `ColorScale` (50–950) and `light`/`dark` `SemanticColors` are required in `colors`; `secondary`/`neutral`/`destructive`/`success`/`warning`/`info` scales and `accent` are optional and fall back to library defaults. Follow an existing brand (e.g. `src/brands/waggleline.ts`) including its header comment documenting the brand palette.
+2. **CSS** — generate and commit `src/brands/<name>.css` from the config: `generateBrandCSS(config)` produces the `:root` + dark-mode blocks. Keep the usage header comment the other brand CSS files carry. `pnpm build`'s `copy:brand-css` step copies it to `dist/brands/` automatically.
+3. **Register** — in `src/brands/index.ts`: add the named export and an entry in the lazy `brands` map. Storybook keeps its own registry in `.storybook/preview.tsx`: add the brand to its `brands` map and to the brand toolbar `items` — unknown keys silently fall back to BlueHive, so skipping this makes step 6 impossible.
+4. **Exports** — add a `"./brands/<name>.css"` entry to `package.json` `exports` (next to the existing brand CSS entries).
+5. **Logos/assets** — only with brand-owner approval; they live under `src/brands/logos/`.
+6. **Verify** — switch Storybook to the new brand and check primary actions, semantic states, and dark mode; run `pnpm typecheck && pnpm lint`.