@morya-ui/setup 0.3.4 → 0.3.5

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

@@ -15,17 +15,18 @@
 
 ## Craft (all lanes — default pass)
 
-- [ ] Style direction resolved (reference / named preset / inferred / offered) — not silent `quiet` every time
-- [ ] Lane craft from [visual-craft.md](visual-craft.md) + [style-presets.md](style-presets.md) applied
+- [ ] Style direction resolved: followed user reference/description, or inferred from clear cues, or **asked** when uncertain — never silent invent; **no preset catalog**
+- [ ] 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
-- [ ] No AI-default look clusters unless the brief asked for them
-- [ ] Motion (if any) is 1–3 intentional moments and follows `useMotion` / `data-m-motion` (not OS `prefers-reduced-motion`)
+- [ ] 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
+- [ ] Motion (if any) is 1–3 intentional moments and follows `useMotion` / `data-m-motion`
 
 ## Ops
 
-- [ ] Matches golden / [page-layouts.md](page-layouts.md) block order
+- [ ] Matches [page-layouts.md](page-layouts.md) block order (snippets composed; golden page optional check only)
 - [ ] `MPage*` used instead of ad-hoc page chrome where applicable
 - [ ] List height: if this is a full-viewport main data list, consider `MPageContent fill` + `MTable fill`; if embedded/short/document-scroll, skip `fill`
 - [ ] Tables not wrapped in decorative `MCard` solely for borders
@@ -37,20 +38,18 @@
 ## Account / Flow / System
 
 - [ ] Primary CTA obvious; escape paths present (back / home / support)
-- [ ] Auth errors stay on the form via field `errorMessage` or a token `role="alert"` (`<MMessage>` is the message host, not an inline alert)
-- [ ] Empty uses `MEmpty` (or table `#empty` with `MEmpty`); success / HTTP errors use `MResult`
-- [ ] Empty / success states tell the user the next action
-- [ ] Inline status prefers `MStatus`; chip-like labels use `MTag`
+- [ ] Auth errors stay on the form via field `errorMessage` or a token `role="alert"`
+- [ ] Empty uses `MEmpty`; success / HTTP errors use `MResult`
+- [ ] Brand / empty atmosphere follows the **resolved direction** (defaults are flat token shells)
 - [ ] Wizard steps: one job each; actions labeled clearly
-- [ ] Brand / empty atmosphere uses token-only CSS (see visual-craft recipes)
 
 ## Express
 
 - [ ] Short design plan existed (subject, palette roles, signature)
-- [ ] First viewport has one job (not a dashboard of promos)
-- [ ] Controls still `M*`; colors/spacing map to `--m-*` / theme
-- [ ] Avoided AI-default looks unless brief requested them ([visual-craft.md](visual-craft.md))
-- [ ] Motion limited and respectful of reduced-motion
+- [ ] First viewport has one job
+- [ ] Controls still `M*`; colors/spacing map to `--m-*`
+- [ ] Avoided AI-default looks unless user/reference requested them
+- [ ] Motion limited and gated by `useMotion` / `data-m-motion`
 
 ## Tokens, a11y, responsive
 
@@ -59,6 +58,6 @@
 - [ ] Usable on a narrow viewport
 - [ ] Focus visible on interactive elements
 
-When MCP is available, contract checks above (**`validate_usage`** / **`validate_page`**) are required — not optional.
+When MCP is available, contract checks (**`validate_usage`** / **`validate_page`**) are required.
 
 If the project has `pnpm check:colors`, suggest running it after edits.

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

@@ -1,73 +1,45 @@
-# Style direction & presets
+# Style direction (no preset catalog)
 
