@diagrammo/dgmo 0.8.25 → 0.8.26

package/.claude/commands/dgmo.md

@@ -244,392 +244,16 @@ palette catppuccin     // directives are space-separated (no colon)
 Inline colors on most elements: append `(colorname)` — e.g. `North(red) 850`, `[Process(blue)]`.
 Named colors: `red`, `orange`, `yellow`, `green`, `blue`, `purple`, `teal`, `cyan`, `gray`.
 
-### sequence (most commonly used)
+### Per-chart-type syntax
 
-```
-sequence Auth Flow
-
-User -Login-> API
-API -Find user-> DB
-DB -user record-> API
-note
-  Indexed lookup on email column
-
-if credentials valid
-  API -200 OK + token-> User
-else
-  API -401 Unauthorized-> User
-
-== Logout ==
-
-note session cleanup
-User -Logout-> API
-API -Delete session-> DB
-```
-
-- Sync: `A -label-> B` · Async: `A ~label~> B` · Unlabeled: `A -> B`
-- Blocks: `if` / `else`, `loop`, `parallel` — closed by indentation (no `end` keyword)
-- Notes: place `note text` after a message — it naturally associates with that position.
-  - Single-line: `note text`
-  - Multi-line: `note` then indent continuation lines beneath it
-  - Anchored: `note right of API` then indent continuation lines
-- Sections: `== Title ==`
-- Groups: `[Group Name]` with indented participants
-
-### flowchart
-
-```
-(Start) -> <Valid Input?>
-  -yes-> [Process Data] -> (Done)
-  -no-> /Get Input/ -> <Valid Input?>
-```
-
-Shapes: `(oval)` `[rect]` `<diamond>` `/parallelogram/` `[[subroutine]]` `[document~]`
-
-### bar / line / pie (data charts)
-
-**Data-chart conventions (apply to every chart under §15 of the spec):**
-- Data rows are **space-separated**. Commas between values are tolerated for back-compat but not idiomatic — do not generate them.
-- Multi-series `series` declarations use the **indented one-per-line form** when there's more than one series; it's easier to read and reviewers prefer it.
-
-```
-// bar (single series)
-bar Revenue by Region
-series Revenue
-North 850
-South 620
-
-// line (multi-series — use indented series block + space-separated values)
-line Quarterly Numbers
-series
-  Sales (red)
-  Costs (blue)
-Q1 100 50
-Q2 120 55
-
-// pie
-pie Market Share
-labels percent
-Company A 40
-Company B 35
-```
-
-### er
-
-```
-users
-  id int [pk]
-  email varchar [unique]
-  1-writes-* posts
-
-posts
-  id int [pk]
-  author_id int [fk]
-```
-
-### org
-
-```
-CEO
-  VP Engineering
-    [Platform Team]
-      Lead
-        Dev 1
-        Dev 2
-  VP Marketing
-```
-
-### infra
-
-```
-infra
-
-edge
-  rps 10000
-  -> CDN
-
-CDN
-  cache-hit 80%
-  -> API
-
-API
-  instances 3
-  max-rps 500
-  latency-ms 45
-```
-
-### slope
-
-```
-slope Fleet Strength
-
-period 1715 1725
-
-Blackbeard 40 4
-Roberts 12 52
-Anne Bonny (red) 8 15
-```
-
-- `period` directive required before data rows (one-line or indented block for multi-token labels)
-- Data rows: `Label value1 value2` — space-separated, no colons
-- Right-scan: parser takes numeric values from the right, everything left is the label
-- Color annotations: `Label (color) value1 value2`
-
-### timeline
-
-```
-timeline Product Roadmap
-sort tag:Team
-
-tag Team alias t
-  Engineering(blue)
-  Design(purple)
-
-era 2024-01 -> 2024-06 Phase 1
-marker 2024-03 Beta Launch
-
-2024-01->2024-03 Core API | t: Engineering
-2024-02->2024-05 UX Research | t: Design
-2024-06 GA Release | t: Engineering
-```
-
-- Dates: `YYYY`, `YYYY-MM`, `YYYY-MM-DD`. Ranges: `start->end`. Durations: `start->6m`, `->2w`, `->30d`
-- Uncertain end: `2024-03?`. Point events: single date, no range
-- `era start -> end Label` — background band. `marker date Label` — vertical line
-- `## Group(color)` headers for manual grouping, or `tag` + `sort tag:Name` for swimlanes
-- Pipe metadata: `| tagalias: Value`
-
-### gantt
-
-```
-gantt Sprint Plan
-start 2024-01-15
-today-marker 2024-03-01
-critical-path
-dependencies
-
-10bd Design | 80%
-parallel
-  [Backend]
-    15bd API Layer
-    5bd? Auth Module
-      -> Frontend.Integration | offset: -3bd
-  [Frontend]
-    10bd Components
-    5bd Integration
-5bd QA Testing
-0d Release
-```
-
-- `start YYYY-MM-DD` — project start date (required)
-- Duration: `10bd Task Name` (business days). Uncertain: `5bd?`. Milestone: `0d`
-- `parallel` block for concurrent tracks. `[Group]` for named sections
-- Progress: `| 80%` or trailing `80%`
-- Dependencies: `-> Target.Task` or `-blocks-> Target.Task`. `offset: -3bd` for overlap
-- `today-marker`, `critical-path`, `dependencies` — top-level directives
-- Tags + eras + markers same as timeline
-
-### c4
-
-```
-c4 Banking System
-
-Customer is a person
-  description: A customer of the bank
-
-Banking is a system
-  description: Online banking portal
-  containers
-    WebApp is a container | tech: React
-    API is a container | tech: Node.js
-    DB is a container is a database | tech: PostgreSQL
-
-Email is a system
-  description: External email service
+For every specific chart type (sequence, flowchart, bar/line/pie, scatter, er, org, infra, slope, timeline, gantt, c4, class, venn, quadrant, sankey/chord, state, boxes-and-lines, and the rest), do not guess from prior knowledge — call the MCP tools:
 
-Customer -Uses-> Banking
-Banking -Sends emails [SMTP]-> Email
 ```
