@morya-ui/setup 0.2.7 → 0.2.9

package/template/.agents/skills/fixing-accessibility/SKILL.md

@@ -0,0 +1,138 @@
+---
+name: fixing-accessibility
+description: Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
+---
+
+# fixing-accessibility
+
+> **morya-ui consumer note:** Prefer library defaults (`label`, `aria-label`, Esc-dismiss overlays). Do not replace `M*` widgets with custom ARIA hacks. When guidance conflicts with `DESIGN.md` or `morya-ui-pages`, **those win**.
+
+Fix accessibility issues.
+
+## how to use
+
+- `/fixing-accessibility`
+  Apply these constraints to any UI work in this conversation.
+
+- `/fixing-accessibility <file>`
+  Review the file against all rules below and report:
+  - violations (quote the exact line or snippet)
+  - why it matters (one short sentence)
+  - a concrete fix (code-level suggestion)
+
+Do not rewrite large parts of the UI. Prefer minimal, targeted fixes.
+
+## when to apply
+
+Reference these guidelines when:
+- adding or changing buttons, links, inputs, menus, dialogs, tabs, dropdowns
+- building forms, validation, error states, helper text
+- implementing keyboard shortcuts or custom interactions
+- working on focus states, focus trapping, or modal behavior
+- rendering icon-only controls
+- adding hover-only interactions or hidden content
+
+## rule categories by priority
+
+| priority | category | impact |
+|----------|----------|--------|
+| 1 | accessible names | critical |
+| 2 | keyboard access | critical |
+| 3 | focus and dialogs | critical |
+| 4 | semantics | high |
+| 5 | forms and errors | high |
+| 6 | announcements | medium-high |
+| 7 | contrast and states | medium |
+| 8 | media and motion | low-medium |
+| 9 | tool boundaries | critical |
+
+## quick reference
+
+### 1. accessible names (critical)
+
+- every interactive control must have an accessible name
+- icon-only buttons must have aria-label or aria-labelledby
+- every input, select, and textarea must be labeled
+- links must have meaningful text (no “click here”)
+- decorative icons must be aria-hidden
+
+### 2. keyboard access (critical)
+
+- do not use div or span as buttons without full keyboard support
+- all interactive elements must be reachable by Tab
+- focus must be visible for keyboard users
+- do not use tabindex greater than 0
+- Escape must close dialogs or overlays when applicable
+
+### 3. focus and dialogs (critical)
+
+- modals must trap focus while open
+- restore focus to the trigger on close
+- set initial focus inside dialogs
+- opening a dialog should not scroll the page unexpectedly
+
+### 4. semantics (high)
+
+- prefer native elements (button, a, input) over role-based hacks
+- if a role is used, required aria attributes must be present
+- lists must use ul or ol with li
+- do not skip heading levels
+- tables must use th for headers when applicable
+
+### 5. forms and errors (high)
+
+- errors must be linked to fields using aria-describedby
+- required fields must be announced
+- invalid fields must set aria-invalid
+- helper text must be associated with inputs
+- disabled submit actions must explain why
+
+### 6. announcements (medium-high)
+
+- critical form errors should use aria-live
+- loading states should use aria-busy or status text
+- toasts must not be the only way to convey critical information
+- expandable controls must use aria-expanded and aria-controls
+
+### 7. contrast and states (medium)
+
+- ensure sufficient contrast for text and icons
+- hover-only interactions must have keyboard equivalents
+- disabled states must not rely on color alone
+- do not remove focus outlines without a visible replacement
+
+### 8. media and motion (low-medium)
+
+- images must have correct alt text (meaningful or empty)
+- videos with speech should provide captions when relevant
+- respect prefers-reduced-motion for non-essential motion
+- avoid autoplaying media with sound
+
+### 9. tool boundaries (critical)
+
+- prefer minimal changes, do not refactor unrelated code
+- do not add aria when native semantics already solve the problem
+- do not migrate UI libraries unless requested
+
+## common fixes
+
+```html
+<!-- icon-only button: add aria-label -->
+<!-- before --> <button><svg>...</svg></button>
+<!-- after -->  <button aria-label="Close"><svg aria-hidden="true">...</svg></button>
+
+<!-- div as button: use native element -->
+<!-- before --> <div onclick="save()">Save</div>
+<!-- after -->  <button onclick="save()">Save</button>
+
+<!-- form error: link with aria-describedby -->
+<!-- before --> <input id="email" /> <span>Invalid email</span>
+<!-- after -->  <input id="email" aria-describedby="email-err" aria-invalid="true" /> <span id="email-err">Invalid email</span>
+```
+
+## review guidance
+
+- fix critical issues first (names, keyboard, focus, tool boundaries)
+- prefer native HTML before adding aria
+- quote the exact snippet, state the failure, propose a small fix
+- for complex widgets (menu, dialog, combobox), prefer established accessible primitives over custom behavior