-Golden pages lock **block order and APIs**. They are **not** the only allowed look. Pick a visual direction **before** coding so generated pages stop looking identical and stiff.
+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-*`.
 
 ## Resolution order (required)
 
-1. **Reference first** — user supplied a screenshot, mock, existing page, URL, or “像 XX / like X”.
-   - Extract: density, hierarchy, surfaces (flat vs filled), accent placement, copy tone.
-   - Remap onto `--m-*` + `M*` only. Do **not** switch UI kits or copy hex themes.
-2. **Named preset** — user asked for `soft` / 柔和留白 / `dense` / …
-3. **Prompt cues** — industry or mood words in the brief → infer the closest preset and **name it** in the reply.
-4. **Offer a choice** — still unclear → ask **one** short question with 3–4 options (ids below). If the user says “直接写 / just ship”, pick by domain heuristic — **do not always use `quiet`**.
+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.
 
-MCP: `list_style_presets` / `get_style_preset` / `recommend_page({ style })` → `styleDirection`.
+2. **Clear prompt cues (when not explicit)**  
+   Industry / mood words in the brief → infer and **state your reading in one sentence**.  
+   Decorative glass / neon / full-page gradients only when the prompt clearly asks.
 
-## Presets (user-selectable)
+3. **Uncertain → ask (required)**  
+   No reference, vague cues → **ask once** for a short description or a reference.  
+   Do not invent the full look in silence.
 
-| Id | 中文 | Best for | Distinct craft | List golden |
-| --- | --- | --- | --- | --- |
-| `quiet` | 克制经典 | Serious enterprise admin | Flat chrome, golden-like Ops polish | `list-page` |
-| `soft` | 柔和留白 | Ops / content admin | `density="spacious"`, filled filters, short descriptions | `list-page` |
-| `dense` | 高密度工具台 | Monitoring / power users | `density="compact"`, `size="small"` table, tight filters | `list-page-dense` |
-| `rail` | 侧栏强调 | Branded B2B shells | Token `color-mix` wash on sider/header only | `list-page-rail` |
-| `studio` | 工作室呼吸感 | Design / collab / knowledge | Stronger header hierarchy; optional one radial wash | `list-page` |
-| `ink` | 线框极简 | Tool / docs feel | Plain filters, bordered table, little fill | `list-page` |
+4. **Only if user declines**  
+   “你看着办 / 直接写” with still no cues → quiet flat on-token admin face, **say so**, continue.  
+   Never default to aurora / neon / unsolicited glass / cream-serif-terracotta.
 
-Full apply/avoid lists: MCP `get_style_preset` or `@morya-ui/mcp` `style-presets`. `recommend_page({ style })` routes list scaffolds to the matching golden when a craft variant exists.
+MCP: `get_style_direction` / `recommend_page({ style? })` → `styleDirection`.  
+`resolution: "ask"` means **ask the user**, not free-style.
 
-### Domain heuristics (when user says “直接写”)
+## What `style` means
 
-| Cue in brief | Prefer |
-| --- | --- |
-| 金融 / 合规 / 政务 | `quiet` or `ink` |
-| 运营 / 内容 / 教育 | `soft` |
-| 监控 / 运维 / 交易 | `dense` |
-| 强调品牌色 / LOGO | `rail` |
-| 设计 / 协作 / 知识库 | `studio` |
-| 登录 / 落地 / 品牌营销 | Account/Express atmosphere — not an Ops preset |
+- Free-text from the user (or a short paraphrase of their reference).  
+- **Not** a preset id.  
+- Optional craft cues for list goldens only: words like `dense` / `compact` / `高密` → `list-page-dense`; `rail` / `品牌侧栏` → `list-page-rail`.
 
-## How to apply on Ops pages
+## Anti-defaults (unless user/reference asks)
 
-1. Mirror golden **structure** via `recommend_page` / `get_golden_page` (list: `list-page` / `list-page-dense` / `list-page-rail` by style).
-2. Apply the chosen preset’s density / filter surface / header copy / chrome wash (or follow the craft golden when one exists).
-3. Still run [visual-craft.md](visual-craft.md) § Ops polish (one primary, menu icons, `MStatus`, designed empty).
-4. Fill height remains **conditional** — see [page-layouts.md](page-layouts.md) § List height.
+- Purple→indigo / aurora / mesh washes  
+- Warm cream + serif + terracotta kit  
+- Broadsheet newspaper columns  
+- Unsolicited glassmorphism, neon glow stacks, neumorph on dense tables  
+- Companion “atmosphere” that overrides the user’s words  
 
-## Reference style checklist
+## How to apply
 
-When following a reference:
-
-- [ ] Hierarchy (what is loud vs quiet) matched with type/space, not random cards
-- [ ] Density matched (`compact` / default / `spacious`)
-- [ ] Surfaces matched (plain vs filled filters; bordered table or not)
-- [ ] Accent placement matched (chrome only vs content) using `--m-*` / `color-mix`
-- [ ] Interaction patterns stay morya-ui (`MTable` `rows`, `message`, etc.)
-
-## Anti-patterns
-
-- Treating the golden page as the only allowed aesthetic
-- Asking nothing and always emitting `quiet`
-- Inventing a second component library to “match the reference”
-- Turning Ops into a marketing landing to “look less stiff”
-- Letting Frontend Design / Impeccable / UI-UX-Pro-Max swap stacks or ignore `M*` / `--m-*` (see [optional-companions.md](optional-companions.md))
-
-## Companion pairing
-
-| Preset | Pairs well with |
-| --- | --- |
-| `quiet` / `ink` | Impeccable Operate + `quieter` / `polish` |
-| `soft` / `studio` | Frontend Design hierarchy cues; Impeccable `bolder` (one signature only) |
-| `dense` | Impeccable Operate — scanability over decoration |
-| `rail` | Frontend Design brand panel taste on **chrome only** |
-| Express (no Ops preset) | Frontend Design design plan → Impeccable `polish` |
+1. Mirror golden **structure** via `recommend_page` / `get_golden_page`.  
+2. Apply the resolved direction with tokens + layout/type — see [visual-craft.md](visual-craft.md).  
+3. Run Ops polish when on Operate surfaces.  
+4. Companions deepen **inside** the resolved direction only ([optional-companions.md](optional-companions.md)).

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

@@ -58,7 +58,7 @@ Use when the brief is landing, pricing, launch, or docs marketing — **not** fo
 
 Before coding Express: short design plan in [visual-craft.md](visual-craft.md). Map colors to `--m-*` / theme overrides; do not paste a second kit.
 
-**Anti-patterns for Express:** inset hero cards instead of a full-bleed thesis; pill-stat strips in the first viewport; purple-on-white / cream-terracotta / broadsheet defaults when the brief did not ask for them.
+**Anti-patterns for Express:** inset hero cards instead of a full-bleed thesis; pill-stat strips in the first viewport; purple aurora / cream-terracotta / broadsheet / unsolicited glass-neon when the user did not ask.
 
 ## Overlay
 
@@ -77,7 +77,7 @@ Host page stays stable; focus management comes from the overlay component.
 
 | Ask | Treat as |
 | --- | --- |
-| “后台列表 + 好看一点” | Ops + pick a non-quiet preset (`soft`/`studio`) or ask once |
+| “后台列表 + 好看一点” | Ops + ask once what “好看” means, or follow any reference they give |
 | “像附件截图一样” | Reference-first style resolution; still M* + `--m-*` |
 | “登录页有品牌感” | Account + Express craft on brand panel only |
 | “产品官网” | Express; Ops patterns do not apply |
@@ -86,6 +86,6 @@ Host page stays stable; focus management comes from the overlay component.
 ## MCP hints
 
 - Ops whole page: `recommend_page({ style? })` → `get_golden_page` → apply `styleDirection` / reference
-- Styles: `list_style_presets` / `get_style_preset`
+- Style: `get_style_direction` (no preset catalog)
 - Section: `get_page_snippet`
 - Any lane: `search` / `get_component` before unfamiliar APIs

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

@@ -1,91 +1,76 @@
 # Visual craft (distilled)
 
-Portable craft for morya-ui consumers. Inspired by **Frontend Design**, **Impeccable**, and **UI-UX-Pro-Max** — without requiring those skills to be installed. Implementation must still honor the morya-ui contract.
+Portable craft for morya-ui consumers. Inspired by **Frontend Design**, **Impeccable**, and **UI-UX-Pro-Max** — without requiring those skills. Still honor the morya-ui contract. **No named style-preset catalog.**
 
 ## When to lean on craft
 
 | Lane | Craft intensity | Default pass |
 | --- | --- | --- |
 | Ops CRUD | Low — clarity, density, golden structure | **Always** run § Ops polish |
-| Account / Flow / System | Medium — trust, hierarchy, one calm brand cue | **Always** run § Atmosphere recipes when relevant |
+| Account / Flow / System | Medium — trust, hierarchy, one calm brand cue | **Always** run § Shell recipes when relevant |
 | Express | High — design plan + one signature risk | **Always** run design plan + anti-defaults |
 
-Do **not** skip craft because the page is “just admin”. Polished Ops is quiet, aligned, and specific — not decorative.
-
-**Style is not fixed to the golden look.** Resolve direction first ([style-presets.md](style-presets.md)): reference → named preset → prompt cues → offer a choice. Golden pages define structure; presets / references define craft variety so pages do not all look stiff and identical.
-
-Market skills (**Frontend Design**, **Impeccable**, **UI-UX-Pro-Max**) deepen taste when installed — see [optional-companions.md](optional-companions.md). This file keeps a **distilled** subset so the skill stays standalone.
+**Style is not fixed to the golden look.** Resolve direction first ([style-presets.md](style-presets.md)): **user reference / description → prompt cues → ask when uncertain**.
 
 ## Companion bridge (distilled)
 
-Use these even when companions are **not** installed. If they **are** installed, run the matching companion pass **after** structure + contract, then remediate with `M*` + `--m-*`.
+Run companions **after** structure + contract + **resolved style direction**, then remediate with `M*` + `--m-*`.
 
 ### Subject first (Frontend Design)
 
-- Name a concrete **subject**, **audience**, and **single job** before visual choices.
-- Pull personality from the subject’s world (materials, artifacts, vernacular) — not from a generic “SaaS admin” mood board.
-- **One signature risk** per surface; everything else quieter (Chanel: remove one accessory).
+- Name **subject**, **audience**, **single job** before visual choices.
+- Personality from the subject’s world — not a generic “SaaS aurora” board.
+- **One signature** per surface; everything else quieter.
+- Signature = type / layout / product artifact / motion — **not** a default gradient wash.
 
 ### Mode (Impeccable)
 
 | Mode | Use when | Craft budget |
 | --- | --- | --- |
-| **Operate** | Ops lists, forms, settings, tools | Clarity, density, style preset; no marketing hero |
-| **Persuade** | Landing, pricing, campaign | Design plan + signature; controls still `M*` |
-| **Read** | Docs / long detail | Typeset + measure; calm chrome |
-| **Experience** | Gallery / showcase | Artifact leads; UI recedes |
-
-### Design plan (Express & branded Account — Frontend Design)
-
-Before code, decide:
-
-1. **Color** — 4–6 roles (bg, surface, text, muted, accent, danger). Prefer existing `--m-*`. If the project already customizes theme, extend that system; do not invent a parallel hex soup in scoped CSS. (Companions may suggest hex — **map** them onto tokens.)
-2. **Type** — display vs body vs utility. For Ops / Operate, stick to theme fonts. For Express / Persuade, a distinctive pairing is OK if fonts are loadable and fallbacks exist.
-3. **Layout concept** — one sentence + rough hierarchy (ASCII wireframe optional). Structure encodes meaning; numbered `01/02/03` only when order is real information.
-4. **Signature** — the single memorable element (motion, crop, editorial type, product artifact). Everything else quieter.
+| **Operate** | Ops lists, forms, settings | Clarity, density, resolved direction; no marketing hero |
+| **Persuade** | Landing, pricing | Design plan + signature; controls still `M*` |
+| **Read** | Docs / long detail | Typeset + measure |
+| **Experience** | Gallery / showcase | Artifact leads |
 
-Critique the plan: if it looks like the plan you would write for *any* SaaS, revise until it fits **this** subject. Brief / reference / named style preset **wins** over companion defaults.
+### Design plan (Express & branded Account)
 
-## Ops polish (baseline — every Operate / Ops page)
+1. **Color** — roles mapped to `--m-*`. Companions may suggest hex — **map** to tokens.
+2. **Type** — Ops stick to theme fonts.
+3. **Layout** — one sentence + hierarchy.
+4. **Signature** — one memorable element that fits the **user’s** direction.
 
-Apply after the golden block order is correct **and** a style direction is resolved. These are **required** baseline rules; presets may change density/chrome on top:
+If the plan looks like any-SaaS (purple wash, cream serif, neon glow) and the user did not ask for that, revise. **User reference / words win.**
 
-1. **One primary** — exactly one filled `severity="primary"` in the main viewport (usually toolbar create / form save). Query can be primary; reset stays secondary.
-2. **Sider icons** — every top-level `MMenu` item has an `icon`; icons come from one set (built-in Tabler names). No random emoji.
-3. **Status cells** — row business state → `MStatus` (dot + label). `MTag` only for categories, filters, or closable chips.
-4. **Row actions** — secondary `text` / `outlined` / `size="small"`; danger only on destructive. Prefer `MSpace` with a consistent gap; avoid a wall of filled buttons.
-5. **Filter rhythm** — search ~`14rem`, compact selects ~`10–12rem`; wrap with `MSpace wrap`. Do not stretch filters full-bleed. Secondary fields → `MPageFilters collapsible` + `#advanced`; active criteria → `MPageFilterChips` + closable `MTag`.
-6. **Empty is designed** — `MEmpty` (or table `#empty` with `MEmpty`) with a next action; never a silent blank table or a lone muted sentence.
-7. **No extra cards** — do not wrap `MPageFilters` / `MTable` in decorative `MCard` “for polish”. Dashboard chart/detail modules may use `MCard`.
-8. **Domain copy** — column labels, placeholders, and empty titles use product vernacular, not “Name / Status / No data”.
-9. **Density** — prefer theme default; use `size="small"` on dense tables inside cards. Do not invent a second spacing scale.
-10. **Quiet chrome** — breadcrumb + toolbar title are enough hierarchy; skip marketing heroes, pill-stat strips, and glow on Ops shells.
+## Ops polish (baseline)
 