-
-- Elements: `Name is a person|system|container|component`
-- Metadata (pipe-delimited): `| description: text, tech: stack`
-- Indented `description:` also works (no pipe needed)
-- Sections: `containers` (inside system), `components` (inside container), `deployment`
-- Deployment: `NodeName is a cloud|database|cache|queue`
-- Arrows: sync `-label [tech]->`, async `~label [tech]~>`, bidirectional `<->`, `<~>`
-
-### class
-
-```
-class Type Hierarchy
-
-Drawable [interface]
-  + draw(): void
-
-Shape implements Drawable [abstract]
-  # x: number
-  + area(): number
-  count: number {static}
-
-Circle extends Shape
-  - radius: number
-
-Color [enum]
-  Red
-  Green
-  Blue
-
-Canvas
-  *-- Shape : contains
-  ..> Logger : uses
-```
-
-- Modifiers: `[abstract]`, `[interface]`, `[enum]`
-- Inheritance: `Child extends Parent`, `Child implements Interface`
-- Visibility: `+` public, `#` protected, `-` private. Static: `{static}`
-- Relationships: `A *-- B` (composition), `A o-- B` (aggregation), `A --|> B` (inheritance), `A ..|> B` (implementation), `A ..> B` (dependency), `A -> B` (association)
-- Optional label: `A *-- B : description`
-
-### venn
-
-```
-venn Full-Stack Skills
-
-Frontend(blue) alias fe
-Backend(green) alias be
-DevOps(orange) alias de
-
-fe + be Web Systems
-be + de Platform Ops
-fe + be + de Full Stack
-```
-
-- Sets: `Name(color) alias id` — declares a circle
-- Overlaps: `id + id Label` — names the intersection region
-- Option: `values on` to show sizes. Sized form: `id(color): 120 "Label"`
-
-### quadrant
-
-```
-quadrant Feature Priorities
-
-x-label Low Effort, High Effort
-y-label Low Impact, High Impact
-
-top-left Quick Wins(green)
-top-right Major Projects
-bottom-left Fill-ins
-bottom-right Avoid(red)
-
-Dark Mode (blue) 0.25 0.85
-API v2 0.8 0.9
-Fix Typos 0.1 0.15
-```
-
-- Axis labels: `x-label Low, High` and `y-label Low, High` (comma is the low/high delimiter here by design, not a data-row delimiter)
-- Quadrant labels: `top-left`, `top-right`, `bottom-left`, `bottom-right`
-- Data points: `Label (color) x y` — space-separated per §15 Rule A (comma-form tolerated for back-compat but not idiomatic)
-
-### sankey / chord
-
-```
-// sankey — flow diagram
-sankey Budget Allocation
-
-Revenue (green)
-  Costs: 600
-  Profit (blue): 400
-
-// arrow syntax also works
-Revenue -> Marketing: 200
-
-// chord — same syntax, circular layout
-chord Team Collaboration
-Engineering -> Design 85
-Design -> Product 68
-```
-
-- Indented syntax: parent → child with `Target: weight`
-- Arrow syntax: `Source -> Target: weight` (sankey) or `Source -> Target weight` (chord)
-- Node colors: `Name (color)`. Link colors: `Target: 600 (red)`
-
-### state
-
-```
-state Order Lifecycle
-direction LR
-
-[*] -> Pending -submit-> Validating
-
-Validating
-  -approved-> Processing
-  -rejected-> Cancelled(red)
-
-## Fulfillment(blue)
-  Processing -ship-> Shipped
-  Shipped -delivered-> Done
-
-Cancelled -> [*]
-Done -> [*]
-```
-
-- `[*]` — start/end pseudostate (filled circle)
-- Transitions: `A -> B`, `A -label-> B`, `A -(color)-> B`
-- Chains: `A -> B -> C` on one line
-- Indented transitions use parent as source
-- Groups: `## GroupName(color)` with indented states
-- Options: `direction LR` (left-right) or `TB` (top-bottom, default)
-
-### scatter
-
-```
-scatter Funding vs Revenue
-x-label Funding ($M)
-y-label Revenue ($M)
-
-[SaaS](blue)
-  Acme 12 8.5
-  DataSync 5.2 3.1
-
-[Fintech](green)
-  PayFlow 45 32
-  LendTech 18 12.5
-```
-
-- Data: `Label x y` or `Label x y size` (bubble chart) — space-separated per §15 Rule A
-- Groups: `[Category](color)` headers
-- Options: `labels on`, `xlabel`, `ylabel`, `sizelabel`
-
-### boxes-and-lines
-
-```
-boxes-and-lines Architecture
-
-tag Team t Backend(blue), Frontend(green), Platform(purple)
-active-tag Team
-direction LR
-
-API Gateway | t: Backend
-  -routes-> AuthService
-  -queries-> DB
-
-AuthService | t: Backend
-DB | t: Platform
-
-[Cloud]
-  API Gateway
-  AuthService
-
-Redis <-syncs-> DB | t: Platform
+mcp__dgmo__get_language_reference("<type>")   // authoritative grammar + directives
+mcp__dgmo__get_examples("<type>")             // real starter templates from the gallery
 ```
 
