@morya-ui/setup 0.3.1 → 0.3.3

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

@@ -43,9 +43,9 @@ import 'morya-ui/styles.css'
 | Admin chrome | `MLayout fillViewport` + sider / header / content |
 | Sider nav | `MMenu` |
 | Page stack | `MPageContent` inside `MLayoutContent` |
-| Filters / toolbar | `MPageFilters` + `MPageToolbar` |
+| List chrome | `MPageHeader` + `MPageFilters` (+ optional batch `MPageToolbar`) |
 | Form surfaces | `MPageHeader` + `MPageSection variant="form|actions"` |
-| Dashboard KPI | `MPageStat` + `MPagePlaceholder` |
+| Dashboard KPI / chart pending | `MPageStat` + `MCard shadow="always"` + `MEmpty` |
 | Module cards | `MCard` / `MPanel` / `MFieldset` |
 | Grid / spacing | `MGrid` + `MGridItem`, or `MFlex` / `MSpace` |
 

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

@@ -2,6 +2,8 @@
 
 **Default rule:** operation feedback uses the `message` API. Use `toast` only when you need a title plus detail, or an async / background notification feel.
 
+Authoritative selection + key API notes also live in MCP / skill decision **`feedback-choice`** ([decision-recipes.md](./decision-recipes.md)). Keep this file and that decision aligned.
+
 ## Three different things
 
 | Name | Shape | API | Typical use |

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

@@ -1,6 +1,6 @@
 # Optional companions
 
