Embedded Builder Skills
The Tier0 Builder Skills repository currently contains 6 skills for requirements, app building, platform alignment, browser capabilities, responsive design, and preview troubleshooting. This page follows its feature/cloud-new-architecture-migration branch.
app-srs
Section titled “app-srs”Meaning: The requirements-analysis entry point for industrial-enterprise apps. It creates an SRS from a request, converts a PRD, or revises an existing SRS.
Example:
Use $app-srs to design a quality exception management system for an automotive parts factory.What it does:
- Maps business roles, workflows, states, validations, and exceptions.
- Defines a bounded first release with visible, usable commitments.
- Saves the complete SRS to
specs/spec.mdby default. - Continues to
app-builderfor a first-time app unless the user asks for requirements only or clarification is needed.
app-builder
Section titled “app-builder”Meaning: Builds a runnable app or substantially extends an existing app from requirements or specs/spec.md.
Example:
Use $app-builder to build the first version from specs/spec.md.Work modes:
- First release: Builds the bounded first version; creates an SRS with
app-srsfirst if needed. - Substantial extension: Adds a business module or workflow while preserving existing behavior.
Ordinary field, copy, style, and isolated UI repairs do not require the full Builder workflow.
What it checks:
- Discoverable entry points and executable user paths for committed capabilities.
- Real data and state changes, validation, and role permissions.
- Build, preview, and interactive workflow evidence.
For list-type pages, it uses the target scaffold’s MetaListPage when suitable and connects it to real services and permissions.
align-platform-app
Section titled “align-platform-app”Meaning: Migrates an imported app to the Tier0 scaffold or aligns an existing Tier0 app with the current scaffold contract.
Example:
Use $align-platform-app to align this app to the latest Tier0 scaffold while keeping its business code.Suitable sources:
- Imported applications and older Tier0 apps.
- Apps with app-owned SQL databases, browser storage, or mock business persistence.
- Existing scaffold apps that need a full update or a scoped platform repair.
What it does:
- Compares the app against an exact commit of the cloud architecture scaffold.
- Preserves business behavior while aligning runtime, routing, Gateway roles, and platform contracts.
- For a full cloud migration, moves app-owned durable records to Tier0 UNS tables through
@tier0/sdk-v2; historical records from the original database require a separate UNS-side import when needed. - Verifies the changed build and runtime behavior before writing the scaffold version marker in
package.json.
browser-platform-capabilities
Section titled “browser-platform-capabilities”Meaning: Guides browser interactions for QR/barcode scanning, photo capture, geolocation, audio recording, file reading, and clipboard access.
Example:
Use $browser-platform-capabilities to add photo capture with a file-upload fallback to an inspection form.What it does:
- Chooses browser APIs and fallbacks for the target device and container.
- Checks secure contexts, permissions, and iframe or WebView restrictions.
- Preserves form input on cancellation or failure and labels fallback data when its meaning differs from live capture.
- Verifies success, denial, retry, and cleanup for the implemented capability.
responsive-craft
Section titled “responsive-craft”Meaning: Handles complex breakpoint decisions, coordinated sticky and scroll regions, and multi-viewport audits or previews. Isolated overflow and clipped controls can be repaired directly.
Invocation modes:
- audit: Audits and repairs an existing responsive layout.
- build: Builds a responsive page from scratch.
- preview: Starts a multi-breakpoint live preview.
Examples:
Use $responsive-craft audit to fix the mobile layout of this dashboard.Use $responsive-craft preview to show 375, 768, 1024, and 1440 px breakpoints.preview-runtime-stability
Section titled “preview-runtime-stability”Meaning: Diagnoses managed preview installation, startup, readiness, role, port, and HMR failures. It does not build business features.
Example:
Use $preview-runtime-stability to diagnose "Preview loading timed out".Suitable issues:
- Missing dependencies, npm
ERESOLVE, or lockfile errors. - Vite or TanStack Start startup failures and port
5173conflicts. /api/healthfailures, preview role errors, orartifact.tomlmismatches.- Frequent full-page reloads during HMR and stale app-owned preview processes.
Standard flow:
- Read the first relevant install or preview error.
- Fix the evidenced cause in the app or use the managed preview control for runtime issues.
- Restart only when needed and verify the original failure, health, and affected route.
Skill Selection Guide
Section titled “Skill Selection Guide”- Use
app-srsto create or revise requirements; it normally hands a new app toapp-builder. - Use
app-builderfor a first release or substantial business extension. - Use
align-platform-appfor migration or scaffold alignment. - Use
browser-platform-capabilitieswhen an app needs one of its six browser capabilities. - Use
responsive-craftfor complex responsive work, andpreview-runtime-stabilityfor managed preview failures.