sanity-plugin-rich-table

Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.

Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.

QA review checklist for plans created or edited in Cursor's plan mode. Covers assumption documentation (especially context-specific assumptions like SDK apps vs plain React, data-fetching primitives, framework specifics), risk identification, failure modes, reversibility, and scope boundary clarity. Use after creating or editing any *.plan.md file in .cursor/plans/ (project or user). The companion postToolUse hook auto-fires this skill on plan file writes.

General-purpose QA review checklist for React, TypeScript, and Sanity codebases. Covers systematic review methodology, risk-based prioritisation, type safety, React key management, polymorphic reference handling, GROQ linting, async error handling, accessibility, security, and field rename completeness. Use when reviewing code changes, performing QA audits, checking pull requests, or validating refactors.

Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, or when reviewing and fixing a Sanity codebase.

Build full-bleed Sanity-brand hero / placeholder screens (coming-soon, maintenance, splash, beta-gate, branded error pages) matching the Sanity marketing site aesthetic — black background with dot texture, large bold headline, pill outline buttons. Use when creating any full-bleed branded landing or placeholder UI in SDK apps (`sdk-apps/*`) or Sanity Studios (`studios/*`), or when the user mentions "coming soon", "splash page", "maintenance page", "marketing-style hero", or asks to make a screen feel like sanity.io.

Sanity CLI commands for schema change management: migrations (create, list, run), document validation, schema validation and deployment, dataset export/import, and GROQ queries. Use when running sanity CLI commands, validating documents or schemas, exporting or importing datasets, querying documents from the terminal, or orchestrating migration workflows.

Build content agents on top of Sanity Agent Actions (Generate, Transform, Translate, Prompt, Patch). Covers when to use each action, the `instructionParams` shapes (`constant` / `field` / `document` / `groq`), the two-phase noWrite→write pattern for editor-in-the-loop ingest with clarifications, schema-deploy + embeddings-index prerequisites for reference-aware generation, AI Assist custom field actions for in-Studio refinement, and the `@sanity/agent-context` plugin for read-side scoped MCP endpoints. Use when designing or implementing any flow that reads or writes Sanity content via `client.agent.action.*`, that wires `@sanity/assist` custom field actions, that bootstraps editor-curated context (e.g. a voice/conventions singleton), or that exposes a read-only MCP for external agents.

Sanity content migration patterns using the CLI and defineMigration API from sanity/migrate. Covers field renames, array restructuring, type conversions, Portable Text transforms, async migrations, content releases, dry-run testing, validation, and common pitfalls. Use when writing, running, or debugging content migrations, renaming schema fields, restructuring document data, or running sanity migrations CLI commands.

