All authors
Claude Skills by WeaveMindAI
github.com/WeaveMindAI84 skills0 installs7 views
- Weft DeployCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft FrontendRead 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 doors, the three variables that say where the program is, one shared PostgreSQL, where the api token lives, pictures as links, the build and its Dockerfile, and the shape for a site whose people each bring their own accounts or settings (...Votes: 0GitHub stars: 1,992
- Weft GrowCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft Live TestCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft New NodeCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft RunCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- Weft DeployCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft GrowCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- Weft GrowCOMMAND, 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 seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- DeployerThe 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.Votes: 0GitHub stars: 1,992
- Frontend BuilderBuilds 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 side, and proves the build and drives the one task as a client of the program before reporting.Votes: 0GitHub stars: 1,992
- Node SmithBuilds 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 (basic and fake, never live) until green, then reports with evidence.Votes: 0GitHub stars: 1,992
- Prompt EngineerWrites 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 matters.Votes: 0GitHub stars: 1,992
- Red TeamerAttacks 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 node code, walks each attack from input to consequence, and reports verified findings with the layer that closes each. Never fixes, never runs the program, never edits.Votes: 0GitHub stars: 1,992
- Run DiggerDeep 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. Research only, never fixes.Votes: 0GitHub stars: 1,992
- Weft ApiRead 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 graph, pictures in and out as links, streaming an answer as it is produced, holding a conversation open, who may call, and how to try it.Votes: 0GitHub stars: 1,992
- Weft LanguageRead 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 compiler error slug.Votes: 0GitHub stars: 1,992
- Weft Node AuthoringRead 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.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- DeployerThe 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.Votes: 0GitHub stars: 1,992
- Frontend BuilderBuilds 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 side, and proves the build and drives the one task as a client of the program before reporting.Votes: 0GitHub stars: 1,992
- Node SmithBuilds 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 (basic and fake, never live) until green, then reports with evidence.Votes: 0GitHub stars: 1,992
- Prompt EngineerWrites 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 matters.Votes: 0GitHub stars: 1,992
- Red TeamerAttacks 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 node code, walks each attack from input to consequence, and reports verified findings with the layer that closes each. Never fixes, never runs the program, never edits.Votes: 0GitHub stars: 1,992
- Run DiggerDeep 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. Research only, never fixes.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead 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.Votes: 0GitHub stars: 1,992