Project Contracts: the decisions your agent never forgets
Product
What is a Project Contract?
A Project Contract is a short, structured record of the decisions that shape your product: frontend, database, accounts, billing, deployment and the rules you never want broken.
What goes inside
Keep it small and factual. If a decision would change how code is written, it belongs in the contract.
Stack and services
Which framework, database, payment provider and host you use, so agents stop proposing alternatives.
Permanent rules
Statements such as “billing belongs to the team” or “production changes require approval” that every agent must follow.
How agents use it
Before starting work an agent loads the contract, asks only about decisions that are still open, and writes the answers back so the next conversation starts further ahead.
Share this article
Related posts
Start shipping with Convio
Connect one MCP endpoint, load your Project Contract and run your first pipeline in the sandbox.
Add authentication to the app.
Loading what I already know about this project.
get_project_context
Contract loaded · 0.4s
search_skills(“authentication”)
2 skills found
activate_skill(auth-supabase)
Activated
Your project uses Supabase and team accounts. Two decisions remain: how people sign in, and whether people can join multiple teams.
request_approval(deploy: production)
Needs you
Describe what you want to ship. Type @ for tools and / for pipelines.
