@morya-ui/setup 0.3.3 → 0.3.5

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

@@ -1,89 +1,91 @@
-# Surface taxonomy
-
-Pick a lane, then a surface. Prefer project golden pages for **Ops**; use the recipes below for everything else. Always implement interactive controls with `morya-ui`.
-
-## Ops (admin / console)
-
-| Surface | Job | Compose from |
-| --- | --- | --- |
-| List | Scan, filter, act on many rows | Golden list + [page-layouts.md](page-layouts.md); **create/edit with ≤~8 fields → `MDialog` on the list** |
-| Form | Create / edit one entity as a **dedicated page** | Golden form — only when multi-section, many fields, or user asked for an independent form route |
-| Dashboard | Orient + jump to work | Golden dashboard |
-| Detail | Read-heavy record + secondary actions | `MPageHeader` + sections via `MCard`/`MPageSection`; edit via `MDialog` / `MDrawer` (prefer over a second form route) |
-| Settings | Grouped preferences | Narrow `MPageContent` + stacked `MPageSection` / `MTabs` + `MForm` |
-| Hybrid list | List + drawer/dialog | **Default Ops CRUD pattern**: list golden + `MDialog`/`MDrawer` form |
-
-## Account
-
-| Surface | Job | Recipe |
-| --- | --- | --- |
-| Login / register | Authenticate with trust | Golden: MCP `get_golden_page` `login-page` — split brand + `MForm` (`MInput`, `MInputPassword`); form-level errors via token `role="alert"` (not Toast). Brand wash: [visual-craft.md](visual-craft.md) § Atmosphere |
-| Invite / accept | Join org | Same shell; show org name clearly |
-| Forgot / reset | Recover access | Short form + success state with next step |
-| Profile / account | Edit self | Settings-like sections; avatar via `MAvatar` |
-
-Keep credential forms quiet: one primary CTA, clear labels, no decorative noise beside the brand panel.
-
-## Flow
-
-| Surface | Job | Recipe |
-| --- | --- | --- |
-| Empty state | Invite first action | Golden: MCP `get_golden_page` `empty-state` — `MEmpty` + primary/secondary `MButton` in `#extra`; dashed shell + radial wash from visual-craft |
-| Onboarding | Teach the product path | `MStepper` or paced cards; one decision per step; finish → Ops home |
-| Wizard | Multi-step create | `MStepper` + `MForm` per step + sticky actions (`上一步` / `下一步` / `提交`) |
-| Success / result | Confirm completion | `MResult status="success"` / `error` + `#footer` next actions (`查看详情` / `返回列表`); same shell idea as `result-page` |
-
-Copy must tell the user **what to do next**, not celebrate the system.
-
-## System
-
-| Surface | Job | Recipe |
-| --- | --- | --- |
-| Permission denied | Explain + escape | Golden: MCP `get_golden_page` `result-page` — `MResult status="403"` + `#footer` (not `#extra`) |
-| 404 / not found | Reorient | `MResult status="404"` + `返回首页` / `返回上一页` (mirror `result-page` shell) |
-| Maintenance / error | Honest status | `MResult status="500"`; what happened + retry + support. Persistent form errors: field `errorMessage` or a token `role="alert"`, not `<MMessage>` as an alert |
-
-Avoid witty 404 essays that hide the exit paths.
-
-## Express (marketing / public)
-
-Use when the brief is landing, pricing, launch, or docs marketing — **not** for Ops CRUD shells.
-
-| Surface | Job | Recipe |
-| --- | --- | --- |
-| Landing | Convert / explain product | Golden: MCP `get_golden_page` `landing-page` — one-job hero; CTAs → `MButton`; chips → `MTag`; FAQ → `MAccordion` |
-| Pricing | Choose a plan | Clear plan cards (`MCard`) + primary CTA; highlight recommended plan without clutter |
-| Feature showcase | Prove capability | Alternating media/copy; live `M*` demo only if lightweight |
-| Docs marketing chrome | Frame documentation | Header + nav using `M*` where suitable; content area stays readable |
-
-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.
-
-## Overlay
-
-When the dialog/drawer **is** the task:
-
-| Surface | Recipe |
-| --- | --- |
-| Edit / create dialog | `MDialog` + compact `MForm` + footer actions |
-| Detail drawer | `MDrawer` + header + sections + optional edit |
-| Confirm | `MConfirmDialog` / `MConfirmPopup` — do not reinvent |
-| Command menu | `MCommandMenu` for keyboard-first jump / actions |
-
-Host page stays stable; focus management comes from the overlay component.
-
-## Lane mixing
-
-| Ask | Treat as |
-| --- | --- |
-| “后台列表 + 好看一点” | Ops first, light craft (spacing/type), no landing hero |
-| “登录页有品牌感” | Account + Express craft on brand panel only |
-| “产品官网” | Express; Ops patterns do not apply |
-| “空状态设计精致一点” | Flow empty + visual-craft signature (one risk) |
-
-## MCP hints
-
-- Ops whole page: `recommend_page` → `get_golden_page` → `get_design_rules`
-- Section: `get_page_snippet`
-- Any lane: `search` / `get_component` before unfamiliar APIs
+# Surface taxonomy
+
+Pick a lane, then a surface. Prefer project golden pages for **Ops**; use the recipes below for everything else. Always implement interactive controls with `morya-ui`.
+
+## Ops (admin / console)
+
+| Surface | Job | Compose from |
+| --- | --- | --- |
+| List | Scan, filter, act on many rows | Golden list + [page-layouts.md](page-layouts.md); **create/edit with ≤~8 fields → `MDialog` on the list** |
+| Form | Create / edit one entity as a **dedicated page** | Golden form — only when multi-section, many fields, or user asked for an independent form route |
+| Dashboard | Orient + jump to work | Golden dashboard |
+| Detail | Read-heavy record + secondary actions | `MPageHeader` + sections via `MCard`/`MPageSection`; edit via `MDialog` / `MDrawer` (prefer over a second form route) |
+| Settings | Grouped preferences | Narrow `MPageContent` + stacked `MPageSection` / `MTabs` + `MForm` |
+| Hybrid list | List + drawer/dialog | **Default Ops CRUD pattern**: list golden + `MDialog`/`MDrawer` form |
+
+## Account
+
+| Surface | Job | Recipe |
+| --- | --- | --- |
+| Login / register | Authenticate with trust | Golden: MCP `get_golden_page` `login-page` — split brand + `MForm` (`MInput`, `MInputPassword`); form-level errors via token `role="alert"` (not Toast). Brand wash: [visual-craft.md](visual-craft.md) § Atmosphere |
+| Invite / accept | Join org | Same shell; show org name clearly |
+| Forgot / reset | Recover access | Short form + success state with next step |
+| Profile / account | Edit self | Settings-like sections; avatar via `MAvatar` |
+
+Keep credential forms quiet: one primary CTA, clear labels, no decorative noise beside the brand panel.
+
+## Flow
+
+| Surface | Job | Recipe |
+| --- | --- | --- |
+| Empty state | Invite first action | Golden: MCP `get_golden_page` `empty-state` — `MEmpty` + primary/secondary `MButton` in `#extra`; dashed shell + radial wash from visual-craft |
+| Onboarding | Teach the product path | `MStepper` or paced cards; one decision per step; finish → Ops home |
+| Wizard | Multi-step create | `MStepper` + `MForm` per step + sticky actions (`上一步` / `下一步` / `提交`) |
+| Success / result | Confirm completion | `MResult status="success"` / `error` + `#footer` next actions (`查看详情` / `返回列表`); same shell idea as `result-page` |
+
+Copy must tell the user **what to do next**, not celebrate the system.
+
+## System
+
+| Surface | Job | Recipe |
+| --- | --- | --- |
+| Permission denied | Explain + escape | Golden: MCP `get_golden_page` `result-page` — `MResult status="403"` + `#footer` (not `#extra`) |
+| 404 / not found | Reorient | `MResult status="404"` + `返回首页` / `返回上一页` (mirror `result-page` shell) |
+| Maintenance / error | Honest status | `MResult status="500"`; what happened + retry + support. Persistent form errors: field `errorMessage` or a token `role="alert"`, not `<MMessage>` as an alert |
+
+Avoid witty 404 essays that hide the exit paths.
+
+## Express (marketing / public)
+
+Use when the brief is landing, pricing, launch, or docs marketing — **not** for Ops CRUD shells.
+
+| Surface | Job | Recipe |
+| --- | --- | --- |
+| Landing | Convert / explain product | Golden: MCP `get_golden_page` `landing-page` — one-job hero; CTAs → `MButton`; chips → `MTag`; FAQ → `MAccordion` |
+| Pricing | Choose a plan | Clear plan cards (`MCard`) + primary CTA; highlight recommended plan without clutter |
+| Feature showcase | Prove capability | Alternating media/copy; live `M*` demo only if lightweight |
+| Docs marketing chrome | Frame documentation | Header + nav using `M*` where suitable; content area stays readable |
+
+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 aurora / cream-terracotta / broadsheet / unsolicited glass-neon when the user did not ask.
+
+## Overlay
+
+When the dialog/drawer **is** the task:
+
+| Surface | Recipe |
+| --- | --- |
+| Edit / create dialog | `MDialog` + compact `MForm` + footer actions |
+| Detail drawer | `MDrawer` + header + sections + optional edit |
+| Confirm | `MConfirmDialog` / `MConfirmPopup` — do not reinvent |
+| Command menu | `MCommandMenu` for keyboard-first jump / actions |
+
+Host page stays stable; focus management comes from the overlay component.
+
+## Lane mixing
+
+| Ask | Treat as |
+| --- | --- |
+| “后台列表 + 好看一点” | 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 |
+| “空状态设计精致一点” | Flow empty + visual-craft signature (one risk) |
+
+## MCP hints
+
+- Ops whole page: `recommend_page({ style? })` → `get_golden_page` → apply `styleDirection` / reference
+- 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,196 +1,129 @@
-# 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.
-
-## 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 |
-| 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.
-
-## Design plan (Express & branded moments)
-
-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.
-2. **Type** — display vs body vs utility. For Ops, stick to theme fonts. For Express, a distinctive pairing is OK if fonts are loadable and fallbacks exist.
-3. **Layout concept** — one sentence + rough hierarchy (ASCII wireframe optional).
-4. **Signature** — the single memorable element (motion, crop, editorial type, product artifact). Everything else quieter.
-
-Critique the plan: if it looks like the plan you would write for *any* SaaS, revise until it fits **this** subject.
-
-## Ops polish (default — every Ops page)
-
-Apply after the golden block order is correct. These are **required**, not optional taste:
-
-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 beauty = **alignment + semantics + restraint**, not gradients.
-
-## Anti-default looks (AI clusters)
-
-Avoid spending free axes on these unless the brief asks:
-
-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
-
-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).
-
-## Hierarchy & composition
-
-- **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`.
-
-### Account — split brand panel
-
-```css
-.login-brand {
-  display: flex;
-  flex-direction: column;
-  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%
-    );
-  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%
-    );
-}
-```
-
-Optional micro-motion (one signature only):
-
-```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
-
-```css
-.empty-state-shell {
-  border: 1px dashed color-mix(in srgb, var(--m-color-border) 80%, var(--m-color-primary));
-  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);
-}
-```
-
-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.
-
-## Polish modes (Impeccable-inspired)
-
-**Default:** after compose, run a lane-appropriate light pass (§ Ops polish and/or atmosphere).
-
-When the user asks to improve an existing surface, pick a named mode:
-
-| Mode | Intent |
-| --- | --- |
-| `audit` | Hierarchy, contrast, a11y, spacing, anti-patterns — report then fix |
-| `clarify` | Labels, errors, empty copy, button verbs |
-| `quieter` | Remove competing accents, chips, shadows; keep one focus |
-| `bolder` | Strengthen the signature only; do not shout everywhere |
-| `typeset` | Scale, weight, line-length, truncation |
-| `adapt` | Responsive breakpoints; touch targets |
-| `delight` | One tasteful micro-interaction — never clutter |
-
-Always remediate with `M*` + tokens, not raw replacement controls.
-
-## 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 → token roles and signature — **then** implement with morya-ui.
-4. 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) before delivery
+# Visual craft (distilled)
+
+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 § Shell recipes when relevant |
+| Express | High — design plan + one signature risk | **Always** run design plan + anti-defaults |
+
+**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)
+
+Run companions **after** structure + contract + **resolved style direction**, then remediate with `M*` + `--m-*`.
+
+### Subject first (Frontend Design)
+
+- 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 | 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 |
+
+### Design plan (Express & branded Account)
+
+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.
+
+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.**
+
+## Ops polish (baseline)
+
+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.
+
+Ops beauty = alignment + semantics + restraint, **not** gradients.
+
+## Anti-default looks
+
+Unless the user **asks** or a reference **shows** them, do not use:
+
+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  
+
+**Token gradients are not a free pass** — only when the user/reference asks.
+
+## Shell recipes (token-only — defaults are flat)
+
+### Account — split brand panel
+
+```css
+.login-brand {
+  display: flex;
+  flex-direction: column;
+  justify-content: flex-end;
+  gap: var(--m-space-4);
+  padding: clamp(2rem, 6vw, 4.5rem);
+  background: color-mix(in srgb, var(--m-color-primary) 12%, var(--m-color-surface));
+  border-right: 1px solid var(--m-color-border);
+}
+```
+
+### Express — hero plane
+
+```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: var(--m-color-surface);
+}
+```
+
+### Flow — empty shell
+
+Prefer stock `MEmpty`. Optional light frame:
+
+```css
+.empty-state-shell {
+  border: 1px dashed var(--m-color-border);
+  border-radius: var(--m-radius-md);
+  background: var(--m-color-surface);
+  padding: var(--m-space-6);
+}
+```
+
+If the user asked for glass / gradient / dark-tech, implement **that** request with `--m-*` — do not escalate into AI mesh.
+
+## Polish modes (Impeccable-inspired)
+
+| 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 |
+
+## Quality floor
+
+- 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/coding-style.mdc