-Ops beauty = **alignment + semantics + restraint**, not gradients.
+1. **One primary** filled button in the main viewport.
+2. **Sider icons** on every top-level `MMenu` item.
+3. **Status** → `MStatus`; `MTag` for categories/filters only.
+4. **Row actions** — text / outlined / small.
+5. **Filter rhythm** — search ~`14rem`, selects ~`10–12rem`.
+6. **Empty** — `MEmpty` with next action.
+7. **No extra cards** around filters/table “for polish”.
+8. **Domain copy**.
+9. **Density** — follow user cues (`compact` / spacious); don’t invent a second scale.
+10. **Quiet chrome** — no marketing heroes / glow unless the user asked.
 
-## Anti-default looks (AI clusters)
+Ops beauty = alignment + semantics + restraint, **not** gradients.
 
-Avoid spending free axes on these unless the brief asks:
+## Anti-default looks
 
-1. Warm cream (~`#F4F1EA`) + high-contrast serif + terracotta
-2. Near-black + single acid-green / vermilion accent
-3. Broadsheet: hairline rules, zero radius, dense newspaper columns
-4. Purple-on-white / purple-to-indigo gradient SaaS cliché
-5. Glow stacks, pill chip clouds, emoji as decoration, multi-layer shadows as personality
+Unless the user **asks** or a reference **shows** them, do not use:
 
