taubyte

@taubyte source repo

22 skills
0 followers
10 hours ago last updated

▌
Starting Dream Locally · taubyte
Starts a Dream local Taubyte cloud (multiverse) using either the newer `dream start` workflow or the older `dream new multiverse` workflow, and explains the default universe naming (`default` for `dream start`, `blackhole` for `dream new multiverse`). Use when bringing up, restarting, or daemonizing a local Dream cloud, or when `dream --help` shows a different shape than expected.

0
installs
▌
Diagnosing Dream Builds · taubyte
Diagnoses Dream local-cloud builds when `tau list/query builds` is empty or unreliable, by hitting the jobs HTTP endpoint directly (`GET /jobs/<project_id>`, `GET /job/<job_id>`) using the GitHub token from `~/tau.yaml`, then downloading logs with `tau query logs --jid`. Use when Dream builds appear silent, the build table is empty after `dream inject`, or you need raw job ids and logs for a failing build.

0
installs
▌
Inspecting Dream Status · taubyte
Inspects a running Dream local cloud — verifies a universe is up, discovers gateway/substrate ports and URLs, and explains the wrong-universe failure mode. Use when probing Dream readiness, finding the gateway port for HTTP function tests, debugging `universe does not exist`, or confirming Dream is reachable before running `tau` or `dream inject`.

0
installs
▌
Triggering Dream Builds · taubyte
Triggers builds on a Dream local cloud after a GitHub push by simulating the webhook with `dream inject`. Encodes the first-run bootstrap rule (`push-all` once before `push-specific` will work reliably) and the flag-ordering gotcha for website/library repos. Use when a Dream local cloud isn't building after `git push`, when bootstrapping a freshly imported project, or when a website/library push fails with `Required flags repository-id, repository-fullname not set`.

0
installs
▌
Pushing Taubyte Projects · taubyte
Pushes Taubyte project changes via `tau push` — `tau push project [--config-only|--code-only]`, `tau push website <name>`, and `tau push library <name>` — with the rule that `--message` is required when `--defaults` is set, and the push-config-before-code ordering for resource-dependent changes. Also explains the `tau pull` "already up-to-date" non-zero-exit quirk. Use when pushing local changes to GitHub through `tau` (instead of raw `git push`), or when triggering remote-cloud webhooks / Dream injects after edits.

0
installs
▌
Building Taubyte Websites · taubyte
Authors a Taubyte website's `.taubyte/build.sh` so the cloud can serve it — the deploy output **must** be written to `/out`. Provides the minimal known-good static-HTML build script and the recommended `html` template baseline (or copying it into an existing site repo). Use when creating a website's build script for the first time, when a website builds but doesn't serve, or when migrating a site between Taubyte template baselines.

0
installs
▌
Editing Taubyte Resources · taubyte
Edits and deletes Taubyte resources via `tau edit <kind> <name> [flags]` and `tau delete <kind> <name>` (covering domain, website, library, function, application, database, storage, messaging, service, smartops). Encodes the rule that domain mutations must go through the CLI (never hand-edited YAML), the `tau edit` non-interactive gotcha (some commands prompt for required list flags like `--paths` even with `--defaults --yes`), and the post-edit push + Dream inject sequence. Use when changing a resource's settings (paths/methods/match/min-max/description/tags) or removing a resource cleanly without leaving stale references.

0
installs
▌
Selecting Taubyte Context · taubyte
Keeps `tau` pointing at the right cloud and project before any mutation — `tau current` / `tau --json current`, `tau select cloud --universe|--fqdn`, `tau select project`, and the `tau clear project` + reselect recovery. Encodes the "projects are per cloud" rule and the `unknown cloud` recovery. Use before any `tau push`, `tau delete`, `dream inject`, or resource creation, and whenever `tau` appears to operate on the wrong project.

0
installs
▌
Writing Taubyte Functions · taubyte
Authoring guide for the Taubyte Go SDK (`github.com/taubyte/go-sdk`) — covers the function signature, `event.Event` dispatch (HTTP / PubSub / P2P), and the SDK packages for HTTP request/response, outbound HTTP client, KV database, object storage, PubSub publish/subscribe + WebSocket URLs, P2P services, and IPFS files; includes the cross-library `//go:wasmimport` pattern, the YAML-to-Go matcher consistency rule, the body-then-Return ordering rule, and a complete handler skeleton. Use when writing or reviewing any Go function/library source for a Taubyte serverless workload.

0
installs
▌
Authenticating Taubyte CLI · taubyte
Authenticates the `tau` CLI to GitHub — token-based login (preferred for automation), browser OAuth fallback (`tau login --new`), and recovery from `GET /me 401`. Also explains how to retrieve the GitHub token stored in `~/tau.yaml` for direct HTTP calls. Use on first-time setup, when `tau` returns 401 Unauthorized, before any `tau new project` / `tau import` / `tau push`, or when a script needs the token to call Dream HTTP endpoints.

0
installs
▌
Creating Taubyte Resources · taubyte
Creates Taubyte resources non-interactively via `tau new` for domain, website, library, function, application, database, storage, messaging, and service. Encodes the project-vs-application scope rule, the database `min < max` constraint, the website/library `--generate-repository` + import sequence, and the forbidden `--generated-fqdn-prefix` flag. Use when adding any resource to a Taubyte project's config repo.

