U
Union Street AI Docs
Home
HomeAdd Api EndpointDb HealthFork Build DeployPromote DeploymentRelease CliRelease SdkRun Quality GatesSandboxed TasksSetup ProductWebhooks And Events

Fork Build Deploy

This is the top-level skill for the actual purpose of this repo:

  1. fork the template
  2. build the app
  3. deploy the app

Use this skill first when the user wants to create or ship a new product from Seed.

Philosophy

  • Keep the workflow simple.
  • Use high-level instructions first.
  • Only add scripts or mechanisms where failure is expensive or easy to miss.
  • Keep product-building decisions agentic.
  • Hard-fail the few paths that can silently break hosted environments.

Skill Web

This skill coordinates the lower-level repo skills:

  • setup-product
    • high-level orientation only
    • product bootstrap mindset
    • initial product shaping
  • run-quality-gates
    • local validation before pushing or promoting
  • db-health
    • migration discipline
    • Neon branch safety
    • preview branch DB workflow
  • promote-deployment
    • preview/staging/production release flow
    • Vercel/Neon parity checks
    • deploy smoke

Use this skill to decide the sequence. Use the lower-level skills when working that layer.

Canonical Workflow

  1. Fork or branch from Seed.
  2. Bootstrap product identity and initial config.
  3. Build the app:
    • schema
    • API
    • UI
    • CLI/SDK/MCP only if the product needs them
  4. Generate and commit migrations locally.
  5. Run quality gates locally.
  6. Push the branch.
  7. Wait for the Vercel preview deployment to exist and become usable.
  8. Validate the live preview URL first.
  9. If direct DB access is still needed, use:
    • vercel env pull to discover branch wiring
    • neonctl for the actual DB access path
  10. Promote through staging and then main.
  11. Run deploy smoke against hosted environments before calling the app shipped.

Hard Rules

  • bun run db:push is banned in this repo.
  • Never use drizzle-kit push for hosted preview, staging, or main.
  • Let remote Vercel deploys apply hosted migrations.
  • Prefer live preview validation over local-only DB validation.
  • Treat env parity failures, deploy smoke failures, and stale CLI artifact failures as hard blockers.

Repo Identity

This repo is not the idea engine and not the GTM engine.

This repo exists to help agents:

  • fork the template
  • build the product
  • deploy the product

Anything outside that loop should usually live elsewhere.