sanity-io sanity
COMMUNITYLABSCO SUMMARY
Twelve of the sixteen are generic engineering-practice skills with nothing Sanity-specific about them: code review, code simplification, architecture improvement, performance optimization, Playwright testing (two skills), RxJS patterns, test-driven development, and React/Next.js performance guidance, plus one skill for writing new skills and one for finding existing ones. A further skill, pr-description, is scoped explicitly to "the Sanity monorepo"'s own PR template — useful only to someone opening a pull request against this repository.
The other three — sanity-config-reducers, sanity-default-plugins, and sanity-plugin-authoring — are for people extending Sanity Studio itself: adding config properties that get reduced across a workspace, wiring core plugins the way this monorepo's plugin system expects, and building public-facing Studio plugins. If you are a Sanity customer building content schemas and front-end integrations rather than extending the Studio's plugin system, none of the sixteen skills here are aimed at that job.
READ THE FULL ANALYSIS
The generic skills aren't presented as Sanity's own invention. vercel-react-best-practices is credited in its own description to "Vercel Engineering," and others (playwright-best-practices, playwright-cli, tdd, rxjs-like-a-pro) read as reusable engineering guidance that would apply to any TypeScript codebase, not something specific to Sanity's product.
The public README never mentions any of this. Sanity's own README documents Sanity Studio, the quickstart (npm create sanity@latest), and the hosted Content Lake — it does not mention skills, this folder, or that sixteen of them ship in the repository at all.
WHAT'S INSIDE
16 showing · 16 totalNothing else to set up — install it and go.
code-review-and-quality
A full read of someone's change before it is merged — does it work, can it be understood, is it safe and fast enough — ending in a plain yes or not yet.
code-simplification
Code that already works but is harder to follow than it needs to be, rewritten to be easier to read, with the behaviour and the passing tests unchanged.
find-skills
Checks whether somebody has already packaged up the thing you were about to build yourself, and installs it for you if they have.
grill-me
Asks you question after question about a plan you are about to commit to, digging out every choice you have not thought through yet, and suggesting an answer to each.
improve-codebase-architecture
Goes hunting for the parts of a codebase that are awkward to work with, gets several different redesigns drafted for one of them, and files the strongest as a proposal for the team.
performance-optimization
Tracking down what is actually making an app or a page slow, fixing that one thing, and proving with numbers that it got faster rather than hoping.
playwright-best-practices
Tests that drive a real browser the way a person would — how to write them with Playwright, and how to stop the ones you have from failing at random.
playwright-cli
You drive a live browser from the command line, and see a fresh snapshot of the page after every click, fill, or navigation.
pr-description
The write-up that goes with a proposed code change: why it was done and what a reviewer should look at, in the format this repository expects.
rxjs-like-a-pro
RxJS deals with values that keep arriving over time, like clicks or server replies — this is how to keep that code one readable chain instead of callbacks inside callbacks.
sanity-config-reducers
In a Sanity Studio the same setting can be supplied by the project itself or by any of its plugins — this is how to decide which one wins, and to fail loudly on a bad value.
sanity-default-plugins
Adding a plugin that ships inside Sanity Studio itself rather than being installed by a user, built to match the ones already in there.
sanity-plugin-authoring
A Sanity Studio plugin is a bundle of settings and screens you drop into a Studio — this is what one is allowed to change, and how to build a small one.
tdd
Building a feature one behaviour at a time: write a test that fails, write just enough code to pass it, tidy up, repeat.
vercel-react-best-practices
A React page can be slow for a dozen unrelated reasons; this walks the code looking for the 57 specific ones Vercel's engineers keep running into.
write-a-skill
Turning something you explain to an AI assistant over and over into a written skill it loads by itself, with a description sharp enough that it picks the right one.
HOW TO GET IT
npx skills add sanity-io/sanitynpx skills add sanity-io/sanity --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.