0
installs
▌
Deploy Taubyte Spore Drive · taubyte
Guides deployment of a self-hosted Taubyte (Tau) cloud using the spore-drive-boilerplate (clone, hosts.csv, .env, npm install, npm run displace) and explains manual DNS records when Namecheap API vars are omitted. Use when the user wants to deploy Taubyte on their own servers with Spore Drive, AI-assisted setup of spore-drive-boilerplate, or post-deploy DNS for tau/seer/generated domains.

0
installs
▌
Deploying To Remote Clouds · taubyte
Deploys to a real (non-Dream) Taubyte cloud — selects the cloud by FQDN with `tau select cloud --fqdn <fqdn>`, registers projects with `tau import project` when missing on that cloud, pushes via `tau push project`, and distinguishes **code** builds from **website** builds (`tau push website`, `AssetCid`). Covers project-id alignment, replacing Dream `*.default.localtau` with remote-suitable FQDNs, `*.gen.<cloud>` CID-suffix naming on some hosts, and verification with `tau query builds/logs`. No `dream inject` on remote. Use when targeting a remote cloud or diagnosing "API works, GET / fails".

0
installs
▌
Installing Taubyte Tooling · taubyte
Installs and verifies the prerequisites for any Taubyte workflow — Node.js, Docker (engine + running daemon), `@taubyte/cli` (the `tau` command), and `@taubyte/dream` (the `dream` command). Acts as a hard gate that runs before every other Taubyte skill, with OS-specific automated installs (winget / brew / apt-get) and explicit stop conditions when an install fails. Use on first-time machine setup, when `tau` or `dream` is missing or broken, when `docker info` fails, or when starting a fresh shell and you don't know if the toolchain is ready.

0
installs
▌
Taubyte Always Follow Rules · taubyte
Non-negotiable Taubyte workflow rules for agents—use `tau` for resources, never invent layouts, choose one build strategy (inline vs library), keep scopes correct, and follow push/inject ordering. Read this FIRST before acting on any Taubyte request.

0
installs
▌
Verifying Taubyte Functions · taubyte
Verifies a Taubyte Go function locally via the `taubyte/go-wasi` Docker recipe (preferred over `tau build`, with tmpfs+bind-mount-ro to avoid root-owned artifacts in the source tree), and verifies a function actually serves on Dream by curling the gateway with the right `Host:` header (plus `/etc/hosts` mapping for `*.localtau`). Use when locally compiling a Go function to WASM, when smoke-testing a function before pushing, or when probing a Dream-hosted HTTP function from the laptop.

0
installs
▌
Enforcing Taubyte Constraints · taubyte
Numbered catalog of the non-negotiable Taubyte rules — naming, push ordering, domain CLI-management, matcher consistency, function layout, build/runtime env placement, and Dream vs remote build triggers — with one-line statements and cross-links to the skill that owns each rule's deep coverage. Use as a final pre-push checklist, when reviewing a teammate's change, or when you need a single audit point that touches every "must / never" rule across the collection.

0
installs
▌
Bootstrapping Taubyte Projects · taubyte
Bootstraps a Taubyte project on the currently selected cloud — `tau new project` to create config + code repos on GitHub and clone them locally, `tau import project` (with repo fullnames, not paths) to register an existing pair, and `tau --json current` to verify selection. Encodes the snake_case project-name rule (dashes break `tau validate config` with `invalid variable name`). Use when creating, importing, or cloning a Taubyte project for the first time.

0
installs
▌
Registering Dream Repositories · taubyte
Registers a website or library GitHub repository with the local Dream auth/repository service via `PUT /repository/github/<repo_id>` so hooks/build triggers are tracked. Use when, after `tau import website|library`, a `dream inject push-specific` for that repo doesn't produce a build, or when the local cloud reports the repo as unknown despite being in the project's config YAML.

0
installs
▌
Authoring Taubyte Function Types · taubyte
Authoritative reference for the four Taubyte function trigger types — `http`, `https`, `p2p`, and `pubsub` — covering the per-type `tau new function` CLI flag matrix from `tau new function --help`, the resulting YAML shape under `trigger:`, the matching Go SDK handler entry points, and the "must-match" wiring strings (channel, protocol, command, call). Use when creating a function whose trigger isn't plain HTTPS, when picking between `http` and `https`, when wiring a PubSub-triggered function to a messaging channel, or when reviewing a function YAML to confirm flag/YAML/Go consistency.

0
installs
▌
Configuring Taubyte Build Runtime · taubyte
Configures the per-resource build/runtime files Taubyte runs server-side — `.taubyte/config.yaml` (image + workflow + similar metadata) and `.taubyte/build.sh` (the actual build script, where build-time environment variables also live as `export …`). Covers Go function builds (`taubyte/go-wasi:latest|v2`), website builds tailored to the actual stack (Vite `dist/`, CRA `build/`, plain static), and library builds. Use when adding/editing build scripts, declaring env vars, switching build images, or debugging "build succeeds but produces nothing" / "env var is empty in handler".

0
installs
▌
Understanding Taubyte Architecture · taubyte
Explains the Taubyte mental model — `tau` CLI vs `dream` local cloud, remote-vs-local cloud types, GitHub as the single source of truth, and the config/code/website/library repo layout that drives builds. Use when the user asks how Taubyte fits together, why pushes don't show up, what repos are needed, or whether to use Dream or a remote cloud.

0
installs

22 published skills