npx skills add ...
npx skills add sanity-io/sanity --skill sanity-plugin-authoring
npx skills add sanity-io/sanity --skill sanity-plugin-authoring
Explain and create Sanity Studio plugins using the public plugin and tool APIs. Use when creating user-facing plugins, adding tools through plugins, or when an agent needs to understand what a Sanity plugin can configure before applying monorepo-specific default plugin wiring.
A Sanity Studio plugin is a named configuration bundle that can be added to a Studio through the plugins array. Plugin configuration accepts most workspace config properties, except workspace-owned settings such as dataset, projectId, auth, and theme.
Always give plugins a stable unique name. Prefer definePlugin() so editors expose useful types and autocomplete.
Use definePlugin((options) => ({...})) when callers need to configure behavior.
Keep option namespaces extensible. Prefer object shapes such as {feature: {enabled: true}} instead of direct booleans when future settings are likely.
Common plugin properties:
document: Document actions, badges, production URL resolvers, and new document defaults.form: Form customizations, asset sources, and custom input rendering.plugins: Nested plugins.tools: Studio tools contributed by the plugin.schema: Schema types and initial value templates.studio: Studio component overrides and middleware.i18n: Locale resource bundles used by plugin UI.title: Human-readable plugin name.onUncaughtError: Custom error handling, logging, or telemetry.Use the smallest surface that solves the feature.
A tool is a top-level Studio view with routing and predictable URLs. Tools commonly represent full-screen workflows such as Structure, Vision, Dashboard, or Presentation.
When adding a tool through a plugin:
tools property.name, title, component, and router when needed.studio.components.toolMenu when the visual menu order needs custom rendering.tools reducer pattern when changing the default opened tool, because visual menu order alone does not choose the default route.studio.components can customize parts of the Studio UI. Components that receive renderDefault are middleware: call props.renderDefault(props) unless intentionally replacing the default UI.
Use this for UI wrappers, navigation changes, or tool menu ordering. Be careful not to change scroll containers or layout ownership accidentally.
If a plugin renders UI text, add an i18n bundle instead of hard-coding user-facing strings. The usual file shape is:
In i18n/index.ts, define a namespace and default US English bundle:
In i18n/resources.ts, export the default strings and key type:
Then register the bundle from the plugin:
For Sanity monorepo default plugin wiring, read sanity-core-plugin after this skill.
export const myPlugin = definePlugin<{enabled?: boolean}>((options) => ({
name: 'my-plugin',
tools: options.enabled === false ? [] : [myTool],
}))feature/
├── i18n/
│ ├── index.ts
│ └── resources.ts
└── plugin/
└── index.tsimport {type LocaleResourceBundle} from '../../i18n'
export const featureNamespace: 'feature' = 'feature'
export const featureUsEnglishLocaleBundle: LocaleResourceBundle = {
locale: 'en-US',
namespace: featureNamespace,
resources: () => import('./resources'),
}
export type {FeatureLocaleResourceKeys} from './resources'const featureLocaleStrings = {
'action.example': 'Example',
}
export type FeatureLocaleResourceKeys = keyof typeof featureLocaleStrings
export default featureLocaleStringsimport {featureUsEnglishLocaleBundle} from '../i18n'
export const feature = definePlugin({
name: 'sanity/feature',
i18n: {
bundles: [featureUsEnglishLocaleBundle],
},
})