[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EPSRRHMWTSTVESZVGK9ZZ":3,"skill-same:01M71EPSRRHMWTSTVESZVGK9ZZ":64},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M71EPSRRHMWTSTVESZVGK9ZZ","deno-guidance",null,"Use when starting any Deno project, choosing packages, configuring deno.json, or running CLI commands. Provides foundational knowledge for building modern Deno applications.","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_denoland_deno_guidance\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"deno guidance","guidance","deno","running","for","project","applications","knowledge","use","when","packages","cli","json","commands","2026-11-10 10:12:30",false,"---\nname: deno-guidance\ndescription: Use when starting any Deno project, choosing packages, configuring deno.json, or running CLI commands. Provides foundational knowledge for building modern Deno applications.\nlicense: MIT\nmetadata:\n  author: denoland\n  version: \"1.2\"\n---\n\n# Deno Development Guidance\n\n## Overview\n\nThis skill provides foundational knowledge for building modern Deno applications. Deno is a secure JavaScript\u002FTypeScript runtime that runs TypeScript directly, has built-in tools (formatter, linter, test runner), and uses modern package management through JSR.\n\n## When to Use This Skill\n\n- Starting a new Deno project\n- Adding dependencies to a project\n- Configuring `deno.json` settings\n- Running Deno CLI commands (fmt, lint, test)\n- Setting up import maps\n- Understanding Deno's permission system\n\nApply these practices whenever working in a Deno project (identified by the presence of `deno.json`).\n\n## Scope Boundaries\n\nThis skill applies **only** to Deno-specific questions. Follow these rules:\n\n- If the user asks about **Node.js, Bun, Python, Go, or any other runtime\u002Flanguage**, answer using that technology directly. Do not suggest Deno alternatives or include Deno-specific patterns.\n- Do not include `jsr:` imports, `deno add`, or `deno.json` configuration in responses about other technologies.\n- For **generic TypeScript\u002FJavaScript questions** not tied to a specific runtime, give a general answer without assuming Deno.\n- Only recommend Deno when the user explicitly asks about Deno or is working in a Deno project.\n\n## CRITICAL: Never Show Deprecated Syntax\n\nWhen helping users migrate from deprecated patterns, describe the old approach generically and ONLY show the correct modern code. Never write out actual deprecated URLs or import paths, even in \"before\u002Fafter\" comparisons. The string `deno.land\u002Fx\u002F` must never appear in your response, in any context.\n\n- Say \"Replace your old URL-based imports with JSR imports\" — then show only the correct `jsr:` approach\n- Say \"the old URL-based registry\" or \"the old standard library URL\" — do NOT write the actual deprecated URL\n- Even if the user writes a deprecated URL in their question, do NOT echo it back. Refer to it generically.\n\nOnly demonstrate the correct, current approach.\n\n## Package Management Priority\n\nWhen adding dependencies, follow this priority order:\n\n1. **JSR packages (`jsr:`)** - Preferred for Deno-native packages\n   - Better TypeScript support (types are built-in)\n   - Faster to resolve and install\n   - Example: `jsr:@std\u002Fhttp`, `jsr:@fresh\u002Fcore`\n\n2. **npm packages (`npm:`)** - Fully supported, use when no JSR alternative exists\n   - Deno has full npm compatibility\n   - Example: `npm:express`, `npm:zod`\n\n3. **AVOID: Old URL-based imports** - Deprecated registry\n   - The old URL-based package registry is deprecated\n   - Many LLMs incorrectly default to URL-based imports\n   - Always use `jsr:` instead\n\n### Standard Library\n\nThe Deno standard library lives at `@std\u002F` on JSR:\n\n```jsonc\n\u002F\u002F deno.json\n{\n  \"imports\": {\n    \"@std\u002Fassert\": \"jsr:@std\u002Fassert@1\",\n    \"@std\u002Fhttp\": \"jsr:@std\u002Fhttp@1\",\n    \"@std\u002Fpath\": \"jsr:@std\u002Fpath@1\"\n  }\n}\n```\n\n```typescript\nimport { serve } from \"@std\u002Fhttp\";\nimport { join } from \"@std\u002Fpath\";\nimport { assertEquals } from \"@std\u002Fassert\";\n```\n\nAlways use `jsr:@std\u002F*` for the standard library (the old URL-based imports are deprecated).\n\n## Understanding Deno\n\nReference: https:\u002F\u002Fdocs.deno.com\u002Fruntime\u002Ffundamentals\u002F\n\nKey concepts:\n- **Native TypeScript** - No build step needed, Deno runs TypeScript directly\n- **Explicit permissions** - Use flags like `--allow-net`, `--allow-read`, `--allow-env`\n- **deno.json** - The config file (similar to package.json but simpler)\n- **Import maps** - Define import aliases in deno.json's `imports` field\n\n## Workflow Best Practices\n\n### After Making Code Changes\n\nRun these commands regularly, especially after significant changes:\n\n```bash\ndeno fmt          # Format all files\ndeno lint         # Check for issues\ndeno test         # Run tests\n```\n\n### Package Management\n\n```bash\ndeno add jsr:@std\u002Fhttp    # Add a package\ndeno install              # Install all dependencies\ndeno update               # Update all dependencies to latest compatible versions\ndeno update jsr:@std\u002Fhttp # Update a specific dependency\n```\n\n**`deno update` vs `deno upgrade`:**\n\n- `deno update` - Updates **project dependencies** in `deno.json` (and `package.json`) to their latest compatible versions. Respects semver ranges. Use this to keep your dependencies current.\n- `deno upgrade` - Updates the **Deno runtime itself** to the latest version. Has nothing to do with project dependencies.\n\nAfter running `deno update`, always check for breaking API changes - especially for alpha\u002Fpre-release packages where semver ranges can pull in breaking updates.\n\n\n### CI\u002FCD\n\nIn CI pipelines, use `--check` with `deno fmt` so it fails without modifying files:\n\n```bash\ndeno fmt --check     # Fail if not formatted\ndeno lint            # Check for issues\ndeno test            # Run tests\n```\n\n### Configuration\n\nIn `deno.json`, you can exclude directories from formatting\u002Flinting:\n\n```json\n{\n  \"fmt\": {\n    \"exclude\": [\"build\u002F\"]\n  },\n  \"lint\": {\n    \"exclude\": [\"build\u002F\"]\n  }\n}\n```\n\nA folder can also be excluded from everything at the top level:\n\n```json\n{\n  \"exclude\": [\"build\u002F\"]\n}\n```\n\n## Deployment\n\nFor deploying to Deno Deploy, see the dedicated **deno-deploy** skill.\n\nQuick command: `deno deploy --prod`\n\n## Documentation Resources\n\nWhen more information is needed:\n\n- **`deno doc \u003Cpackage>`** - Generate docs for any JSR or npm package locally\n- **https:\u002F\u002Fdocs.deno.com** - Official Deno documentation\n- **https:\u002F\u002Fjsr.io** - Package registry with built-in documentation\n- **https:\u002F\u002Ffresh.deno.dev\u002Fdocs** - Fresh framework documentation\n\n## Quick Reference: Deno CLI Commands\n\n| Command | Purpose |\n|---------|---------|\n| `deno run file.ts` | Run a TypeScript\u002FJavaScript file |\n| `deno task \u003Cname>` | Run a task from deno.json |\n| `deno fmt` | Format code |\n| `deno lint` | Lint code |\n| `deno test` | Run tests |\n| `deno add \u003Cpkg>` | Add a package |\n| `deno install` | Install dependencies |\n| `deno update` | Update project dependencies |\n| `deno upgrade` | Update Deno runtime itself |\n| `deno doc \u003Cpkg>` | View package documentation |\n| `deno deploy --prod` | Deploy to Deno Deploy |\n\n## Common Mistakes\n\n**Using old URL-based imports instead of JSR**\n\nThe old URL-based imports are deprecated. Always use `jsr:` imports with bare specifiers instead.\n\n```ts\n\u002F\u002F ✅ Correct - use JSR and a bare specifier\nimport { serve } from \"@std\u002Fhttp\";\nimport { join } from \"@std\u002Fpath\";\n```\n\n```jsonc\n\u002F\u002F deno.json\n{\n  \"imports\": {\n    \"@std\u002Fhttp\": \"jsr:@std\u002Fhttp@1\",\n    \"@std\u002Fpath\": \"jsr:@std\u002Fpath@1\"\n  }\n}\n```\n\nInline specifiers are fine in single file scripts, but if a deno.json exists then it should go there. It's preferable to place npm dependencies in a package.json if a package.json exists.\n\n**Forgetting to run fmt\u002Flint before committing**\n\nAlways format and lint before committing:\n\n```bash\n# ✅ Always format and lint first\ndeno fmt && deno lint && git add . && git commit -m \"changes\"\n```\n\n**Running code without permission flags**\n\n```bash\n# ✅ Grant specific permissions\ndeno run --allow-net server.ts\n```\n\nWithout permission flags, Deno will show \"Requires net access\" errors. Always grant the specific permissions your code needs.\n\n**Not using `deno add` for dependencies**\n\n```bash\n# ✅ Use deno add to manage dependencies\ndeno add jsr:@std\u002Fhttp\n```\n\nUsing `deno add` ensures your lockfile stays in sync. Manually editing imports without updating deno.json works but misses lockfile benefits.\n","# Deno Development Guidance\n\n## Overview\n\nThis skill provides foundational knowledge for building modern Deno applications. Deno is a secure JavaScript\u002FTypeScript runtime that runs TypeScript directly, has built-in tools (formatter, linter, test runner), and uses modern package management through JSR.\n\n## When to Use This Skill\n\n- Starting a new Deno project\n- Adding dependencies to a project\n- Configuring `deno.json` settings\n- Running Deno CLI commands (fmt, lint, test)\n- Setting up import maps\n- Understanding Deno's permission system\n\nApply these practices whenever working in a Deno project (identified by the presence of `deno.json`).\n\n## Scope Boundaries\n\nThis skill applies **only** to Deno-specific questions. Follow these rules:\n\n- If the user asks about **Node.js, Bun, Python, Go, or any other runtime\u002Flanguage**, answer using that technology directly. Do not suggest Deno alternatives or include Deno-specific patterns.\n- Do not include `jsr:` imports, `deno add`, or `deno.json` configuration in responses about other technologies.\n- For **generic TypeScript\u002FJavaScript questions** not tied to a specific runtime, give a general answer without assuming Deno.\n- Only recommend Deno when the user explicitly asks about Deno or is working in a Deno project.\n\n## CRITICAL: Never Show Deprecated Syntax\n\nWhen helping users migrate from deprecated patterns, describe the old approach generically and ONLY show the correct modern code. Never write out actual deprecated URLs or import paths, even in \"before\u002Fafter\" comparisons. The string `deno.land\u002Fx\u002F` must never appear in your response, in any context.\n\n- Say \"Replace your old URL-based imports with JSR imports\" — then show only the correct `jsr:` approach\n- Say \"the old URL-based registry\" or \"the old standard library URL\" — do NOT write the actual deprecated URL\n- Even if the user writes a deprecated URL in their question, do NOT echo it back. Refer to it generically.\n\nOnly demonstrate the correct, current approach.\n\n## Package Management Priority\n\nWhen adding dependencies, follow this priority order:\n\n1. **JSR packages (`jsr:`)** - Preferred for Deno-native packages\n   - Better TypeScript support (types are built-in)\n   - Faster to resolve and install\n   - Example: `jsr:@std\u002Fhttp`, `jsr:@fresh\u002Fcore`\n\n2. **npm packages (`npm:`)** - Fully supported, use when no JSR alternative exists\n   - Deno has full npm compatibility\n   - Example: `npm:express`, `npm:zod`\n\n3. **AVOID: Old URL-based imports** - Deprecated registry\n   - The old URL-based package registry is deprecated\n   - Many LLMs incorrectly default to URL-based imports\n   - Always use `jsr:` instead\n\n### Standard Library\n\nThe Deno standard library lives at `@std\u002F` on JSR:\n\n```jsonc\n\u002F\u002F deno.json\n{\n  \"imports\": {\n    \"@std\u002Fassert\": \"jsr:@std\u002Fassert@1\",\n    \"@std\u002Fhttp\": \"jsr:@std\u002Fhttp@1\",\n    \"@std\u002Fpath\": \"jsr:@std\u002Fpath@1\"\n  }\n}\n```\n\n```typescript\nimport { serve } from \"@std\u002Fhttp\";\nimport { join } from \"@std\u002Fpath\";\nimport { assertEquals } from \"@std\u002Fassert\";\n```\n\nAlways use `jsr:@std\u002F*` for the standard library (the old URL-based imports are deprecated).\n\n## Understanding Deno\n\nReference: https:\u002F\u002Fdocs.deno.com\u002Fruntime\u002Ffundamentals\u002F\n\nKey concepts:\n- **Native TypeScript** - No build step needed, Deno runs TypeScript directly\n- **Explicit permissions** - Use flags like `--allow-net`, `--allow-read`, `--allow-env`\n- **deno.json** - The config file (similar to package.json but simpler)\n- **Import maps** - Define import aliases in deno.json's `imports` field\n\n## Workflow Best Practices\n\n### After Making Code Changes\n\nRun these commands regularly, especially after significant changes:\n\n```bash\ndeno fmt          # Format all files\ndeno lint         # Check for issues\ndeno test         # Run tests\n```\n\n### Package Management\n\n```bash\ndeno add jsr:@std\u002Fhttp    # Add a package\ndeno install              # Install all dependencies\ndeno update               # Update all dependencies to latest compatible versions\ndeno update jsr:@std\u002Fhttp # Update a specific dependency\n```\n\n**`deno update` vs `deno upgrade`:**\n\n- `deno update` - Updates **project dependencies** in `deno.json` (and `package.json`) to their latest compatible versions. Respects semver ranges. Use this to keep your dependencies current.\n- `deno upgrade` - Updates the **Deno runtime itself** to the latest version. Has nothing to do with project dependencies.\n\nAfter running `deno update`, always check for breaking API changes - especially for alpha\u002Fpre-release packages where semver ranges can pull in breaking updates.\n\n\n### CI\u002FCD\n\nIn CI pipelines, use `--check` with `deno fmt` so it fails without modifying files:\n\n```bash\ndeno fmt --check     # Fail if not formatted\ndeno lint            # Check for issues\ndeno test            # Run tests\n```\n\n### Configuration\n\nIn `deno.json`, you can exclude directories from formatting\u002Flinting:\n\n```json\n{\n  \"fmt\": {\n    \"exclude\": [\"build\u002F\"]\n  },\n  \"lint\": {\n    \"exclude\": [\"build\u002F\"]\n  }\n}\n```\n\nA folder can also be excluded from everything at the top level:\n\n```json\n{\n  \"exclude\": [\"build\u002F\"]\n}\n```\n\n## Deployment\n\nFor deploying to Deno Deploy, see the dedicated **deno-deploy** skill.\n\nQuick command: `deno deploy --prod`\n\n## Documentation Resources\n\nWhen more information is needed:\n\n- **`deno doc \u003Cpackage>`** - Generate docs for any JSR or npm package locally\n- **https:\u002F\u002Fdocs.deno.com** - Official Deno documentation\n- **https:\u002F\u002Fjsr.io** - Package registry with built-in documentation\n- **https:\u002F\u002Ffresh.deno.dev\u002Fdocs** - Fresh framework documentation\n\n## Quick Reference: Deno CLI Commands\n\n| Command | Purpose |\n|---------|---------|\n| `deno run file.ts` | Run a TypeScript\u002FJavaScript file |\n| `deno task \u003Cname>` | Run a task from deno.json |\n| `deno fmt` | Format code |\n| `deno lint` | Lint code |\n| `deno test` | Run tests |\n| `deno add \u003Cpkg>` | Add a package |\n| `deno install` | Install dependencies |\n| `deno update` | Update project dependencies |\n| `deno upgrade` | Update Deno runtime itself |\n| `deno doc \u003Cpkg>` | View package documentation |\n| `deno deploy --prod` | Deploy to Deno Deploy |\n\n## Common Mistakes\n\n**Using old URL-based imports instead of JSR**\n\nThe old URL-based imports are deprecated. Always use `jsr:` imports with bare specifiers instead.\n\n```ts\n\u002F\u002F ✅ Correct - use JSR and a bare specifier\nimport { serve } from \"@std\u002Fhttp\";\nimport { join } from \"@std\u002Fpath\";\n```\n\n```jsonc\n\u002F\u002F deno.json\n{\n  \"imports\": {\n    \"@std\u002Fhttp\": \"jsr:@std\u002Fhttp@1\",\n    \"@std\u002Fpath\": \"jsr:@std\u002Fpath@1\"\n  }\n}\n```\n\nInline specifiers are fine in single file scripts, but if a deno.json exists then it should go there. It's preferable to place npm dependencies in a package.json if a package.json exists.\n\n**Forgetting to run fmt\u002Flint before committing**\n\nAlways format and lint before committing:\n\n```bash\n# ✅ Always format and lint first\ndeno fmt && deno lint && git add . && git commit -m \"changes\"\n```\n\n**Running code without permission flags**\n\n```bash\n# ✅ Grant specific permissions\ndeno run --allow-net server.ts\n```\n\nWithout permission flags, Deno will show \"Requires net access\" errors. Always grant the specific permissions your code needs.\n\n**Not using `deno add` for dependencies**\n\n```bash\n# ✅ Use deno add to manage dependencies\ndeno add jsr:@std\u002Fhttp\n```\n\nUsing `deno add` ensures your lockfile stays in sync. Manually editing imports without updating deno.json works but misses lockfile benefits.\n",{"name":5,"license":15,"metadata":38,"description":7},{"author":39,"version":40},"denoland","1.2","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_denoland_deno_guidance",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill deno-guidance",{"tool":56,"command":57},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill deno-guidance",{"tool":59,"command":60},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill deno-guidance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_denoland_deno_guidance\u002Fskill.md",true,[],[65,97,119,141,160,183],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":96},"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",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[77,78,79,80,81,82,83,84,85,86,87,88,89,90,28,91,92,93,94,95],"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":96},"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",[103],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[77,105,106,81,107,108,109,110,90,111,28,112,91,113,114,115,116,117,118,23],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":96},"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",[125],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[77,127,128,81,129,110,130,28,131,112,91,132,133,134,135,136,137,138,139,140],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":96},"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",[147],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[149,81,150,137,151,152,153,154,140,155,156,27,28,157,112,91,158,159,92,77],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":96},"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",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000010","后端与接口",[170,171,172,173,129,174,175,176,23,138,110,177,178,130,179,27,180,181,182,28],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":190,"publishedAt":206},"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",[189],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[191,192,193,194,195,87,196,154,197,90,198,199,28,77,200,201,202,203,204,205],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]