@diagrammo/dgmo 0.48.1 → 0.49.0

package/.cursorrules

@@ -6,7 +6,7 @@ When the user asks for a diagram, visualization, or chart, generate a `.dgmo` fi
 <!-- DGMO-AI-CORE:START -->
 ## DGMO AI Core
 
-_Generated from `language-reference.md` — the anti-patterns and 43-type index below are identical across every DGMO AI surface._
+_Generated from `language-reference.md` — the anti-patterns and 46-type index below are identical across every DGMO AI surface._
 
 ### Disambiguation — where DGMO diverges from LLM priors
 
@@ -60,7 +60,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 - **Let the defaults show.** Don't add `no-*` opt-outs unless the user asked to hide or disable something — they strip helpful labels, values, and color.
 - **Pick a fitting direction.** Top-to-bottom for hierarchies and processes; left-to-right for pipelines and flows (where the type supports a direction).
 
-### Chart-type index (43) — pick the type, then fetch its section
+### Chart-type index (45) — pick the type, then fetch its section
 
 | id | when to use |
 | -- | ----------- |
@@ -75,6 +75,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `sitemap` | site / app navigation structure |
 | `mindmap` | radial hierarchy of ideas from a central topic |
 | `org` | reporting hierarchy |
+| `family` | family tree / genealogy: unions (couples), children, remarriage, adoption, GEDCOM-style metadata |
 | `kanban` | task-board columns |
 | `gantt` | project scheduling with task dependencies and milestones |
 | `pert` | project network with three-point estimates and critical path |
@@ -82,6 +83,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `version-control` | git / version-control branch-and-merge graph: commits, branches, merges, rebase, HEAD and remote-tracking (gitGraph-style) |
 | `timeline` | events, eras, and date ranges |
 | `event-line` | annotated narrative timeline — events on a line with descriptions, optionally not to scale (NOT the date-scaled `timeline`) |
+| `body` | human anatomy figure annotated by muscle name — for medical, exercise, and educational diagrams |
 | `journey-map` | UX flow with emotion scores, phases, annotations |
 | `cycle` | cyclical process (PDCA, OODA, DevOps loops) |
 | `raci` | tasks × roles responsibility matrix; variant (RACI / RASCI / DACI) is inferred from the markers used |
@@ -91,6 +93,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `ring` | concentric rings of nested categories |
 | `treemap` | nested rectangles sized by value (budgets, disk usage, portfolios) |
 | `block` | author-controlled grid of nested, collapsible blocks (system / architecture layouts) |
+| `sketch` | GUI-first free-placement canvas: uniform shapes on a snap grid, arrows, tags (markup is app-generated) |
 | `map` | geographic concept map: regions, points, routes |
 | `wireframe` | low-fidelity UI layout with panels and controls |
 | `bar` | categorical comparisons (multi-series via `stack` / `group`) |
@@ -114,7 +117,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 
 ### Common examples (curated, parse-clean)
 
-_The most common types, inline so you can generate them without a fetch. For the other 35, get the per-type section (see below)._
+_The most common types, inline so you can generate them without a fetch. For the other 38, get the per-type section (see below)._
 
 #### journey-map
 