-Also avoid: Inter/Roboto/Arial as the *expressive* display choice on Express surfaces when the brief allows character (utility UI may keep system/theme fonts).
+1. Cream + serif + terracotta  
+2. Acid-green / dual neon on black  
+3. Broadsheet newspaper columns  
+4. Purple aurora / mesh washes (even via `color-mix`)  
+5. Glow stacks, pill clouds, emoji decoration  
+6. Unsolicited glass, neumorph on dense tables, full-page gradients  
+7. Stacked radial + linear “atmosphere” brand panels  
 
-## Hierarchy & composition
+**Token gradients are not a free pass** — only when the user/reference asks.
 
-- **Hero is a thesis** (Express): one job in the first viewport — not stats + schedule + promos together.
-- **Structure encodes meaning**: numbered steps only when order is real information.
-- **Cards**: default off for Express heroes; use `MCard` when it groups an interaction or plan choice.
-- **Motion**: orchestrate 2–3 intentional moments max; gate custom CSS motion with `[data-m-motion="full"]` (library intensity from `useMotion`). Prefer transform/opacity over layout thrash.
-- **Density**: Ops may be compact; Express needs breathing room — match the lane.
-
-## Atmosphere recipes (token-only)
-
-Copy patterns, remap brand copy. **No hex.** Prefer `color-mix` / gradients from `--m-*`. See golden pages `login-page`, `landing-page`, `empty-state`.
+## Shell recipes (token-only — defaults are flat)
 
 ### Account — split brand panel
 
