claude-code-hubs: Instructions file for Claude Code

---

Plugin Version Management

When updating plugin versions, ALWAYS update ALL of these locations:

For each plugin (e.g., nano-banana)

1. Plugin metadata (REQUIRED):

   • plugins/{plugin-name}/.claude-plugin/plugin.json - version field

2. Plugin documentation (REQUIRED):

   • plugins/{plugin-name}/README.md - Recent Improvements section
   • plugins/{plugin-name}/skills/{skill-name}/SKILL.md - metadata version field

3. Marketplace version table (REQUIRED):

   • /README.md - "Available Plugins" table (line ~705)

Checklist Template

When bumping plugin version from X.Y.Z to X.Y.(Z+1):

# 1. Update plugin.json
plugins/{name}/.claude-plugin/plugin.json → version: "X.Y.(Z+1)"

# 2. Update README.md - Add new section at top
plugins/{name}/README.md → "## ✨ Recent Improvements (vX.Y.(Z+1))"

# 3. Update SKILL.md metadata
plugins/{name}/skills/{name}/SKILL.md → metadata.version: "X.Y.(Z+1)"

# 4. Update marketplace table
README.md → Available Plugins table → update version column

# 5. Verify no missed references
grep -r "X.Y.Z" plugins/{name}/ README.md

Common Mistakes to Avoid

• ❌ Updating plugin.json but forgetting marketplace table in root README.md
• ❌ Updating version number but not adding "Recent Improvements" section
• ❌ Forgetting to update SKILL.md metadata version
• ❌ Leaving old version numbers in documentation examples

Automation Idea (Future)

Consider adding a version bump script:

./scripts/bump-plugin-version.sh nano-banana 0.0.8