@morya-ui/setup 0.4.0 → 0.4.2

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@morya-ui/setup",
   "type": "module",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "description": "One-shot setup for morya-ui: install the library, multi-editor MCP, Agent skills, and design config.",
   "license": "MIT",
   "homepage": "https://github.com/morya-space/morya-ui/tree/main/packages/setup#readme",

package/template/.agents/skills/morya-ui-pages/SKILL.md

@@ -19,12 +19,15 @@ description: >
 
 Guide agents that **consume morya-ui** across the full product surface — not only admin CRUD.
 
-Two layers always apply:
+## Must follow (restrained)
 
-1. **Contract** — only `M*` controls, `--m-*` tokens, real APIs (MCP/docs). Never invent props or mix UI kits.
-2. **Craft** — pick the right surface pattern, then apply intentional visual direction (distilled from Frontend Design / Impeccable / UI-UX-Pro-Max ideas). Ops stays disciplined; expressive surfaces (landing, auth brand moments, empty states) may take a justified aesthetic risk — still on-token and on-component.
+1. **Contract first** — only `M*` + `--m-*` + real MCP/docs APIs. No second UI kit, no invented props.
+2. **Default quieter** — no reference / vague ask → quiet flat on-token face. Do not invent glass, neon, aurora, or marketing heroes.
+3. **Reference wins atmosphere** — if the user gives a screenshot/mock/description, follow traits that appear there (map via [reference-visual-map.md](references/reference-visual-map.md)); do **not** strip them to “look safer,” and do **not** add decorations the reference lacks.
+4. **Say the direction** — in the reply, one line `style:` + optional `signature:` (e.g. `style: quiet flat`, or `style: follow reference — soft frosted cards + round primary`).
+5. **Gate** — `validate_usage` + `validate_page({ brief })`. With a visual reference, also run the fidelity check in [review-checklist.md](references/review-checklist.md).
 
-**Default build path (composition-first):** pin surface → **`map_reference` / `recommend_page({ brief, density })`** → L2 decisions + page snippets → signature shell (`get_style_shells`) → craft → **`validate_usage` + `validate_page({ brief })`**. Golden pages are an **optional** whole-page block-order check — not the default clone target.
+**Default build path:** pin surface → **`map_reference` / `recommend_page({ brief, density })`** → decisions + snippets → shell only if needed → craft → **`validate_usage` + `validate_page`**. Golden pages are an **optional** block-order check.
 
 When companions conflict with this skill or project `DESIGN.md`, **this skill wins**.
 