@@ -96,126 +81,49 @@ Copy patterns, remap brand copy. **No hex.** Prefer `color-mix` / gradients from
   justify-content: flex-end;
   gap: var(--m-space-4);
   padding: clamp(2rem, 6vw, 4.5rem);
-  background:
-    radial-gradient(
-      80% 60% at 10% 20%,
-      color-mix(in srgb, var(--m-color-primary) 22%, transparent),
-      transparent 55%
-    ),
-    linear-gradient(
-      165deg,
-      color-mix(in srgb, var(--m-color-primary) 16%, var(--m-color-surface)) 0%,
-      var(--m-color-surface) 55%,
-      color-mix(in srgb, var(--m-color-border) 35%, var(--m-color-surface)) 100%
-    );
+  background: color-mix(in srgb, var(--m-color-primary) 12%, var(--m-color-surface));
   border-right: 1px solid var(--m-color-border);
 }
-.login-brand__title {
-  margin: 0;
-  max-width: 12em;
-  font-size: clamp(2rem, 4vw, 3rem);
-  font-weight: 650;
-  line-height: 1.15;
-  letter-spacing: -0.03em;
-}
 ```
 
-Form side stays calm: one panel ~`22rem`, token `role="alert"` for form-level errors (not Toast, not `<MMessage severity>`).
-
 ### Express — hero plane
 
-Full-bleed thesis: brand mark (small) → one headline → one lead → CTA group → **one** dominant visual (timeline, product artifact, or edge-to-edge wash). Atmosphere:
-
 ```css
 .landing-hero__visual {
   margin-top: var(--m-space-5);
   padding: var(--m-space-5);
   border: 1px solid var(--m-color-border);
   border-radius: var(--m-radius-md);
-  background:
-    linear-gradient(
-      135deg,
-      color-mix(in srgb, var(--m-color-primary) 12%, var(--m-color-surface)),
-      var(--m-color-surface) 60%
-    );
+  background: var(--m-color-surface);
 }
 ```
 
-Optional micro-motion (one signature only):
+### Flow — empty shell
 
-```css
-[data-m-motion="full"] .landing-hero__track span {
-  animation: m-craft-fade-up 480ms ease both;
-}
-[data-m-motion="full"] .landing-hero__track span:nth-child(2) { animation-delay: 60ms; }
-[data-m-motion="full"] .landing-hero__track span:nth-child(3) { animation-delay: 120ms; }
-[data-m-motion="full"] .landing-hero__track span:nth-child(4) { animation-delay: 180ms; }
-@keyframes m-craft-fade-up {
-  from { opacity: 0; transform: translateY(0.4rem); }
-  to { opacity: 1; transform: translateY(0); }
-}
-```
-
-### Flow — empty state shell
+Prefer stock `MEmpty`. Optional light frame:
 
 ```css
 .empty-state-shell {
-  border: 1px dashed color-mix(in srgb, var(--m-color-border) 80%, var(--m-color-primary));
+  border: 1px dashed var(--m-color-border);
   border-radius: var(--m-radius-md);
-  background:
-    radial-gradient(
-      120% 80% at 50% 0%,
-      color-mix(in srgb, var(--m-color-primary) 10%, transparent),
-      transparent 55%
-    ),
-    var(--m-color-surface);
+  background: var(--m-color-surface);
+  padding: var(--m-space-6);
 }
 ```
 
-Pair with `MEmpty` + primary next step + optional secondary text button. One memory cue (icon / wash) — no emoji collage.
-
-## UX writing
-
-- Name controls by user intent (`保存更改`), not system guts (`提交表单实体`).
-- Active voice; same verb through the flow (Publish → Published).
-- Errors: what failed + how to fix; no vague apology.
-- Empty states: invitation to act, not a dead end.
-- Ops copy stays plain; Express may have voice, still specific to the product.
+If the user asked for glass / gradient / dark-tech, implement **that** request with `--m-*` — do not escalate into AI mesh.
 
 ## Polish modes (Impeccable-inspired)
 
-**Default:** after compose, run a lane-appropriate light pass (§ Ops polish and/or atmosphere / design plan).
+| Mode | Intent |
+| --- | --- |
+| `quieter` | Strip competing accents **and unearned gradients/glow/glass** |
+| `bolder` | Strengthen one signature **inside** the user’s direction — do not invent a new face |
+| `polish` / `clarify` / `typeset` / `adapt` / `delight` | As named |
 
-When the user asks to improve an existing surface — or when `impeccable` is installed — pick a named mode:
+## Quality floor
 
-| Mode | Intent | Companion command (if installed) |
-| --- | --- | --- |
-| `audit` | Hierarchy, contrast, a11y, spacing, anti-patterns — report then fix | `impeccable audit` / `critique` |
-| `clarify` | Labels, errors, empty copy, button verbs | `impeccable clarify` |
-| `quieter` | Remove competing accents, chips, shadows; keep one focus | `impeccable quieter` |
-| `bolder` | Strengthen the signature / style preset only; do not shout everywhere | `impeccable bolder` |
-| `typeset` | Scale, weight, line-length, truncation | `impeccable typeset` |
-| `adapt` | Responsive breakpoints; touch targets | `impeccable adapt` |
-| `delight` | One tasteful micro-interaction — never clutter | `impeccable delight` / `animate` |
-| `polish` | Final ship pass: Ops polish + style cues + a11y basics | `impeccable polish` |
-
-Always remediate with `M*` + tokens, not raw replacement controls. Full routing: [optional-companions.md](optional-companions.md).
-
-## Industry / mood (UI-UX-Pro-Max-inspired)
-
-For Express briefs that only say “modern / professional / playful”:
-
-1. Infer industry from the product (fintech ≠ kids education).
-2. Pick mood keywords (e.g. “editorial + precise”, “warm workshop”, “clinical calm”).
-3. Map mood → [style preset](style-presets.md) and/or token roles and signature — **then** implement with morya-ui.
-4. If `ui-ux-pro-max` is installed, use it for **keyword / palette search only**; discard any suggestion to switch stacks (shadcn, generic Tailwind kit, etc.).
-
-## Quality floor (all lanes)
-
-- Responsive to a usable mobile layout
-- Visible `:focus-visible`
-- Keyboard reaches primary actions
-- No raw theme colors that break dark mode when the app supports it
-- Icons decorative vs informative handled correctly (`aria-hidden` vs `aria-label`)
-- Craft pass completed for the lane (Ops polish and/or atmosphere / design plan) before delivery
-- If a companion ran: still pass MCP `validate_usage` / `validate_page`
+- Responsive, focus visible, keyboard to primary actions  
+- No raw hex theme colors  
+- Craft pass done; MCP `validate_usage` / `validate_page` when available  
+- No unearned AI atmosphere  

package/template/.cursor/rules/design-system.mdc

@@ -5,13 +5,13 @@ alwaysApply: true
 
 # Morya UI 设计系统
 
-1. **先读** 项目根目录 `DESIGN.md`。组件选型用 MCP `recommend_component`（含 recipe），或 skill `references/decision-recipes.md` / `component-index.md`。
+1. **先读** 项目根目录 `DESIGN.md`。组件选型用 MCP `recommend_component`（含 recipe + `relatedSnippets`），或 skill `references/decision-recipes.md` / `component-index.md`。
 2. **只用** `morya-ui` 的 `M*` 组件；全局样式 `morya-ui/styles.css`。
 3. **颜色/间距/圆角** 使用 `--m-*` CSS 变量，禁止裸 hex/rgb（见 `scripts/check-raw-colors.mjs`）。
-4. **页面结构** 用 MCP `get_golden_page` 对齐区块顺序与 API；**视觉方向**按参考样式 / 用户指定风格 / 提示词推断（`list_style_presets`：quiet、soft、dense、rail、studio、ink）。已安装 `frontend-design` / `impeccable` 时只加深审美与抛光，**不得**换组件库或推翻黄金结构。
+4. **页面组装（composition-first）**：用 MCP `recommend_page` → `suggestedSnippets` / `get_page_snippet` + `recommend_component` 拼装；`page-layouts` 块顺序作 checklist。`get_golden_page` **可选**（核对整页块顺序或用户明确要求对齐样例时）。**视觉方向**：有明确参考或明确描述 → 必须跟用户；提示词有清晰线索 → 推断并说明；不确定 → 先问（`get_style_direction`）。**没有命名风格预设表。** 禁止未询问就套 AI 默认渐变/霓虹/毛玻璃。已安装 `frontend-design` / `impeccable` 时只加深已定方向，**不得**换组件库或推翻块顺序 / 用户指定。
 5. **表单选项** 用 `MSelect` / `MTreeSelect`；**动作菜单** 用 `MDropdown`。
 6. 不确定 API 时查文档站或 MCP `get_component`，**禁止臆造 prop**；写完后必须 `validate_usage`。
 7. 根节点用 `MConfigProvider`；后台布局用 `MLayout` 系列。
 8. **操作反馈默认 `message` API**；仅 `summary + detail` 或异步通知用 `toast`；表单常驻错误用字段 `errorMessage` 或 token 样式的 `role="alert"`（`<MMessage>` 只是 message 宿主）。见 skill `references/feedback.md`。
 
-Token / 风格 / companion：MCP `get_design_rules`、`list_style_presets`；skill `optional-companions.md`（运行时以 `morya-ui/styles.css` 为准）
+Token / 风格 / companion：MCP `get_design_rules`、`get_style_direction`；skill `optional-companions.md`（运行时以 `morya-ui/styles.css` 为准）

package/template/.cursor/rules/page-layout.mdc

@@ -5,25 +5,25 @@ alwaysApply: false
 
 # 页面布局（Agent Requested）
 
-生成完整页面时，先确定类型并 **复制黄金样例结构**：
-
-| 类型 | MCP `get_golden_page` |
-| --- | --- |
-| 列表页 | `list-page` |
-| 表单页 | `form-page`（仅长表单 / 独立配置页） |
-| 列表内弹窗表单 | `form-in-dialog` |
-| 详情页 | `detail-page` |
-| 结果 / 阻断页 | `result-page` |
-| 设置页 | `settings-page` |
-| 分步向导 | `wizard-form` |
-| 仪表盘 | `dashboard-page` |
-| 登录页 | `login-page` |
-| 营销落地 | `landing-page` |
-| 空状态 | `empty-state` |
+生成完整页面时，先确定类型，按 **块顺序 checklist** 用 MCP **`get_page_snippet`** / `recommend_page.suggestedSnippets` 拼装（composition-first）。仅在不确定整页顺序或用户要求对齐样例时再读 `get_golden_page`。
+
+| 类型 | 主要 snippets | 可选黄金样例 |
+| --- | --- | --- |
+| 列表页 | `layout-app-shell` / `page-header-actions` / **`list-filters-stack`**（dense → `list-filters-dense`）/ `list-table` / `form-in-dialog` / `confirm-delete` | `list-page` |
+| 表单页 | `form-header` / `form-body` / `form-actions` | `form-page`（仅长表单 / 独立配置页） |
+| 列表内弹窗表单 | **`form-in-dialog`** | `form-in-dialog` |
+| 详情页 | `detail-toolbar` / `form-in-dialog` | `detail-page` |
+| 结果 / 阻断页 | **`result-block`** | `result-page` |
+| 设置页 | `form-header` / `form-body` / `form-actions` | `settings-page` |
+| 分步向导 | **`wizard-steps`** | `wizard-form` |
+| 仪表盘 | `dashboard-kpi-grid` / `dashboard-chart-card` / `dashboard-recent-table` | `dashboard-page` |
+| 登录页 | **`auth-split-shell`** | `login-page` |
+| 营销落地 | —（见 surfaces） | `landing-page` |
+| 空状态 | **`empty-block`** | `empty-state` |
 
 ## 列表内新建 / 编辑（默认）
 
-后台 CRUD **优先**：列表页 + `MDialog`（或 `MDrawer`）内 `MForm`，不要把「新建用户 / 编辑角色」做成单独路由，除非字段很多或多步骤。
+后台 CRUD **优先**：列表页 + `MDialog`（或 `MDrawer`）内 `MForm`（snippets `form-in-dialog` / `form-in-drawer`），不要把「新建用户 / 编辑角色」做成单独路由，除非字段很多或多步骤。
 
 ## 列表页区块顺序
 
@@ -31,13 +31,13 @@ alwaysApply: false
 2. 侧栏 `MMenu`
 3. `MLayoutHeader` → `MBreadcrumb`
 4. `MLayoutContent` → `MPageContent`（**仅在下方高度规则适用时**再加 `fill`）
-5. `MPageHeader`（页面标题 + `#actions` 主操作；视口内 **唯一** filled primary）
-6. `MPageFilters`（可选 `variant="filled"`、`collapsible` + `#advanced`；查询/重置用 secondary）
-7. 可选 `MPageFilterChips` + 可关闭 `MTag`（有已选条件时，放在筛选与表格之间）
+5. `MPageHeader`（页面标题 + `#actions` 主操作；视口内 **唯一** filled primary）→ `page-header-actions`
+6. `MPageFilters`（默认 **`list-filters-stack`**：折叠高级 + FilterChips；查询/重置 secondary；dense → `list-filters-dense`）
+7. 可选独立 `MPageFilterChips`（若未用 stack）
 8. 可选 `MPageToolbar`（仅批量操作，**不要**页面标题）
 9. `MTable`（直接放置；`#empty` → `MEmpty`）
 10. 分页由 `MTable paginator` 或同级 `MPagination`
