Curated file collections to hand to Claude Design for generating UIs that expose [&] Protocol backend functionality through the web.
Claude Design works best with narrow, self-contained context. Feeding the whole 100k-file monorepo dilutes the signal. Each bundle below is ~10-20 files, covers one scope, and includes cover notes explaining intent.
| Bundle | Scope | What it generates |
|---|---|---|
webhost-systems/ | The unified operator dashboard | Single React/Vite SPA that exposes every product's MCP surface under one nav, one auth, one theme |
runefort/ | Spatial memory-graph visualizer | SvelteKit canvas UI rendering Graphonomous + body-* traces as a navigable 3D space |
_shared/ | Cross-cutting context | Protocol spec, nav component, palette — referenced by both bundles |
For each bundle:
Zip the bundle: tar -czf webhost-systems.tar.gz claude-design-bundles/webhost-systems/ claude-design-bundles/_shared/
Upload to Claude Design as the project context
Paste the bundle's COVER.md into the first prompt as the brief
Iterate from there
Shared context is included in both bundles. Unzip twice and dedupe if that's wasteful.
WebHost.Systems is already started (React SPA, Supabase auth). Its master spec calls for it to be the meta-platform aggregating every product. Today it's a shell — Claude Design should flesh out the dashboards that expose FleetPrompt / Agentelic / SpecPrompt / Graphonomous / Delegatic / PRISM / body-* MCP tools as first-class web pages.
RuneFort is specced as the spatial-cognition visualization layer. Its mission is to make Graphonomous memory graphs + body-* traces visible. A 3D-ish SvelteKit SPA is the natural form.
Both are greenfield enough that Claude Design has room to design, but grounded by existing specs (1087 + 131 lines respectively) so it won't invent products.
Per-product Studio UIs (Agentelic Studio, SpecPrompt editor, FleetPrompt publisher) — these should ship as sections inside WebHost.Systems rather than separate deployments. Keeping only two UI buildouts keeps the operator nav singular.
Graphonomous / Delegatic / body-* dashboards — same reason; they're sections inside either WebHost.Systems (ops) or RuneFort (viz).
Each bundle directory is a manifest + symlinks to source files in the repo. If you update the source, the bundle auto-reflects on next tar. Run ./build.sh in each bundle dir to refresh.