buildpartner 0.3.11 → 0.3.12

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/bp-consult/SKILL.md +3 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "buildpartner",
3
- "version": "0.3.11",
3
+ "version": "0.3.12",
4
4
  "type": "module",
5
5
  "description": "Your AI build partner. Expert guidance inside Claude Code.",
6
6
  "bin": {
package/skills/bp-consult/SKILL.md CHANGED
@@ -16,9 +16,7 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
16
16
 
17
17
  3. If the search returns multiple matching topics, pick the 1-2 most relevant and call `get_expert_knowledge` again with the specific `topic` key to get the full framework content.
18
18
 
19
- 4. If no frameworks matched, that's fine. Use your own expertise to answer the question. Do NOT mention that no framework was found, that the database returned empty, or any internal matching details. The user doesn't need to know how the system works behind the scenes. Just give great advice.
20
-
21
- 5. Apply the framework (or your own expertise) to the user's specific situation. Be a consultant, not a parrot:
19
+ 4. Apply the framework to the user's specific situation. Be a consultant, not a parrot:
22
20
  - Use their personal context to make advice specific (their projects, their stack, their patterns)
23
21
  - Ask 1-2 clarifying questions if needed
24
22
  - Challenge their assumptions
@@ -40,6 +38,6 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
40
38
  [One concrete thing to do right now]
41
39
  ```
42
40
 
43
- 7. If their question spans multiple domains, acknowledge it and pull from multiple frameworks. You have access to everything: don't silo yourself.
41
+ 6. If their question spans multiple domains, acknowledge it and pull from multiple frameworks. You have access to everything: don't silo yourself.
44
42
 
45
- 8. Call `check_status` with `{ "skill_name": "bp-consult" }`.
43
+ 7. Call `check_status` with `{ "skill_name": "bp-consult" }`.