@@ -1,41 +1,41 @@
----
-description: Vue 3 + TypeScript 业务代码风格（Morya UI 项目）
-globs: "**/*.{ts,vue}"
-alwaysApply: false
----
-
-# 编码风格
-
-## Vue
-
-- 使用 `<script setup lang="ts">`。
-- 组件名 PascalCase；模板中用 `M*` 前缀组件。
-- `v-model` 与组件库 emit 对齐（如 `v-model:page`）。
-- 页面级样式 `scoped`；仅使用 `--m-*` 与设计令牌。
-
-## TypeScript
-
-- Props/emit 显式类型；避免 `any`。
-- 异步提交：`loading` ref + `try/finally`。
-
-## 文件组织
-
-```text
-src/
-  views/          # 路由页面
-  components/     # 业务组件
-  composables/    # 复用逻辑
-  api/            # 请求层
-```
-
-## 命名
-
-- 页面：`UserListView.vue` / `UserFormView.vue`
-- 路由 path kebab-case：`/users/create`
-
-## 检查
-
-```bash
-pnpm check:colors   # 裸色值扫描
-pnpm typecheck
-```
+---
+description: Vue 3 + TypeScript 业务代码风格（Morya UI 项目）
+globs: "**/*.{ts,vue}"
+alwaysApply: false
+---
+
+# 编码风格
+
+## Vue
+
+- 使用 `<script setup lang="ts">`。
+- 组件名 PascalCase；模板中用 `M*` 前缀组件。
+- `v-model` 与组件库 emit 对齐（如 `v-model:page`）。
+- 页面级样式 `scoped`；仅使用 `--m-*` 与设计令牌。
+
+## TypeScript
+
+- Props/emit 显式类型；避免 `any`。
+- 异步提交：`loading` ref + `try/finally`。
+
+## 文件组织
+
+```text
+src/
+  views/          # 路由页面
+  components/     # 业务组件
+  composables/    # 复用逻辑
+  api/            # 请求层
+```
+
+## 命名
+
+- 页面：`UserListView.vue` / `UserFormView.vue`
+- 路由 path kebab-case：`/users/create`
+
+## 检查
+
+```bash
+pnpm check:colors   # 裸色值扫描
+pnpm typecheck
+```