-This skill is **standalone**. Distilled craft lives in [visual-craft.md](visual-craft.md). Companions are optional soft upgrades installed by `@morya-ui/setup` (or already present in the repo).
+This skill is **standalone**. Distilled craft lives in [visual-craft.md](visual-craft.md). Companions are optional soft upgrades installed by `@morya-ui/setup` via the [skills CLI](https://skills.sh/) (always the latest published version).
 
 ## Conflict rule
 
@@ -13,15 +13,15 @@ This skill is **standalone**. Distilled craft lives in [visual-craft.md](visual-
 npx @morya-ui/setup ai
 
 # Non-interactive
-npx @morya-ui/setup ai --skills=morya-ui-pages,frontend-design,fixing-accessibility
+npx @morya-ui/setup ai --skills=morya-ui-pages,frontend-design,fixing-accessibility,impeccable
 npx @morya-ui/setup ai --skills=all
 ```
 
-| Companion | Safe use | Unsafe use |
-| --- | --- | --- |
-| `frontend-design` | Express / brand panel taste after surface + contract are fixed | Replacing Ops golden shell or introducing a second UI kit |
-| `fixing-accessibility` | Names, keyboard, focus, form errors on top of `M*` | Replacing library dialogs/menus with custom ARIA widgets |
-| `impeccable` (if present locally) | Named polish passes aligned with [visual-craft.md](visual-craft.md) | New token schema or swapping `M*` for raw HTML controls |
+| Companion | Source | Safe use | Unsafe use |
+| --- | --- | --- | --- |
+| `frontend-design` | `anthropics/skills` | Express / brand panel taste after surface + contract are fixed | Replacing Ops golden shell or introducing a second UI kit |
+| `fixing-accessibility` | `ibelick/ui-skills` | Names, keyboard, focus, form errors on top of `M*` | Replacing library dialogs/menus with custom ARIA widgets |
+| `impeccable` | `pbakaus/impeccable` | Named polish / audit passes aligned with [visual-craft.md](visual-craft.md) | New token schema or swapping `M*` for raw HTML controls |
 
 ## Load budget
 

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

@@ -30,11 +30,13 @@ Via MCP: `recommend_page` → `get_golden_page`; local edits: `get_page_snippet`
 2. Sider `MMenu` (**every item has `icon`**)
 3. `MLayoutHeader` → `MBreadcrumb`
 4. `MLayoutContent` → `MPageContent`
-5. `MPageFilters` — inner `MSpace wrap` + Input/Select + query/reset (search ~`14rem`, select ~`10–12rem`)
-6. `MPageToolbar` — title + `#actions` primary action (**one** filled primary)
-7. `MTable` directly in content (usually **no** wrapping `MCard`); status → `MStatus`; `#empty` → `MEmpty`
-8. Pagination via `MTable` paginator or sibling `MPagination`
-9. Short create/edit → `MDialog` + `MForm` on the same page (default)
+5. `MPageHeader` — page title + `#actions` primary (**one** filled primary in viewport)
+6. `MPageFilters` — `variant="filled"` optional; inner `MSpace wrap` + Input/Select + query/reset (query/reset → secondary); optional `collapsible` + `#advanced` for secondary fields
+7. Optional `MPageFilterChips` + closable `MTag` when filters are applied (after filters, before table)
+8. Optional `MPageToolbar` — batch actions only (no page title)
+9. `MTable` directly in content (usually **no** wrapping `MCard`); status → `MStatus`; `#empty` → `MEmpty`
+10. Pagination via `MTable` paginator or sibling `MPagination`
+11. Short create/edit → `MDialog` + `MForm` on the same page (default)
 
 Craft: [visual-craft.md](visual-craft.md) § Ops polish.
 
@@ -51,7 +53,7 @@ Craft: [visual-craft.md](visual-craft.md) § Ops polish.
 1. `MLayout fillViewport` → `MLayoutHeader` → `MBreadcrumb`
 2. `MPageContent density="spacious"` → `MPageHeader` (title + short domain description when useful)
 3. KPI row: `MGrid` + `MPageStat` (4 columns or responsive) — real metric names, not “Metric 1”
-4. Main split: `MCard` + `MPagePlaceholder` and/or recent `MTable` (row status → `MStatus`)
+4. Main split: `MCard shadow="always"` + `MEmpty` (chart pending) and/or recent `MTable` (row status → `MStatus`)
 
 Craft: spacious density + Ops polish; do not turn the first viewport into a marketing hero.
 
@@ -82,7 +84,7 @@ Mirror MCP `get_golden_page` `detail-page`.
 
 ## List create/edit dialog — block order
 
-1. Stay on the list page (`MPageToolbar` + `MTable`)
+1. Stay on the list page (`MPageHeader` + filters/table; optional batch `MPageToolbar`)
 2. `MDialog` ~`28–36rem` + `MForm` fields
 3. Actions in Dialog `#footer` (cancel secondary/text + save primary)
 4. Success → `message.success` one-liner, then close

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

@@ -19,7 +19,7 @@
 - [ ] 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 respects `prefers-reduced-motion`
+- [ ] Motion (if any) is 1–3 intentional moments and follows `useMotion` / `data-m-motion` (not OS `prefers-reduced-motion`)
 
 ## Ops
 

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

@@ -31,7 +31,7 @@ Apply after the golden block order is correct. These are **required**, not optio
 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.
+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”.
@@ -57,7 +57,7 @@ Also avoid: Inter/Roboto/Arial as the *expressive* display choice on Express sur
 - **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; respect `prefers-reduced-motion`. Prefer transform/opacity over layout thrash.
+- **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)
@@ -121,14 +121,12 @@ Full-bleed thesis: brand mark (small) → one headline → one lead → CTA grou
 Optional micro-motion (one signature only):
 
 ```css
-@media (prefers-reduced-motion: no-preference) {
-  .landing-hero__track span {
-    animation: m-craft-fade-up 480ms ease both;
-  }
-  .landing-hero__track span:nth-child(2) { animation-delay: 60ms; }
-  .landing-hero__track span:nth-child(3) { animation-delay: 120ms; }
-  .landing-hero__track span:nth-child(4) { animation-delay: 180ms; }
+[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); }

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

@@ -38,4 +38,4 @@ import { MButton, MInput } from 'morya-ui'
 - 用 `MDropdown` 代替 Select 做枚举选择。
 - 手写 table/modal 替代 `MTable` / `MDialog`。
 
-完整清单：MCP，或 skill `references/component-index.md`
+完整清单：MCP `recommend_component`（含 recipe），或 skill `references/decision-recipes.md` / `component-index.md`。

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

@@ -5,7 +5,7 @@ alwaysApply: true
 
 # Morya UI 设计系统
 
-1. **先读** 项目根目录 `DESIGN.md`。组件选型用 MCP，或 skill `references/component-index.md`。
+1. **先读** 项目根目录 `DESIGN.md`。组件选型用 MCP `recommend_component`（含 recipe），或 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`（`list-page` / `form-page` / `form-in-dialog` / `detail-page` / `dashboard-page` / `login-page` / `landing-page` / `empty-state` / `result-page` / `settings-page` / `wizard-form`），不要发明新布局范式。

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

@@ -31,11 +31,13 @@ alwaysApply: false
 2. 侧栏 `MMenu`
 3. `MLayoutHeader` → `MBreadcrumb`
 4. `MLayoutContent` → `MPageContent`
-5. `MPageFilters`（内 `MSpace` + Input/Select + 查询/重置）
-6. `MPageToolbar`（标题 + `#actions` 主操作）
-7. `MTable`（直接放置，通常不必包 `MCard`）
-8. 分页由 `MTable paginator` 或同级 `MPagination`
-9. 短新建/编辑：同页 `MDialog` + `MForm`
+5. `MPageHeader`（页面标题 + `#actions` 主操作；视口内 **唯一** filled primary）
+6. `MPageFilters`（可选 `variant="filled"`、`collapsible` + `#advanced`；查询/重置用 secondary）
+7. 可选 `MPageFilterChips` + 可关闭 `MTag`（有已选条件时，放在筛选与表格之间）
+8. 可选 `MPageToolbar`（仅批量操作，**不要**页面标题）
+9. `MTable`（直接放置；`#empty` → `MEmpty`）
+10. 分页由 `MTable paginator` 或同级 `MPagination`
+11. 短新建/编辑：同页 `MDialog` + `MForm`
 
 ## 表单页区块顺序
 
@@ -50,7 +52,7 @@ alwaysApply: false
 1. `MLayout fillViewport` → `MLayoutHeader` → `MBreadcrumb`
 2. `MPageContent density="spacious"` → `MPageHeader`
 3. KPI：`MGrid` + `MPageStat`（4 列或响应式）
-4. 主区两栏：`MCard` + `MPagePlaceholder` / 最近列表 `MTable`
+4. 主区两栏：`MCard shadow="always"` + `MEmpty`（图表未接入）/ 最近列表 `MTable`
 
 ## 页面标准
 

package/template/DESIGN.md

@@ -34,7 +34,7 @@
 | 动效时长 | `--m-motion-fast/normal/enter/exit` |
 | 进出场位移 / 缓动 | `--m-motion-distance` / `--m-motion-ease` |
 
-动效强度用 `useMotion`（`data-m-motion`）；进出场预设用 `motion.transitions` / 组件 `transition`（见文档站「动效」）。
+动效强度用 `useMotion`（`data-m-motion`：`full` / `reduced` / `none`），不跟随系统 `prefers-reduced-motion`；进出场预设用 `motion.transitions` / 组件 `transition`（见文档站「动效」）。
 
 ## 4. 禁止项
 

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

@@ -1,138 +0,0 @@
----
-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

@@ -1,177 +0,0 @@
-
-                                 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

@@ -1,57 +0,0 @@
----
-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.