Summary
Each node and edge detail panel gets a text input + "Copy prompt" button. The user writes what they want (free text), and the tool assembles a complete prompt with all the context an LLM needs to do it.
UX
─────────────────────────────────
🔧 Ask an LLM about this node
┌───────────────────────────────┐
│ Update to reflect v0.15 ... │
└───────────────────────────────┘
[Copy prompt]
─────────────────────────────────
The user provides intent. The tool provides context and process.
What "Copy prompt" assembles
- User's text — verbatim, as the task
- Current node/edge JSON — the data being discussed, plus connected edges
- JSON schemas — links to the schema files so the LLM knows the exact format:
schema/graph.schema.json (nodes and edges)
schema/config.schema.json
schema/tutorial.schema.json and schema/tutorial-index.schema.json (if touching tutorials)
- Source repo URL — from
config.sourceUrl, so the LLM knows where to file a PR
- File paths —
data/graph.json, data/config.json, data/tutorials/ structure
- PR instructions — how to fork, branch, edit the JSON, and submit
Key principle
The button is not "refresh this node." It's a context assembler — the user says what they want, the tool wraps it with everything needed for an LLM to execute and propose changes via PR.
Schema references
The schemas already exist in the repo:
schema/graph.schema.json
schema/config.schema.json
schema/tutorial.schema.json
schema/tutorial-index.schema.json
schema/manifest.schema.json
The generated prompt should link to these via the raw GitHub URL derived from config.sourceUrl (e.g. https://raw.githubusercontent.com/{owner}/{repo}/main/schema/graph.schema.json). If sourceUrl points to a graph-browser consumer repo (not graph-browser itself), the schema URLs should point to graph-browser's repo instead.
Works for any dataset
Nothing is hardcoded to a specific graph. The prompt is built from config.sourceUrl + the selected node/edge data + the schema URLs.
Summary
Each node and edge detail panel gets a text input + "Copy prompt" button. The user writes what they want (free text), and the tool assembles a complete prompt with all the context an LLM needs to do it.
UX
The user provides intent. The tool provides context and process.
What "Copy prompt" assembles
schema/graph.schema.json(nodes and edges)schema/config.schema.jsonschema/tutorial.schema.jsonandschema/tutorial-index.schema.json(if touching tutorials)config.sourceUrl, so the LLM knows where to file a PRdata/graph.json,data/config.json,data/tutorials/structureKey principle
The button is not "refresh this node." It's a context assembler — the user says what they want, the tool wraps it with everything needed for an LLM to execute and propose changes via PR.
Schema references
The schemas already exist in the repo:
schema/graph.schema.jsonschema/config.schema.jsonschema/tutorial.schema.jsonschema/tutorial-index.schema.jsonschema/manifest.schema.jsonThe generated prompt should link to these via the raw GitHub URL derived from
config.sourceUrl(e.g.https://raw.githubusercontent.com/{owner}/{repo}/main/schema/graph.schema.json). IfsourceUrlpoints to a graph-browser consumer repo (not graph-browser itself), the schema URLs should point to graph-browser's repo instead.Works for any dataset
Nothing is hardcoded to a specific graph. The prompt is built from
config.sourceUrl+ the selected node/edge data + the schema URLs.