[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P2WST0X0AS95C6VHQN11P":3,"skill-same:01M71P2WST0X0AS95C6VHQN11P":69},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M71P2WST0X0AS95C6VHQN11P","portable-text-conversion",null,"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.","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\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_conversion\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"text","portable text conversion","portable","conversion","blocks","block","markdown","sanity","markdown content","specification","convert","when","documents","Legacy","use","ingest","custom","manual","for","rich","2026-11-10 10:56:23",false,"---\nname: portable-text-conversion\ndescription: 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.\nlicense: MIT\nmetadata:\n  author: sanity\n  version: \"1.0.0\"\n---\n\n# Portable Text Conversion\n\nConvert external content (HTML, Markdown) into Portable Text for Sanity. Three main approaches:\n\n1. **`markdownToPortableText`** — Convert Markdown directly using `@portabletext\u002Fmarkdown` (recommended for Markdown)\n2. **`htmlToBlocks`** — Parse HTML into PT blocks using `@portabletext\u002Fblock-tools` (for HTML migration)\n3. **Manual construction** — Build PT blocks directly from any source (APIs, databases, etc.)\n\n## Portable Text Specification\n\nUnderstand the target format before converting. PT is an array of blocks:\n\n```json\n[\n  {\n    \"_type\": \"block\",\n    \"_key\": \"abc123\",\n    \"style\": \"normal\",\n    \"children\": [\n      {\"_type\": \"span\", \"_key\": \"def456\", \"text\": \"Hello \", \"marks\": []},\n      {\"_type\": \"span\", \"_key\": \"ghi789\", \"text\": \"world\", \"marks\": [\"strong\"]}\n    ],\n    \"markDefs\": []\n  },\n  {\n    \"_type\": \"block\",\n    \"_key\": \"jkl012\",\n    \"style\": \"h2\",\n    \"children\": [\n      {\"_type\": \"span\", \"_key\": \"mno345\", \"text\": \"A heading\", \"marks\": []}\n    ],\n    \"markDefs\": []\n  },\n  {\n    \"_type\": \"image\",\n    \"_key\": \"pqr678\",\n    \"asset\": {\"_type\": \"reference\", \"_ref\": \"image-abc-200x200-png\"}\n  }\n]\n```\n\n**Key rules:**\n- Every block and span needs `_key` (unique within the array)\n- `_type: \"block\"` is for text blocks; custom types use their own `_type`\n- `markDefs` holds annotation data; `marks` on spans reference `markDefs[*]._key` or are decorator strings\n- Lists use `listItem` (\"bullet\" | \"number\") and `level` (1, 2, 3...) on regular blocks\n\n## Conversion Rules\n\nRead the rule file matching your source format:\n\n- **Markdown → Portable Text**: `rules\u002Fmarkdown_to_pt.md` — `@portabletext\u002Fmarkdown` with `markdownToPortableText` (recommended)\n- **HTML → Portable Text**: `rules\u002Fhtml_to_pt.md` — `@portabletext\u002Fblock-tools` with `htmlToBlocks`\n- **Manual PT Construction**: `rules\u002Fmanual_construction.md` — build blocks programmatically from any source\n\n> **Note:** `@sanity\u002Fblock-tools` is the legacy package name. Always use `@portabletext\u002Fblock-tools` for new projects. The API is the same.\n","# Portable Text Conversion\n\nConvert external content (HTML, Markdown) into Portable Text for Sanity. Three main approaches:\n\n1. **`markdownToPortableText`** — Convert Markdown directly using `@portabletext\u002Fmarkdown` (recommended for Markdown)\n2. **`htmlToBlocks`** — Parse HTML into PT blocks using `@portabletext\u002Fblock-tools` (for HTML migration)\n3. **Manual construction** — Build PT blocks directly from any source (APIs, databases, etc.)\n\n## Portable Text Specification\n\nUnderstand the target format before converting. PT is an array of blocks:\n\n```json\n[\n  {\n    \"_type\": \"block\",\n    \"_key\": \"abc123\",\n    \"style\": \"normal\",\n    \"children\": [\n      {\"_type\": \"span\", \"_key\": \"def456\", \"text\": \"Hello \", \"marks\": []},\n      {\"_type\": \"span\", \"_key\": \"ghi789\", \"text\": \"world\", \"marks\": [\"strong\"]}\n    ],\n    \"markDefs\": []\n  },\n  {\n    \"_type\": \"block\",\n    \"_key\": \"jkl012\",\n    \"style\": \"h2\",\n    \"children\": [\n      {\"_type\": \"span\", \"_key\": \"mno345\", \"text\": \"A heading\", \"marks\": []}\n    ],\n    \"markDefs\": []\n  },\n  {\n    \"_type\": \"image\",\n    \"_key\": \"pqr678\",\n    \"asset\": {\"_type\": \"reference\", \"_ref\": \"image-abc-200x200-png\"}\n  }\n]\n```\n\n**Key rules:**\n- Every block and span needs `_key` (unique within the array)\n- `_type: \"block\"` is for text blocks; custom types use their own `_type`\n- `markDefs` holds annotation data; `marks` on spans reference `markDefs[*]._key` or are decorator strings\n- Lists use `listItem` (\"bullet\" | \"number\") and `level` (1, 2, 3...) on regular blocks\n\n## Conversion Rules\n\nRead the rule file matching your source format:\n\n- **Markdown → Portable Text**: `rules\u002Fmarkdown_to_pt.md` — `@portabletext\u002Fmarkdown` with `markdownToPortableText` (recommended)\n- **HTML → Portable Text**: `rules\u002Fhtml_to_pt.md` — `@portabletext\u002Fblock-tools` with `htmlToBlocks`\n- **Manual PT Construction**: `rules\u002Fmanual_construction.md` — build blocks programmatically from any source\n\n> **Note:** `@sanity\u002Fblock-tools` is the legacy package name. Always use `@portabletext\u002Fblock-tools` for new projects. The API is the same.\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":26,"version":45},"1.0.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_conversion",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill portable-text-conversion",{"tool":61,"command":62},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill portable-text-conversion",{"tool":64,"command":65},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill portable-text-conversion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_conversion\u002Fskill.md",true,[],[70,102,124,146,165,188],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":101},"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",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[82,83,84,85,86,87,88,89,90,91,92,93,94,95,30,96,97,98,99,100],"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":101},"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",[108],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[82,110,111,86,112,113,114,115,95,116,30,117,96,118,119,120,121,122,123,37],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":101},"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",[130],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[82,132,133,86,134,115,135,30,136,117,96,137,138,139,140,141,142,143,144,145],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":101},"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",[152],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[154,86,155,142,156,157,158,159,145,160,161,33,30,162,117,96,163,164,97,82],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":101},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口",[175,176,177,178,134,179,180,181,37,143,115,182,183,135,184,33,185,186,187,30],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":39},"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",[194],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[19,196,21,197,198,92,199,159,200,95,201,202,30,82,26,203,204,25,205,206],"portable text serialization","serialization","extracting","strings","issues","frontend","svelte","astro","server","rendering","vue"]