Skip to content

Export manual

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.

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:

Terminal window
Use $app-srs to design a quality exception management system for an automotive parts factory.

What it does:

  1. Maps business roles, workflows, states, validations, and exceptions.
  2. Defines a bounded first release with visible, usable commitments.
  3. Saves the complete SRS to specs/spec.md by default.
  4. Continues to app-builder for a first-time app unless the user asks for requirements only or clarification is needed.

Meaning: Builds a runnable app or substantially extends an existing app from requirements or specs/spec.md.

Example:

Terminal window
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-srs first 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.

Meaning: Migrates an imported app to the Tier0 scaffold or aligns an existing Tier0 app with the current scaffold contract.

Example:

Terminal window
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.

Meaning: Guides browser interactions for QR/barcode scanning, photo capture, geolocation, audio recording, file reading, and clipboard access.

Example:

Terminal window
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.

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:

Terminal window
Use $responsive-craft audit to fix the mobile layout of this dashboard.
Terminal window
Use $responsive-craft preview to show 375, 768, 1024, and 1440 px breakpoints.

Meaning: Diagnoses managed preview installation, startup, readiness, role, port, and HMR failures. It does not build business features.

Example:

Terminal window
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 5173 conflicts.
  • /api/health failures, preview role errors, or artifact.toml mismatches.
  • Frequent full-page reloads during HMR and stale app-owned preview processes.

Standard flow:

  1. Read the first relevant install or preview error.
  2. Fix the evidenced cause in the app or use the managed preview control for runtime issues.
  3. Restart only when needed and verify the original failure, health, and affected route.
  • Use app-srs to create or revise requirements; it normally hands a new app to app-builder.
  • Use app-builder for a first release or substantial business extension.
  • Use align-platform-app for migration or scaffold alignment.
  • Use browser-platform-capabilities when an app needs one of its six browser capabilities.
  • Use responsive-craft for complex responsive work, and preview-runtime-stability for managed preview failures.