Labsco
Labsco/Repos/sanity-io/plugins
REPO PACKAGE

sanity-io plugins

COMMUNITY
sanity-io · publisher14 repository starsMIT · Freegithub.com/sanity-io/plugins
10skills
6ready to use

Four of the ten are generic build-tooling guidance that would read the same in almost any JavaScript monorepo: pnpm (workspace and dependency management, catalogs, patches), turborepo (task pipelines, caching, --filter), vite (plugin API, SSR, the Vite 8 Rolldown migration), and vitest (unit testing with a Jest-compatible API). The other six are specific to this codebase: sanity-plugin-best-practices sets anti-patterns and styling/performance rules for plugin code written under plugins/; plugin-transfer walks an agent through migrating an outside plugin into the monorepo via its copy-plugin generator; i18n-array-groq-query-migration updates one legacy GROQ pattern for two named plugins' v4-to-v5 and v5-to-v6 migrations; test-studio-script-runner documents the dev/test-studio Script Runner tool; and find-skills is a meta-skill for discovering other installable skills rather than anything about Sanity itself.

None of the ten teaches how to configure or use a published plugin — @sanity/assist, dashboard, orderable-document-list, and the rest of the readme's own plugin table — from inside a consuming Sanity Studio project. This package is for someone contributing to sanity-io/plugins itself, or working in a similarly-shaped pnpm-and-turborepo monorepo, not for a Studio user looking for help with a plugin they've already installed.

READ THE FULL ANALYSIS

One of the ten isn't really about this repository either. vercel-react-best-practices carries the description "React and Next.js performance optimization guidelines from Vercel Engineering," worded close to identically to a skill we've seen credited elsewhere as coming from vercel-labs/agent-skills — it reads as vendored in rather than written for this monorepo, alongside the other generic tooling skills.

Getting it running costs little, on our reading. Six of the ten need nothing beyond installing the skill, three assume the monorepo's own local toolchain is already set up, and one carries an account-key dependency in our database that we cannot attribute to a specific skill by name from the material we have.

6Work with nothing else to set up.
14Stars on the GitHub repository, at last check.