spaday-studio

AI-native visual development environment for spaday

Overview

spaday-studio is a pilot AI-native visual development environment built on spaday's real component runtime. A structured project document is mirrored through transports; browser and MCP clients submit validated semantic edits; spaday applies the resulting tree diff without remounting unaffected elements.

The pilot includes:

• a selectable live application canvas with schema-driven property controls;
• opt-in installed component catalogs and component insertion;
• revision-checked insert, move, remove, and property operations;
• transactional MCP preview, commit, discard, inspection, and undo tools;
• atomic structured-project persistence and deterministic Python export;
• one transports-backed state shared by browser and agent clients;
• a Python+JavaScript Copier scaffold, Playwright coverage, and Yardang/Sphinx documentation.

Run the pilot

make develop
make build
spaday-studio --project orbit.studio.json

Open http://127.0.0.1:8020. Select the headline, change its text or style, and apply the edit. The browser receives the accepted document through transports and applies a spaday component-tree patch. Canonical edits are saved to orbit.studio.json. Use Export Python to download an ordinary spaday page() function for the accepted revision.

The MCP endpoint is http://127.0.0.1:8020/mcp. Start with the guided tutorial, connect an agent with the MCP how-to guide, save and export a project, use an installed component package, consult the API reference, or read why Studio uses a structured document.

Pilot boundaries

• One preview is shared by all clients; per-client drafts and collaboration are not implemented.
• Component insertion targets the selected component's default slot. Named-slot authoring is not yet exposed in the editor.
• Property schemas cover JSON-compatible constructor properties. Binding and action editors are not yet implemented.
• Component packages are selected when the server starts; the browser cannot activate a package live.
• Arbitrary handwritten Python is not losslessly round-tripped.
• Python export is one-way generated output; the structured JSON project remains the editable source.

[!NOTE] This library was generated using copier from the Base Python Project Template repository.