package/template/.agents/skills/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/template/.agents/skills/frontend-design/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: frontend-design
+description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
+license: Complete terms in LICENSE.txt
+---
+
+# Frontend Design
+
+> **morya-ui consumer note:** Use this skill for Express / brand taste only. Always implement interactive controls with `M*` and colors/spacing with `--m-*`. When this skill conflicts with project `DESIGN.md`, `morya-ui-pages`, or MCP APIs, **those win**.
+
+Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify.
+
+## Ground it in the subject
+
+If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout.
+
+## Design principles
+
+For web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option.
+
+Typography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content.
+
+Structure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them.
+
+Leverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated.
+
+Match complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well.
+
+Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
+
+## Process: brainstorm, explore, plan, critique, build, critique again
+
+For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. Just like a human designer who's hired, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
+
+Work in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type: the typefaces for 2+ roles (a characterful display face that's used with restraint, a complementary body face, and a utility face for captions or data if needed). Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Signature: the single unique element this page will be remembered by that embodies the brief in an appropriate way.
+
+Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan exactly and deriving every color and type decision from it.
+
+When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and a element-based selector like .cta). This can happen often with paddings/margins between sections.
+
+Try to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.
+
+## Restraint and self-critique
+
+Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
+
+## More on writing in design
+
+Words appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
+
+Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.
+
+Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
+
+Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
+
+Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.

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

@@ -44,9 +44,7 @@ Full taxonomy: [references/surfaces.md](references/surfaces.md).
 
 1. `morya-ui` installed; `morya-ui/styles.css` imported.
 2. Prefer `@morya-ui/mcp` — never invent prop / event / slot names.
-3. If the AI config pack is merged, prefer project files over bundled copies:
-   - `DESIGN.md`
-   - `docs/golden-pages/*.vue`, `docs/components.md`, `docs/feedback-message-vs-toast.md`
+3. Golden pages, component APIs, and feedback rules come from `@morya-ui/mcp`. Without MCP, use this skill's `references/`. Project `DESIGN.md` overrides generic taste when the AI pack is merged.
 
 ## Workflow
 
