capyai 0.5.0 → 0.5.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "capyai",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "type": "module",
   "description": "Unofficial Capy.ai CLI for agent orchestration with quality gates",
   "bin": {

package/skills/capy/SKILL.md

@@ -257,17 +257,26 @@ capy pool [status|set|test|instances|instance|clear]  # → warm pool management
 
 ## Prompting tips
 
-When writing prompts for `capy captain` or `capy build`, be specific. The Capy agent is another AI. Vague prompts produce vague results.
+Captain and Build need different prompting styles.
 
-Bad: `"Fix the CI issue"`
+**Captain** has full codebase context and plans its own approach. Tell it WHAT to accomplish, not HOW. Link the issue, set the quality bar, get out of its way.
 
-Good: `"Fix CI for crypto-trading pack. The changeset file is missing. Add a changeset entry for @veto/crypto-trading with patch bump. Run 'npx changeset status' to validate. Files: packages/crypto-trading/. Reference: PLW-201."`
+Bad: `"Fix CI for crypto-trading pack. The changeset file is missing. Add a changeset entry for @veto/crypto-trading with patch bump. Run 'npx changeset status' to validate. Files: packages/crypto-trading/."`
+
+Good: `"We have a CI failure on the crypto-trading pack — missing changeset. Fix it. Reference: PLW-201. Don't finish until CI is green and tests pass."`
+
+Good: `"https://linear.app/plaw/issue/PLW-201 — get this done. Make sure all tests pass, CI is green, and code review comes back clean."`
+
+Captain prompts should include:
+- What the problem or goal is (natural language)
+- A link to the issue if one exists (GitHub, Linear)
+- The quality bar ("tests pass", "CI green", "code review clean")
 
-Always include:
-- Which files to touch
-- What the acceptance criteria are
-- What commands to run to verify
-- References to related issues or tasks
+Do NOT include specific files, specific commands, or implementation details. Captain figures that out.
+
+**Build** is isolated and has no codebase context. Be specific. Name the files, the commands, the acceptance criteria.
+
+Good: `"Fix CI for crypto-trading pack. The changeset file is missing. Add a changeset entry for @veto/crypto-trading with patch bump. Run 'npx changeset status' to validate. Files: packages/crypto-trading/. Reference: PLW-201."`
 
 ## Triggers