pixelclaw 0.1.0 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/skill/SKILL.md
CHANGED
|
@@ -23,12 +23,20 @@ If the tools are missing, the server is not connected:
|
|
|
23
23
|
dealt with: `note done <id>`.
|
|
24
24
|
3. `plan` at the start of the session and again after each finished asset: it lists the
|
|
25
25
|
**requests** people made in the dashboard first, then what is left and what is failing.
|
|
26
|
+
If you are driving a project served with `pixelclaw serve` and a person may be watching, start
|
|
27
|
+
a background wait right away and keep one running between tasks:
|
|
28
|
+
`pixelclaw await <project folder>` (run it in the background; it blocks, prints what people asked
|
|
29
|
+
for and a cursor, then exits). When it exits, handle what it printed (`work` for a request,
|
|
30
|
+
`changes` for an approval or rejection), then **start it again with `--since <cursor>`**. Exit
|
|
31
|
+
code 3 means nothing happened; restart it the same way. Without it, nobody knows you are there
|
|
32
|
+
and a request the person filed just sits. `plan` tells you when open requests have no listener.
|
|
26
33
|
4. **Requests before planned work.** `work` claims the next open request and says what is asked
|
|
27
34
|
(draw a planned asset, change a drawn one, or a new asset the person added to the manifest).
|
|
28
35
|
Do it, then `work(action="done", text=<what changed>)`. If you cannot go on without the person
|
|
29
36
|
(a choice only they can make), `work(action="blocked", text=<one clear question>)` and move on;
|
|
30
37
|
their answer opens the request again. Post `work(action="progress", text=…)` on long ones: the
|
|
31
|
-
person sees it on the card.
|
|
38
|
+
person sees it on the card. Without PixelClaw's MCP tools, the same actions are
|
|
39
|
+
`pixelclaw work <project> claim | progress "…" | done "…" | block "…"` (below).
|
|
32
40
|
|
|
33
41
|
## House rules
|
|
34
42
|
|
|
@@ -126,7 +134,10 @@ asset back down, and `plan` says why.
|
|
|
126
134
|
|
|
127
135
|
People ask for work without talking to you: "Draw this" on a planned card, "Ask for changes" on
|
|
128
136
|
a drawn one (also a `mark rejected "…"` on its tape), "Add an asset" (a new manifest entry). They
|
|
129
|
-
wait in `requests.jsonl`; `plan` lists them first and `work` hands them out one at a time.
|
|
137
|
+
wait in `requests.jsonl`; `plan` lists them first and `work` hands them out one at a time. The
|
|
138
|
+
person's card reads *sent* until something hands it to you, then *seen by claude*: keep a background
|
|
139
|
+
`pixelclaw await <project>` running (restart it after each exit, `--since` the cursor it printed) so
|
|
140
|
+
that happens as soon as they press the button, and the card never claims more than is true.
|
|
130
141
|
|
|
131
142
|
1. `work` → read what is asked, the asset's plan entry and status, and any answer to an earlier
|
|
132
143
|
question.
|
|
@@ -137,7 +148,22 @@ wait in `requests.jsonl`; `plan` lists them first and `work` hands them out one
|
|
|
137
148
|
reply lists them; fix them, or block with a question when only the person can decide. Then `plan`, and `work` again until it says there are
|
|
138
149
|
no open requests; then carry on with planned work.
|
|
139
150
|
|
|
140
|
-
|
|
151
|
+
**No PixelClaw MCP tools in this session** (the project is served with `serve --no-mcp`, or you
|
|
152
|
+
only have a shell): the same routine with the CLI, which goes through the running server so the
|
|
153
|
+
cards move live:
|
|
154
|
+
|
|
155
|
+
```sh
|
|
156
|
+
pixelclaw work <project> list # the open requests (now seen by claude)
|
|
157
|
+
pixelclaw work <project> claim # step 1: the next open one (or claim r3)
|
|
158
|
+
pixelclaw work <project> progress "<a short note>"
|
|
159
|
+
pixelclaw work <project> done "<what changed>" # step 3; refused while a check fails
|
|
160
|
+
pixelclaw work <project> block "<one clear question>"
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
Draw with `pixelclaw run <project> -e "…"` (or a script file), look with `pixelclaw view`, check
|
|
164
|
+
with `pixelclaw check`; `pixelclaw plan <project>` for what is left.
|
|
165
|
+
|
|
166
|
+
A headless worker (`pixelclaw work <project> start`, or Start Claude in the dashboard when the project enables
|
|
141
167
|
it) follows the same routine with no one at the keyboard: never ask in chat, ask with `blocked`.
|
|
142
168
|
It has only the PixelClaw tools (no shell, files or web; files outside the project are refused),
|
|
143
169
|
its system prompt ends with every command of the language, and a session that makes no tool call
|