@morya-ui/setup 0.3.5 → 0.3.7

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

@@ -1,91 +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 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
+# 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,129 +1,131 @@
-# 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  
+# 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)
+
+Prefer MCP **`get_style_shells`** for pasteable CSS (`account-split`, `account-centered`, `express-hero`, `flow-empty-frame`, `flow-result-hero`, `ops-quiet`). Below are the same defaults for offline use.
+
+### Account — split brand panel (`account-split`)
+
+```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 (`express-hero`)
+
+```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: color-mix(in srgb, var(--m-color-primary) 8%, var(--m-color-surface));
+}
+```
+
+### Flow — empty shell (`flow-empty-frame`)
+
+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. Brand palette changes belong in theme overrides (project `DESIGN.md` § 主题覆盖).
+
+## 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
+```

package/template/.cursor/rules/component-usage.mdc

@@ -1,41 +1,41 @@
----
-description: Morya UI 组件用法与选型（Vue 业务代码）
-globs: src/**/*.vue
-alwaysApply: false
----
-
-# 组件用法
-
-## 引入
-
-```ts
-import { MButton, MInput } from 'morya-ui'
-// 按需：import MButton from 'morya-ui/button'
-//        import 'morya-ui/button/style'
-```
-
-## 必选模式
-
-- 表单：`MForm` + `MFormItem` + 字段组件；提交用 `@submit` + `type="submit"`。
-- 表格：`MTable` 的 `columns` + `rows` + `row-key`；单元格用 `#cell-{key}` 插槽。没有 `data` prop。
-- 浮层：详情/编辑 `MDialog`；侧栏 `MDrawer`；删除确认 `MConfirmDialog`。
-- 反馈（**默认 Message**）：
-  - 单行操作结果 → `message.success/info/warn/error('…')`
-  - 有标题 + 详情 / 异步通知 → `toast.*({ summary, detail })`
-  - 表单区常驻错误 → 字段 `errorMessage`，或 token 样式的 `role="alert"`（`<MMessage>` 只是 message 宿主，不是内嵌 Alert）
-  - 详见 skill `references/feedback.md`
-
-## Props 约定
-
-- 尺寸：`size="small" | "large"`（默认 medium）。
-- 危险：`severity="danger"` 或 `invalid` + `errorMessage`。
-- 清除：优先 `clearable`（Select 亦支持 `showClear` 别名）。
-- 宽度：表单字段 `fluid`；页面级宽度用 layout CSS + `max-width`。
-
-## 禁止
-
-- 同一页面混用其他 UI 库。
-- 用 `MDropdown` 代替 Select 做枚举选择。
-- 手写 table/modal 替代 `MTable` / `MDialog`。
-
-完整清单：MCP `recommend_component`（含 recipe），或 skill `references/decision-recipes.md` / `component-index.md`。
+---
+description: Morya UI 组件用法与选型（Vue 业务代码）
+globs: src/**/*.vue
+alwaysApply: false
+---
+
+# 组件用法
+
+## 引入
+
+```ts
+import { MButton, MInput } from 'morya-ui'
+// 按需：import MButton from 'morya-ui/button'
+//        import 'morya-ui/button/style'
+```
+
+## 必选模式
+
+- 表单：`MForm` + `MFormItem` + 字段组件；提交用 `@submit` + `type="submit"`。
+- 表格：`MTable` 的 `columns` + `rows` + `row-key`；单元格用 `#cell-{key}` 插槽。没有 `data` prop。
+- 浮层：详情/编辑 `MDialog`；侧栏 `MDrawer`；删除确认 `MConfirmDialog`。
+- 反馈（**默认 Message**）：
+  - 单行操作结果 → `message.success/info/warn/error('…')`
+  - 有标题 + 详情 / 异步通知 → `toast.*({ summary, detail })`
+  - 表单区常驻错误 → 字段 `errorMessage`，或 token 样式的 `role="alert"`（`<MMessage>` 只是 message 宿主，不是内嵌 Alert）
+  - 详见 skill `references/feedback.md`
+
+## Props 约定
+
+- 尺寸：`size="small" | "large"`（默认 medium）。
+- 危险：`severity="danger"` 或 `invalid` + `errorMessage`。
+- 清除：优先 `clearable`（Select 亦支持 `showClear` 别名）。
+- 宽度：表单字段 `fluid`；页面级宽度用 layout CSS + `max-width`。
+
+## 禁止
+
+- 同一页面混用其他 UI 库。
+- 用 `MDropdown` 代替 Select 做枚举选择。
+- 手写 table/modal 替代 `MTable` / `MDialog`。
+
+完整清单：MCP `recommend_component`（含 recipe），或 skill `references/decision-recipes.md` / `component-index.md`。