[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FX922SJS5GMXKBSJ2KB8T":3,"skill-same:01M71FX922SJS5GMXKBSJ2KB8T":74},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M71FX922SJS5GMXKBSJ2KB8T","prisma-database-setup",null,"Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on \"configure postgres\", \"connect to mysql\", \"setup mongodb\", \"sqlite setup\".","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_prisma_prisma_database_setup\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"prisma","prisma database setup","setup","database","guides","sqlite","configure","when","connect","use","new","mongodb","triggers","issues","up","project","for","postgres","databases","setting","2026-11-10 10:12:30",false,"---\nname: prisma-database-setup\ndescription: Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on \"configure postgres\", \"connect to mysql\", \"setup mongodb\", \"sqlite setup\".\nlicense: MIT\nmetadata:\n  author: prisma\n  version: \"7.6.0\"\n---\n\n# Prisma Database Setup\n\nComprehensive guides for configuring Prisma ORM with various database providers.\n\n## When to Apply\n\nReference this skill when:\n- Initializing a new Prisma project\n- Switching database providers\n- Configuring connection strings and environment variables\n- Troubleshooting database connection issues\n- Setting up database-specific features\n- Generating and instantiating Prisma Client\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Provider Guides | CRITICAL | provider names |\n| 2 | Prisma Postgres | HIGH | `prisma-postgres` |\n| 3 | Client Setup | CRITICAL | `prisma-client-setup` |\n\n## System Prerequisites\n\n- **Node.js 20.19.0+**\n- **TypeScript 5.4.0+**\n\n## Bun Runtime\n\nIf you're using Bun, run Prisma CLI commands with `bunx --bun prisma ...` so Prisma uses the Bun runtime instead of falling back to Node.js.\n\n## Supported Databases\n\n| Database | Provider String | Notes |\n|----------|-----------------|-------|\n| PostgreSQL | `postgresql` | Default, full feature support |\n| MySQL | `mysql` | Widespread support, some JSON diffs |\n| SQLite | `sqlite` | Local file-based, no enum\u002Fscalar lists |\n| MongoDB | `mongodb` | Mongo-specific workflow; do not apply SQL driver-adapter guidance |\n| SQL Server | `sqlserver` | Microsoft ecosystem |\n| CockroachDB | `cockroachdb` | Distributed SQL, Postgres-compatible |\n| Prisma Postgres | `postgresql` | Managed serverless database |\n\n## Configuration Files\n\nYour configuration shape depends on the provider and Prisma major version:\n\n1. **All providers** use **`prisma\u002Fschema.prisma`**.\n2. **Prisma 7 SQL setups** typically use **`prisma.config.ts`** for datasource URLs.\n3. **MongoDB projects should stay on Prisma 6.x**, keep `url = env(\"DATABASE_URL\")` in the schema, and continue using the classic MongoDB setup.\n\n## Driver Adapters\n\nThe standard SQL workflow uses a driver adapter. Choose the adapter and driver for your database and pass the adapter to `PrismaClient`.\n\n| Database | Adapter | JS Driver |\n|----------|---------|-----------|\n| PostgreSQL | `@prisma\u002Fadapter-pg` | `pg` |\n| CockroachDB | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (Node.js) | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (edge\u002Fserverless) | `@prisma\u002Fadapter-ppg` | `@prisma\u002Fppg` |\n| MySQL \u002F MariaDB | `@prisma\u002Fadapter-mariadb` | `mariadb` |\n| SQLite | `@prisma\u002Fadapter-better-sqlite3` | `better-sqlite3` |\n| SQLite (Turso\u002FLibSQL) | `@prisma\u002Fadapter-libsql` | `@libsql\u002Fclient` |\n| SQL Server | `@prisma\u002Fadapter-mssql` | `node-mssql` |\n\nMongoDB should not follow the Prisma 7 SQL adapter workflow. Use the latest Prisma 6.x release for MongoDB projects and do not install a SQL `@prisma\u002Fadapter-*` package for it.\n\nExample (PostgreSQL):\n\n```ts\nimport 'dotenv\u002Fconfig'\nimport { PrismaClient } from '..\u002Fgenerated\u002Fclient'\nimport { PrismaPg } from '@prisma\u002Fadapter-pg'\n\nconst adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\nconst prisma = new PrismaClient({ adapter })\n```\n\n## Prisma Client Setup (Required)\n\nPrisma Client must be installed and generated for any database.\n\n1. Install Prisma CLI and Prisma Client:\n   ```bash\n   npm install prisma --save-dev\n   npm install @prisma\u002Fclient\n   ```\n\n1. Add a generator block (`prisma-client` requires an explicit output path):\n   ```prisma\n   generator client {\n     provider = \"prisma-client\"\n     output   = \"..\u002Fgenerated\"\n   }\n   ```\n\n1. Generate Prisma Client:\n   ```bash\n   npx prisma generate\n   ```\n\n1. For SQL providers, instantiate Prisma Client with the database-specific driver adapter:\n   ```typescript\n   import { PrismaClient } from '..\u002Fgenerated\u002Fclient'\n   import { PrismaPg } from '@prisma\u002Fadapter-pg'\n\n   const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\n   const prisma = new PrismaClient({ adapter })\n   ```\n\n1. Re-run `prisma generate` after every schema change.\n\n## Quick Reference\n\n### PostgreSQL\n```prisma\ndatasource db {\n  provider = \"postgresql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MySQL\n```prisma\ndatasource db {\n  provider = \"mysql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### SQLite\n```prisma\ndatasource db {\n  provider = \"sqlite\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MongoDB\n```prisma\ndatasource db {\n  provider = \"mongodb\"\n  url      = env(\"DATABASE_URL\")\n}\n\ngenerator client {\n  provider = \"prisma-client-js\"\n}\n```\n\nFor MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup.\n\n## Rule Files\n\nSee individual rule files for detailed setup instructions:\n\n```\nreferences\u002Fpostgresql.md\nreferences\u002Fmysql.md\nreferences\u002Fsqlite.md\nreferences\u002Fmongodb.md\nreferences\u002Fsqlserver.md\nreferences\u002Fcockroachdb.md\nreferences\u002Fprisma_postgres.md\nreferences\u002Fprisma_client_setup.md\n```\n\n## How to Use\n\nChoose the provider reference file for your database, then apply `references\u002Fprisma_client_setup.md` to complete client generation and adapter setup. For MongoDB, use `references\u002Fmongodb.md` instead of copying the SQL adapter examples or Prisma 7 config pattern.\n","# Prisma Database Setup\n\nComprehensive guides for configuring Prisma ORM with various database providers.\n\n## When to Apply\n\nReference this skill when:\n- Initializing a new Prisma project\n- Switching database providers\n- Configuring connection strings and environment variables\n- Troubleshooting database connection issues\n- Setting up database-specific features\n- Generating and instantiating Prisma Client\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Provider Guides | CRITICAL | provider names |\n| 2 | Prisma Postgres | HIGH | `prisma-postgres` |\n| 3 | Client Setup | CRITICAL | `prisma-client-setup` |\n\n## System Prerequisites\n\n- **Node.js 20.19.0+**\n- **TypeScript 5.4.0+**\n\n## Bun Runtime\n\nIf you're using Bun, run Prisma CLI commands with `bunx --bun prisma ...` so Prisma uses the Bun runtime instead of falling back to Node.js.\n\n## Supported Databases\n\n| Database | Provider String | Notes |\n|----------|-----------------|-------|\n| PostgreSQL | `postgresql` | Default, full feature support |\n| MySQL | `mysql` | Widespread support, some JSON diffs |\n| SQLite | `sqlite` | Local file-based, no enum\u002Fscalar lists |\n| MongoDB | `mongodb` | Mongo-specific workflow; do not apply SQL driver-adapter guidance |\n| SQL Server | `sqlserver` | Microsoft ecosystem |\n| CockroachDB | `cockroachdb` | Distributed SQL, Postgres-compatible |\n| Prisma Postgres | `postgresql` | Managed serverless database |\n\n## Configuration Files\n\nYour configuration shape depends on the provider and Prisma major version:\n\n1. **All providers** use **`prisma\u002Fschema.prisma`**.\n2. **Prisma 7 SQL setups** typically use **`prisma.config.ts`** for datasource URLs.\n3. **MongoDB projects should stay on Prisma 6.x**, keep `url = env(\"DATABASE_URL\")` in the schema, and continue using the classic MongoDB setup.\n\n## Driver Adapters\n\nThe standard SQL workflow uses a driver adapter. Choose the adapter and driver for your database and pass the adapter to `PrismaClient`.\n\n| Database | Adapter | JS Driver |\n|----------|---------|-----------|\n| PostgreSQL | `@prisma\u002Fadapter-pg` | `pg` |\n| CockroachDB | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (Node.js) | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (edge\u002Fserverless) | `@prisma\u002Fadapter-ppg` | `@prisma\u002Fppg` |\n| MySQL \u002F MariaDB | `@prisma\u002Fadapter-mariadb` | `mariadb` |\n| SQLite | `@prisma\u002Fadapter-better-sqlite3` | `better-sqlite3` |\n| SQLite (Turso\u002FLibSQL) | `@prisma\u002Fadapter-libsql` | `@libsql\u002Fclient` |\n| SQL Server | `@prisma\u002Fadapter-mssql` | `node-mssql` |\n\nMongoDB should not follow the Prisma 7 SQL adapter workflow. Use the latest Prisma 6.x release for MongoDB projects and do not install a SQL `@prisma\u002Fadapter-*` package for it.\n\nExample (PostgreSQL):\n\n```ts\nimport 'dotenv\u002Fconfig'\nimport { PrismaClient } from '..\u002Fgenerated\u002Fclient'\nimport { PrismaPg } from '@prisma\u002Fadapter-pg'\n\nconst adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\nconst prisma = new PrismaClient({ adapter })\n```\n\n## Prisma Client Setup (Required)\n\nPrisma Client must be installed and generated for any database.\n\n1. Install Prisma CLI and Prisma Client:\n   ```bash\n   npm install prisma --save-dev\n   npm install @prisma\u002Fclient\n   ```\n\n1. Add a generator block (`prisma-client` requires an explicit output path):\n   ```prisma\n   generator client {\n     provider = \"prisma-client\"\n     output   = \"..\u002Fgenerated\"\n   }\n   ```\n\n1. Generate Prisma Client:\n   ```bash\n   npx prisma generate\n   ```\n\n1. For SQL providers, instantiate Prisma Client with the database-specific driver adapter:\n   ```typescript\n   import { PrismaClient } from '..\u002Fgenerated\u002Fclient'\n   import { PrismaPg } from '@prisma\u002Fadapter-pg'\n\n   const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\n   const prisma = new PrismaClient({ adapter })\n   ```\n\n1. Re-run `prisma generate` after every schema change.\n\n## Quick Reference\n\n### PostgreSQL\n```prisma\ndatasource db {\n  provider = \"postgresql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MySQL\n```prisma\ndatasource db {\n  provider = \"mysql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### SQLite\n```prisma\ndatasource db {\n  provider = \"sqlite\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MongoDB\n```prisma\ndatasource db {\n  provider = \"mongodb\"\n  url      = env(\"DATABASE_URL\")\n}\n\ngenerator client {\n  provider = \"prisma-client-js\"\n}\n```\n\nFor MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup.\n\n## Rule Files\n\nSee individual rule files for detailed setup instructions:\n\n```\nreferences\u002Fpostgresql.md\nreferences\u002Fmysql.md\nreferences\u002Fsqlite.md\nreferences\u002Fmongodb.md\nreferences\u002Fsqlserver.md\nreferences\u002Fcockroachdb.md\nreferences\u002Fprisma_postgres.md\nreferences\u002Fprisma_client_setup.md\n```\n\n## How to Use\n\nChoose the provider reference file for your database, then apply `references\u002Fprisma_client_setup.md` to complete client generation and adapter setup. For MongoDB, use `references\u002Fmongodb.md` instead of copying the SQL adapter examples or Prisma 7 config pattern.\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":24,"version":50},"7.6.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_prisma_prisma_database_setup",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill prisma-database-setup",{"tool":66,"command":67},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill prisma-database-setup",{"tool":69,"command":70},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill prisma-database-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_prisma_prisma_database_setup\u002Fskill.md",true,[],[75,105,127,148,167,186],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":84,"publishedAt":104},"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",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[85,86,87,88,89,90,91,92,93,94,95,96,97,98,31,99,100,101,102,103],"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":104},"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",[111],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},[85,113,114,89,115,116,117,118,98,119,31,120,99,121,122,123,124,125,126,40],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":104},"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",[133],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},[85,135,136,89,137,118,138,31,139,120,99,140,141,142,143,144,145,146,147,36],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":104},"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",[154],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},[156,89,157,145,158,159,160,161,36,162,163,33,31,164,120,99,165,166,100,85],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":104},"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",[173],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[175,176,41,177,137,178,179,180,40,146,118,181,182,138,183,33,184,185,27,31],"postgres best practices","supabase","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":208},"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",[192],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},[194,195,196,197,198,95,199,161,37,98,200,201,31,85,202,203,204,205,206,207],"text","portable text serialization","portable","serialization","extracting","strings","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]