Read when running or activating a program: the CLI command map, the daemon (never yours to restart), running a command so it never asks and never sits quiet (with how long each normally takes), the build and run flow, trigger activation and the three deactivate modes, the infra lifecycle, and what each kind of trigger…
Read when a program talks to a model, messages people, spends money or writes into other systems: the swiss cheese model, the free layers built by default, the layers that cost something and the one-sentence test for when a program is high stakes, the wiring shapes, and the red-teamer pass.
Read when growing a program stage by stage: carving a run, supplying starting values, baking a trigger and firing it without activating, reusing completed work with a seed, freezing an accepted example, checking a new run against one, and what each refusal means.
Read when the user asks to update or upgrade weft, or when something broke right after one: locating the checkout, the git pull plus setup.sh walk, what setup.sh rebuilds and what it preserves, and fixing a failed update.
Builds the project's frontend under front/ end to end, unsupervised. Dispatched by Tangle with the pages a person must use and the signals behind them. Reads the weft-frontend and weft-consumers skills, builds on the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth, shadcn-svelte), holds the api token server…
Builds exactly one weft node end to end, unsupervised. Dispatched by Tangle with a typed contract (one job, exact ports); researches the real API documentation when the node wraps a service, writes the node and extensive tests in the project's nodes/ folder, and proves it by running weft test-node on the local tiers…
Attacks a weft program before it faces the world, hunting every credible hole: an outsider lying through an input, a hallucination the graph trusts, a rogue step with agency, an unguarded path to something that matters. Dispatched by Tangle when the program is high-stakes; reads the weft source, the prompts, and the…
Deep post-mortem digging into a weft execution. Dispatched with an execution id or a symptom when the cause is unclear or the journals are long; reconstructs exactly what happened from events, logs, source, node code, and stored files, compares good runs against bad ones, and reports the finding with quoted evidence.…
COMMAND, not reference: Validate and build the weft program, fix diagnostics until clean. Run this when the user asks for this step by name. The weft- reference skills beside it are things you read; this is a procedure you carry out.
COMMAND, not reference: Inspect the last execution and chase the failure to one node. Run this when the user asks for this step by name, optionally naming an execution id. The weft- reference skills beside it are things you read; this is a procedure you carry out.
COMMAND, not reference: Grow the program one stage at a time against a real input, seeded runs and frozen examples included. Run this when the user asks for this step by name, optionally naming the stage to grow next or an example to check. The weft- reference skills beside it are things you read; this is a procedure…
COMMAND, not reference: Walk the user through setting up and running a node's live test. Run this when the user asks for this step by name, optionally naming the node type or package name. The weft- reference skills beside it are things you read; this is a procedure you carry out.
COMMAND, not reference: Expert entry: have a specific node built, or take the hand and write it yourself. Run this when the user asks for this step by name, optionally naming what the node should do, in plain words. The weft- reference skills beside it are things you read; this is a procedure you carry out.
COMMAND, not reference: Build and run the weft program, then report what came out. Run this when the user asks for this step by name, optionally naming node ids to target. The weft- reference skills beside it are things you read; this is a procedure you carry out.
Read when a program serves several PEOPLE, each with their own account, number, bot, spreadsheet or schedule (a WhatsApp assistant for many customers, a Slack bot per workspace, a report per client): the table that says which person owns which instances, one instance per person as the simple case, people who own…
The only agent that acts on a cloud install. Dispatched by Tangle with what to do on a named target (deploy, roll back, set up CI, read a failed cloud build); names the target with --on on every command, reads the weft-deploying skill, and reports the deployed version and route addresses, or the exact failure.
Read when the user wants weft itself on their Google Cloud for the first time, or to upgrade or resize the weft already there: getting the user's GitHub and Google Cloud accounts and CLIs ready, the fork, the one-time gcloud block, the database, the fork's variables and secrets, running the install workflow, the first…
Read when the user wants weft or a program live for real people on their cloud, asks about prod, a target, --on, a domain or GCP, or a deploy failed: targets and logging in, domains, the deploy workflow weft ci add writes, handing it its settings with weft target export, a project's frontends (weft frontend), what a…
Read whenever part of a program must run as several separate copies, each under its own id, even with ONE user: a session per chat, a sandbox per job, a workspace per document, a bot per customer. @perinstance (a container each), @instancefilled (a value each, a connection included), which instance a run is for, the…
The only agent that acts on a cloud install. Dispatched by Tangle with what to do on a named target (deploy, roll back, set up CI, read a failed cloud build); names the target with --on on every command, reads the weft-deploying skill, and reports the deployed version and route addresses, or the exact failure.
COMMAND, not reference: Deploy the program to a cloud install, through the deployer. Run this when the user asks for this step by name, naming the target and optionally what to do. The weft- reference skills beside it are things you read; this is a procedure you carry out.
Read when a cloud install needs its database: the user has no Postgres for it, or asks which to use. Gets one that scales to zero (Neon), with the user only signing up and pasting one key, and puts its addresses in the fork's secrets. Part of weft-cloud-install.
★not rated 2.0k▲
+6
changed 4d agoA68 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: