Creating Taubyte Resources

When to use

• "Add a domain / website / library / function / database / storage / messaging / service"
• "Create an application for app-scoped resources"
• Building out a project after bootstrapping-taubyte-projects
• Reviewing or scripting non-interactive resource creation

Intent-first resource planning (agent behavior)

When a user asks to "create an app" (not just a resource), first infer the minimum Taubyte resource set required to make that app real, then create those resources with correct scope + wiring.

General heuristics:

• Web app UI → create a website (project-scoped if needed or mentioned) + a domain (project-scoped if mentioned) and attach the site to the domain and path(s).
• Persistent data → create a database (application-scoped if needed). create storage if needed ; choose only when implied by the intent.
• UI ↔ data/API glue → create at least one HTTP function that reads/writes the database and returns JSON for the website to consume. Attach the function to the same domain when a same-origin /api/... pattern is implied.