[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DYHQG96APC7EV3FANC90WX":3,"skill-same:01M7DYHQG96APC7EV3FANC90WX":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DYHQG96APC7EV3FANC90WX","portable-text-serialization",null,"Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","vercel\u002Feve","vercel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14985020?v=4","01M75TEEHHNJR9E6CG84ENB3MS","Vercel","01M75TEEJ5BJVTCPRH9YAWSMW4",5902,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.\"\n---\n# Portable Text Serialization\n\nRender Portable Text content across frameworks using the `@portabletext\u002F*` library family. Each library follows the same component-mapping pattern: you provide a `components` object that maps PT node types to framework-specific renderers.\n\n## Portable Text Structure (Quick Reference)\n\nPT is an array of blocks. Each block has `_type`, optional `style`, `children` (spans), `markDefs`, `listItem`, and `level`.\n\n```\nRoot array\n├── block (_type: \"block\")\n│   ├── style: \"normal\" | \"h1\" | \"h2\" | \"blockquote\" | ...\n│   ├── children: [span, span, ...]\n│   │   └── span: { _type: \"span\", text: \"...\", marks: [\"strong\", \"\u003CmarkDefKey>\"] }\n│   ├── markDefs: [{ _key, _type: \"link\", href: \"...\" }, ...]\n│   ├── listItem: \"bullet\" | \"number\" (optional)\n│   └── level: 1, 2, 3... (optional, for nested lists)\n├── custom block (_type: \"image\" | \"code\" | any custom type)\n└── ...more blocks\n```\n\n**Marks** come in two forms:\n- **Decorators**: string values in `marks[]` like `\"strong\"`, `\"em\"`, `\"underline\"`, `\"code\"`\n- **Annotations**: keys in `marks[]` referencing entries in `markDefs[]` (e.g., links, internal references)\n\n## Component Mapping Pattern (All Frameworks)\n\nEvery `@portabletext\u002F*` library accepts a `components` object with these keys:\n\n| Key | Renders | Props\u002FData |\n|-----|---------|------------|\n| `types` | Custom block\u002Finline types (image, code, CTA) | `value` (the block data) |\n| `marks` | Decorators + annotations | `children` + `value` (mark data) |\n| `block` | Block styles (h1, normal, blockquote) | `children` |\n| `list` | List wrappers (ul, ol) | `children` |\n| `listItem` | List items | `children` |\n| `hardBreak` | Line breaks within a block | — |\n\n## Framework-Specific Rules\n\nRead the rule file matching your framework:\n\n- **React \u002F Next.js**: `rules\u002Freact.md` — `@portabletext\u002Freact` or `next-sanity`\n- **Svelte \u002F SvelteKit**: `rules\u002Fsvelte.md` — `@portabletext\u002Fsvelte`\n- **Vue \u002F Nuxt**: `rules\u002Fvue.md` — `@portabletext\u002Fvue`\n- **Astro**: `rules\u002Fastro.md` — `astro-portabletext`\n- **HTML (server-side)**: `rules\u002Fhtml.md` — `@portabletext\u002Fto-html`\n- **Markdown**: `rules\u002Fmarkdown.md` — `@portabletext\u002Fmarkdown`\n- **Plain text extraction**: `rules\u002Fplain-text.md` — `@portabletext\u002Ftoolkit`\n\n### Additional Community Serializers\n\nThese are listed on [portabletext.org](https:\u002F\u002Fwww.portabletext.org\u002Fintegrations\u002Fserializers\u002F) but don't have dedicated rule files:\n\n| Target | Package |\n|--------|---------|\n| React Native | `@portabletext\u002Freact-native-portabletext` |\n| React PDF | `@portabletext\u002Freact-pdf-portabletext` |\n| Solid | `solid-portabletext` |\n| Qwik | `portabletext-qwik` |\n| Shopify Liquid | `portable-text-to-liquid` |\n| PHP | `sanity-php` (SanityBlockContent class) |\n| Python | `portabletext-html` |\n| C# \u002F .NET | `dotnet-portable-text` |\n| Dart \u002F Flutter | `flutter_sanity_portable_text` |\n\n## Common Patterns (All Frameworks)\n\n### Custom Types Need Explicit Components\n\nPT renderers only handle standard blocks by default. Custom types (`image`, `code`, `callToAction`, etc.) require explicit component mappings — they won't render otherwise.\n\n### Keep Components Object Stable\n\nIn React\u002FVue, define `components` outside the render function or memoize it. Recreating on every render causes unnecessary re-renders.\n\n### Handle Missing Components Gracefully\n\nAll libraries accept `onMissingComponent` to control behavior when encountering unknown types:\n- `false` — suppress warnings\n- Custom function — log or report\n\n### Querying PT with GROQ\n\nAlways expand references inside custom blocks:\n\n```groq\nbody[]{\n  ...,\n  _type == \"image\" => {\n    ...,\n    asset->\n  },\n  markDefs[]{\n    ...,\n    _type == \"internalLink\" => {\n      ...,\n      \"slug\": @.reference->slug.current\n    }\n  }\n}\n```\n","# Portable Text Serialization\n\nRender Portable Text content across frameworks using the `@portabletext\u002F*` library family. Each library follows the same component-mapping pattern: you provide a `components` object that maps PT node types to framework-specific renderers.\n\n## Portable Text Structure (Quick Reference)\n\nPT is an array of blocks. Each block has `_type`, optional `style`, `children` (spans), `markDefs`, `listItem`, and `level`.\n\n```\nRoot array\n├── block (_type: \"block\")\n│   ├── style: \"normal\" | \"h1\" | \"h2\" | \"blockquote\" | ...\n│   ├── children: [span, span, ...]\n│   │   └── span: { _type: \"span\", text: \"...\", marks: [\"strong\", \"\u003CmarkDefKey>\"] }\n│   ├── markDefs: [{ _key, _type: \"link\", href: \"...\" }, ...]\n│   ├── listItem: \"bullet\" | \"number\" (optional)\n│   └── level: 1, 2, 3... (optional, for nested lists)\n├── custom block (_type: \"image\" | \"code\" | any custom type)\n└── ...more blocks\n```\n\n**Marks** come in two forms:\n- **Decorators**: string values in `marks[]` like `\"strong\"`, `\"em\"`, `\"underline\"`, `\"code\"`\n- **Annotations**: keys in `marks[]` referencing entries in `markDefs[]` (e.g., links, internal references)\n\n## Component Mapping Pattern (All Frameworks)\n\nEvery `@portabletext\u002F*` library accepts a `components` object with these keys:\n\n| Key | Renders | Props\u002FData |\n|-----|---------|------------|\n| `types` | Custom block\u002Finline types (image, code, CTA) | `value` (the block data) |\n| `marks` | Decorators + annotations | `children` + `value` (mark data) |\n| `block` | Block styles (h1, normal, blockquote) | `children` |\n| `list` | List wrappers (ul, ol) | `children` |\n| `listItem` | List items | `children` |\n| `hardBreak` | Line breaks within a block | — |\n\n## Framework-Specific Rules\n\nRead the rule file matching your framework:\n\n- **React \u002F Next.js**: `rules\u002Freact.md` — `@portabletext\u002Freact` or `next-sanity`\n- **Svelte \u002F SvelteKit**: `rules\u002Fsvelte.md` — `@portabletext\u002Fsvelte`\n- **Vue \u002F Nuxt**: `rules\u002Fvue.md` — `@portabletext\u002Fvue`\n- **Astro**: `rules\u002Fastro.md` — `astro-portabletext`\n- **HTML (server-side)**: `rules\u002Fhtml.md` — `@portabletext\u002Fto-html`\n- **Markdown**: `rules\u002Fmarkdown.md` — `@portabletext\u002Fmarkdown`\n- **Plain text extraction**: `rules\u002Fplain-text.md` — `@portabletext\u002Ftoolkit`\n\n### Additional Community Serializers\n\nThese are listed on [portabletext.org](https:\u002F\u002Fwww.portabletext.org\u002Fintegrations\u002Fserializers\u002F) but don't have dedicated rule files:\n\n| Target | Package |\n|--------|---------|\n| React Native | `@portabletext\u002Freact-native-portabletext` |\n| React PDF | `@portabletext\u002Freact-pdf-portabletext` |\n| Solid | `solid-portabletext` |\n| Qwik | `portabletext-qwik` |\n| Shopify Liquid | `portable-text-to-liquid` |\n| PHP | `sanity-php` (SanityBlockContent class) |\n| Python | `portabletext-html` |\n| C# \u002F .NET | `dotnet-portable-text` |\n| Dart \u002F Flutter | `flutter_sanity_portable_text` |\n\n## Common Patterns (All Frameworks)\n\n### Custom Types Need Explicit Components\n\nPT renderers only handle standard blocks by default. Custom types (`image`, `code`, `callToAction`, etc.) require explicit component mappings — they won't render otherwise.\n\n### Keep Components Object Stable\n\nIn React\u002FVue, define `components` outside the render function or memoize it. Recreating on every render causes unnecessary re-renders.\n\n### Handle Missing Components Gracefully\n\nAll libraries accept `onMissingComponent` to control behavior when encountering unknown types:\n- `false` — suppress warnings\n- Custom function — log or report\n\n### Querying PT with GROQ\n\nAlways expand references inside custom blocks:\n\n```groq\nbody[]{\n  ...,\n  _type == \"image\" => {\n    ...,\n    asset->\n  },\n  markDefs[]{\n    ...,\n    _type == \"internalLink\" => {\n      ...,\n      \"slug\": @.reference->slug.current\n    }\n  }\n}\n```\n",{"description":7},"main","2e99dc3564dd243224e74b970a3c990b625cc8c0","apps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization",656,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve","https:\u002F\u002Feve.dev","https:\u002F\u002Fgithub.com\u002Fvercel","https:\u002F\u002Fvercel.com","Agentic infrastructure for every app and agent.","2026-11-15 05:08:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vercel\u002Feve --skill portable-text-serialization",{"tool":40,"command":41},"bunx","bunx skills add vercel\u002Feve --skill portable-text-serialization",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vercel\u002Feve --skill portable-text-serialization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002FSKILL.md",true,[48,54,58,62,66,70,74],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"rules\u002Fastro.md","REFERENCE","参考文档",2341,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002Frules\u002Fastro.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"rules\u002Fhtml.md",3170,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002Frules\u002Fhtml.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"rules\u002Fmarkdown.md",3918,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002Frules\u002Fmarkdown.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"rules\u002Fplain-text.md",1698,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002Frules\u002Fplain-text.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"rules\u002Freact.md",3621,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002Frules\u002Freact.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"rules\u002Fsvelte.md",2741,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002Frules\u002Fsvelte.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"rules\u002Fvue.md",3110,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002Frules\u002Fvue.md",[79,86,92,99,106,113],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DYJETPKENT6T9THCB7WKFD","writing-quality","The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fsubagents\u002Freviewer\u002Fskills\u002Fwriting-quality\u002FSKILL.md",[],[],{"skillNo":87,"name":81,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DYJAZM6Y5VNF2PCM01N145","Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fwriting-quality\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DYJ40G4YADA5P8YAEQ7W7F","seo-aeo-best-practices","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.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fseo-aeo-best-practices\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DYHX5JXJFHF2DZV64VFC13","sanity-best-practices","Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, 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, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity\u002Ffunctions, @sanity\u002Fblueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fsanity-best-practices\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7DYHJJ89WGRXXVWJAQNQW9M","portable-text-conversion","Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext\u002Fmarkdown (markdownToPortableText), @portabletext\u002Fblock-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-conversion\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7DYHDTV4WAFQ2YPK5HAHASE","content-modeling-best-practices","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.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fcontent-modeling-best-practices\u002FSKILL.md",[],[]]