// Guides agents through migrating an existing plugin into this monorepo with the copy-plugin generator workflow.
| name | plugin-transfer |
| description | Guides agents through migrating an existing plugin into this monorepo with the copy-plugin generator workflow. |
Use this skill when migrating an existing plugin repository into sanity-io/plugins.
Always start with:
pnpm generate "copy plugin"
This is the canonical transfer flow and scaffolds monorepo-compatible files, test-studio wiring, and migration TODOs.
Keep and maintain these monorepo config files in the transferred plugin:
package.jsonpackage.config.tstsconfig.jsontsconfig.build.jsonvitest.config.tsDo not copy standalone-repo-only setup such as custom root CI/build/lint/test configs that are already handled by this monorepo.
README.md in the new plugin workspace.dev/test-studio/src/<plugin-example>/index.tsx.dev/test-studio/sanity.config.ts..github/CODEOWNERS during transfer unless explicitly requested.README.md plugins table with the transferred plugin.pnpm build, pnpm test, and pnpm dev to verify migration quality.Explains the dev/test-studio Script Runner tool. Use when adding, editing, running, or documenting scripts in dev/test-studio/src/script-runner, or when the user mentions the Scripts tool, Studio runner scripts, script variables, or browser-side Sanity Studio scripts.
Explains the dev/test-studio Script Runner tool. Use when adding, editing, running, or documenting scripts in dev/test-studio/src/script-runner, or when the user mentions the Scripts tool, Studio runner scripts, script variables, or browser-side Sanity Studio scripts.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Detect and update legacy GROQ patterns where language is read from _key for sanity-plugin-internationalized-array when users mention v4 to v5 migration, or @sanity/document-internationalization from v5 to v6. GROQ query updates, localized arrays, or patterns like `_key == "en"` and `_key == $language`.
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.