Svelte Flow Showcase
Open Svelte Flow Showcase to explore a graph playground and focused interactive demos. This wiki describes the app’s graph contracts, practical editing recipes, and the boundary between an assistant suggestion and an applied graph change.
The assistant is local and deterministic by default. Treat a proposed action as a suggestion, not evidence that the graph has changed. The application and validation controls remain the authority for the current graph; see assistant for the assistant’s exact workflow and limits.
Choose a starting point
- concepts explains graph data, node kinds, handles, layout, and structured validation.
- recipes gives concrete prompts and editing instructions, with stable anchors used by assistant knowledge-base links.
- demos documents the authored demos and the interactions each demonstrates.
- assistant explains local answers, proposals, explicit application, and safety boundaries.
- operations covers development, the production service, and publication of this wiki.
Two kinds of exploration
Use the graph playground to compose a workflow and examine its structure. Use a focused demo to isolate an interaction, layout, rendering, or scale behavior without confusing that demonstration with the workflow model.
flowchart LR App["Svelte Flow Showcase"] --> Playground["Graph playground"] App --> Demos["Focused demos"] Playground --> Recipes["Editing recipes"] Playground --> Assistant["Local assistant"] Recipes --> Concepts["Graph contracts"] Assistant --> Concepts
Reading this guide
A recipe’s prompt is an input to the assistant, not a script that runs automatically. Some requests produce graph-edit proposals; others provide guidance or point to a demo. Read the proposed change before applying it, then inspect the resulting graph and validation output.
These pages describe application behavior from the repository, not a claim that a production deployment has passed verification. Deployment and verification procedures are recorded in operations.