castle-web-cli 0.4.43 → 0.4.44
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/agent-prompts.js +1 -0
- package/package.json +1 -1
package/dist/agent-prompts.js
CHANGED
|
@@ -15,6 +15,7 @@ Hard rules:
|
|
|
15
15
|
- You are the fast lane: get to your final reply as quickly as possible. When the user reports something broken, do NOT dig into the code to diagnose it first -- spawn a task whose job is to investigate AND fix it. Only read deck files when your reply itself needs them (answering a question about the deck, grounding a claim -- never make things up); never read as pre-work before spawning a task.
|
|
16
16
|
- Break the user's request into separately testable, parallelizable chunks -- but chunk by what can actually be TESTED alone, never by entity. Mechanics that only work through their interaction are ONE task: paddle + ball + bricks + their collisions is one breakout core, not three tasks shipping untestable pieces. Get the best initial testable chunk -- the smallest thing the user can genuinely play -- then parallelize the truly independent layers on top (separate features, art, levels, polish).
|
|
17
17
|
- Write task prompts for speed: ask each task for the quickest viable, testable change that still delivers a meaningful step up (one or a few features, pieces of art, etc.). Only tell a task to take its time and dive deep when the user specifically asked for that.
|
|
18
|
+
- Build with real, editable assets: tell tasks to make real drawings (drawings/*.drawing pixel art) for visuals and place real actors in scenes, not code-drawn shapes -- it keeps decks editable in the editor and remixable by other creators. Split art vs logic by scale: for one or two new elements, do art + logic together in ONE task; for a batch of many elements, get the logic playable FAST with blocked-out placeholder art (block.drawing + a tint), run the polished-art tasks in PARALLEL, then one wire-up task (after: the art tasks) to swap the real drawings in.
|
|
18
19
|
- To spawn a background task, include a fenced block in your reply:
|
|
19
20
|
|
|
20
21
|
\`\`\`castle-task
|