-11. 短新建/编辑：同页 `MDialog` + `MForm`
+11. 短新建/编辑：同页 `MDialog` + `MForm`；删除：`MConfirmDialog`（`confirm-delete`）
 
 ### 列表高度 — 先判断，再决定是否 fill
 
@@ -91,7 +91,7 @@ alwaysApply: false
 
 ## MCP
 
-- 整页：`recommend_page`（可传 `style`）→ `get_golden_page` → `get_design_rules` / `list_style_presets`
-- 风格：有参考则跟参考；否则按 `styleDirection` 或请用户从 quiet/soft/dense/rail/studio/ink 选
-- 局部：`get_page_snippet`（如 `filters` / `toolbar` / `form-actions` / `scrollable-panel`）
+- 整页：`recommend_page`（可传 `style`）→ **`suggestedSnippets` / `get_page_snippet`** + `recommend_component` → `get_design_rules` / `get_style_direction`；可选 `get_golden_page` 核对块顺序
+- 风格：有明确参考或明确描述 → 跟用户；有提示词线索 → 推断并说明；不确定 → 先问（无预设表）
+- 局部：`get_page_snippet`（如 `form-in-dialog` / `confirm-delete` / `list-filters` / `wizard-steps`）
 - 可选：`validate_page`（参考建议，不阻断）