You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prioritize new diagram families from product demand and eval evidence. Each family should be a real contract with notation and layout semantics, not a display label over generic flowchart output.
Candidate sequence for grooming:
State/decision trees: close to the current graph pipeline while adding meaningful semantics.
Organization/tree diagrams: hierarchical layouts with family-specific constraints.
Sequence/swimlane diagrams: lane and ordering semantics.
ER/class/dataflow diagrams: specialized notation and richer node models.
Timeline, Gantt, network, matrix, and other specialized families only when justified by demand.
Definition of done for each family
A typed intermediate representation and semantic validator in diagram-core.
Deterministic layout and scene generation in diagram-renderer.
Validated persisted Excalidraw output in diagram-excalidraw.
Generation guidance and candidate parsing.
Maintained scenarios and quality assertions.
Unit/functional tests and Storybook coverage.
No fallback to another diagram type when the requested contract is unsupported.
Acceptance criteria
This issue is groomed into one issue per selected diagram family or coherent family group.
Priority is based on product demand and implementation fit, not the deleted 23-type inventory.
Every shipped family satisfies the complete contract above.
Unsupported types fail explicitly and are not advertised.
Goal
Expand Sketchi v2 beyond its currently supported
flowchartandmindmapcontracts without restoring the legacy generic fallback behavior.Current state
packages/diagram-coreregistersflowchartandmindmapas explicit typed diagram families.tools/sketchi-generatorsdefines the intended extension path for new diagram families.Direction
Prioritize new diagram families from product demand and eval evidence. Each family should be a real contract with notation and layout semantics, not a display label over generic flowchart output.
Candidate sequence for grooming:
Definition of done for each family
diagram-core.diagram-renderer.diagram-excalidraw.Acceptance criteria
Current touchpoints
packages/diagram-core/src/diagram-types.tspackages/diagram-core/src/diagram-types/packages/diagram-renderer/src/packages/diagram-excalidraw/src/packages/diagram-generation/packages/diagram-scenarios/tools/sketchi-generators/src/generators/diagram-type/Rewritten after the Sketchi v2 replacement in #217. The old 19-of-23 inventory and fallback template map no longer exist.