Sanity History API for reading real document change history — who changed what, and when. Covers the two HTTP endpoints (documents snapshots + transactions log), every query parameter (excludeContent, effectFormat=mendoza, fromTime/toTime, fromTransaction/toTransaction, authors, reverse, limit), the NDJSON transaction shape (id/timestamp/author/mutations/effects/documentIDs), resolving author ids to people, the draft-vs-published + dataset footguns, and how to call it from an SDK app (sdk-apps/*) via client.request or useAuthToken. Use when building change/diff/activity/audit UIs, "who edited this", review surfaces, or anything that needs real revision history rather than a published-vs-draft field diff.

Use the Sanity ID design system to build UI with Sanity's brand components, colors, and typography. Includes 23 React components, TailwindCSS v4 integration, design tokens, and theming support. Use when building interfaces that need Sanity brand consistency, creating marketing pages, or implementing component-based UIs with TypeScript and React.

How to handle Sanity document `_id`s and array `_key`s correctly across every write surface in this repo. Covers why deterministic IDs (hashed emails, derived strings) are an anti-pattern, the reference-field + GROQ-filter pattern that replaces them, and the per-surface mechanism for `_key` generation: `autoGenerateArrayKeys` for `@sanity/client`, automatic key handling in App SDK hooks (`useEditDocument`, `useApplyDocumentActions`), and automatic key handling in `sanity/migrate`. Use when writing or reviewing any code that creates, upserts, or patches Sanity content -- particularly `client.create*`, `client.patch().commit()`, mutations from `@sanity/sdk-react`, or `defineMigration`. Triggers on `_id`, `_key`, `generateKey`, hashed document IDs, `createIfNotExists`, `append/insert/setIfMissing`, and any helper that builds a Sanity `_id` or `_key` from another value.

Display Sanity Media Library videos in a frontend using Mux Player. Covers the recommended GROQ `documents::get()` pattern for fetching playback id + aspect ratio in a single query, the alternative `client.mediaLibrary.video .getPlaybackInfo()` runtime call, schema setup with `defineVideoField`, signed playback handling, and common pitfalls (library-id regex strictness, TypeGen returning `unknown` for cross-resource projections, response shape confusion). Use when adding video playback to an SDK app or web frontend, building a `VideoPlayer` component, fetching `videoAsset` data from a Media Library video field, debugging "Invalid video asset instance identifier" errors, or wiring `@mux/mux-player-react` to Sanity content.

Sanity Media Library integration for centralized asset management across Studios and SDK apps. Covers Studio enablement, per-field filters, aspects, collections, video fields, programmatic uploads, asset linking, and CLI commands. Use when enabling Media Library in a Studio config, adding image or file fields that reference library assets, creating or deploying aspects, writing GROQ queries against library assets, configuring per-app asset scoping, or working with video playback from the library.

How to add, configure, and deploy Sanity Scheduled Functions in this repo. Scheduled functions run on a cron schedule and live on a separate organization-scoped Blueprint stack at `blueprints/scheduled/`, distinct from the project-scoped document functions in the root `sanity.blueprint.ts`. Covers `defineScheduledFunction`, robot tokens, cron expressions / natural-language schedules, the `blueprints promote` one-way migration to org scope, the `scheduledEventHandler` runtime, local `sanity functions dev`, and the per-stack `blueprints plan` / `deploy` workflow. Use when the user asks to schedule a function, run a cron job in Sanity, add a periodic / monthly / daily / hourly task, work with `blueprints/scheduled/sanity.blueprint.ts`, deploy an org-scoped blueprint, or move an existing function from event-triggered to scheduled.

How to recognise, fix, and suppress false-positive warnings from the @sanity-labs/eslint-plugin schema rules — especially the name-based `sanity/schema-heading-level-in-schema` heuristic. Covers where the disable comment must go (above the `defineType` call, not the field), why TypeScript changes cannot silence these rules, the `Rule.custom<T>` generic constraint, and which Portable Text patterns are NOT affected. Use when an ESLint warning from `@sanity-labs/eslint-plugin` looks wrong, when a Sanity schema field is flagged for "appears to store heading levels", when adding a field whose name ends in `Level` / `h1`–`h6`, or when wiring `Rule.custom` validators on enum-typed string fields.

Sanity schema validation patterns for warning vs error severity, chaining Rule methods, and custom validation functions. Use when writing or reviewing defineField validation rules, adding warnings to Sanity schemas, or debugging validation messages that render at the wrong severity level.

Patterns for building Sanity Studio tools, plugins, custom inputs, and document actions using @sanity/ui. Covers component API, layout composition, real-time data, theming, React 19 baseline, and anti-patterns. Sourced from Sanity production apps (Media Library, Canvas) and the Studio codebase.

SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.

Sanity's house style rules based on AP Stylebook with company overrides. Covers capitalization, numbers, punctuation, hyphens, abbreviations, dates, code formatting, and US English spelling. Use when writing, editing, or reviewing any content. Triggers on copy editing, style checking, proofreading, and content review. Layers under authentic-content (voice) and sanity-messaging (positioning) to handle mechanical consistency.

Guides upgrading and refactoring this rich-table plugin's Portable Text editor and Sanity Studio integration — which native @portabletext/* API replaces which hand-rolled code, safe version-pin decisions (@sanity/icons, react-icons, pkg-utils peers), deprecations to avoid, and the verify loop. Use when bumping sanity / @portabletext/* / @sanity/* versions, reviewing PT or Studio code for stale patterns, or deciding whether to hand-roll something vs adopt a native API.