이 저장소의 skills
SkillsMP는 WeaveMindAI/weft에서 207개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
WeaveMindAI/weft수집된 skill 207개 중 40개를 표시합니다.
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 when a run failed, did the wrong thing, never started, got stuck or was cancelled, or when you need to read what a past run did: the order to read a run in (runs, logs, events), what each skip and cancel reason means, and the debugging playbook, from a…
원문 언어: 영어
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…
원문 언어: 영어
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 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. `@per_instance` (a container each), `@instance_filled` (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, how names are spelled, included files, loops, the pulse model, @file, @asset and…
원문 언어: 영어
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…
원문 언어: 영어
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 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 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 when the user asks about connections, API keys, sign-ins or permissions: your part and the user's, the connect flow in the terminal and door by door in the editor, and what each banner means.
원문 언어: 영어
Read when a run failed, did the wrong thing, never started, got stuck or was cancelled, or when you need to read what a past run did: the order to read a run in (runs, logs, events), what each skip and cancel reason means, and the debugging playbook, from a…
원문 언어: 영어
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 before writing or editing any .weft source: declarations, wiring, config literals, reserved keys, inline signatures and expressions, types, groups and the level rule, how names are spelled, included files, loops, the pulse model, @file, @asset and…
원문 언어: 영어
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 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 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 when the user asks about connections, API keys, sign-ins or permissions: your part and the user's, the connect flow in the terminal and door by door in the editor, and what each banner means.
원문 언어: 영어
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 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. `@per_instance` (a container each), `@instance_filled` (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, how names are spelled, included files, loops, the pulse model, @file, @asset and…
원문 언어: 영어
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…
원문 언어: 영어
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 telling the user where to click or what they are looking at in VS Code: the toolbar, running and turning triggers and infra on or off from a selection, the state pill on each trigger and infra node, the action bar, the palette, context menus,…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
Read before writing, fixing or reviewing a node that reads a bus or a stream (a bus reader, a `Generator` input), above all one that also waits, yields or reads at more than one line, and when a node fails with `read directly (not through its state)`, `opened…
원문 언어: 영어
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…
원문 언어: 영어
Deep post-mortem digging into a weft run. Dispatched with a run 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,…
원문 언어: 영어
Deep post-mortem digging into a weft run. Dispatched with a run 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,…
원문 언어: 영어
Read when a program on a cloud install is failing, stuck or slow for real users: reading what is failing there, a database infra node that ran out of memory, weft's own database logs, stuck runs, a resync that stopped, weft held back by its own database, and…
원문 언어: 영어
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, runs,…
원문 언어: 영어