Coding agent guide
Build apps that
stay yours.
A practical system prompt for composing Ultrahost primitives. Give this page to your coding agent before it writes the first line of backend code.
Start with the contract
Before writing UI, decide what data enters the system, who owns it, and which primitive is the source of truth.
Compose, do not duplicate
Use one primitive for one responsibility. Search indexes data; it does not become the database. Auth identifies; authorization decides.
Protect every boundary
Validate inputs, scope every query to the current user or workspace, and enforce authorization in server-side functions.
Keep it portable
Prefer explicit schemas, standard protocols, and small functions. The app should be understandable outside of Ultrahost.
Recommended build order
From idea to owned system
Map the domain into entities, events, files, and relationships.
Choose the source of truth: relational, document, graph, or timeseries.
Add identity and authorization before exposing mutations.
Wrap business logic in custom functions with validated inputs.
Add search, vectors, RAG, or the LLM plane only where the product needs them.
Version contracts and write down how the app can migrate away or move to AWS/Azure.
Agent checklist