[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ED03W606350NYAVDD0ASG":3,"skill-same:01M71ED03W606350NYAVDD0ASG":77},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M71ED03W606350NYAVDD0ASG","rover",null,"Guide for using Apollo Rover CLI to manage GraphQL schemas and federation. Use this skill when: (1) publishing or fetching subgraph\u002Fgraph schemas, (2) composing supergraph schemas locally or via GraphOS, (3) running local supergraph development with rover dev, (4) validating schemas with check and lint commands, (5) configuring Rover authentication and environment.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_apollographql_rover\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"commands","manage","for","development","federation","windows","running","macos","graph","guide","edit","node","write","read","cli","Bash","when","local","authentication","2026-11-10 10:12:30",false,"---\nname: rover\ndescription: >\n  Guide for using Apollo Rover CLI to manage GraphQL schemas and federation. Use this skill when:\n  (1) publishing or fetching subgraph\u002Fgraph schemas,\n  (2) composing supergraph schemas locally or via GraphOS,\n  (3) running local supergraph development with rover dev,\n  (4) validating schemas with check and lint commands,\n  (5) configuring Rover authentication and environment.\nlicense: MIT\ncompatibility: Node.js v18+, Linux\u002FmacOS\u002FWindows\nmetadata:\n  author: apollographql\n  version: \"1.0.1\"\nallowed-tools: Bash(rover:*) Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep\n---\n\n# Apollo Rover CLI Guide\n\nRover is the official CLI for Apollo GraphOS. It helps you manage schemas, run composition locally, publish to GraphOS, and develop supergraphs on your local machine.\n\n## Quick Start\n\n### Step 1: Install\n\n```bash\n# macOS\u002FLinux\ncurl -sSL https:\u002F\u002Frover.apollo.dev\u002Fnix\u002Flatest | sh\n\n# npm (cross-platform)\nnpm install -g @apollo\u002Frover\n\n# Windows PowerShell\niwr 'https:\u002F\u002Frover.apollo.dev\u002Fwin\u002Flatest' | iex\n```\n\n### Step 2: Authenticate\n\n```bash\n# Interactive authentication (opens browser)\nrover config auth\n\n# Or set environment variable\nexport APOLLO_KEY=your-api-key\n```\n\n### Step 3: Verify Installation\n\n```bash\nrover --version\nrover config whoami\n```\n\n## Core Commands Overview\n\n| Command | Description | Use Case |\n|---------|-------------|----------|\n| `rover subgraph publish` | Publish subgraph schema to GraphOS | CI\u002FCD, schema updates |\n| `rover subgraph check` | Validate schema changes | PR checks, pre-deploy |\n| `rover subgraph fetch` | Download subgraph schema | Local development |\n| `rover supergraph compose` | Compose supergraph locally | Local testing |\n| `rover dev` | Local supergraph development | Development workflow |\n| `rover graph publish` | Publish monograph schema | Non-federated graphs |\n\n## Graph Reference Format\n\nMost commands require a graph reference in the format:\n\n```\n\u003CGRAPH_ID>@\u003CVARIANT>\n```\n\nExamples:\n- `my-graph@production`\n- `my-graph@staging`\n- `my-graph@current` (default variant)\n\nSet as environment variable:\n```bash\nexport APOLLO_GRAPH_REF=my-graph@production\n```\n\n## Subgraph Workflow\n\n### Publishing a Subgraph\n\n```bash\n# From schema file\nrover subgraph publish my-graph@production \\\n  --name products \\\n  --schema .\u002Fschema.graphql \\\n  --routing-url https:\u002F\u002Fproducts.example.com\u002Fgraphql\n\n# From running server (introspection)\nrover subgraph publish my-graph@production \\\n  --name products \\\n  --schema \u003C(rover subgraph introspect http:\u002F\u002Flocalhost:4001\u002Fgraphql) \\\n  --routing-url https:\u002F\u002Fproducts.example.com\u002Fgraphql\n```\n\n### Checking Schema Changes\n\n```bash\n# Check against production traffic\nrover subgraph check my-graph@production \\\n  --name products \\\n  --schema .\u002Fschema.graphql\n```\n\n### Fetching Schema\n\n```bash\n# Fetch from GraphOS\nrover subgraph fetch my-graph@production --name products\n\n# Introspect running server\nrover subgraph introspect http:\u002F\u002Flocalhost:4001\u002Fgraphql\n```\n\n## Supergraph Composition\n\n### Local Composition\n\nCreate `supergraph.yaml`:\n\n```yaml\nfederation_version: =2.9.0\nsubgraphs:\n  products:\n    routing_url: http:\u002F\u002Flocalhost:4001\u002Fgraphql\n    schema:\n      file: .\u002Fproducts\u002Fschema.graphql\n  reviews:\n    routing_url: http:\u002F\u002Flocalhost:4002\u002Fgraphql\n    schema:\n      subgraph_url: http:\u002F\u002Flocalhost:4002\u002Fgraphql\n```\n\nCompose:\n```bash\nrover supergraph compose --config supergraph.yaml > supergraph.graphql\n```\n\n### Fetch Composed Supergraph\n\n```bash\nrover supergraph fetch my-graph@production\n```\n\n## Local Development with `rover dev`\n\nStart a local Router with automatic schema composition:\n\n```bash\n# Start with supergraph config\nrover dev --supergraph-config supergraph.yaml\n\n# Start with GraphOS variant as base\nrover dev --graph-ref my-graph@staging --supergraph-config local.yaml\n```\n\n### With MCP Integration\n\n```bash\n# Start with MCP server enabled\nrover dev --supergraph-config supergraph.yaml --mcp\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Subgraphs (`references\u002Fsubgraphs.md`) - fetch, publish, check, lint, introspect, delete\n- Graphs (`references\u002Fgraphs.md`) - monograph commands (non-federated)\n- Supergraphs (`references\u002Fsupergraphs.md`) - compose, fetch, config format\n- Dev (`references\u002Fdev.md`) - rover dev for local development\n- Configuration (`references\u002Fconfiguration.md`) - install, auth, env vars, profiles\n\n## Common Patterns\n\n### CI\u002FCD Pipeline\n\n```bash\n# 1. Check schema changes\nrover subgraph check $APOLLO_GRAPH_REF \\\n  --name $SUBGRAPH_NAME \\\n  --schema .\u002Fschema.graphql\n\n# 2. If check passes, publish\nrover subgraph publish $APOLLO_GRAPH_REF \\\n  --name $SUBGRAPH_NAME \\\n  --schema .\u002Fschema.graphql \\\n  --routing-url $ROUTING_URL\n```\n\n### Schema Linting\n\n```bash\n# Lint against GraphOS rules\nrover subgraph lint --name products .\u002Fschema.graphql\n\n# Lint monograph\nrover graph lint my-graph@production .\u002Fschema.graphql\n```\n\n### Output Formats\n\n```bash\n# JSON output for scripting\nrover subgraph fetch my-graph@production --name products --format json\n\n# Plain output (default)\nrover subgraph fetch my-graph@production --name products --format plain\n```\n\n## Ground Rules\n\n- ALWAYS authenticate before using GraphOS commands (`rover config auth` or `APOLLO_KEY`)\n- ALWAYS use the correct graph reference format: `graph@variant`\n- PREFER `rover subgraph check` before `rover subgraph publish` in CI\u002FCD\n- USE `rover dev` for local supergraph development instead of running Router manually\n- NEVER commit `APOLLO_KEY` to version control; use environment variables\n- USE `--format json` when parsing output programmatically\n- SPECIFY `federation_version` explicitly in supergraph.yaml for reproducibility\n- USE `rover subgraph introspect` to extract schemas from running services\n","# Apollo Rover CLI Guide\n\nRover is the official CLI for Apollo GraphOS. It helps you manage schemas, run composition locally, publish to GraphOS, and develop supergraphs on your local machine.\n\n## Quick Start\n\n### Step 1: Install\n\n```bash\n# macOS\u002FLinux\ncurl -sSL https:\u002F\u002Frover.apollo.dev\u002Fnix\u002Flatest | sh\n\n# npm (cross-platform)\nnpm install -g @apollo\u002Frover\n\n# Windows PowerShell\niwr 'https:\u002F\u002Frover.apollo.dev\u002Fwin\u002Flatest' | iex\n```\n\n### Step 2: Authenticate\n\n```bash\n# Interactive authentication (opens browser)\nrover config auth\n\n# Or set environment variable\nexport APOLLO_KEY=your-api-key\n```\n\n### Step 3: Verify Installation\n\n```bash\nrover --version\nrover config whoami\n```\n\n## Core Commands Overview\n\n| Command | Description | Use Case |\n|---------|-------------|----------|\n| `rover subgraph publish` | Publish subgraph schema to GraphOS | CI\u002FCD, schema updates |\n| `rover subgraph check` | Validate schema changes | PR checks, pre-deploy |\n| `rover subgraph fetch` | Download subgraph schema | Local development |\n| `rover supergraph compose` | Compose supergraph locally | Local testing |\n| `rover dev` | Local supergraph development | Development workflow |\n| `rover graph publish` | Publish monograph schema | Non-federated graphs |\n\n## Graph Reference Format\n\nMost commands require a graph reference in the format:\n\n```\n\u003CGRAPH_ID>@\u003CVARIANT>\n```\n\nExamples:\n- `my-graph@production`\n- `my-graph@staging`\n- `my-graph@current` (default variant)\n\nSet as environment variable:\n```bash\nexport APOLLO_GRAPH_REF=my-graph@production\n```\n\n## Subgraph Workflow\n\n### Publishing a Subgraph\n\n```bash\n# From schema file\nrover subgraph publish my-graph@production \\\n  --name products \\\n  --schema .\u002Fschema.graphql \\\n  --routing-url https:\u002F\u002Fproducts.example.com\u002Fgraphql\n\n# From running server (introspection)\nrover subgraph publish my-graph@production \\\n  --name products \\\n  --schema \u003C(rover subgraph introspect http:\u002F\u002Flocalhost:4001\u002Fgraphql) \\\n  --routing-url https:\u002F\u002Fproducts.example.com\u002Fgraphql\n```\n\n### Checking Schema Changes\n\n```bash\n# Check against production traffic\nrover subgraph check my-graph@production \\\n  --name products \\\n  --schema .\u002Fschema.graphql\n```\n\n### Fetching Schema\n\n```bash\n# Fetch from GraphOS\nrover subgraph fetch my-graph@production --name products\n\n# Introspect running server\nrover subgraph introspect http:\u002F\u002Flocalhost:4001\u002Fgraphql\n```\n\n## Supergraph Composition\n\n### Local Composition\n\nCreate `supergraph.yaml`:\n\n```yaml\nfederation_version: =2.9.0\nsubgraphs:\n  products:\n    routing_url: http:\u002F\u002Flocalhost:4001\u002Fgraphql\n    schema:\n      file: .\u002Fproducts\u002Fschema.graphql\n  reviews:\n    routing_url: http:\u002F\u002Flocalhost:4002\u002Fgraphql\n    schema:\n      subgraph_url: http:\u002F\u002Flocalhost:4002\u002Fgraphql\n```\n\nCompose:\n```bash\nrover supergraph compose --config supergraph.yaml > supergraph.graphql\n```\n\n### Fetch Composed Supergraph\n\n```bash\nrover supergraph fetch my-graph@production\n```\n\n## Local Development with `rover dev`\n\nStart a local Router with automatic schema composition:\n\n```bash\n# Start with supergraph config\nrover dev --supergraph-config supergraph.yaml\n\n# Start with GraphOS variant as base\nrover dev --graph-ref my-graph@staging --supergraph-config local.yaml\n```\n\n### With MCP Integration\n\n```bash\n# Start with MCP server enabled\nrover dev --supergraph-config supergraph.yaml --mcp\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Subgraphs (`references\u002Fsubgraphs.md`) - fetch, publish, check, lint, introspect, delete\n- Graphs (`references\u002Fgraphs.md`) - monograph commands (non-federated)\n- Supergraphs (`references\u002Fsupergraphs.md`) - compose, fetch, config format\n- Dev (`references\u002Fdev.md`) - rover dev for local development\n- Configuration (`references\u002Fconfiguration.md`) - install, auth, env vars, profiles\n\n## Common Patterns\n\n### CI\u002FCD Pipeline\n\n```bash\n# 1. Check schema changes\nrover subgraph check $APOLLO_GRAPH_REF \\\n  --name $SUBGRAPH_NAME \\\n  --schema .\u002Fschema.graphql\n\n# 2. If check passes, publish\nrover subgraph publish $APOLLO_GRAPH_REF \\\n  --name $SUBGRAPH_NAME \\\n  --schema .\u002Fschema.graphql \\\n  --routing-url $ROUTING_URL\n```\n\n### Schema Linting\n\n```bash\n# Lint against GraphOS rules\nrover subgraph lint --name products .\u002Fschema.graphql\n\n# Lint monograph\nrover graph lint my-graph@production .\u002Fschema.graphql\n```\n\n### Output Formats\n\n```bash\n# JSON output for scripting\nrover subgraph fetch my-graph@production --name products --format json\n\n# Plain output (default)\nrover subgraph fetch my-graph@production --name products --format plain\n```\n\n## Ground Rules\n\n- ALWAYS authenticate before using GraphOS commands (`rover config auth` or `APOLLO_KEY`)\n- ALWAYS use the correct graph reference format: `graph@variant`\n- PREFER `rover subgraph check` before `rover subgraph publish` in CI\u002FCD\n- USE `rover dev` for local supergraph development instead of running Router manually\n- NEVER commit `APOLLO_KEY` to version control; use environment variables\n- USE `--format json` when parsing output programmatically\n- SPECIFY `federation_version` explicitly in supergraph.yaml for reproducibility\n- USE `rover subgraph introspect` to extract schemas from running services\n",{"name":5,"license":15,"metadata":48,"description":51,"allowed-tools":52,"compatibility":53},{"author":49,"version":50},"apollographql","1.0.1","Guide for using Apollo Rover CLI to manage GraphQL schemas and federation. Use this skill when: (1) publishing or fetching subgraph\u002Fgraph schemas, (2) composing supergraph schemas locally or via GraphOS, (3) running local supergraph development with rover dev, (4) validating schemas with check and lint commands, (5) configuring Rover authentication and environment.\n","Bash(rover:*) Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep","Node.js v18+, Linux\u002FmacOS\u002FWindows","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_apollographql_rover",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill rover",{"tool":69,"command":70},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill rover",{"tool":72,"command":73},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill rover","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_apollographql_rover\u002Fskill.md",true,[],[78,108,130,152,172,195],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"publishedAt":107},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,40,102,103,104,105,106],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":107},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[114],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[88,116,117,92,118,119,120,121,101,122,40,123,102,124,125,126,127,128,129,26],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":107},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[136],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[88,138,139,92,140,121,141,40,142,123,102,143,144,145,146,147,148,149,150,151],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":107},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[158],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[160,92,161,148,162,163,164,165,151,166,167,168,40,169,123,102,170,171,103,88],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":107},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[182,183,184,185,140,186,187,188,26,149,121,189,190,141,191,168,192,193,194,40],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":218},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","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.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[201],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[203,204,205,206,207,98,208,165,209,101,210,211,40,88,212,213,214,215,216,217],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]