anima-upgrade-migration
Upgrade @animaapp/anima-sdk versions and handle API changes. Use when upgrading SDK versions, migrating from the Figma plugin workflow to SDK-based automation, or adapting to new Anima API features. '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill anima-upgrade-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Anima Upgrade & Migration ## Migration Paths | From | To | Complexity | |------|----|-----------| | Figma plugin (manual) | SDK automation | Medium | | SDK v1 → v2 | SDK latest | Low | | Anima Playground | SDK API | Low | ## Instructions ### Step 1: Upgrade SDK ```bash # Check current version npm list @animaapp/anima-sdk # Upgrade to latest npm install @animaapp/anima-sdk@latest # Check for brea
What does the anima-upgrade-migration skill do?
Upgrade @animaapp/anima-sdk versions and handle API changes. Use when upgrading SDK versions, migrating from the Figma plugin workflow to SDK-based automation, or adapting to new Anima API features. '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill anima-upgrade-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
