Sanity Best Practices
Official Sanity best practices: schemas, GROQ, TypeGen, Visual Editing, framework integrations
- What
- Official Sanity best practices: schemas, GROQ, TypeGen, Visual Editing, framework integrations
- Cost
- Free
- Needs
- none beyond a working agent; a Sanity project to apply the practices to
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official Sanity development best-practices guide, maintained by Sanity itself: schema design (defineType/defineField, validation, deprecation), GROQ query patterns and performance, TypeGen for type safety, Visual Editing and live preview, images and Portable Text, Studio structure, localization, content migrations, Sanity Functions and webhooks, Blueprints (infrastructure as code), and framework integrations — Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Shopify Hydrogen, and the App SDK. Includes hard-won rules: let Sanity generate document IDs, model relationships with references, never serve production video from file assets. No published duplicate. By @sanity-io, listed here with credit to its creator. Honest caveats: it's a reference guide with per-topic files — the agent should load only the one or two matching the task; it covers Sanity's current APIs — older codebases may need the migration guides; it's guidance, not a project generator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Sanity Best Practices is a free Muse skill and the official Sanity development guide, maintained by Sanity itself. It covers schema design, GROQ query patterns and performance, TypeGen for type safety, Visual Editing and live preview, images and Portable Text, Studio structure, localization, content migrations, Functions, webhooks, Blueprints and framework integrations.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 3fe6c8aStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none beyond a working agent; a Sanity project to apply the practices to Install "Sanity Best Practices" for me. Official Sanity best practices: schemas, GROQ, TypeGen, Visual Editing, framework integrations Repository: https://raw.githubusercontent.com/sanity-io/agent-toolkit/3fe6c8a078e6c27bdaedf4d2b4a6229e1d1dbbde/skills/sanity-best-practices/SKILL.md Pinned version: install the code at commit 3fe6c8a078e6c27bdaedf4d2b4a6229e1d1dbbde exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the sanity-io-sanity-best-practices skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "sanity-io-sanity-best-practices". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 3fe6c8a · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.