-- Nodes: explicit `Name | metadata` or implicit from edges
-- Edges: `A -label-> B` (directed), `A <-label-> B` (bidirectional)
-- Indented edges use parent as source: `Parent` then `  -label-> Target`
-- Groups: `[Name]` with indented children (max 2 levels deep)
-- Tags: `tag Name alias Value1(color), Value2(color)` + `active-tag Name` + `hide alias:value`
-- Options: `direction LR` (left-right) or `TB` (top-bottom, default)
-- Shape inference: names containing DB/database → cylinder, Cache/Redis → diamond, Queue → hexagon, etc.
+Both ship inside `@diagrammo/dgmo` and always reflect the installed version, so they never drift from the actual parsers. This replaces the per-type sections that used to live here and went stale every time a chart type's syntax evolved.
 
 ## Anti-Patterns
 

package/.cursorrules

@@ -121,9 +121,9 @@ API Gateway | t: Backend
 
 Nodes: implicit from edges or explicit with `| metadata`. Edges: `A -label-> B`, `A <-label-> B` (bidi). Groups: `[Name]` with indented children (max 2 levels). Tags: `tag Name alias values`, `active-tag`, `hide`. Options: `direction LR|TB`.
 
-## All 33 chart types
+## Supported chart types
 
-bar, line, multi-line, area, pie, doughnut, radar, polar-area, bar-stacked, scatter, sankey, chord, function, heatmap, funnel, slope, wordcloud, arc, timeline, venn, quadrant, sequence, flowchart, state, class, er, org, kanban, c4, sitemap, infra, gantt, boxes-and-lines
+If the dgmo MCP server is configured, call `list_chart_types` for the authoritative list (with descriptions) and `suggest_chart_type({ prompt })` to pick the best match for a request. Otherwise run `dgmo --chart-types` in a terminal. The static list previously here drifted with every new chart type — the MCP tool / CLI is the source of truth.
 
 ## Common patterns
 

