Agent toolkit

Most Foundation apps are built by an agent, not by hand. This is what you point your agent at — the workflow, references, and starter prompt that let it build your app correctly.

Point your agent at the docs

Every page here has a clean Markdown version (add .md to any URL), plus a bundle for ingest:

Resource	URL
App builder workflow	https://docs.foundationmvp.com/agents/foundation-app-builder.md
SDK reference	https://docs.foundationmvp.com/agents/foundation-sdk-reference.md
Deploy contract	https://docs.foundationmvp.com/agents/foundation-deploy-contract.md
Everything (one file)	https://docs.foundationmvp.com/llms-full.txt

Starter prompt

Paste this into your agent and fill in the blanks:

Use https://docs.foundationmvp.com/agents/foundation-app-builder.md to build a production-ready
frontend app that consumes the Foundation backend.

App goal:
Framework and router:
Styling system:
Auth provider: Cognito or Auth0
Foundation config URL for local development:
Foundation tenant ID for local development:
Foundation app ID for local development:
Optional local API proxy base URL:
Entities to use through foundation.db:
File workflows to support through foundation.files:
Integrations to support through foundation.integration:
Account/profile fields:
Deployment output directory:
Deployment entry file:

What the agent will do

Given those docs, your agent installs foundation-sdk, sets up one SDK initialization, builds login / registration / guarded routes, implements your data and file workflows, adds mvp.config.json, and checks the app is deploy-ready — following the app builder workflow.

Reference

• Set up the SDK · Deploy your app
• Agent Docs — how these agent docs are served