---
title: "Saas UI + Effectified TanStack Start fork of maestro-template"
url: https://stacklist.com/card/4665f5c4-5731-4300-9395-c9fe5cb9839e
source_url: "https://github.com/modernagencysales/maestro-template-saas-ui"
stack: https://stacklist.com/stack/c691055b-de15-47a1-ad6a-6c4ecec55f18
summary: "Maestro Template is a private internal framework for building custom AI brain, workflow, and context-engineering applications with reusable architecture components including workspace tenancy, contracts, workflows, and provider adapters. It serves as an internal accelerator for custom AI implementation work rather than a public starter kit, featuring a full-stack reference app with live Convex backend integration and deterministic CI/CD gates."
tags: "saas-ui, framework, ai-agents, workflow-engine, typescript, confect-effect, template"
key_entities: "Maestro Template (technology), Confect (technology), Effect (technology), Convex (technology), WorkOS (technology), Buildkite (technology), PostHog (technology), workspace-tenancy (concept), context-engineering (concept), provider-adapters (concept)"
classification: "framework"
content_hash: "sha256:ece45e6f2f8f966f0ec10430fc5e8c2b8f9f375087f98464e35ea0cfe47251f2"
acp_version: "0.2"
token_counts_approximate: 1137
visibility: public
agent_accessible: true
status: "final"
---

# Saas UI + Effectified TanStack Start fork of maestro-template

Maestro Template Maestro Template is a private internal framework for building custom AI brain, workflow, and context-engineering apps. It extracts the reusable Maestro architecture into a generic product factory: workspace tenancy, Confect/Effect contracts, workflows, capabilities, agents, Brain sources, headless surfaces, provider adapters, CI gates, and a reviewer-safe reference app. This is not a public starter kit. It is an internal accelerator for custom AI implementation work and technical diligence. Quickstart pnpm install pnpm review:readiness pnpm review:completion pnpm check:format pnpm lint pnpm typecheck pnpm test pnpm build review:readiness and review:completion are presence/evidence audits. They check required files and listed evidence paths; run pnpm verify for behavioral proof. Run the hostable reference app: pnpm --dir apps/web dev -- --port 5174 Open http://127.0.0.1:5174/ . Hosted reference app: https://maestro-template.pages.dev For a technical diligence path, start with docs/template/investor-reviewer-packet.md . The hosted app is a working full-stack deployment: the Workflows page streams live data from a deployed Convex backend, and every push to main runs the full Buildkite gate pipeline (deterministic gates, LLM review gates, staging deploy, gated production promote). Other providers (WorkOS, PostHog, Dodo, MailerSend, storage, LLM) default to fake/local adapters and are switched on per client fork. Design decisions Fresh reviewers tend to flag the same four things. Each one is a decision, not an accident: Auth is a seam, not a feature. The template ships fake-safe identity wiring (WorkOS-shaped) and a server-derived tenancy spine, but no live auth flow. Client forks choose their own provider; the template's job is to make that a contained swap instead of a rewrite. Some backend capabilities are contract fixtures. Domains that manage live data ( access , auth , brain , demo ) are database-backed. Domains that demonstrate contract shape ( ops/* , agents , capabilities , jobs ) return deterministic fixtures behind real typed specs. The spec, typed errors, and tests are the deliverable; a fork replaces fixture bodies with persistence. See AGENTS.md for the exact map. The live surface is deliberately thin. One seeded workspace and one live query prove the full path (static app → deployed backend → typed contract → UI). Everything else stays inert until a client fork gives it real data. A template that pretends to be a product ages badly. repos/ vendors Effect and Confect sources on purpose. AI coding agents produce measurably better changes with framework source in-tree. It is reference material, excluded from builds, lint, and scanning. How this repo was built — and why the commit history looks the way it does — is documented in docs/template/delivery-story.md . The fast receipt path is docs/template/delivery-receipts.md . Architecture web routes -> screens -> features -> blocks -> Saas UI/shared primitives client hooks -> @confect/react refs -> Confect specs -> Convex functions agents -> workflows -> capabilities -> domain/checks -> schema API/CLI/MCP -> headless registry -> same capabilities/workflows as web storage/notifications/observability -> Effect services -> provider adapters admin/support/privacy -> audited capabilities -> narrow operator surfaces Reference App Routes The reference app converges on these default surfaces: Home Brain Workflows Capabilities Agents Runs Documents Source Intake Integrations API Onboarding Data Map Notifications Settings Billing Analytics Health Admin/Support The default first screen is a plain Saas UI business dashboard. It demonstrates the intended frontend path with a live demo.showcase.overview Confect query, and /data-lifecycle demonstrates the fake-safe Confect query/mutation pattern that client forks should copy first. Verification Fast local verification: pnpm check:format && pnpm lint && pnpm typecheck && pnpm test && pnpm build Investor completion audit: pnpm review:completion Full verification after safety gates land: pnpm verify Navigation Agent instructions: AGENTS.md Repo map: docs/template/repo-map.md Reviewer guide: docs/template/reviewer-guide.md Investor reviewer packet: docs/template/investor-reviewer-packet.md Extraction policy: docs/template/extraction-redaction-guide.md Confect/Effect guide: docs/template/confect-effect-guide.md Golden path business slice: docs/template/golden-path-business-slice.md