@morya-ui/mcp 0.4.4 → 0.4.5

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Morya UI contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Morya UI contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,154 +1,154 @@
-# @morya-ui/mcp
-
-Optional [Model Context Protocol](https://modelcontextprotocol.io/) (stdio) server for [`morya-ui`](https://www.npmjs.com/package/morya-ui).
-
-It indexes component docs, guides, examples, and reusable page patterns so **any MCP-capable AI client** can look up the real API before writing code. It does **not** replace installing the UI library:
-
-```bash
-pnpm add morya-ui
-```
-
-Public docs: run the docs site (`pnpm dev`) and open **Docs → MCP**.
-
-## Run
-
-```bash
-npx -y @morya-ui/mcp
-```
-
-Typical client config (field names vary by client):
-
-```json
-{
-  "command": "npx",
-  "args": ["-y", "@morya-ui/mcp"]
-}
-```
-
-Local checkout:
-
-```bash
-pnpm --filter @morya-ui/mcp build
-node packages/ui-mcp/bin/morya-ui-mcp.js
-```
-
-## Tools
-
-MCP also exposes **resources** and **resource templates** for clients that support `resources/list`, `resources/templates/list`, and `resources/read`. Call `version` to see the current resource and template counts.
-
-Static resources:
-
-- `m://catalog/index.json`
-- `m://design-rules.json`
-
-Resource templates:
-
-- `component-docs` → `m://components/{component}/docs/{locale}`
-- `component-api` → `m://components/{component}/api.json`
-- `guide-docs` → `m://guides/{guide}/docs/{locale}`
-
-### Core — component docs
-
-| Tool             | Purpose                                      |
-| ---------------- | -------------------------------------------- |
-| `list`           | List components / guides / examples / categories / patterns |
-| `search`         | Search docs, examples, patterns, and decisions |
-| `get_component`  | Component metadata and API                   |
-| `get_example`    | One source-backed example                    |
-| `get_guide`      | Guide docs                                   |
-| `get_setup`      | Install / setup bundle                       |
-| `validate_usage` | Soft-check props / events                    |
-| `version`        | Package + catalog status                     |
-
-### Advanced — page composition (optional)
-
-| Tool                  | Purpose                                                       |
-| --------------------- | ------------------------------------------------------------- |
-| `list_patterns`       | List reusable page composition patterns                       |
-| `get_pattern`         | Read a pattern's structure, layout, and rules                 |
-| `recommend_page`      | Recommend a pattern from page intent; optional `density`, `brief`, starter scaffold |
-| `map_reference`       | Map a reference brief → snippets, token roles, signature shell                     |
-| `get_design_rules`    | Design-token, shells catalog, and composition rules                            |
-| `recommend_component` | List, read, or recommend component selection guides                           |
-| `list_golden_pages`   | List golden page samples (list / form / dashboard)                            |
-| `get_golden_page`     | Read golden page Vue source                                                   |
-| `list_page_snippets`  | List section snippets for local page edits                                      |
-| `get_page_snippet`    | Read a section snippet (`filters`, `toolbar`, `form-actions`…)                  |
-| `get_style_direction` | Resolve visual style from user words / cues (or ask)                            |
-| `get_style_shells`    | List or read token-only signature shells with pasteable CSS                     |
-| `validate_page`       | Contract (`ok`) + craft suggestions; pass `brief` for fidelity checks           |
-
-`mode`: `zh` (default) or `en`.
-
-Component lookup accepts common aliases such as `DataTable`, `数据表格`, `Pager`, and `确认弹窗`.
-
-### Recommended workflow
-
-**Look up a component:**
-
-1. `search` or `get_component`
-2. `get_example` for unfamiliar APIs
-3. `validate_usage` on generated snippets
-
-**Plan a page:**
-
-1. `recommend_page` with business intent, page type, features, optional `density` / `brief`
-2. If the user gave a screenshot/mock description → `map_reference` (or reuse `recommend_page.referenceMapping`)
-3. `get_page_snippet` for each mapped block; optional `get_style_shells` for Account / Express / Flow
-4. `get_golden_page` only when unsure of whole-page block order
-5. `get_design_rules` / `get_component` / `get_example` for APIs
-6. `recommend_component` when choosing between similar components
-7. `validate_usage` + `validate_page({ brief })` — contract must pass (`ok: true`)
-
-**Edit one section of an existing page:**
-
-1. `list_page_snippets` with `query` or `pageType`
-2. `get_page_snippet` for the matched section (`list-filters`, `form-actions`, …)
-3. `get_component` / `get_example` for unfamiliar imports
-4. `validate_usage` + `validate_page` on the merged result
-
-For a starter Vue file, pass `includeScaffold: true` to `recommend_page`:
-
-```json
-{
-  "intent": "Oil well management list",
-  "pageType": "list",
-  "features": ["filters", "create", "pagination"],
-  "mode": "en",
-  "includeScaffold": true
-}
-```
-
-`recommend_component` modes:
-
-- omit `query` and `decision` → list decision guides
-- `decision` only → read one guide with **when / avoidWhen / recipe (props, slots, events) / antiPatterns** (e.g. `overlay-choice`, `selection-choice`, `feedback-choice`, `confirm-choice`)
-- `query` → recommend a guide for a UI question (same recipe payload)
-
-Offline mirror for the page skill: `design-kit/.../references/decision-recipes.md` (regenerate with `pnpm --filter @morya-ui/mcp generate:recipes`).
-
-## Develop
-
-```bash
-pnpm install
-pnpm mcp:generate
-pnpm mcp:build
-```
-
-After editing `src/decisions.ts`, run `pnpm --filter @morya-ui/mcp generate:recipes` (also runs as part of `build`) so the skill offline recipes stay in sync.
-
-```bash
-pnpm mcp:generate
-pnpm mcp:check-catalog
-pnpm mcp:validate-catalog
-pnpm mcp:audit-examples
-```
-
-## Release
-
-From the repo root (version syncs from `morya-ui`):
-
-```bash
-pnpm release:mcp -- --dry-run
-pnpm release:mcp
-```
+# @morya-ui/mcp
+
+Optional [Model Context Protocol](https://modelcontextprotocol.io/) (stdio) server for [`morya-ui`](https://www.npmjs.com/package/morya-ui).
+
+It indexes component docs, guides, examples, and reusable page patterns so **any MCP-capable AI client** can look up the real API before writing code. It does **not** replace installing the UI library:
+
+```bash
+pnpm add morya-ui
+```
+
+Public docs: run the docs site (`pnpm dev`) and open **Docs → MCP**.
+
+## Run
+
+```bash
+npx -y @morya-ui/mcp
+```
+
+Typical client config (field names vary by client):
+
+```json
+{
+  "command": "npx",
+  "args": ["-y", "@morya-ui/mcp"]
+}
+```
+
+Local checkout:
+
+```bash
+pnpm --filter @morya-ui/mcp build
+node packages/ui-mcp/bin/morya-ui-mcp.js
+```
+
+## Tools
+
+MCP also exposes **resources** and **resource templates** for clients that support `resources/list`, `resources/templates/list`, and `resources/read`. Call `version` to see the current resource and template counts.
+
+Static resources:
+
+- `m://catalog/index.json`
+- `m://design-rules.json`
+
+Resource templates:
+
+- `component-docs` → `m://components/{component}/docs/{locale}`
+- `component-api` → `m://components/{component}/api.json`
+- `guide-docs` → `m://guides/{guide}/docs/{locale}`
+
+### Core — component docs
+
+| Tool             | Purpose                                      |
+| ---------------- | -------------------------------------------- |
+| `list`           | List components / guides / examples / categories / patterns |
+| `search`         | Search docs, examples, patterns, and decisions |
+| `get_component`  | Component metadata and API                   |
+| `get_example`    | One source-backed example                    |
+| `get_guide`      | Guide docs                                   |
+| `get_setup`      | Install / setup bundle                       |
+| `validate_usage` | Soft-check props / events                    |
+| `version`        | Package + catalog status                     |
+
+### Advanced — page composition (optional)
+
+| Tool                  | Purpose                                                       |
+| --------------------- | ------------------------------------------------------------- |
+| `list_patterns`       | List reusable page composition patterns                       |
+| `get_pattern`         | Read a pattern's structure, layout, and rules                 |
+| `recommend_page`      | Recommend a pattern from page intent; optional `density`, `brief`, starter scaffold |
+| `map_reference`       | Map a reference brief → snippets, token roles, signature shell                     |
+| `get_design_rules`    | Design-token, shells catalog, and composition rules                            |
+| `recommend_component` | List, read, or recommend component selection guides                           |
+| `list_golden_pages`   | List golden page samples (list / form / dashboard)                            |
+| `get_golden_page`     | Read golden page Vue source                                                   |
+| `list_page_snippets`  | List section snippets for local page edits                                      |
+| `get_page_snippet`    | Read a section snippet (`filters`, `toolbar`, `form-actions`…)                  |
+| `get_style_direction` | Resolve visual style from user words / cues (or ask)                            |
+| `get_style_shells`    | List or read token-only signature shells with pasteable CSS                     |
+| `validate_page`       | Contract (`ok`) + craft suggestions; pass `brief` for fidelity checks           |
+
+`mode`: `zh` (default) or `en`.
+
+Component lookup accepts common aliases such as `DataTable`, `数据表格`, `Pager`, and `确认弹窗`.
+
+### Recommended workflow
+
+**Look up a component:**
+
+1. `search` or `get_component`
+2. `get_example` for unfamiliar APIs
+3. `validate_usage` on generated snippets
+
+**Plan a page:**
+
+1. `recommend_page` with business intent, page type, features, optional `density` / `brief`
+2. If the user gave a screenshot/mock description → `map_reference` (or reuse `recommend_page.referenceMapping`)
+3. `get_page_snippet` for each mapped block; optional `get_style_shells` for Account / Express / Flow
+4. `get_golden_page` only when unsure of whole-page block order
+5. `get_design_rules` / `get_component` / `get_example` for APIs
+6. `recommend_component` when choosing between similar components
+7. `validate_usage` + `validate_page({ brief })` — contract must pass (`ok: true`)
+
+**Edit one section of an existing page:**
+
+1. `list_page_snippets` with `query` or `pageType`
+2. `get_page_snippet` for the matched section (`list-filters`, `form-actions`, …)
+3. `get_component` / `get_example` for unfamiliar imports
+4. `validate_usage` + `validate_page` on the merged result
+
+For a starter Vue file, pass `includeScaffold: true` to `recommend_page`:
+
+```json
+{
+  "intent": "Oil well management list",
+  "pageType": "list",
+  "features": ["filters", "create", "pagination"],
+  "mode": "en",
+  "includeScaffold": true
+}
+```
+
+`recommend_component` modes:
+
+- omit `query` and `decision` → list decision guides
+- `decision` only → read one guide with **when / avoidWhen / recipe (props, slots, events) / antiPatterns** (e.g. `overlay-choice`, `selection-choice`, `feedback-choice`, `confirm-choice`)
+- `query` → recommend a guide for a UI question (same recipe payload)
+
+Offline mirror for the page skill: `design-kit/.../references/decision-recipes.md` (regenerate with `pnpm --filter @morya-ui/mcp generate:recipes`).
+
+## Develop
+
+```bash
+pnpm install
+pnpm mcp:generate
+pnpm mcp:build
+```
+
+After editing `src/decisions.ts`, run `pnpm --filter @morya-ui/mcp generate:recipes` (also runs as part of `build`) so the skill offline recipes stay in sync.
+
+```bash
+pnpm mcp:generate
+pnpm mcp:check-catalog
+pnpm mcp:validate-catalog
+pnpm mcp:audit-examples
+```
+
+## Release
+
+From the repo root (version syncs from `morya-ui`):
+
+```bash
+pnpm release:mcp -- --dry-run
+pnpm release:mcp
+```

package/bin/morya-ui-mcp.js

@@ -1,2 +1,2 @@
-#!/usr/bin/env node
-import '../dist/index.js'
+#!/usr/bin/env node
+import '../dist/index.js'