From juicebox-pack
Manage Juicebox SDK upgrades. Use when upgrading SDK versions, migrating between API versions, or handling breaking changes. Trigger with phrases like "upgrade juicebox", "juicebox migration", "update juicebox SDK", "juicebox breaking changes".
How this skill is triggered — by the user, by Claude, or both
Slash command
/juicebox-pack:juicebox-upgrade-migrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Plan and execute safe Juicebox SDK version upgrades with minimal disruption.
Plan and execute safe Juicebox SDK version upgrades with minimal disruption.
For full implementation details and code examples, load:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
After upgrade, verify with juicebox-prod-checklist for production readiness.
See migration implementation details for output format specifications.
| Error | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with migration |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
Basic usage: Apply juicebox upgrade migration to a standard project setup with default configuration options.
Advanced scenario: Customize juicebox upgrade migration for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin juicebox-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026