seeflowlisted

# seeflow Turn a natural-language prompt into a registered SeeFlow flow at `$repoPath/flows/<flowSlug>/flow.json` (skill-created projects default to `flowSlug: 'main'`), with node-attached content (scripts, detail.md, view.html) under `$repoPath/flows/<flowSlug>/nodes/<id>/`. Orchestrate five sub-agents and the `seeflow` CLI; never read the codebase directly, never author `seeflow.json` or `flow.json` by hand (`projects:create` writes both the manifest and the first flow envelope). ## When NOT to invoke - Editing nodes on an existing flow → use the canvas, or hit the CLI directly (`nodes:patch`). - Deleting a flow → `flows:delete`. - Re-laying out an existing flow without semantic changes → `flows:layout`. - Debugging a single broken Play/Status script → edit in-place, re-run Phase 6. (A project with no source tree is **not** an exclusion — it routes to the `document` branch at the Phase 0 input-source gate without asking.) ## Project layout convention A host repo opts into seeflow by creating a `<host>/.seeflow/` directory (the **only** place this skill introduces a `.seeflow` folder — the studio itself is path-agnostic). `LEARN.md` is shared across every project and flow in the host and lives at `<host>/.seeflow/LEARN.md`; each project lives in its own subdirectory beside it, with one folder per flow nested inside under `flows/`: ``` <host>/ ← the user's repo .seeflow/ ← container, created by this skill