taubyte-core-constraints

Original：🇺🇸 English

Translated

Non-negotiable Taubyte constraints that prevent config/build/runtime failures.

2installs

Sourcetaubyte/skills

Added on2026-04-27

NPX Install

npx skill4agent add taubyte/skills taubyte-core-constraints

SKILL.md Content

View Translation Comparison →

Core Constraints

Must-follow rules

Never ask user to run setup commands manually; agent performs setup.
Run CLI preflight (
```
taubyte-cli-prereqs
```
) before all Taubyte operations.
For Dream/local, never run backend-contacting
```
tau
```
commands before Dream is up and universe exists.
Use
```
dream
```
commands directly; never use
```
tau dream
```
.
Use default universe
```
default
```
unless user explicitly requests another.
After resource creation, push config (
```
tau push project --config-only
```
) before relying on resource visibility.
After code changes, push code (
```
tau push project --code-only
```
) and verify builds/logs.
Never set function timeout to
```
0
```
; use valid durations (
```
30s
```
,
```
1m
```
, etc.).
HTTP functions: one function per path+method; never comma-separated methods.
For functions/websites in automation, use empty template; for Go functions, include
```
--language Go
```
.
Use matcher values for DB/storage SDK calls, not resource names.
Do not bypass failing
```
tau push project
```
with direct git operations.
On Git Bash Windows for path-like flags, prefix with
```
MSYS_NO_PATHCONV=1
```
.
Website
```
.taubyte/build.sh
```
must be non-empty and must write deploy output to
```
/out
```
.
Verify project selection with
```
tau --json current
```
before resource mutations.
Website/library git fallback is an exception path only when
```
tau push website|library
```
is unavailable; never apply this exception to project config/code pushes.
Never create website/library without explicit repository strategy:
- use
```
--generate-repository
```
  with deterministic
```
--repository-name
```
  , or
- use explicit existing
```
--repository-name
```
  /
```
--repository-id
```
  .
After creating website/library, verify repository binding in config (
```
websites/*.yaml
```
or
```
libraries/*.yaml
```
) before pushing.

Layout constraints

Project has
```
tb_config_<name>
```
+
```
tb_code_<name>
```
.
Website/library have separate repositories.
Function build layout must be discoverable by build system (avoid misplaced function paths).

taubyte-core-constraints

NPX Install

Tags

SKILL.md Content

Core Constraints

Must-follow rules

Layout constraints