package/.windsurfrules

@@ -121,9 +121,9 @@ API Gateway | t: Backend
 
 Nodes: implicit from edges or explicit with `| metadata`. Edges: `A -label-> B`, `A <-label-> B` (bidi). Groups: `[Name]` with indented children (max 2 levels). Tags: `tag Name alias values`, `active-tag`, `hide`. Options: `direction LR|TB`.
 
-## All 33 chart types
+## Supported chart types
 
-bar, line, multi-line, area, pie, doughnut, radar, polar-area, bar-stacked, scatter, sankey, chord, function, heatmap, funnel, slope, wordcloud, arc, timeline, venn, quadrant, sequence, flowchart, state, class, er, org, kanban, c4, sitemap, infra, gantt, boxes-and-lines
+If the dgmo MCP server is configured, call `list_chart_types` for the authoritative list (with descriptions) and `suggest_chart_type({ prompt })` to pick the best match for a request. Otherwise run `dgmo --chart-types` in a terminal. The static list previously here drifted with every new chart type — the MCP tool / CLI is the source of truth.
 
 ## Common patterns
 

package/AGENTS.md

@@ -15,12 +15,15 @@ This installs the MCP server and writes the dgmo config to `.codex/config.toml`.
 ## MCP Tools
 
 When the `dgmo` MCP server is configured, use these tools directly:
-- `preview_diagram` — renders diagram(s) and opens a live HTML preview in the browser (default for showing diagrams)
+- `suggest_chart_type` — first call when creating a new diagram; ranks the best chart types for a plain-English prompt
+- `list_chart_types` — lists every supported chart type with descriptions
+- `get_language_reference` — fetches full syntax for any chart type (call this before generating an unfamiliar chart type)
+- `get_examples` — real example diagrams from the gallery; useful as few-shot references
+- `validate_diagram` — fast syntax check before rendering (much cheaper than a failed render)
 - `render_diagram` — renders to PNG or SVG, returns file path
+- `preview_diagram` — renders diagram(s) and opens a live HTML preview in the browser
 - `share_diagram` — creates a shareable diagrammo.app URL
 - `open_in_app` — opens diagram in Diagrammo desktop app (macOS)
-- `list_chart_types` — lists all 34 supported chart types with descriptions
-- `get_language_reference` — fetches full syntax for any chart type (call this before generating an unfamiliar chart type)
 - `generate_report` — renders multiple diagrams into an HTML report with table of contents
 
 ## When to use dgmo
@@ -113,9 +116,9 @@ API
   latency-ms: 45
 ```
 
-## All 33 chart types
+## Supported chart types
 
-bar, line, multi-line, area, pie, doughnut, radar, polar-area, bar-stacked, scatter, sankey, chord, function, heatmap, funnel, slope, wordcloud, arc, timeline, venn, quadrant, sequence, flowchart, state, class, er, org, kanban, c4, sitemap, infra, gantt, boxes-and-lines
+Call `list_chart_types` for the authoritative list with descriptions, or `suggest_chart_type({ prompt })` to rank candidates against a user request. The static list previously here drifted with every new chart type — the MCP tool is the source of truth.
 
 ### Boxes and lines
 ```