Skip to content

🚀 Start an App

This is the entry point for building a new application from the blueprint. The goal is one deterministic pass: you supply only the two axes, and the agent does the rest by reading the standards MCP, importing Tier A libraries, and copying Tier B template components.

Doc model: this page is the human entry point. The deterministic, machine-facing checklist lives in the reference page Build Recipe, served as doc://modules/build_recipe.

🧾 What the agent needs from you

Gather these before starting — the start_app MCP prompt asks for them:

  1. App name + one-line purpose.
  2. Axis 1 — resources. Each resource, its fields, and relationships. Paste openapi.yaml if you already have it.
  3. Axis 2 — pipelines. Only if an input needs a multi-step transformation: the families and their input formats (or "none").
  4. Auth needed now? Default no; auth is deferred (py-jwt only).
  5. Integrations. Mongo, ingestion formats, email, LLM provider.

If you can state axes 1 and 2, the rest is mechanical.

▶️ How to start

From an MCP client connected to the standards server:

  1. Invoke the start_app prompt with no arguments to get the intake questions.
  2. Answer them, then invoke start_app(app_name=..., resources=..., pipelines=..., auth=...).
  3. The prompt hands off to doc://modules/build_recipe; the agent pulls exact files with get_app_component(kind, resource=..., family=...) and authors only the app-specific parts.

Manual alternative — copy the skeleton and follow the reference recipe:

1
cp -r <docs>/standards/src/templates/app apps/<your-app>

📚 Reference