@@ -67,7 +65,7 @@ For Express / branded Account moments, also draft a tiny **design plan** (see [v
 | --- | --- | --- |
 | Ops pattern | `recommend_page` → `get_golden_page` | [page-layouts.md](references/page-layouts.md) |
 | Account / Express / empty | `recommend_page` → `get_golden_page` (`login-page` / `landing-page` / `empty-state`) | [surfaces.md](references/surfaces.md) |
-| Visual direction | — | [visual-craft.md](references/visual-craft.md) (Express / polish / anti-defaults) |
+| Visual direction | — | [visual-craft.md](references/visual-craft.md) (Ops polish / atmosphere / anti-defaults) |
 | Components | `search` / `get_component` / `recommend_component` | [component-index.md](references/component-index.md) |
 | Tokens / rules | `get_design_rules` | [design-system.md](references/design-system.md) |
 | Snippet | `get_page_snippet` | golden / surface excerpt |
@@ -78,7 +76,7 @@ For Express / branded Account moments, also draft a tiny **design plan** (see [v
 
 **Ops:** mirror golden-page block order; prefer `MPage*` over custom chrome.
 
-**Account / Flow / System:** centered or split shells with `MCard` / `MForm` / `MMessage` / `MEmpty` / `MResult` (see surfaces); keep controls as `M*`.
+**Account / Flow / System:** centered or split shells with `MCard` / `MForm` / `MEmpty` / `MResult` (see surfaces); keep controls as `M*`. Persistent form errors use field `errorMessage` or a token-styled `role="alert"` — `<MMessage>` is the `message` host, not an inline alert.
 
 **Express:** hero + sections with intentional hierarchy; interactive bits still `MButton` / `MTag` / etc.; atmosphere via layout, motion, and tokens — not a second component library.
 
@@ -88,23 +86,25 @@ For Express / branded Account moments, also draft a tiny **design plan** (see [v
 
 - Import from `morya-ui` (or documented subpath + style).
 - Forms: `MForm` + fields; `@submit` + `type="submit"`.
-- Tables: `columns` + `data` + `row-key`; `#cell-{key}`.
+- Tables: `columns` + `rows` + `row-key`; `#cell-{key}`. There is no `data` prop.
 - Enums → `MSelect` / `MTreeSelect`; action menus → `MDropdown`.
 - Destructive → `MConfirmDialog` / `MConfirmPopup`.
 - Feedback → default **`message`**; `toast` only for summary+detail / async. See [feedback.md](references/feedback.md).
 
-### 5. Craft pass (lane-aware)
+### 5. Craft pass (always — lane-aware)
 
-- **Ops:** restraint — clarity over spectacle; cut decoration.
-- **Express / branded auth:** one signature moment; avoid AI-default looks listed in [visual-craft.md](references/visual-craft.md).
-- **All lanes:** responsive, focus visible, respect `prefers-reduced-motion` when adding motion.
-- Copy: user language, active voice, specific — not filler marketing on Ops screens.
+Run **before** delivery. Do not stop at a structurally correct shell.
 
-Optional polish modes (Impeccable-inspired): `quieter` | `bolder` | `clarify` | `audit` — apply as a second pass when the user asks. See [visual-craft.md](references/visual-craft.md) § Polish modes.
+- **Ops:** apply [visual-craft.md](references/visual-craft.md) § Ops polish (one primary, menu icons, `MStatus` in tables, designed empty, no decorative cards).
+- **Account / Flow:** one calm brand or empty-state cue from § Atmosphere recipes; form errors via `errorMessage` / token `role="alert"`.
+- **Express:** short design plan + one signature; avoid AI-default looks; optional 1–2 token-only motions with `prefers-reduced-motion`.
+- **All lanes:** responsive, focus visible, domain-real copy (active voice).
+
+Named polish modes (`quieter` | `bolder` | `clarify` | `audit` | …): use as an **extra** pass when the user asks to improve an existing screen. See [visual-craft.md](references/visual-craft.md) § Polish modes.
 
 ### 6. Review
 
-Use [review-checklist.md](references/review-checklist.md) (Ops + Express sections). Run MCP `validate_page` when available (advisory).
+Use [review-checklist.md](references/review-checklist.md) (contract + craft sections). Run MCP `validate_page` when available (advisory).
 
 ## Hard boundaries
 
@@ -132,8 +132,9 @@ Details: [optional-companions.md](references/optional-companions.md). Distilled
 
 - Vue 3 `<script setup lang="ts">`.
 - PascalCase `M*` in templates.
-- Domain-real copy and data shapes.
-- Scoped CSS minimal; tokens only (control widths may be inline).
+- Domain-real copy and data shapes (not placeholder “示例 / Name / No data” when the brief names a product).
+- Scoped CSS minimal; tokens only (`color-mix` / gradients from `--m-*` OK; control widths may be inline).
+- Craft pass completed for the lane (see step 5).
 - For multi-file asks: sensible `views/` / `components/` split; otherwise one SFC is fine.
 
 ## Bundled references
@@ -142,7 +143,7 @@ Details: [optional-companions.md](references/optional-companions.md). Distilled
 | --- | --- |
 | [surfaces.md](references/surfaces.md) | Choosing / composing non-Ops (and hybrid) surfaces |
 | [page-layouts.md](references/page-layouts.md) | Ops golden layouts |
-| [visual-craft.md](references/visual-craft.md) | Design plan, anti-defaults, polish modes, Express craft |
+| [visual-craft.md](references/visual-craft.md) | Ops polish, atmosphere recipes, anti-defaults, polish modes |
 | [design-system.md](references/design-system.md) | Principles, tokens, bans |
 | [component-index.md](references/component-index.md) | Scenario → component |
 | [feedback.md](references/feedback.md) | message / toast / MMessage |

package/template/.agents/skills/morya-ui-pages/evals/evals.json

@@ -3,38 +3,38 @@
   "evals": [
     {
       "id": 1,
-      "prompt": "我们内部教务系统用 Vue3 + morya-ui。请做一个「课程列表」后台页：按课程名搜索、按开课状态（全部/开课中/已结课）筛选；表格列：名称、状态 Tag、学分、更新时间；行内「编辑」进抽屉表单，「删除」要二次确认；右上角「新建课程」。保存/删除成功只要一句话提示。输出单个 Vue SFC，结构对齐列表黄金样例。",
-      "expected_output": "Ops list: MLayout/MPageFilters/MPageToolbar/MTable, MSelect status, MDrawer or route edit, MConfirmDialog delete, message not toast, MTag for status, no second UI kit.",
+      "prompt": "我们内部教务系统用 Vue3 + morya-ui。请做一个「课程列表」后台页：按课程名搜索、按开课状态（全部/开课中/已结课）筛选；表格列：名称、状态、学分、更新时间；行内「编辑」进抽屉表单，「删除」要二次确认；右上角「新建课程」。保存/删除成功只要一句话提示。输出单个 Vue SFC，结构对齐列表黄金样例，并做 Ops 精致化（侧栏图标、状态用 MStatus、空态用 MEmpty、行操作不要一排实心按钮）。",
+      "expected_output": "Ops list: MLayout/MPageFilters/MPageToolbar/MTable rows, MSelect status, MDrawer edit, MConfirmDialog delete, message not toast, MStatus for status, MEmpty in #empty, menu icons, text/small row actions, craft pass applied, no second UI kit.",
       "files": []
     },
     {
       "id": 2,
       "prompt": "同一个 morya-ui 项目里，生成「新建员工」独立表单页：姓名、工作邮箱、部门（下拉）、入职日期；窄栏；页头有标题和一句说明；底栏保存（primary）/取消（secondary）。不要做成营销落地页，不要用 Toast 提示「已保存」。输出单个 Vue SFC。",
-      "expected_output": "Ops form golden: narrow MPageContent, MPageHeader, MPageSection form/actions, MForm + MSelect/MDatePicker, message for success if shown, no landing hero.",
+      "expected_output": "Ops form golden: narrow MPageContent, MPageHeader, MPageSection form/actions, MForm + MSelect/MDatePicker, message for success if shown, one primary, no landing hero.",
       "files": []
     },
     {
       "id": 3,
-      "prompt": "运营后台首页仪表盘：四个 KPI（今日订单、待处理、转化率、退款率）、中间一块图表占位、右侧或下方「最近告警」表格（级别、内容、时间）。Vue3 + morya-ui，可先用静态假数据。",
-      "expected_output": "Dashboard: MPageStat grid, MPagePlaceholder/chart card, recent MTable, MLayout shell, --m-* only.",
+      "prompt": "运营后台首页仪表盘：四个 KPI（今日订单、待处理、转化率、退款率）、中间一块图表占位、右侧或下方「最近告警」表格（级别、内容、时间）。Vue3 + morya-ui，可先用静态假数据；告警级别可用 Tag，状态用 MStatus。",
+      "expected_output": "Dashboard: MPageStat grid with domain labels, MPagePlaceholder/chart card, recent MTable with MStatus, MLayout shell, --m-* only, spacious density.",
       "files": []
     },
     {
       "id": 4,
-      "prompt": "给「青禾书房」这个独立书店品牌做登录页：左品牌、右表单（邮箱+密码+登录）。要有一点品牌感，但控件必须用 morya-ui；登录失败用表单区常驻错误，不要一闪而过的 Toast。输出单个 Vue SFC。",
-      "expected_output": "Account+craft: split shell, MForm/MInputPassword/MButton, MMessage or field error for failure, brand panel without second UI kit, tokens for colors.",
+      "prompt": "给「青禾书房」这个独立书店品牌做登录页：左品牌、右表单（邮箱+密码+登录）。要有一点品牌感（token 氛围即可），但控件必须用 morya-ui；登录失败用表单区常驻错误（字段 errorMessage 或 token role=alert），不要一闪而过的 Toast，也不要把 MMessage 当成内嵌 Alert。输出单个 Vue SFC。",
+      "expected_output": "Account+craft: split shell, MForm/MInputPassword/MButton, token role=alert or field error for failure, brand panel with --m-* color-mix, no MMessage severity alert, no second UI kit.",
       "files": []
     },
     {
       "id": 5,
-      "prompt": "课程列表在零数据时太空了。请设计一个空状态区块（可嵌在列表页内容区）：说明还没有课程、引导「创建第一门课程」，视觉克制但有一个记忆点。只要空状态相关模板片段或带空状态的列表 SFC 均可，须 morya-ui。",
-      "expected_output": "Flow empty: clear next action CTA with MButton, short copy, one signature visual, no emoji clutter, fits list content slot.",
+      "prompt": "课程列表在零数据时太空了。请设计一个空状态区块（可嵌在列表页内容区）：说明还没有课程、引导「创建第一门课程」，视觉克制但有一个记忆点（dashed shell + 轻径向光）。只要空状态相关模板片段或带空状态的列表 SFC 均可，须 morya-ui。",
+      "expected_output": "Flow empty: MEmpty + next-action MButton, short copy, token atmosphere shell, no emoji clutter, fits list content slot.",
       "files": []
     },
     {
       "id": 6,
-      "prompt": "为「流水线 CI」产品写一个营销落地首页（不是后台）：首屏只有品牌名、一句主标题、一句副文、一组 CTA；下面再分「为何选择」「能力」「客户」三节。技术实现用 Vue3 + morya-ui 组件做按钮/标签/折叠 FAQ；颜色走 --m-*，避免紫渐变和奶油衬线陶土那套 AI 默认脸。输出单个 Vue SFC。",
-      "expected_output": "Express landing: single-job hero, MButton CTAs, sections with one job each, MAccordion FAQ optional, no purple/cream-terracotta defaults, no admin MPageFilters shell.",
+      "prompt": "为「流水线 CI」产品写一个营销落地首页（不是后台）：首屏只有品牌名、一句主标题、一句副文、一组 CTA；下面再分「为何选择」「能力」「客户」三节。技术实现用 Vue3 + morya-ui 组件做按钮/标签/折叠 FAQ；颜色走 --m-*，避免紫渐变和奶油衬线陶土那套 AI 默认脸。可有 1–2 个微动效并尊重 prefers-reduced-motion。输出单个 Vue SFC。",
+      "expected_output": "Express landing: single-job hero, MButton CTAs, sections with one job each, MAccordion FAQ optional, no purple/cream-terracotta defaults, no admin MPageFilters shell, reduced-motion aware.",
       "files": []
     },
     {
@@ -46,7 +46,13 @@
     {
       "id": 8,
       "prompt": "用户点了删除项目但权限不足：做一张「无权限」系统页（或全页占位），说明原因，并提供返回上一页、联系管理员。用 morya-ui，文案直接别玩梗。",
-      "expected_output": "System surface: plain explanation, escape actions with MButton, no jokey 404 essay, on-token.",
+      "expected_output": "System surface: MResult 403 or equivalent, plain explanation, escape actions with MButton, no jokey 404 essay, on-token.",
+      "files": []
+    },
+    {
+      "id": 9,
+      "prompt": "把上面的课程列表再 polish 一轮：去掉多余实心按钮、保证只有一个主按钮、表格状态改成 MStatus、补上 MEmpty。不要改成营销页。",
+      "expected_output": "Ops quieter polish: one primary, MStatus, MEmpty, text row actions, still list golden structure.",
       "files": []
     }
   ]

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

@@ -7,21 +7,27 @@ Full API: docs site `/components` or MCP (`get_component`, `search`, `validate_u
 | Component | Use |
 | --- | --- |
 | `MConfigProvider` | Root locale / theme / density / defaults |
-| `MLayout` family | Admin chrome |
+| `MLayout` family | Admin chrome (`MLayoutSider` is the layout sider) |
+| `MSidebar` | Standalone nav rail (not a `MDrawer`, not a substitute for `MLayoutSider` inside `MLayout`) |
 | `MBreadcrumb` | Path |
 | `MPageContent` / `MPageFilters` / `MPageToolbar` / `MPageHeader` / `MPageSection` / `MPageStat` / `MPagePlaceholder` | Page composition |
+| `MDock` | App dock / launcher, not page actions |
+
+## Actions
+
+`MButton` / `MButtonGroup` (primary `severity="primary"`, danger `severity="danger"`), `MSplitButton` (main action + menu), `MSpeedDial` (floating action cluster)
 
 ## Forms · inputs
 
-`MForm`, `MFormItem`, `MInput`, `MInputPassword`, `MInputNumber`, `MTextarea`, `MSelect`, `MTreeSelect`, `MCascadeSelect`, `MDatePicker`, `MAutoComplete`, `MCheckbox` / `MCheckboxGroup`, `MRadio` / `MRadioGroup`, `MSwitch`, `MSlider`, `MRating`, `MInputTags`, `MFileUpload`, `MFloatLabel`, `MIconField`
+`MForm`, `MFormItem`, `MInput`, `MInputPassword`, `MInputNumber`, `MTextarea`, `MInputOtp`, `MInputColor`, `MInputGroup`, `MInputTags`, `MSelect`, `MTreeSelect`, `MCascadeSelect`, `MListbox`, `MSelectButton`, `MDatePicker`, `MAutoComplete`, `MCheckbox` / `MCheckboxGroup`, `MRadio` / `MRadioGroup`, `MSwitch`, `MToggleButton`, `MSlider`, `MRating`, `MKnob`, `MFileUpload`, `MFloatLabel`, `MIconField`, `MLabel`
 
 ## Layout helpers
 
-`MGrid` / `MGridItem`, `MFlex`, `MSpace`, `MFluid`, `MDivider`, `MFieldset`
+`MGrid` / `MGridItem`, `MFlex`, `MSpace`, `MFluid`, `MDivider`, `MFieldset`, `MSplitter`, `MToolbar`
 
 ## Data
 
-`MTable`, `MTreeTable`, `MDataView`, `MTree`, `MPagination`, `MStatus` / `MTag` / `MChip` / `MBadge`, `MAvatar` / `MAvatarGroup`, `MTimeline`, `MMeterGroup`, `MVirtualScroller`
+`MTable` (`columns` + **`rows`**, not `data`), `MTreeTable`, `MDataView`, `MTree`, `MPagination`, `MOrderList`, `MPickList`, `MStatus` / `MTag` / `MChip` / `MBadge`, `MAvatar` / `MAvatarGroup`, `MTimeline`, `MMeterGroup`, `MVirtualScroller`
 
 ## Feedback
 
@@ -29,18 +35,23 @@ Full API: docs site `/components` or MCP (`get_component`, `search`, `validate_u
 | --- | --- |
 | `message` | **Default** one-line CRUD result |
 | `toast` | `summary` + `detail`, or async / background feel |
-| `<MMessage>` | Persistent in-page error / warning |
+| `<MMessage>` | Optional host for the `message` service (`appendTo` / placement). **Not** an inline alert |
+| field `errorMessage` or token `role="alert"` | Persistent form / auth error |
 | `MEmpty` | No-data / first-use / filtered empty (not an error) |
 | `MResult` | Terminal outcome: success, failure, 403 / 404 / 500 |
-| `MProgressBar` / `MProgressSpinner` / `MSkeleton` / `MBlockUI` | Loading / blocking |
+| `MLoading` / `v-loading` / `loading.service` | **Default** region or fullscreen loading mask |
+| `MSkeleton` | Layout is already known; placeholder while content arrives |
+| `MProgressBar` | Determinate progress |
+| `MProgressSpinner` | Inline spinner only, not a region mask |
+| `MBlockUI` | Block interaction without a loading message |
 
 ## Overlays & menus
 
-`MDialog`, `MDrawer`, `MConfirmDialog` / `MConfirmPopup`, `MPopover`, `MTooltip`, `MDropdown` (**actions only**), `MMenu` / `MMenubar` / `MTieredMenu` / `MMegaMenu`, `MTabs`, `MStepper`, `MCommandMenu`
+`MDialog`, `MDrawer`, `MConfirmDialog` / `MConfirmPopup`, `MPopover`, `MTooltip`, `MDropdown` (**actions only**), `MContextMenu` (right-click), `MCommandMenu` (searchable command palette), `MMenu` / `MMenubar` / `MTieredMenu` / `MMegaMenu`, `MTabs`, `MStepper`
 
 ## Surfaces / media
 
-`MCard`, `MPanel`, `MAccordion`, `MCarousel`, `MGallery`, `MIcon`, `MScrollbar`
+`MCard`, `MPanel`, `MAccordion`, `MCarousel`, `MGallery`, `MIcon`, `MScrollbar`, `MInplace`, `MScrollTop`, `MTerminal`
 
 ## Scenario → pick
 
@@ -59,15 +70,26 @@ Full API: docs site `/components` or MCP (`get_component`, `search`, `validate_u
 | Marketing landing | `landing-page` golden + `MButton` / `MTag` / `MAccordion` |
 | Empty list / zero state | `MEmpty` (+ `empty-state` golden or `MTable` `#empty`) |
 | Submit success / HTTP error page | `MResult` |
+| Region or page is waiting | `MLoading`, `v-loading`, or `loading.service`; known layout → `MSkeleton` |
 | Local capped scroll | Explicit `MScrollbar` |
-| Admin sider nav | `MMenu` |
+| Admin sider nav | `MMenu` inside `MLayoutSider` (or `MSidebar` when the shell is not `MLayout`) |
+| Few options, all visible | `MRadio` or `MSelectButton` |
+| Always-visible option list | `MListbox` |
+| Multi-level cascade (not a tree dropdown) | `MCascadeSelect` |
+| Right-click actions | `MContextMenu` |
+| Global command search | `MCommandMenu` |
+| Count or dot on a control | `MBadge` |
+| Removable entity chip | `MChip` |
 
 ## Common mistakes
 
 | Wrong | Right |
 | --- | --- |
 | `MDropdown` as form enum | `MSelect` |
+| `MTable` `:data` | `:rows` (`row-key` defaults to `id`) |
+| `<MMessage severity>` as an inline alert | Field `errorMessage`, or a token-styled `role="alert"` |
 | Hand `<table>` | `MTable` |
 | Hand modal div | `MDialog` |
+| Hand spinner or `MProgressSpinner` as a region / page mask | `MLoading` / `v-loading` |
 | Extra `MCard` around every `MPage*` block | Use page components' own surface/gap |
 | Assume undocumented props | MCP / docs lookup |