Connected projects & lineage
A project is a system, not a single drawing. Skeema keeps the root architecture and everything derived from it linked — so your ER schema, flows, and code never drift away from the design.
The project model
Creating a project gives you a root architecture board. From there you derive other boards, and the project page organizes them into three sections: the root, the flows(sequences), and the derived views (ER, code). Everything about one system lives in one place.
Deriving views from a node
Hover any node and a contextual action strip appears — but only with the actions that node supports. Skeema infers each node’s capabilities from its label and tech (schema, cache, queue, stream, compute, gateway…) and offers only the relevant derivations:
- •A
databasenode → derive an ER diagram or schema code. - •A
servicenode → derive API routes. - •A set of services in a flow → derive a sequence diagram.
Lineage & drift
Every derived board records its parent board and source node. Skeema computes a lineage statusfor each: linked, orphaned (source node deleted), parent_deleted, or standalone. When a source disappears, the derived board shows a banner — amber for an orphan, rose for a deleted parent — with a link back to the project. Nothing breaks silently.
Project documentation
One click reads the root architecture, the ER boards, and the flows, and generates a structured Markdown document — overview, architecture (component table), data model, flows, integrations, and technical notes. Copy or download docs.md, and regenerate whenever the system changes.
- ✓A project bundles a root architecture with its derived ER, sequence, and code boards.
- ✓Derivation menus show only the actions a node’s capabilities support.
- ✓Lineage tracks where every view came from; drift surfaces as a banner, never a silent break.
- ✓Generate full project documentation as Markdown in one click.