@diagrammo/dgmo 0.33.0 → 0.35.0

package/.claude/commands/dgmo.md

@@ -18,37 +18,15 @@ If the MCP tools are **not** available, run the setup flow below — do not ask
 which dgmo || npm install -g @diagrammo/dgmo
 ```
 
-### Step 2 — Install the MCP server (if missing)
+### Step 2 — Run the one-step installer
 
 ```bash
-which dgmo-mcp || npm install -g @diagrammo/dgmo-mcp
+dgmo install claude-code
 ```
 
-### Step 3 — Configure the MCP server
+That single command writes this skill, configures the MCP server in `~/.claude/settings.json` (entry: `{ "command": "dgmo", "args": ["mcp"] }`), and ensures the server is available — no prompts, no separate `dgmo-mcp` package to install. (Use `--scope project` to write `.mcp.json` in the current directory instead of the global settings.)
 
-Ask the user:
-
-> "Where should I configure the MCP server?
-> 1) This project only — write `.mcp.json` here [default]
-> 2) Globally — add to `~/.claude/settings.json` (works in all projects)"
-
-**Option 1 (default):** Create or update `.mcp.json` in the current working directory:
-
-```json
-{
-  "mcpServers": {
-    "dgmo": {
-      "command": "dgmo-mcp"
-    }
-  }
-}
-```
-
-If `.mcp.json` already exists and has other servers, merge the `dgmo` entry in — do not overwrite the file.
-
-**Option 2 (global):** Add the `dgmo` entry to the `mcpServers` object in `~/.claude/settings.json`. Read the file first and merge — do not overwrite other keys.
-
-### Step 4 — Prompt restart
+### Step 3 — Prompt restart
 
 Tell the user:
 
@@ -56,7 +34,7 @@ Tell the user:
 
 Then proceed with the user's original request using CLI fallback (see "Other output options" below).
 
-> **Note for future users:** To set up in one step from the terminal before starting a Claude Code session, run `dgmo --install-claude-code-integration`. It handles everything: installs `@diagrammo/dgmo-mcp`, writes the skill, and configures the MCP server.
+> **One-step from a fresh machine:** `dgmo install` with no target auto-detects and sets up every AI assistant you have (Claude Code, Codex, Claude Desktop, Cursor, Windsurf, Copilot) at once.
 
 ## Project Awareness
 
@@ -89,7 +67,7 @@ For **examples** of real diagrams, call `mcp__dgmo__get_examples("<type>")` —
 
 ### Creating a new diagram
 
-1. **Pick the right chart type** — always call `mcp__dgmo__suggest_chart_type({ prompt: <user's request> })` first. It returns up to 3 ranked candidates with a confidence banner and matched trigger phrases. Use the top match unless you have a strong reason to override it. If the MCP tool is unavailable (Setup Check fallback path), run `dgmo --chart-types` in a terminal to list supported types and pick from that list.
+1. **Pick the right chart type** — always call `mcp__dgmo__suggest_chart_type({ prompt: <user's request> })` first. It returns up to 3 ranked candidates with a confidence banner and matched trigger phrases. Use the top match unless you have a strong reason to override it. If the MCP tool is unavailable (Setup Check fallback path), run `dgmo types` in a terminal and pick from that list — do not pick from memory or assume a requested type is unsupported (see "Supported Chart Types" below).
 2. **Get syntax + examples** — call `mcp__dgmo__get_language_reference("<type>")` and `mcp__dgmo__get_examples("<type>")`.
 3. **Write the `.dgmo` content** — compose the markup.
 4. **Validate first** — call `mcp__dgmo__validate_diagram(dgmo)` to catch syntax errors before rendering. If errors come back, fix them and validate again.
@@ -216,19 +194,26 @@ Then tell the user it's been copied. Otherwise, the default is always `open <url
 ```
 dgmo <input.dgmo> [options]
 cat input.dgmo | dgmo [options]
+dgmo share <input.dgmo>          # shareable diagrammo.app URL (copies to clipboard)
+dgmo types                       # list all supported chart types
 ```
 
 Key options:
 - `-o <file>` — output file; format inferred from extension (`.svg` → SVG, else PNG)
-- `-o url` — output a shareable diagrammo.app URL
 - `--theme <theme>` — `light` (default), `dark`, `transparent`
 - `--palette <name>` — `slate` (default), `atlas`, `blueprint`, `catppuccin`, `nord`, `tidewater`, `tokyo-night`
-- `--copy` — copy the URL to clipboard (use with `-o url`)
-- `--chart-types` — list all supported chart types
+- `--json` — output structured JSON
 
 ## Supported Chart Types
 
-Call `mcp__dgmo__list_chart_types` to see every supported type with descriptions, or `dgmo --chart-types` in a terminal as a CLI fallback. When picking for a new diagram, use `mcp__dgmo__suggest_chart_type` — it scores the full list against the user's prompt (see "Creating a new diagram → step 1").
+**There are ~45 chart types. The authoritative, complete list comes ONLY from the live tool — never from memory and never from any prose list in this skill.** Any chart types named elsewhere in this document (in examples, tips, or the "diagram this" table) are illustrative, NOT the full set. dgmo supports many specialized types people don't expect — including `journey-map`, `mindmap`, `pert`, `raci`, `pyramid`, `wireframe`, `ring`, `tech-radar`, `cycle`, and more.
+
+**Hard rule:** before telling the user a chart type "doesn't exist," isn't supported, or that you'll use "the closest fit instead" — you MUST first query the live list:
+
+- MCP active: `mcp__dgmo__list_chart_types` (full list + descriptions), and `mcp__dgmo__suggest_chart_type({ prompt })` to pick.
+- MCP unavailable: run `dgmo types` in a terminal.
+
+If the user asks for a named visualization (e.g. "user journey", "mind map", "RACI matrix"), assume dgmo supports it and verify against the live list — do not substitute a different type unless the list confirms the requested one is genuinely absent.
 
 ## Key Syntax Patterns
 

package/.github/copilot-instructions.md

@@ -573,7 +573,7 @@ The canonical, ordered list lives in `src/chart-types.ts`.
 
 ```bash
 dgmo file.dgmo -o output.svg       # SVG
-dgmo file.dgmo -o url              # shareable link
+dgmo share file.dgmo               # shareable link (copied to clipboard)
 dgmo file.dgmo --json              # structured JSON output
 ```
 

package/README.md

@@ -110,7 +110,13 @@ Using a docs framework? First-class plugins wrap all of this:
 
 ## Use it from your AI tool
 
-There's an MCP server ([`@diagrammo/dgmo-mcp`](https://www.npmjs.com/package/@diagrammo/dgmo-mcp)) so Claude, Cursor, and other agents can author and render DGMO directly. Setup: **[diagrammo.app/ai](https://diagrammo.app/ai)**.
+Claude, Cursor, Codex, and other agents can author and render DGMO directly. One command sets up every assistant you have — no second package, no prompts:
+
+```bash
+dgmo install
+```
+
+It auto-detects Claude Code, Codex, Claude Desktop, Cursor, Windsurf, and Copilot and wires each one to the bundled MCP server. More: **[diagrammo.app/ai](https://diagrammo.app/ai)**.
 
 ## Chart types
 

package/SKILL.md

@@ -548,7 +548,7 @@ API
 
 ```bash
 dgmo file.dgmo -o output.svg       # SVG
-dgmo file.dgmo -o url              # shareable link
+dgmo share file.dgmo               # shareable link (copied to clipboard)
 dgmo file.dgmo --json              # structured JSON output
 ```