2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| pocketbase-microapp-builder | Use when creating or updating regulated microapps that must run on the PocketBase plus Deno gVisor platform. This skill scaffolds only from the approved template, validates the repo contract, and prepares control-plane metadata for delivery. |
PocketBase Microapp Builder
Build only template-compliant microapps for the internal PocketBase + Deno + gVisor platform.
When to use
Use this skill when the user asks to:
- create a new regulated microapp;
- update an existing microapp that must stay inside the allowed platform contract;
- prepare a repo for preview/prod delivery on the microapp platform.
Do not use this skill for arbitrary apps, unrestricted package installation, or custom runtime wiring outside the approved platform.
Approved platform contract
- Template source:
../../microapps/templates/pocketbase-deno-dashboard - Validator:
../../microapps/validator/validate_microapp_repo.ts - Runtime image:
../../microapps/runtime/Dockerfile - Control-plane persistence:
../../backend/src/microapps/service.ts
The app must keep:
app.config.tsdeno.jsonmain.tspocketbase/client.ts
Only the approved top-level entries are allowed.
Workflow
- Copy the template from
../../microapps/templates/pocketbase-deno-dashboard. - Edit only the app name, slug, collection names, UI copy, and business logic that still fits the template.
- Keep runtime as
deno-gvisor. - Keep PocketBase access through the local wrapper in
pocketbase/client.ts. - Run:
deno run --allow-read ../../microapps/validator/validate_microapp_repo.ts <app-dir>
- Prepare control-plane metadata:
- repository path
- branch
- PocketBase URL
- PocketBase instance id
- preview/prod domains
- allowed hosts/env keys/libraries
Delivery expectations
- Preview should be created from a validated repo version.
- Production should be promoted from a previously validated version.
- Rollback should target a previous deployment record instead of ad hoc hotfixing in runtime.