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:
Install
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://github.com/sanity-io/agent-toolkit/blob/main/skills/sanity-best-practices/SKILL.md 1. Fetch the SKILL.md file for the sanity-io-sanity-best-practices skill from the repository into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.