@@ -226,6 +229,8 @@ ports
 ```dgmo
 class Ship Class Hierarchy
 
+solid-fill 
+
 interface Vessel
   + sail(): void
   + anchor(): void

package/.github/copilot-instructions.md

@@ -6,7 +6,7 @@ When the user asks for a diagram, visualization, or chart, generate a `.dgmo` fi
 <!-- DGMO-AI-CORE:START -->
 ## DGMO AI Core
 
-_Generated from `language-reference.md` — the anti-patterns and 43-type index below are identical across every DGMO AI surface._
+_Generated from `language-reference.md` — the anti-patterns and 46-type index below are identical across every DGMO AI surface._
 
 ### Disambiguation — where DGMO diverges from LLM priors
 
@@ -60,7 +60,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 - **Let the defaults show.** Don't add `no-*` opt-outs unless the user asked to hide or disable something — they strip helpful labels, values, and color.
 - **Pick a fitting direction.** Top-to-bottom for hierarchies and processes; left-to-right for pipelines and flows (where the type supports a direction).
 
-### Chart-type index (43) — pick the type, then fetch its section
+### Chart-type index (45) — pick the type, then fetch its section
 
 | id | when to use |
 | -- | ----------- |
@@ -75,6 +75,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `sitemap` | site / app navigation structure |
 | `mindmap` | radial hierarchy of ideas from a central topic |
 | `org` | reporting hierarchy |
+| `family` | family tree / genealogy: unions (couples), children, remarriage, adoption, GEDCOM-style metadata |
 | `kanban` | task-board columns |
 | `gantt` | project scheduling with task dependencies and milestones |
 | `pert` | project network with three-point estimates and critical path |
@@ -82,6 +83,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `version-control` | git / version-control branch-and-merge graph: commits, branches, merges, rebase, HEAD and remote-tracking (gitGraph-style) |
 | `timeline` | events, eras, and date ranges |
 | `event-line` | annotated narrative timeline — events on a line with descriptions, optionally not to scale (NOT the date-scaled `timeline`) |
+| `body` | human anatomy figure annotated by muscle name — for medical, exercise, and educational diagrams |
 | `journey-map` | UX flow with emotion scores, phases, annotations |
 | `cycle` | cyclical process (PDCA, OODA, DevOps loops) |
 | `raci` | tasks × roles responsibility matrix; variant (RACI / RASCI / DACI) is inferred from the markers used |
@@ -91,6 +93,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `ring` | concentric rings of nested categories |
 | `treemap` | nested rectangles sized by value (budgets, disk usage, portfolios) |
 | `block` | author-controlled grid of nested, collapsible blocks (system / architecture layouts) |
+| `sketch` | GUI-first free-placement canvas: uniform shapes on a snap grid, arrows, tags (markup is app-generated) |
 | `map` | geographic concept map: regions, points, routes |
 | `wireframe` | low-fidelity UI layout with panels and controls |
 | `bar` | categorical comparisons (multi-series via `stack` / `group`) |
@@ -114,7 +117,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 
 ### Common examples (curated, parse-clean)
 
-_The most common types, inline so you can generate them without a fetch. For the other 35, get the per-type section (see below)._
+_The most common types, inline so you can generate them without a fetch. For the other 38, get the per-type section (see below)._
 
 #### journey-map
 
@@ -226,6 +229,8 @@ ports
 ```dgmo
 class Ship Class Hierarchy
 
+solid-fill 
+
 interface Vessel
   + sail(): void
   + anchor(): void

package/.windsurfrules

@@ -6,7 +6,7 @@ When the user asks for a diagram, visualization, or chart, generate a `.dgmo` fi
 <!-- DGMO-AI-CORE:START -->
 ## DGMO AI Core
 
-_Generated from `language-reference.md` — the anti-patterns and 43-type index below are identical across every DGMO AI surface._
+_Generated from `language-reference.md` — the anti-patterns and 46-type index below are identical across every DGMO AI surface._
 
 ### Disambiguation — where DGMO diverges from LLM priors
 
@@ -60,7 +60,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 - **Let the defaults show.** Don't add `no-*` opt-outs unless the user asked to hide or disable something — they strip helpful labels, values, and color.
 - **Pick a fitting direction.** Top-to-bottom for hierarchies and processes; left-to-right for pipelines and flows (where the type supports a direction).
 
-### Chart-type index (43) — pick the type, then fetch its section
+### Chart-type index (45) — pick the type, then fetch its section
 
 | id | when to use |
 | -- | ----------- |
@@ -75,6 +75,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `sitemap` | site / app navigation structure |
 | `mindmap` | radial hierarchy of ideas from a central topic |
 | `org` | reporting hierarchy |
+| `family` | family tree / genealogy: unions (couples), children, remarriage, adoption, GEDCOM-style metadata |
 | `kanban` | task-board columns |
 | `gantt` | project scheduling with task dependencies and milestones |
 | `pert` | project network with three-point estimates and critical path |
@@ -82,6 +83,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `version-control` | git / version-control branch-and-merge graph: commits, branches, merges, rebase, HEAD and remote-tracking (gitGraph-style) |
 | `timeline` | events, eras, and date ranges |
 | `event-line` | annotated narrative timeline — events on a line with descriptions, optionally not to scale (NOT the date-scaled `timeline`) |
+| `body` | human anatomy figure annotated by muscle name — for medical, exercise, and educational diagrams |
 | `journey-map` | UX flow with emotion scores, phases, annotations |
 | `cycle` | cyclical process (PDCA, OODA, DevOps loops) |
 | `raci` | tasks × roles responsibility matrix; variant (RACI / RASCI / DACI) is inferred from the markers used |
