buildpartner 0.3.2 → 0.3.3

package/dist/src/commands/setup.js

@@ -155,8 +155,8 @@ export async function setup() {
     const skillCount = installedSkills.length;
     if (skillCount > 0) {
         // Highlight key skills
-        const hasConsult = installedSkills.includes("he-consult");
-        const hasInterview = installedSkills.includes("he-interview");
+        const hasConsult = installedSkills.includes("bp-consult");
+        const hasInterview = installedSkills.includes("bp-interview");
         if (hasConsult)
             console.log(chalk.green(`        ✓ ${skillCommand("consult")} (expert advice on any topic)`));
         if (hasInterview)

package/dist/src/constants.d.ts

@@ -2,8 +2,8 @@
  * Global constants shared across CLI, MCP server, and web app.
  * Change SKILL_PREFIX here and it propagates everywhere.
  */
-export declare const SKILL_PREFIX = "he-";
+export declare const SKILL_PREFIX = "bp-";
 /**
- * Format a skill command for display (e.g., "interview" -> "/he-interview").
+ * Format a skill command for display (e.g., "interview" -> "/bp-interview").
  */
 export declare function skillCommand(name: string): string;

package/dist/src/constants.js

@@ -2,9 +2,9 @@
  * Global constants shared across CLI, MCP server, and web app.
  * Change SKILL_PREFIX here and it propagates everywhere.
  */
-export const SKILL_PREFIX = "he-";
+export const SKILL_PREFIX = "bp-";
 /**
- * Format a skill command for display (e.g., "interview" -> "/he-interview").
+ * Format a skill command for display (e.g., "interview" -> "/bp-interview").
  */
 export function skillCommand(name) {
     return `/${SKILL_PREFIX}${name}`;

package/dist/src/installer/skill-installer.js

@@ -8,7 +8,7 @@ const __dirname = dirname(__filename);
 // Package root = 3 levels up from there
 const PACKAGE_ROOT = join(__dirname, "..", "..", "..");
 const GLOBAL_SKILLS_DIR = join(homedir(), ".claude", "skills");
-const SKILLS = ["he-consult", "he-coach", "he-recap-week", "he-flex-socials", "he-interview", "he-life-story", "he-quest-status", "he-enhance-claude-md", "he-open-dashboard", "he-log-experience", "he-improve-skill", "he-full-audit"];
+const SKILLS = ["bp-consult", "bp-coach", "bp-recap-week", "bp-flex-socials", "bp-interview", "bp-life-story", "bp-quest-status", "bp-enhance-claude-md", "bp-open-dashboard", "bp-log-experience", "bp-improve-skill", "bp-full-audit"];
 /**
  * Find the source skills directory from the package.
  */

package/dist/src/installer/skill-sync.d.ts

@@ -1,6 +1,6 @@
 /**
  * Skill sync: pulls latest skill definitions from the API.
- * Called on MCP server startup. Writes to ~/.claude/skills/he-*.
+ * Called on MCP server startup. Writes to ~/.claude/skills/bp-*.
  * Falls back to bundled skills if offline.
  */
 /**

package/dist/src/installer/skill-sync.js

@@ -1,6 +1,6 @@
 /**
  * Skill sync: pulls latest skill definitions from the API.
- * Called on MCP server startup. Writes to ~/.claude/skills/he-*.
+ * Called on MCP server startup. Writes to ~/.claude/skills/bp-*.
  * Falls back to bundled skills if offline.
  */
 import { writeFileSync, readFileSync, mkdirSync } from "fs";

package/dist/src/store/quest-store.js

@@ -127,16 +127,16 @@ export const COMING_SOON_QUESTS = [
 ];
 // Skill-to-quest auto-completion mapping (a skill can complete multiple quests)
 const SKILL_QUEST_MAP = {
-    "he-coach": ["run-first-skill", "systems-coach-review"],
-    "he-flex-socials": ["run-first-skill"],
-    "he-recap-week": ["run-first-skill", "storyteller-weekly-recap"],
-    "he-interview": ["build-training-data"],
-    "he-life-story": ["build-training-data", "storyteller-life-story"],
-    "he-consult": ["consult-an-expert", "storyteller-content-consult", "systems-launch-strategy"],
-    "he-enhance-claude-md": ["run-first-skill"],
-    "he-log-experience": ["build-training-data"],
-    "he-full-audit": ["run-first-skill", "systems-coach-review"],
-    "he-improve-skill": ["builder-improve-skill"],
+    "bp-coach": ["run-first-skill", "systems-coach-review"],
+    "bp-flex-socials": ["run-first-skill"],
+    "bp-recap-week": ["run-first-skill", "storyteller-weekly-recap"],
+    "bp-interview": ["build-training-data"],
+    "bp-life-story": ["build-training-data", "storyteller-life-story"],
+    "bp-consult": ["consult-an-expert", "storyteller-content-consult", "systems-launch-strategy"],
+    "bp-enhance-claude-md": ["run-first-skill"],
+    "bp-log-experience": ["build-training-data"],
+    "bp-full-audit": ["run-first-skill", "systems-coach-review"],
+    "bp-improve-skill": ["builder-improve-skill"],
 };
 // --- Quest State ---
 export function readQuests() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "buildpartner",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "type": "module",
   "description": "Your AI build partner. Expert guidance inside Claude Code.",
   "bin": {

package/skills/{he-coach → bp-coach}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-coach
+# /bp-coach
 
 Review my setup and tell me what to improve. Looks at how you use Claude Code, what tools you're missing, what patterns to fix. Gives you 3 action items.
 
@@ -51,6 +51,6 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
 
 4. Keep the tone direct and encouraging. No fluff, just "here's what to do."
 
-5. If they have < 5 sessions, say: "Keep going. After a few more sessions I'll have real recommendations. For now, try /he-interview to build your profile."
+5. If they have < 5 sessions, say: "Keep going. After a few more sessions I'll have real recommendations. For now, try /bp-interview to build your profile."
 
 6. Call `check_status` with `{ "skill_name": "coach" }`.

package/skills/{he-consult → bp-consult}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-consult
+# /bp-consult
 
 I need expert help with something. Ask any question and get matched to the right framework: pricing, content, launch, AI automation, marketing, sales, product strategy, and more.
 

package/skills/{he-enhance-claude-md → bp-enhance-claude-md}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-enhance-claude-md
+# /bp-enhance-claude-md
 
 Make my CLAUDE.md better. Reads your session patterns and suggests rules to add, remove, or sharpen. Only suggests what your data backs.
 

package/skills/{he-flex-socials → bp-flex-socials}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-flex-socials
+# /bp-flex-socials
 
 Give me something to share. Generates a shareable stats card you can screenshot and post. Like Strava for Claude Code.
 

package/skills/{he-full-audit → bp-full-audit}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-full-audit
+# /bp-full-audit
 
 Full audit of your Claude Code environment, skills, and workflows. Finds what's missing, what's broken, and what to improve. Prioritized by impact.
 

package/skills/{he-improve-skill → bp-improve-skill}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-improve-skill
+# /bp-improve-skill
 
 Enhance a skill so you don't make the same mistake twice. After using any skill (BuildPartner or your own custom ones), run this to improve it based on what just happened.
 
@@ -10,8 +10,8 @@ Ask:
 > "Which skill do you want to improve?"
 
 List skills from:
-- BuildPartner skills: `~/.claude/skills/he-*/SKILL.md`
-- Their custom skills: `~/.claude/skills/*/SKILL.md` (excluding he-* prefix)
+- BuildPartner skills: `~/.claude/skills/bp-*/SKILL.md`
+- Their custom skills: `~/.claude/skills/*/SKILL.md` (excluding bp-* prefix)
 
 If the user says "based on our conversation" without naming a skill, infer from context which skill is relevant.
 

package/skills/{he-interview → bp-interview}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-interview
+# /bp-interview
 
 Get to know how I work. Quick Q&A that teaches BuildPartner your role, stack, and preferences. Every skill gets better after this.
 

package/skills/{he-life-story → bp-life-story}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-life-story
+# /bp-life-story
 
 Let me tell you my full story. Deep conversation about your background, career, and goals. Makes every consultation deeply personal.
 
@@ -59,6 +59,6 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
 }
 ```
 
-5. End with a summary, then: "Your life story is saved. Run /he-life-story again to add more."
+5. End with a summary, then: "Your life story is saved. Run /bp-life-story again to add more."
 
 6. Call `check_status` with `{ "skill_name": "life-story" }`.

package/skills/{he-log-experience → bp-log-experience}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-log-experience
+# /bp-log-experience
 
 Get better responses by documenting your lived experience. The more context BuildPartner has about what you've built, learned, and struggled with, the better every skill works for you.
 
@@ -56,7 +56,7 @@ Save to `~/.buildpartner/knowledge/experiences/{YYYY-MM-DD}-{brief-slug}.md`
 
 7. Confirm:
 
-> "Saved. This experience now feeds into /he-coach, /he-consult, and /he-recap-week. The more you log, the more personalized everything gets."
+> "Saved. This experience now feeds into /bp-coach, /bp-consult, and /bp-recap-week. The more you log, the more personalized everything gets."
 
 8. Rules:
    - Keep it fast. This should take 30 seconds, not 5 minutes.

package/skills/{he-open-dashboard → bp-open-dashboard}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-open-dashboard
+# /bp-open-dashboard
 
 Open my dashboard in the browser, automatically signed in.
 

package/skills/{he-quest-status → bp-quest-status}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-quest-status
+# /bp-quest-status
 
 What should I do next in BuildPartner? Shows your quest progress and guides you through the next step. Start here if you're new.
 
@@ -23,10 +23,10 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
 
 3. If there's an active quest, guide them through it. Don't just describe it, DO it with them:
 
-   - **"Run Your First Skill"**: Tell them to type /he-flex-socials or /he-coach right now.
-   - **"Build Your Training Data"**: Start the /he-interview flow.
+   - **"Run Your First Skill"**: Tell them to type /bp-flex-socials or /bp-coach right now.
+   - **"Build Your Training Data"**: Start the /bp-interview flow.
    - **"Plan Before You Build"**: Walk them through the planning approach.
-   - **"Consult an Expert"**: Ask what they need help with, run /he-consult.
+   - **"Consult an Expert"**: Ask what they need help with, run /bp-consult.
    - Path quests: guide them to the relevant skill.
 
 4. If core is done and paths are unlocked, show all three paths and let them pick.
@@ -35,8 +35,8 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
 
 ```
 All quests complete! You've mastered the fundamentals.
-More quests coming soon. In the meantime: /he-coach for setup reviews,
-/he-recap-week for weekly digests, and /he-consult for expert advice.
+More quests coming soon. In the meantime: /bp-coach for setup reviews,
+/bp-recap-week for weekly digests, and /bp-consult for expert advice.
 ```
 
 6. Rules:

package/skills/{he-recap-week → bp-recap-week}/SKILL.md

@@ -1,4 +1,4 @@
-# /he-recap-week
+# /bp-recap-week
 
 What happened this week? Weekly summary of what you built, your numbers, and what to add to your workflow. Run this on Fridays.
 
@@ -31,7 +31,7 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
 {1-2 specific things they should start doing based on this week's patterns. Concrete, not abstract.}
 
 Examples:
-- "You researched pricing 3 times this week. Run /he-consult next time to get expert frameworks instantly."
+- "You researched pricing 3 times this week. Run /bp-consult next time to get expert frameworks instantly."
 - "You built 2 new features but didn't deploy either. Ship one this week."
 - "You used Claude Code 12 times but never used Plan mode. Try planning before your next big feature."