Taubyte Core Rules

Use this skill together with taubyte-reference-docs for command flags and SDK details.

When to use

Creating or modifying Taubyte projects, functions, websites, databases, storage, Dream deployments, or multiverse resources.
Before running tau, dream, or changing generated config.

Do not ask the user to run setup commands manually — automate setup.
For Dream/local: ensure Dream is running and the default universe exists before backend tau calls; use dream commands directly, not tau dream.
After resource changes: tau push project --config-only; after code changes: tau push project --code-only and verify builds.
Use tau new with full flags; use --template empty for functions and websites (Go: add --language Go with empty template).
One HTTP method per function — never comma-separated methods on one function.
Use matcher values from config for database/storage in code, not resource filenames.
Code layout: <app_name>/functions/<name>/ at the code repo root (not only under applications/).
Do not use raw git to work around tau failures — fix the underlying issue.