@@ -91,6 +93,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `ring` | concentric rings of nested categories |
 | `treemap` | nested rectangles sized by value (budgets, disk usage, portfolios) |
 | `block` | author-controlled grid of nested, collapsible blocks (system / architecture layouts) |
+| `sketch` | GUI-first free-placement canvas: uniform shapes on a snap grid, arrows, tags (markup is app-generated) |
 | `map` | geographic concept map: regions, points, routes |
 | `wireframe` | low-fidelity UI layout with panels and controls |
 | `bar` | categorical comparisons (multi-series via `stack` / `group`) |
@@ -114,7 +117,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 
 ### Common examples (curated, parse-clean)
 
-_The most common types, inline so you can generate them without a fetch. For the other 35, get the per-type section (see below)._
+_The most common types, inline so you can generate them without a fetch. For the other 38, get the per-type section (see below)._
 
 #### journey-map
 
@@ -226,6 +229,8 @@ ports
 ```dgmo
 class Ship Class Hierarchy
 
+solid-fill 
+
 interface Vessel
   + sail(): void
   + anchor(): void

package/SKILL.md

@@ -11,7 +11,7 @@ Use dgmo tools to create, render, and share diagrams. dgmo is a text-based diagr
 <!-- DGMO-AI-CORE:START -->
 ## DGMO AI Core
 
-_Generated from `language-reference.md` — the anti-patterns and 43-type index below are identical across every DGMO AI surface._
+_Generated from `language-reference.md` — the anti-patterns and 46-type index below are identical across every DGMO AI surface._
 
 ### Disambiguation — where DGMO diverges from LLM priors
 
@@ -65,7 +65,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 - **Let the defaults show.** Don't add `no-*` opt-outs unless the user asked to hide or disable something — they strip helpful labels, values, and color.
 - **Pick a fitting direction.** Top-to-bottom for hierarchies and processes; left-to-right for pipelines and flows (where the type supports a direction).
 
-### Chart-type index (43) — pick the type, then fetch its section
+### Chart-type index (45) — pick the type, then fetch its section
 
 | id | when to use |
 | -- | ----------- |
@@ -80,6 +80,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `sitemap` | site / app navigation structure |
 | `mindmap` | radial hierarchy of ideas from a central topic |
 | `org` | reporting hierarchy |
+| `family` | family tree / genealogy: unions (couples), children, remarriage, adoption, GEDCOM-style metadata |
 | `kanban` | task-board columns |
 | `gantt` | project scheduling with task dependencies and milestones |
 | `pert` | project network with three-point estimates and critical path |
@@ -87,6 +88,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `version-control` | git / version-control branch-and-merge graph: commits, branches, merges, rebase, HEAD and remote-tracking (gitGraph-style) |
 | `timeline` | events, eras, and date ranges |
 | `event-line` | annotated narrative timeline — events on a line with descriptions, optionally not to scale (NOT the date-scaled `timeline`) |
+| `body` | human anatomy figure annotated by muscle name — for medical, exercise, and educational diagrams |
 | `journey-map` | UX flow with emotion scores, phases, annotations |
 | `cycle` | cyclical process (PDCA, OODA, DevOps loops) |
 | `raci` | tasks × roles responsibility matrix; variant (RACI / RASCI / DACI) is inferred from the markers used |
@@ -96,6 +98,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `ring` | concentric rings of nested categories |
 | `treemap` | nested rectangles sized by value (budgets, disk usage, portfolios) |
 | `block` | author-controlled grid of nested, collapsible blocks (system / architecture layouts) |
+| `sketch` | GUI-first free-placement canvas: uniform shapes on a snap grid, arrows, tags (markup is app-generated) |
 | `map` | geographic concept map: regions, points, routes |
 | `wireframe` | low-fidelity UI layout with panels and controls |
 | `bar` | categorical comparisons (multi-series via `stack` / `group`) |
@@ -119,7 +122,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 
 ### Common examples (curated, parse-clean)
 
-_The most common types, inline so you can generate them without a fetch. For the other 35, get the per-type section (see below)._
+_The most common types, inline so you can generate them without a fetch. For the other 38, get the per-type section (see below)._
 
 #### journey-map
 
@@ -231,6 +234,8 @@ ports
 ```dgmo
 class Ship Class Hierarchy
 
+solid-fill 
+
 interface Vessel
   + sail(): void
   + anchor(): void