For developers
Developers — build apps on Zeresoft
Clone VTC Cursor rules, sign in and create an app in your Space, scaffold locally, and deploy to apps.vtc.com with push-to-publish.
Cursor rule pack
Public repository — app authoring rules only. Copy into your project as .cursor/rules/ (never symlink; never commit .cursor/ to your app repo).
git clone https://git.vtc.com/zeresoft/vtc-app-rules.git ~/vtc-app-rulesgit clone git@git.vtc.com:zeresoft/vtc-app-rules.git ~/vtc-app-rules~/vtc-app-rules/scripts/copy-cursor-rules.sh /path/to/your-app- Open Cursor at your app folder root — one app per workspace.
- Ask Cursor to follow scaffold-checklist.mdc when scaffolding.
- Shared apps isolate data per Space; Dedicated apps use one publisher database.
- Pull rule updates periodically and re-run copy-cursor-rules.sh.
How it works
You build the app locally with Cursor. Zeresoft hosts it, injects auth and platform env at deploy, and serves it from your Space catalog.
- 1
Clone the Cursor rules
Clone the public vtc-app-rules repository (above). These are the standards our AI and build pipeline expect — auth, env files, app shell, i18n, and deploy layout.
- 2
Sign in to Zeresoft
Use an account with admin access to the Space where the app will live.
https://app.vtc.com - 3
Create the app in your Space
In the app dashboard, open your Space → Apps → Create. Set the app name, short name, Shared vs Dedicated deployment, and catalog visibility (Space, Network, or Platform).
- 4
Copy the Git remote
After the app is created, open its developer settings and copy the Git URL (SSH or HTTPS). That remote is where you push code — the platform builds and deploys on each push.
- 5
Scaffold locally in Cursor
Copy rules into your project folder, open that folder in Cursor (not a parent directory with many repos), and scaffold using scaffold-checklist.mdc. Point your local repo at the Git remote from step 4.
- 6
Push to publish
Commit and push to the app remote. The build service produces your image or static bundle and serves it on the publisher hostname — no manual deploy step.
Live URL pattern:
https://myapp.apps.vtc.com
Space MCP in Cursor
Connect Cursor (or Claude / VS Code) to a Space you already belong to. MCP is space-scoped — not a way to plug an external product database into Zeresoft.
- 1
Connect
Add https://mcp.vtc.com/mcp in Cursor Settings → MCP (config below). Click Connect — a browser opens for VTC login.
- 2
Sign in and pick a Space
Complete OTP in the popup, choose your Space, then return to Cursor. The client stores and refreshes tokens automatically.
- 3
Ask against that Space
Inspect Shared app data (list_collections → sample/find), catalog and manifests, Guide actions (list_available_actions → execute_action), or propose/run workflows. Mutations and real workflow runs require a confirmation_token shown to you first.
{
"mcpServers": {
"vtc-space-db": {
"type": "http",
"url": "https://mcp.vtc.com/mcp"
}
}
}Interactive clients use OAuth Connect (browser login + Space picker). Headless agents can pass a Developer Help admin JWT as Bearer instead.
- Same role gates and billing path as in-product Guide where applicable.
- CI / headless: generate an admin JWT in Developer Help and set Authorization: Bearer <jwt> in MCP headers.
- Never invent another group_id for DB tools — the silo is the JWT Space only.
What the rules cover
Auth & Spaces
JWT via ?token= from the shell, localStorage bootstrap, and group_id scoping for Shared apps.
UI & i18n
Standard app shell, Tailwind v4, runtime accent colors, and locale files from day one.
APIs & data
CRUD routes, soft delete, env-driven URLs, and @posif/sdk for tenanted production DB access.
Deploy
Committed .env.production for app-owned keys only; platform injects API URLs, MongoDB, and identity at build.
VTC Ledger
Permissioned, gasless EVM for immutable records, on-chain proofs, and wallet signing — integrate from apps when you need tamper-proof issuance.
Ready to build?
Clone the rules, create the app in your Space, and push when you are ready.