Scaffold from a manifest
Pick a name, an icon, a scope, and the capabilities your Space needs. SpaceKit generates the boilerplate, the routes, the Operator config.
Built in · Personal
SpaceKit. Build a Space.
The Space we use to build every other Space — including itself. Scaffold, edit, preview, publish. Same SDK as yours, same Operator, same OS. If it ships the platform, it can ship your workflow.
Screenshot needed
The SpaceKit Space inside Construct. Left rail: Manifest, Code, Preview, Publish. Center: a manifest.json being edited with capability hints inline. Right: a live preview of the new Space rendering in a sibling window. Bottom: a status strip showing 'manifest valid · build ok · ready to publish'. Boxes icon in the header.
/shots/space-spacekit.pngWhat it does
Six things SpaceKit handles for you.
Edit with the SDK in reach
Code in Monaco, jump to SDK definitions, see capability hints inline. The agent knows the @construct-space/sdk surface.
Live preview, in another Space
Hot-reload the new Space in a sibling window. Real OS, real identity, real Operator — not a sandboxed lie.
Manifest validation as you type
Bad capability declaration, missing route, conflicting scope — caught while typing, not at publish time.
Publish where it belongs
Public marketplace, private to your org, scoped to a single project. One command, three audiences.
The same loop, recursive
SpaceKit was built with SpaceKit. The autonomous coding loop that ships your Space is the same one we use to ship the platform.
In practice
Three Spaces already built this way.
Internal tool for one team
Your team has a workflow nobody built software for. Scaffold, fit it, ship privately to the org. Done in an afternoon.
Marketplace publish
Build a Space worth selling. SpaceKit handles the manifest, the signing, the listing flow. You handle the idea.
A Space that wraps an API
Your favorite SaaS has an API but no UI you actually want. Wrap it in a Space — SpaceKit gets you 80% there before you write the second prompt.