@@ -76,6 +79,7 @@ For Express / branded Account moments, also draft a tiny **design plan** (see [v
 | Reference fidelity | **`map_reference`** (description / requiredBlocks / density) → follow `mapping` | Describe blocks in chat; compose matching snippets |
 | Ops pattern + snippets | `recommend_page({ density, brief })` → **`suggestedSnippets`** / **`referenceMapping`** / **`get_page_snippet`** + **`recommend_component`** | [page-layouts.md](references/page-layouts.md) + [decision-recipes.md](references/decision-recipes.md) |
 | Style direction | `recommend_page({ style })` / **`get_style_direction`** | [style-presets.md](references/style-presets.md) |
+| Screenshot / mock → library moves | — | [reference-visual-map.md](references/reference-visual-map.md) |
 | Signature shells (Account / Express / Flow) | **`get_style_shells`** (`account-split`, `express-hero`, …) | [visual-craft.md](references/visual-craft.md) |
 | Account / Express / empty / result | snippets (`auth-split-shell`, `empty-block`, `result-block`, …) + `recommend_page` | [surfaces.md](references/surfaces.md) |
 | Optional whole-page block order | `get_golden_page` only when unsure of section order or user asks to mirror a golden sample | [page-layouts.md](references/page-layouts.md) |
@@ -112,19 +116,20 @@ For Express / branded Account moments, also draft a tiny **design plan** (see [v
 
 Run **before** delivery. Do not stop at a structurally correct shell.
 
-1. Resolve **style direction** ([style-presets.md](references/style-presets.md)) — reference/description first; else prompt cues; else **ask**; never silent AI face. **No preset catalog.**
-2. Apply lane craft from [visual-craft.md](references/visual-craft.md):
-   - **Ops / Operate:** resolved direction + § Ops polish (one primary, menu icons, `MStatus`, designed empty, no decorative cards).
-   - **Account / Flow:** one calm brand or empty-state cue from § Shell recipes; form errors via `errorMessage` / token `role="alert"`.
-   - **Express / Persuade:** short design plan + one signature; avoid AI-default looks; optional 1–2 token-only motions via `useMotion`. Signature ≠ unearned gradient/glass/neon.
-3. **If companions are already installed** (see [optional-companions.md](references/optional-companions.md)):
-   - Express / brand → may load **`frontend-design`** for POV after contract **and style direction** are fixed
-   - User asks 更大胆/更克制/polish/audit → may load **`impeccable`** command (`bolder` / `quieter` / `polish` / …) **inside** the resolved direction
-   - Mood/industry keywords only → optional **`ui-ux-pro-max`** search, then map to `--m-*` (not a preset id)
-   - a11y pass → optional **`fixing-accessibility`** after visual
-   - Max **one** visual companion per task; always remediate with `M*` + `--m-*`; strip companion-added AI atmosphere the user did not ask for
-4. If companions are **absent**, use distilled visual-craft / style-direction — do **not** block or ask to install mid-task.
-5. **All lanes:** responsive, focus visible, domain-real copy. User **reference** overrides companion taste within the morya contract.
+1. Resolve **style direction** ([style-presets.md](references/style-presets.md)) — reference first; else cues; else **ask**; else quieter flat. **No preset catalog.**
+2. If a screenshot/mock is present, translate visible traits with [reference-visual-map.md](references/reference-visual-map.md) — approximate with `M*` + tokens; state what cannot be 1:1.
+3. Apply lane craft from [visual-craft.md](references/visual-craft.md):
+   - **Ops / Operate:** resolved direction + § Ops polish (one primary, menu icons, `MStatus`, designed empty, no decorative cards). Stay restrained unless the reference shows more.
+   - **Account / Flow:** calm shell; form errors via `errorMessage` / token `role="alert"`.
+   - **Express / Persuade:** short design plan + one signature **only when** the brief/reference calls for it; optional 1–2 token-only motions via `useMotion`.
+4. **If companions are already installed** (see [optional-companions.md](references/optional-companions.md)):
+   - Express / brand → may load **`frontend-design`** after contract **and style direction** are fixed
+   - User asks 更大胆/更克制/polish/audit → may load **`impeccable`** **inside** the resolved direction
+   - Mood keywords only → optional **`ui-ux-pro-max`** search → map to `--m-*`
+   - a11y → optional **`fixing-accessibility`**
+   - Max **one** visual companion; remediate with `M*` + `--m-*`; strip companion atmosphere the user/reference did not ask for
+5. Companions absent → do **not** block or ask to install mid-task.
+6. **All lanes:** responsive, focus visible, domain-real copy. State `style:` (+ `signature:` when useful) before delivery.
 
 Named polish modes (`quieter` | `bolder` | `clarify` | `audit` | …): extra pass when the user asks to improve an existing screen.
 
@@ -136,7 +141,7 @@ Use [review-checklist.md](references/review-checklist.md) (contract + craft sect
 
 1. `validate_usage` on the page (or per component) — API accuracy gate  
 2. `validate_page` with the **same `brief`** used in `map_reference` / `recommend_page` — **`ok` must be true** (contract); craft suggestions addressed or consciously waived  
-3. Optional screenshot self-check when the user gave a visual reference (see [review-checklist.md](references/review-checklist.md))
+3. **Required** fidelity check when the user gave a visual reference (see [review-checklist.md](references/review-checklist.md) § Reference fidelity)
 
 Do not deliver with unresolved `unknown-prop` / `unknown-event` or `validate_page` contract failures (`brief-missing-*`, wrong table props, …).
 
@@ -150,7 +155,8 @@ Do not deliver with unresolved `unknown-prop` / `unknown-event` or `validate_pag
 - Ops surfaces follow page-layout **block order** — do not replace them with marketing heroes.
 - Express surfaces still use `M*` for controls and `--m-*` for color/space; do not introduce shadcn/Element/etc. stacks suggested by generic design skills.
 - Soft-load companions only; never require Impeccable / UI-UX-Pro-Max / Frontend Design to be installed.
-- Do **not** invent decorative glass / neon / aurora / neumorph / full-page gradients unless the **user reference or description** clearly asks for them.
+- **Restrained by default:** do **not** invent decorative glass / neon / aurora / neumorph / full-page gradients when there is no reference/description asking for them.
+- **With a reference:** follow atmosphere that is **visible in the reference**; do not “sanitize” it away; do not add extra decoration beyond it. Approximate with tokens — pixel-perfect art is out of scope.
 - Do **not** add new golden-page craft variants (`list-page-*`); express density/sider via style direction + polish.
 
 ## Soft companions
@@ -171,7 +177,8 @@ Routing, conflict rules, and load budget: [optional-companions.md](references/op
 - Vue 3 `<script setup lang="ts">`.
 - PascalCase `M*` in templates.
 - Domain-real copy and data shapes (not placeholder “示例 / Name / No data” when the brief names a product).
-- Scoped CSS minimal; tokens only (`color-mix` OK). Prefer **flat** surfaces; gradients / glass / glow **only** when the user/reference asks (control widths may be inline).
+- Scoped CSS minimal; tokens only (`color-mix` OK). Prefer **flat** surfaces by default; gradients / glass / glow only from user/reference (control widths may be inline).
+- Reply includes `style:` (and `signature:` when following a richer reference).
 - Craft pass completed for the lane (see step 5).
 - For multi-file asks: sensible `views/` / `components/` split; otherwise one SFC is fine.
 
@@ -181,11 +188,12 @@ Routing, conflict rules, and load budget: [optional-companions.md](references/op
 | --- | --- |
 | [surfaces.md](references/surfaces.md) | Choosing / composing non-Ops (and hybrid) surfaces |
 | [page-layouts.md](references/page-layouts.md) | Ops block-order checklists (fill with snippets) |
-| [style-presets.md](references/style-presets.md) | Style resolution (no preset catalog) |
+| [style-presets.md](references/style-presets.md) | Style resolution (no preset catalog); reference vs restrained default |
+| [reference-visual-map.md](references/reference-visual-map.md) | Screenshot/mock traits → `M*` / token / shell moves |
 | [visual-craft.md](references/visual-craft.md) | Ops polish, shell recipes, anti-defaults, polish modes |
 | [design-system.md](references/design-system.md) | Principles, tokens, bans |
 | [component-index.md](references/component-index.md) | Catalog + decision-id index |
 | [decision-recipes.md](references/decision-recipes.md) | Scenario → component → key props (generated; offline MCP mirror) |
 | [feedback.md](references/feedback.md) | message / toast / MMessage |
-| [review-checklist.md](references/review-checklist.md) | Pre-delivery checks |
+| [review-checklist.md](references/review-checklist.md) | Pre-delivery checks + reference fidelity |
 | [optional-companions.md](references/optional-companions.md) | Combining with external design skills |

package/template/.agents/skills/morya-ui-pages/references/component-index.md

@@ -18,7 +18,7 @@ Full API: docs site `/components` or MCP (`get_component`, `search`, `validate_u
 
 ## Actions
 
-`MButton` / `MButtonGroup` (primary `severity="primary"`, danger `severity="danger"`), `MSplitButton` (main action + menu), `MSpeedDial` (floating action cluster)
+`MButton` / `MButtonGroup` (primary `type="primary"`, danger `danger` / `color="danger"`; counts via wrapping `MBadge`, not Button props), `MSplitButton` (main action + menu), `MSpeedDial` (floating action cluster)
 
 ## Forms · inputs
 
@@ -93,6 +93,8 @@ Open MCP `recommend_component({ decision })` or the matching section in [decisio
 | `MDropdown` as form enum | `MSelect` (`selection-choice`) |
 | `MTable` `:data` | `:rows` (`data-display-choice`) |
 | `<MMessage severity>` as an inline alert | Field `errorMessage`, or token `role="alert"` (`feedback-choice`) |
+| `MButton severity="primary"` / `severity="danger"` | `type="primary"` / `danger` or `color="danger"` |
+| `MButton badge` / `badgeColor` | Wrap with `MBadge` (`status-label-choice`) |
 | Hand `<table>` | `MTable` |
 | Hand modal div | `MDialog` / `MConfirmDialog` |
 | Hand spinner or `MProgressSpinner` as a region / page mask | `MLoading` / `v-loading` (`loading-choice`) |

package/template/.agents/skills/morya-ui-pages/references/decision-recipes.md

@@ -32,7 +32,7 @@ This file is the **offline** mirror for agents without MCP.
 - v-model / modelValue 控制开关（不要用 visible）
 - header 或 title 设弹窗标题
 - width 约 32rem 适配短表单（见 form-in-dialog snippet）
-- 表单字段用 fluid；主按钮 severity="primary"
+- 表单字段用 fluid；主按钮 type="primary"
 
 **Recipe · slots**
 
@@ -117,7 +117,7 @@ This file is the **offline** mirror for agents without MCP.
 **Recipe · events**
 
 - MForm @submit（或 @submit.prevent）
-- 提交按钮 type="submit" + severity="primary"
+- 提交按钮 html-type="submit" + type="primary"
 
 **Related snippets**
 
@@ -770,7 +770,7 @@ This file is the **offline** mirror for agents without MCP.
 **Recipe · props**
 
 - 左侧标题、右侧主按钮
-- 主按钮 severity="primary"；全页仅一个主按钮
+- 主按钮 type="primary"；全页仅一个主按钮
 - 批量操作条也可放工具栏区
 
 **Recipe · slots**
@@ -1282,6 +1282,7 @@ This file is the **offline** mirror for agents without MCP.
 **Anti-patterns**
 
 - 独立状态文案用 Badge → Status / Tag
+- MButton badge / badgeColor → 用 MBadge 包裹按钮
 
 
 ---
@@ -1588,7 +1589,7 @@ This file is the **offline** mirror for agents without MCP.
 - v-model / modelValue
 - header + message
 - acceptLabel / rejectLabel
-- acceptSeverity="danger" 用于删除
+- acceptColor="danger" 用于删除
 
 **Recipe · events**
 
@@ -1620,7 +1621,7 @@ This file is the **offline** mirror for agents without MCP.
 **Recipe · props**
 
 - v-model / modelValue
-- message；acceptSeverity="danger" 按需
+- message；acceptColor="danger" 按需
 - target 锚定触发元素（或 position）
 - placement top|bottom|left|right
 

package/template/.agents/skills/morya-ui-pages/references/design-system.md

@@ -6,7 +6,7 @@ Canonical long form lives in project-root `DESIGN.md` when the AI config pack is
 
 1. **Components first** — layout, forms, tables, overlays use `M*` from `morya-ui`, not equivalent hand-rolled DOM.
 2. **Tokens first** — color, space, radius, shadow, motion via `--m-*`. No raw `#hex` / `rgb()` in page styles.
-3. **Semantic actions** — primary work uses `MButton severity="primary"`; destructive uses `severity="danger"` or confirm dialogs.
+3. **Semantic actions** — primary work uses `MButton type="primary"`; destructive uses `danger` / `color="danger"` or confirm dialogs. Badge / Tag / Alert still use `severity`.
 4. **Accessibility** — fields have visible labels; icon buttons have `aria-label`; overlays dismiss with Esc (library default).
 5. **ConfigProvider** — wrap the app (or isolated demo) in `MConfigProvider` for locale, theme, density, overlay mount.
 

package/template/.agents/skills/morya-ui-pages/references/page-layouts.md

@@ -118,7 +118,7 @@ Inline style is acceptable for control widths (e.g. filter `width: 14rem`).
 2. `MPageHeader` (title + short description)
 3. `MTabs` with **`v-model` + `:tabs`** (not `:items` / `:value`)
 4. Per tab: `MPageSection variant="form"` + `MForm` + save in `variant="actions"`
-5. Dangerous zone last: `severity="danger"` + confirm
+5. Dangerous zone last: `MButton danger` (or `color="danger"`) + confirm
 
 ## Wizard — block order
 

package/template/.agents/skills/morya-ui-pages/references/reference-visual-map.md

@@ -0,0 +1,50 @@
+# Reference visual map (emergency only)
+
+Use this **only when the user provides a screenshot, mock, URL, or “像 XX”**.  
+It is **not** a default style catalog. Without a reference, stay quieter ([style-presets.md](style-presets.md)).
+
+Goal: translate visible traits into **`M*` + `--m-*`** moves. Prefer approximation over a second UI kit. Pixel-perfect art / custom illustrations are out of scope unless assets already exist in the project.
+
+## Conflict rule
+
+| Situation | Do |
+| --- | --- |
+| No reference | Quiet flat / restrained Ops polish. Do not invent glass, neon, aurora, wash, or marketing heroes. |
+| Reference shows a trait | Follow that trait with tokens/`M*`. Do not strip it to “look safer.” |
+| Reference does **not** show a trait | Do not add it. |
+| Trait cannot be 1:1 | Approximate; say so in `signature:` / delivery notes. |
+
+## Structure first (always)
+
+Call MCP **`map_reference`** / `recommend_page({ brief })` for blocks (`filters`, `table`, `kpi`, `auth`, …).  
+This file only covers **visual traits** after structure mapping exists.
+
+## Trait → library move
+
+| If you see… | Prefer… | Avoid… |
+| --- | --- | --- |
+| Soft tinted page background | Light `color-mix` wash on page shell from `--m-color-primary` / surface (small %) | Raw hex wash; stacked aurora meshes |
+| Frosted / translucent cards | Semi-opaque `--m-color-surface` + border + soft `--m-shadow-*`; optional limited `backdrop-filter` only if clearly in the reference | Heavy multi-layer glass on every control |
+| Soft elevated cards (no blur) | `MCard` / section surface + `--m-shadow-sm/md` + `--m-radius-md` | Extra nested cards for decoration only |
+| Pill / capsule primary CTA | `MButton type="primary" shape="round"` — **one** in the main viewport | Multiple filled primaries |
+| Quiet secondary actions | `MButton type="text"` / default outlined | Competing solid colors |
+| Soft status / category chips | `MStatus` for state; `MTag` for labels; soft severity — not a row of solid blocks | Decorative `MTag` where `MStatus` belongs |
+| Count on a control | Wrap host with `MBadge` | Invented `MButton badge` props |
+| Left brand art + right form | `auth-split-shell` / Account split; art slot = project asset or simple token panel | Hand-rolled auth outside `MForm` |
+| Empty state with illustration | `MEmpty` + `illustration` / `#illustration` when available; clear next action | Blank table with no empty |
+| Dense admin table + filters | Ops block order + `list-filters-*` / `MTable`; keep chrome restrained even if reference is prettier | Marketing hero above CRUD |
+| Dark chrome + bright chart accents | Dark theme tokens + restrained accent; charts are project/chart lib territory | Full-page neon glow stacks copied literally |
+| Soft blue primary / lilac accents | Theme `--m-color-primary` (and related) overrides — not page-local hex soup | Second palette unrelated to tokens |
+
+## Delivery lines (required with a reference)
+
+```text
+style: follow reference — <one short reading>
+signature: <one visible cue you kept, e.g. round primary + light card elevation>
+approx: <what you could not 1:1, if any>
+```
+
+## Fidelity bar
+
+Match: block order, primary CTA role, density, status treatment, and **atmosphere that is clearly in the reference**.  
+Do not require: identical illustration artwork, identical blur strength, or non-`M*` chrome.

package/template/.agents/skills/morya-ui-pages/references/review-checklist.md

@@ -17,24 +17,38 @@
 ## Craft (all lanes — default pass)
 
 - [ ] Style direction resolved: followed user reference/description, or inferred from clear cues, or **asked** when uncertain — never silent invent; **no preset catalog**
-- [ ] Reference fidelity: `map_reference` mapping blocks present (filters/table/status/… as required)
-- [ ] Signature shell from `get_style_shells` when Account / Express / Flow need presence
+- [ ] Reply states `style:` (and `signature:` when a richer reference exists)
+- [ ] Default stays restrained when there is **no** reference (quiet flat / Ops polish)
 - [ ] Lane craft from [visual-craft.md](visual-craft.md) applied
 - [ ] If companions ran: still only `M*` + `--m-*`; no second kit ([optional-companions.md](optional-companions.md))
 - [ ] At most one primary filled button in the main viewport
 - [ ] Copy is domain-real; empty / error states say what to do next
 - [ ] Numeric table columns use `align: 'end'` + tabular nums when amounts/counts are shown
-- [ ] No AI-default look clusters unless the user/reference asked for them
-- [ ] No unearned atmosphere: stacked radial+linear washes, purple mesh, frosted glass, neon glow stacks
+- [ ] No **unearned** AI-default look clusters (reference-visible atmosphere is allowed — see [style-presets.md](style-presets.md))
 - [ ] Motion (if any) is 1–3 intentional moments and follows `useMotion` / `data-m-motion`
 - [ ] Brand differences via theme `--m-*` overrides, not page hex
 
-## Screenshot self-check (optional — when user gave a visual reference)
+## Reference fidelity (required when user gave a visual reference)
+
+Structure:
+
+- [ ] `map_reference` / `recommend_page({ brief })` mapping blocks present (filters/table/status/… as required)
+- [ ] Same `brief` passed to `validate_page`; contract `ok`
+
+Visual (use [reference-visual-map.md](reference-visual-map.md)):
+
+- [ ] Atmosphere present in the reference was approximated (not stripped “to be safe”)
+- [ ] Decorations **absent** from the reference were not invented
+- [ ] Primary CTA role/shape roughly matches (e.g. round primary when the reference shows a pill)
+- [ ] Density and status treatment roughly match
+- [ ] Delivery notes include `style:` / `signature:` / `approx:` when needed
+
+Screenshot self-check:
 
 1. Start the consumer app locally (Vite / Nuxt preview).
 2. Open the generated route; capture the first viewport.
-3. Compare to the reference: block order, primary CTA, density, status treatment — not pixel-perfect chrome.
-4. If blocks are missing, fix via snippets + re-run `validate_page({ brief })`.
+3. Compare to the reference on the bullets above — not pixel-perfect chrome or custom illustration art.
+4. If blocks or required atmosphere are missing, fix via snippets/tokens + re-run `validate_page({ brief })`.
 
 If Playwright / `webapp-testing` is available in the project, prefer an automated screenshot; otherwise a manual capture is enough.
 ## Ops

package/template/.agents/skills/morya-ui-pages/references/style-presets.md

@@ -2,11 +2,21 @@
 
 Golden pages lock **block order and APIs**. They are **not** the only allowed look. There is **no** named style-preset table (`simple` / `glass` / …). Resolve the look from the **user**, then map onto `M*` + `--m-*`.
 
+**Stance:** this skill stays **restrained by default**. Rich atmosphere is allowed when the user brings a reference or clear description — not as everyday invention.
+
+## Conflict rule (required)
+
+| Case | Rule |
+| --- | --- |
+| **No reference** | Quieter flat / restrained Ops. Do not invent glass, neon, aurora, purple mesh, or marketing heroes. |
+| **Has reference** | Follow traits **visible in the reference** (see [reference-visual-map.md](reference-visual-map.md)). Do not sanitize them away to “look safer.” Do not add decorations the reference lacks. |
+| **Anti-defaults** | Apply only to **unearned** decoration (not present in user reference/description). |
+
 ## Resolution order (required)
 
 1. **User reference or explicit description (highest)**  
    Screenshot / mock / existing page / URL / “像 XX”, or clear words (“毛玻璃一点”、“深蓝科技风”).  
-   **Must follow.** Remap to `--m-*` + `M*`. Do not switch kits, do not “improve” into another face.
+   **Must follow.** Remap to `--m-*` + `M*` via [reference-visual-map.md](reference-visual-map.md). Do not switch kits, do not “improve” into another face.
 
 2. **Clear prompt cues (when not explicit)**  
    Industry / mood words in the brief → infer and **state your reading in one sentence**.  
@@ -44,14 +54,23 @@ Pass `density` to `recommend_page` / `map_reference` — do not rely only on reg
 
 When the user provides a screenshot / mock / “像 XX”, call **`map_reference`** (or pass `brief` into `recommend_page`) with:
 
-- `description` — what you see (layout, density, primary CTA)
+- `description` — what you see (layout, density, primary CTA, **atmosphere cues**)
 - `requiredBlocks` — e.g. `filters`, `table`, `status`, `kpi`, `auth`
 - `requiredComponents` — e.g. `Table`, `Status`
 - `density` / `primaryAction` when visible
 
-Then compose **only** via returned `mapping[].snippetId`. Pass the **same brief** to `validate_page` so missing blocks fail as contract issues.
+Then compose structure via returned `mapping[].snippetId`, and map visual traits with [reference-visual-map.md](reference-visual-map.md). Pass the **same brief** to `validate_page` so missing blocks fail as contract issues. Run the **reference fidelity** checklist before delivery.
 
-## Anti-defaults (unless user/reference asks)
+In the reply, state:
+
+```text
+style: follow reference — …
+signature: …
+```
+
+## Anti-defaults (unearned only)
+
+Block these when the **user/reference did not ask**:
 
 - Purple→indigo / aurora / mesh washes  
 - Warm cream + serif + terracotta kit  
@@ -59,6 +78,8 @@ Then compose **only** via returned `mapping[].snippetId`. Pass the **same brief*
 - Unsolicited glassmorphism, neon glow stacks, neumorph on dense tables  
 - Companion “atmosphere” that overrides the user’s words  
 
+If the reference **shows** soft frosted cards or a tinted wash, reproducing a **tokenized approximation** is following the reference — not an anti-default violation.
+
 ## How to apply
 
 1. Map reference → snippets (`map_reference` / `recommend_page.referenceMapping`).  

package/template/.agents/skills/morya-ui-pages/references/visual-craft.md

@@ -77,7 +77,7 @@ Ops beauty = alignment + semantics + restraint + the right `M*` for the job, **n
 
 ## Anti-default looks
 
-Unless the user **asks** or a reference **shows** them, do not use:
+**Default is restrained.** Unless the user **asks** or a reference **shows** them, do not use:
 
 1. Cream + serif + terracotta  
 2. Acid-green / dual neon on black  
@@ -87,7 +87,8 @@ Unless the user **asks** or a reference **shows** them, do not use:
 6. Unsolicited glass, neumorph on dense tables, full-page gradients  
 7. Stacked radial + linear “atmosphere” brand panels  
 
-**Token gradients are not a free pass** — only when the user/reference asks.
+**Token gradients are not a free pass** without user/reference ask.  
+If a **reference shows** frosted cards or a light tinted wash, a tokenized approximation is following the reference — see [reference-visual-map.md](reference-visual-map.md). Do not invent richer atmosphere beyond the reference.
 
 ## Shell recipes (token-only — defaults are flat)
 

package/template/DESIGN.md

@@ -7,7 +7,7 @@
 
 1. **组件优先**：交互与布局使用库内 `M*`，不手写等价 DOM。
 2. **令牌优先**：颜色、间距、圆角、阴影、动效使用 `--m-*`；禁止裸 `#hex` / `rgb()`（`scripts/check-raw-colors.mjs` 可扫描）。
-3. **语义一致**：主操作 `severity="primary"`；破坏性操作用 `severity="danger"` 或确认。
+3. **语义一致**：主操作 `type="primary"`；破坏性操作用 `danger` / `color="danger"` 或确认。Badge / Tag / Alert 仍用 `severity`。
 4. **可访问性**：控件有可访问名称；仅图标的按钮带 `aria-label`；浮层可键盘关闭。
 5. **单一事实源**：组件 API 以 MCP / 文档为准，禁止臆造 prop、event、slot。