[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FSKDES37WX0DSJSVCQS6E":3,"skill-same:01M71FSKDES37WX0DSJSVCQS6E":70},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71FSKDES37WX0DSJSVCQS6E","mastra",null,"Comprehensive Mastra framework guide. Teaches how to find current documentation, verify API signatures, and build agents and workflows. Covers documentation lookup strategies (embedded docs, remote docs), core concepts (agents vs workflows, tools, memory, RAG), TypeScript requirements, and common patterns. Use this skill for all Mastra development to ensure you're using current APIs from the installed version or latest documentation.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_mastra_ai_mastra\u002Fskill.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"documentation","framework","guide","Tools","concepts","patterns","typescript","rag","how","strategies","common","api","you","workflows","remote","how to","signatures","re","memory","2026-11-10 10:12:30",false,"---\nname: mastra\ndescription: \"Comprehensive Mastra framework guide. Teaches how to find current documentation, verify API signatures, and build agents and workflows. Covers documentation lookup strategies (embedded docs, remote docs), core concepts (agents vs workflows, tools, memory, RAG), TypeScript requirements, and common patterns. Use this skill for all Mastra development to ensure you're using current APIs from the installed version or latest documentation.\"\nlicense: Apache-2.0\nmetadata:\n  author: Mastra\n  version: \"2.0.0\"\n  repository: https:\u002F\u002Fgithub.com\u002Fmastra-ai\u002Fskills\n---\n\n# Mastra Framework Guide\n\nBuild AI applications with Mastra. This skill teaches you how to find current documentation and build agents and workflows.\n\n## ⚠️ Critical: Do not trust internal knowledge\n\nEverything you know about Mastra is likely outdated or wrong. Never rely on memory. Always verify against current documentation.\n\nYour training data contains obsolete APIs, deprecated patterns, and incorrect usage. Mastra evolves rapidly - APIs change between versions, constructor signatures shift, and patterns get refactored.\n\n## Prerequisites\n\nBefore writing any Mastra code, check if packages are installed:\n\n```bash\nls node_modules\u002F@mastra\u002F\n```\n\n- **If packages exist:** Use embedded docs first (most reliable)\n- **If no packages:** Install first or use remote docs\n\n## Available files\n\n### References\n\n| User Question                       | First Check                                                      | How To                                         |\n| ----------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------- |\n| \"Create\u002Finstall Mastra project\"     | `references\u002Fcreate_mastra.md` (`references\u002Fcreate_mastra.md`)     | Setup guide with CLI and manual steps          |\n| \"How do I use Agent\u002FWorkflow\u002FTool?\" | `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)     | Look up in `node_modules\u002F@mastra\u002F*\u002Fdist\u002Fdocs\u002F` |\n| \"How do I use X?\" (no packages)     | `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)         | Fetch from `https:\u002F\u002Fmastra.ai\u002Fllms.txt`        |\n| \"I'm getting an error...\"           | `references\u002Fcommon_errors.md` (`references\u002Fcommon_errors.md`)     | Common errors and solutions                    |\n| \"Upgrade from v0.x to v1.x\"         | `references\u002Fmigration_guide.md` (`references\u002Fmigration_guide.md`) | Version upgrade workflows                      |\n\n### Scripts\n\n- `scripts\u002Fprovider-registry.mjs`: Look up current providers and models available in the model router. Always run this before using a model to verify provider keys and model names.\n\n## Priority order for writing code\n\n⚠️ Never write code without checking current docs first.\n\n1. **Embedded docs first** (if packages installed)\n\n   Look up current docs in `node_modules` for a package. Example of looking up \"Agent\" docs in `@mastra\u002Fcore`:\n\n   ```bash\n   grep -r \"Agent\" node_modules\u002F@mastra\u002Fcore\u002Fdist\u002Fdocs\u002Freferences\n   ```\n\n   - **Why:** Matches your EXACT installed version\n   - **Most reliable source of truth**\n   - **More information:** `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)\n\n2. **Source code second** (if packages installed)\n\n   If you can't find what you need in the embedded docs, look directly at the source code. This is more time consuming but can provide insights into implementation details.\n\n   ```bash\n   # Check what's available\n   cat node_modules\u002F@mastra\u002Fcore\u002Fdist\u002Fdocs\u002Fassets\u002FSOURCE_MAP.json | grep '\"Agent\"'\n\n   # Read the actual type definition\n   cat node_modules\u002F@mastra\u002Fcore\u002Fdist\u002F[path-from-source-map]\n   ```\n\n   - **Why:** Ultimate source of truth if docs are missing or unclear\n   - **Use when:** Embedded docs don't cover your question\n   - **More information:** `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)\n\n3. **Remote docs third** (if packages not installed)\n\n   You can fetch the latest docs from the Mastra website:\n\n   ```bash\n   https:\u002F\u002Fmastra.ai\u002Fllms.txt\n   ```\n\n   - **Why:** Latest published docs (may be ahead of installed version)\n   - **Use when:** Packages not installed or exploring new features\n   - **More information:** `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)\n\n## Core concepts\n\n### Agents vs workflows\n\n**Agent**: Autonomous, makes decisions, uses tools\nUse for: Open-ended tasks (support, research, analysis)\n\n**Workflow**: Structured sequence of steps\nUse for: Defined processes (pipelines, approvals, ETL)\n\n### Key components\n\n- **Tools**: Extend agent capabilities (APIs, databases, external services)\n- **Memory**: Maintain context (message history, working memory, semantic recall, observational memory)\n- **RAG**: Query external knowledge (vector stores, graph relationships)\n- **Storage**: Persist data (Postgres, LibSQL, MongoDB)\n\n### Mastra Studio\n\nStudio provides an interactive UI for building, testing, and managing agents, workflows, and tools. It helps with debugging and improving your applications iteratively.\n\nInside a Mastra project, run:\n\n```bash\nnpm run dev\n```\n\nThen open `http:\u002F\u002Flocalhost:4111` in your browser to access Mastra Studio.\n\n## Critical requirements\n\n### TypeScript config\n\nMastra requires **ES2022 modules**. CommonJS will fail.\n\n```json\n{\n  \"compilerOptions\": {\n    \"target\": \"ES2022\",\n    \"module\": \"ES2022\",\n    \"moduleResolution\": \"bundler\"\n  }\n}\n```\n\n### Model format\n\nAlways use `\"provider\u002Fmodel-name\"` when defining models using Mastra's model router.\n\nUse the provider registry script to look up available providers and models:\n\n```bash\n# List all available providers\nnode scripts\u002Fprovider-registry.mjs --list\n\n# List all models for a specific provider (sorted newest first)\nnode scripts\u002Fprovider-registry.mjs --provider openai\nnode scripts\u002Fprovider-registry.mjs --provider anthropic\n```\n\nWhen the user asks to use a model or provider, **always run the script first** to verify the provider key and model name are valid. Do not guess model names from memory as they change frequently.\n\nExample model strings:\n\n- `\"openai\u002Fgpt-5.4\"`\n- `\"anthropic\u002Fclaude-sonnet-4-5\"`\n- `\"google\u002Fgemini-2.5-pro\"`\n\n## When you see errors\n\n**Type errors often mean your knowledge is outdated.**\n\n**Common signs of outdated knowledge:**\n\n- `Property X does not exist on type Y`\n- `Cannot find module`\n- `Type mismatch` errors\n- Constructor parameter errors\n\n**What to do:**\n\n1. Check `references\u002Fcommon_errors.md` (`references\u002Fcommon_errors.md`)\n2. Verify current API in embedded docs\n3. Don't assume the error is a user mistake - it might be your outdated knowledge\n\n## Development workflow\n\n**Always verify before writing code:**\n\n1. **Check packages installed**\n\n   ```bash\n   ls node_modules\u002F@mastra\u002F\n   ```\n\n2. **Look up current API**\n   - If installed → Use embedded docs `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)\n   - If not → Use remote docs `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)\n\n3. **Write code based on current docs**\n\n4. **Test in Studio**\n   ```bash\n   npm run dev  # http:\u002F\u002Flocalhost:4111\n   ```\n\n## Resources\n\n- **Setup**: `references\u002Fcreate_mastra.md` (`references\u002Fcreate_mastra.md`)\n- **Embedded docs lookup**: `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`) - Start here if packages are installed\n- **Remote docs lookup**: `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)\n- **Common errors**: `references\u002Fcommon_errors.md` (`references\u002Fcommon_errors.md`)\n- **Migrations**: `references\u002Fmigration_guide.md` (`references\u002Fmigration_guide.md`)\n","# Mastra Framework Guide\n\nBuild AI applications with Mastra. This skill teaches you how to find current documentation and build agents and workflows.\n\n## ⚠️ Critical: Do not trust internal knowledge\n\nEverything you know about Mastra is likely outdated or wrong. Never rely on memory. Always verify against current documentation.\n\nYour training data contains obsolete APIs, deprecated patterns, and incorrect usage. Mastra evolves rapidly - APIs change between versions, constructor signatures shift, and patterns get refactored.\n\n## Prerequisites\n\nBefore writing any Mastra code, check if packages are installed:\n\n```bash\nls node_modules\u002F@mastra\u002F\n```\n\n- **If packages exist:** Use embedded docs first (most reliable)\n- **If no packages:** Install first or use remote docs\n\n## Available files\n\n### References\n\n| User Question                       | First Check                                                      | How To                                         |\n| ----------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------- |\n| \"Create\u002Finstall Mastra project\"     | `references\u002Fcreate_mastra.md` (`references\u002Fcreate_mastra.md`)     | Setup guide with CLI and manual steps          |\n| \"How do I use Agent\u002FWorkflow\u002FTool?\" | `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)     | Look up in `node_modules\u002F@mastra\u002F*\u002Fdist\u002Fdocs\u002F` |\n| \"How do I use X?\" (no packages)     | `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)         | Fetch from `https:\u002F\u002Fmastra.ai\u002Fllms.txt`        |\n| \"I'm getting an error...\"           | `references\u002Fcommon_errors.md` (`references\u002Fcommon_errors.md`)     | Common errors and solutions                    |\n| \"Upgrade from v0.x to v1.x\"         | `references\u002Fmigration_guide.md` (`references\u002Fmigration_guide.md`) | Version upgrade workflows                      |\n\n### Scripts\n\n- `scripts\u002Fprovider-registry.mjs`: Look up current providers and models available in the model router. Always run this before using a model to verify provider keys and model names.\n\n## Priority order for writing code\n\n⚠️ Never write code without checking current docs first.\n\n1. **Embedded docs first** (if packages installed)\n\n   Look up current docs in `node_modules` for a package. Example of looking up \"Agent\" docs in `@mastra\u002Fcore`:\n\n   ```bash\n   grep -r \"Agent\" node_modules\u002F@mastra\u002Fcore\u002Fdist\u002Fdocs\u002Freferences\n   ```\n\n   - **Why:** Matches your EXACT installed version\n   - **Most reliable source of truth**\n   - **More information:** `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)\n\n2. **Source code second** (if packages installed)\n\n   If you can't find what you need in the embedded docs, look directly at the source code. This is more time consuming but can provide insights into implementation details.\n\n   ```bash\n   # Check what's available\n   cat node_modules\u002F@mastra\u002Fcore\u002Fdist\u002Fdocs\u002Fassets\u002FSOURCE_MAP.json | grep '\"Agent\"'\n\n   # Read the actual type definition\n   cat node_modules\u002F@mastra\u002Fcore\u002Fdist\u002F[path-from-source-map]\n   ```\n\n   - **Why:** Ultimate source of truth if docs are missing or unclear\n   - **Use when:** Embedded docs don't cover your question\n   - **More information:** `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)\n\n3. **Remote docs third** (if packages not installed)\n\n   You can fetch the latest docs from the Mastra website:\n\n   ```bash\n   https:\u002F\u002Fmastra.ai\u002Fllms.txt\n   ```\n\n   - **Why:** Latest published docs (may be ahead of installed version)\n   - **Use when:** Packages not installed or exploring new features\n   - **More information:** `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)\n\n## Core concepts\n\n### Agents vs workflows\n\n**Agent**: Autonomous, makes decisions, uses tools\nUse for: Open-ended tasks (support, research, analysis)\n\n**Workflow**: Structured sequence of steps\nUse for: Defined processes (pipelines, approvals, ETL)\n\n### Key components\n\n- **Tools**: Extend agent capabilities (APIs, databases, external services)\n- **Memory**: Maintain context (message history, working memory, semantic recall, observational memory)\n- **RAG**: Query external knowledge (vector stores, graph relationships)\n- **Storage**: Persist data (Postgres, LibSQL, MongoDB)\n\n### Mastra Studio\n\nStudio provides an interactive UI for building, testing, and managing agents, workflows, and tools. It helps with debugging and improving your applications iteratively.\n\nInside a Mastra project, run:\n\n```bash\nnpm run dev\n```\n\nThen open `http:\u002F\u002Flocalhost:4111` in your browser to access Mastra Studio.\n\n## Critical requirements\n\n### TypeScript config\n\nMastra requires **ES2022 modules**. CommonJS will fail.\n\n```json\n{\n  \"compilerOptions\": {\n    \"target\": \"ES2022\",\n    \"module\": \"ES2022\",\n    \"moduleResolution\": \"bundler\"\n  }\n}\n```\n\n### Model format\n\nAlways use `\"provider\u002Fmodel-name\"` when defining models using Mastra's model router.\n\nUse the provider registry script to look up available providers and models:\n\n```bash\n# List all available providers\nnode scripts\u002Fprovider-registry.mjs --list\n\n# List all models for a specific provider (sorted newest first)\nnode scripts\u002Fprovider-registry.mjs --provider openai\nnode scripts\u002Fprovider-registry.mjs --provider anthropic\n```\n\nWhen the user asks to use a model or provider, **always run the script first** to verify the provider key and model name are valid. Do not guess model names from memory as they change frequently.\n\nExample model strings:\n\n- `\"openai\u002Fgpt-5.4\"`\n- `\"anthropic\u002Fclaude-sonnet-4-5\"`\n- `\"google\u002Fgemini-2.5-pro\"`\n\n## When you see errors\n\n**Type errors often mean your knowledge is outdated.**\n\n**Common signs of outdated knowledge:**\n\n- `Property X does not exist on type Y`\n- `Cannot find module`\n- `Type mismatch` errors\n- Constructor parameter errors\n\n**What to do:**\n\n1. Check `references\u002Fcommon_errors.md` (`references\u002Fcommon_errors.md`)\n2. Verify current API in embedded docs\n3. Don't assume the error is a user mistake - it might be your outdated knowledge\n\n## Development workflow\n\n**Always verify before writing code:**\n\n1. **Check packages installed**\n\n   ```bash\n   ls node_modules\u002F@mastra\u002F\n   ```\n\n2. **Look up current API**\n   - If installed → Use embedded docs `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`)\n   - If not → Use remote docs `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)\n\n3. **Write code based on current docs**\n\n4. **Test in Studio**\n   ```bash\n   npm run dev  # http:\u002F\u002Flocalhost:4111\n   ```\n\n## Resources\n\n- **Setup**: `references\u002Fcreate_mastra.md` (`references\u002Fcreate_mastra.md`)\n- **Embedded docs lookup**: `references\u002Fembedded_docs.md` (`references\u002Fembedded_docs.md`) - Start here if packages are installed\n- **Remote docs lookup**: `references\u002Fremote_docs.md` (`references\u002Fremote_docs.md`)\n- **Common errors**: `references\u002Fcommon_errors.md` (`references\u002Fcommon_errors.md`)\n- **Migrations**: `references\u002Fmigration_guide.md` (`references\u002Fmigration_guide.md`)\n",{"name":5,"license":15,"metadata":43,"description":7},{"author":44,"version":45,"repository":46},"Mastra","2.0.0","https:\u002F\u002Fgithub.com\u002Fmastra-ai\u002Fskills","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_mastra_ai_mastra",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill mastra",{"tool":62,"command":63},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill mastra",{"tool":65,"command":66},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill mastra","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_mastra_ai_mastra\u002Fskill.md",true,[],[71,104,127,148,168,191],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":103},"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.","MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,30,100,101,102],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","when","components","route","create","libraries","2026-11-10 13:02:02",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":103},"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",[110],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[84,112,113,88,114,115,116,117,97,118,98,119,99,120,121,122,123,124,125,126],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"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":75,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":103},"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":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[84,135,136,88,137,117,138,98,139,119,99,140,141,142,143,144,24,145,146,147],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","Optimization","guidelines","triggers",{"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":75,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":103},"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":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[156,88,157,24,158,159,160,161,147,162,163,164,98,165,119,99,166,167,30,84],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":103},"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",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000010","后端与接口",[178,179,180,181,137,182,183,184,126,145,117,185,186,138,187,164,188,189,190,98],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":214},"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",[197],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[199,200,201,202,203,94,204,161,205,97,206,207,98,84,208,209,210,211,212,213],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]