Menu
SkillsMP has collected 71 skills from WeaveMindAI/weft. Open a skill to review its source and details.
Showing 40 of 71 collected skills.
Shipping weft: merging into main through a PR, what the release workflow publishes, the record tags that decide which stores publish, and the store rules that have actually bitten us. Load before merging to main, bumping an extension version, or debugging a…
Read before picking nodes for a job: the three reads that find a node and tell you how it wires, the metadata vocabulary you will meet there, the wiring shapes that recur (a connection, a provider, infrastructure, ports that come from a list), where a…
Read before writing or editing any .weft source: declarations, wiring, config literals, reserved keys, inline signatures and expressions, types, groups and the level rule, included files, loops, the pulse execution model, @file, @asset and @include, and every…
Read before dispatching a node-smith (the brief and the review) and when an expert writes a node by hand: the node authoring manual, the test tiers, and the shapes half-done work takes. The node-smith reads this same file as its manual.
Read when running, activating or debugging a program: the CLI command map, the daemon (never yours to restart), the build and run flow, trigger activation and the three deactivate modes, the infra lifecycle, sizing a command's timeout, journal inspection…
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,…
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,…
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,…
Read when someone asks to be taught, shown around or onboarded, asks what a thing on screen means, or opens a project they have clearly just made: the guided tour of the two views, the graph, building in it, running, the three things that are alive,…
Read when the user asks about connections, API keys, sign-ins, permissions, the browser extension, human tasks, or a public URL: the connect flow door by door, what each banner means, tokens and scoping, and how HumanQuery tasks reach people. Also read it…
Read when the user asks about connections, API keys, sign-ins, permissions, the browser extension, human tasks, or a public URL: the connect flow door by door, what each banner means, tokens and scoping, and how HumanQuery tasks reach people.
Read when the user wants their own website, app, bot or extension to list, show, answer, skip or cancel what a program is waiting on, fetch a file it carries, or show what one of its nodes is displaying (a WhatsApp bridge's QR code, a database's minted…
Read when telling the user where to click or what they are looking at in VS Code: the toolbar, the action bar, the palette, context menus, editing gestures, groups and loops in the graph, run and replay, the inspector, the connect flow, the problems panel.…
Read when the program needs to answer calls from outside (an HTTP route, a websocket, anything a page or a service will call), and before briefing a frontend on what it will call: the URL known before activation, how a request's parts and body reach the…
Read when the user wants a page, app or site for the program, and before dispatching the frontend-builder: the verified scaffold commands, the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth, shadcn-svelte), calling the program's own routes and signal…
Read when no node, group or node-smith contract can honestly deliver what the request needs, or when a node just built belongs in the shared catalog: the tracker to search first, the issue templates with their exact field ids, and the pre-filled issue URL to…
Read when the user asks what a run costs, or when a node is wired to a paid API weft does not already price: the three pieces of a custom paid service, a meter to copy, and the rules that keep a number honest.
Read when a program calls a language model and you need it to behave: whether it reasons before answering and how hard, what bounds a reply's length and why one comes back empty, what a class of model costs in time and money, and how prompt caching works…
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…
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…
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,…
Writes and overhauls the LLM prompts inside a weft program (system prompts in prompts/, user prompt templates, JSON extraction instructions). Runs on the WeaveMind prompt-building playbook. Dispatched by Tangle when a stage talks to a model and the prompt…
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…
Deep post-mortem digging into a weft execution. Dispatched with a color 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…
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 sixteen `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 color. The sixteen `weft-` reference skills beside it are things you read; this is a…
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 sixteen…
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 sixteen `weft-` reference skills beside it are things you read;…
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 sixteen `weft-` reference skills beside…
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 sixteen `weft-` reference skills beside it are things you read; this is a procedure…
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.
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 or an example name to rerun. The sixteen…
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.
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 or an example to check. The sixteen `weft-`…
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,…
Writes and overhauls the LLM prompts inside a weft program (system prompts in prompts/, user prompt templates, JSON extraction instructions). Runs on the WeaveMind prompt-building playbook. Dispatched by Tangle when a stage talks to a model and the prompt…
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…
Deep post-mortem digging into a weft execution. Dispatched with a color 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…