flowstate-app-flowchart Package Skill

Package: @epicdm/flowstate-app-flowchart Repository: epic-flowstate-apps Path: packages/flowstate-app-flowchart Version: 1.0.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

Flowchart Editor

Status: Active
Purpose: Guide editor and persistence changes without overstating current implementation.
Scope: FlowEditor, useFlowSync, useFlowTabs, node components, and types.ts.
Trigger: A task changes canvas behavior, node definitions, palette actions, edges, viewport, tabs, or flow persistence.
Input: Target editor behavior.
Output: Editor change aligned with React Flow and current app boundaries.

Workflow

1. Start in src/components/FlowEditor.tsx. It owns ReactFlow, nodeTypes, Background, Controls, MiniMap, and NodePalette.
2. If adding a node type, update all three places: src/types.ts, the node component under src/components/nodes, and the nodeTypes map in FlowEditor.
3. For tab behavior, edit src/hooks/useFlowTabs.ts. Preserve max tab count of 10 unless the product change requires otherwise.
4. For persistence, implement src/hooks/useFlowSync.ts; it is currently a stub returning empty nodes/edges and TODO callbacks.
5. Do not claim autosave or manual save works until useFlowSync and toolbar save behavior persist data.

Verification

yarn workspace @epicdm/flowstate-app-flowchart build

For visual/editor changes, run the app and inspect a canvas with at least one node and edge.

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-app-flowchart

Composition

Use the orchestrator for shell-level work. Use editor for canvas and persistence tasks. Use examples for static diagrams and viewer tasks.

Review Gate

Review: @epicdm/flowstate-app-flowchart Skills

Status: Passed for local package use
Reviewed: 2026-06-30

Checks

Residual Risk

Persistence and node creation are currently stubbed. Future skills or implementation work should update these notes once useFlowSync and handleAddNode are real.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-app-flowchart/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.