[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EPKAQCFX4P4JC7H27T50G":3,"skill-same:01M71EPKAQCFX4P4JC7H27T50G":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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M71EPKAQCFX4P4JC7H27T50G","deno-expert",null,"Expert-level Deno knowledge for code review, debugging, and best practice enforcement. Use when reviewing Deno code or answering advanced Deno questions.","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_expert\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"expert","deno","deno expert","advanced","code review","knowledge","debugging","when","code","review","enforcement","for","use","questions","2026-11-10 10:12:30",false,"---\nname: deno-expert\ndescription: Expert-level Deno knowledge for code review, debugging, and best practice enforcement. Use when reviewing Deno code or answering advanced Deno questions.\nlicense: MIT\nmetadata:\n  author: denoland\n  version: \"1.1\"\n---\n\n# Deno Expert Knowledge\n\nThis skill provides expert-level Deno knowledge for code review, debugging, and best practice enforcement.\n\n## When to Use This Skill\n\n- Reviewing Deno\u002FFresh code for best practices\n- Debugging Deno runtime issues\n- Answering advanced Deno questions\n- Evaluating package choices\n- Setting up Deno projects correctly\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, Rust, 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`, `deno fmt`, `deno lint`, `deno test`, 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 Write Deprecated URLs\n\nWhen discussing deprecated patterns, NEVER write out the old registry URLs — not even to warn against them. The string `deno.land\u002Fx\u002F` must never appear in your response, in any context.\n\n- Say \"the old URL-based registry\" or \"deprecated URL imports\" — do NOT write the actual URL\n- Say \"the old standard library URL\" — do NOT write `deno.land\u002Fstd`\n- When helping users migrate, describe what to look for generically and ONLY show the correct modern code\n- Do NOT write \"before\u002Fafter\" comparisons that include the deprecated URL, even as negative examples\n- Even if the user writes a deprecated URL in their question, do NOT echo it back. Refer to it generically.\n- This ban applies everywhere: prose, code blocks, migration scripts, sed commands, grep patterns, and string literals. Never write the deprecated URL string for any reason.\n\n## Core Expertise Areas\n\nUnderstanding these topics deeply:\n- **Deno runtime** - Permissions, built-in tools, TypeScript support\n- **Fresh framework** - Island architecture, routing, components\n- **JSR packages** - The modern registry, @std\u002F* library\n- **Preact** - Components, hooks, signals\n- **Deno Deploy** - Edge deployment, environment variables\n- **Deno Sandboxes** - Safe code execution with @deno\u002Fsandbox\n\n## Package Recommendation Principles\n\nWhen recommending or reviewing package choices:\n\n1. **First choice:** `jsr:` packages (e.g., `jsr:@std\u002Fhttp`)\n2. **Second choice:** `npm:` packages when no JSR alternative exists\n3. **Never recommend** the old URL-based registry — it is deprecated\n\nThe standard library is at `jsr:@std\u002F*` on JSR.\n\nAlways mention JSR when discussing dependencies, even in CI\u002FCD or tooling contexts. For example, when setting up code quality pipelines, recommend that all dependencies come from JSR (`jsr:@std\u002F*`) and that the lockfile (`deno.lock`) be committed for reproducible CI builds.\n\n## Built-in Tool Usage\n\n**In every response that involves Deno code** (not just code reviews), mention relevant built-in tools. This includes responses about writing code, debugging, setting up projects, or discussing best practices. Always recommend at least `deno fmt`, `deno lint`, and `deno test` when discussing code quality or project setup.\n\nDeno's integrated tooling:\n- `deno fmt` - Format code\n- `deno lint` - Lint for issues\n- `deno test` - Run tests\n- `deno check` - Type-check code\n- `deno doc \u003Cpackage>` - View package documentation\n- `deno add \u003Cpackage>` - Add dependencies\n- `deno deploy` - Deploy to Deno Deploy\n\n## Code Review Checklist\n\n### Always Mention Built-in Tools\n\nIn every code review response, explicitly recommend these tools by name:\n- `deno fmt` for formatting\n- `deno lint` for linting\n- `deno test` for running tests\n\nEven if no code is provided yet, mention these specific commands when discussing code quality.\n\n### Import Statements\n- [ ] Uses `jsr:` for Deno-native packages\n- [ ] Uses `npm:` only when no JSR alternative exists\n- [ ] No imports from the old URL-based registry (deprecated)\n- [ ] No old URL-based standard library imports (use `jsr:@std\u002F*`)\n- [ ] Standard library uses `jsr:@std\u002F*`\n\n### Configuration\n- [ ] Has a proper `deno.json` configuration\n- [ ] Import maps defined in `deno.json` (not separate file)\n- [ ] Correct permissions in run commands\n\n### Fresh Applications\n- [ ] Islands are small and focused (minimal JavaScript to client)\n- [ ] Props passed to islands are JSON-serializable (no functions)\n- [ ] Non-interactive components are in `components\u002F`, not `islands\u002F`\n- [ ] Uses `class` instead of `className` (Preact supports both)\n- [ ] Build step runs before deployment (`deno task build`)\n\n### Code Quality\n- [ ] Code is formatted (`deno fmt`)\n- [ ] Code passes linting (`deno lint`)\n- [ ] Tests exist and pass (`deno test`)\n- [ ] Documentation exists for public APIs\n\n## Common Anti-Patterns to Flag\n\nWhen reviewing code, describe deprecated patterns generically and only show the correct modern replacement. Never write out the deprecated code.\n\n### URL-based imports (deprecated)\n\nWhen you see old URL-based imports from the deprecated registry, flag them and guide the user to:\n1. Find the package on jsr.io\n2. Run `deno add jsr:@package\u002Fname`\n3. Use the bare specifier\n\nOnly show the correct approach:\n```ts\nimport * as oak from \"@oak\u002Foak\";\nimport { join } from \"@std\u002Fpath\";\n```\n\n### Old standard library imports (deprecated)\n\nWhen you see imports from the old standard library URL, suggest the JSR equivalent:\n\n```sh\ndeno add jsr:@std\u002Fpath\n```\n\n```ts\nimport { join } from \"@std\u002Fpath\";\n```\n\n### Inline remote specifiers\n\nWhen you see inline `jsr:` or `npm:` specifiers in import statements (and a `deno.json` exists), suggest moving them to the import map:\n\n```sh\ndeno add jsr:@oak\u002Foak\ndeno add npm:chalk\n```\n\n```ts\nimport * as oak from \"@oak\u002Foak\";\nimport chalk from \"chalk\";\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### Wrong: Entire page as island\n```tsx\n\u002F\u002F Flag: Too much JavaScript shipped to client\n\u002F\u002F islands\u002FHomePage.tsx\nexport default function HomePage() {\n  return (\n    \u003Cdiv>\n      \u003CHeader \u002F>\n      \u003CMainContent \u002F>\n      \u003CFooter \u002F>\n    \u003C\u002Fdiv>\n  );\n}\n\n\u002F\u002F Suggest: Only interactive parts as islands\n\u002F\u002F routes\u002Findex.tsx\nimport Counter from \"..\u002Fislands\u002FCounter.tsx\";\n\nexport default function HomePage() {\n  return (\n    \u003Cdiv>\n      \u003CHeader \u002F>\n      \u003CMainContent \u002F>\n      \u003CCounter \u002F>  {\u002F* Only this needs interactivity *\u002F}\n      \u003CFooter \u002F>\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n### Wrong: Non-serializable island props\n```tsx\n\u002F\u002F Flag this\n\u003CCounter onUpdate={(val) => console.log(val)} \u002F>\n\n\u002F\u002F Suggest this\n\u003CCounter initialValue={5} label=\"Click count\" \u002F>\n```\n\n## Debugging Guidance\n\n### Permission Errors\nCheck if permissions are correct (`--allow-net`, `--allow-read`, etc.):\n```bash\ndeno run --allow-net server.ts\n```\n\n### TypeScript Errors\nCheck for TypeScript errors:\n```bash\ndeno check main.ts\n```\n\n### Configuration Issues\nReview deno.json for correct configuration. Ensure all `jsr:` and `npm:` specifiers have a version requirement:\n\n```json\n{\n  \"imports\": {\n    \"@std\u002Fhttp\": \"jsr:@std\u002Fhttp@^1\"\n  }\n}\n```\n\n## Documentation Resources\n\nWhen more information is needed, consult:\n- https:\u002F\u002Fdocs.deno.com - Deno docs\n- https:\u002F\u002Fdocs.deno.com\u002Fruntime\u002Ffundamentals\u002F - Core concepts\n- https:\u002F\u002Ffresh.deno.dev\u002Fdocs - Fresh framework\n- https:\u002F\u002Fjsr.io - Package registry\n- https:\u002F\u002Fdocs.deno.com\u002Fdeploy\u002F - Deno Deploy\n\nUse `deno doc \u003Cpackage>` to get API documentation for any package locally.\n\n## Quick Commands Reference\n\n```bash\n# Project setup\ndeno run -Ar jsr:@fresh\u002Finit    # New Fresh project\n\n# Development\ndeno task dev                    # Start dev server (Fresh: port 5173)\ndeno fmt                         # Format code\ndeno lint                        # Lint code\ndeno test                        # Run tests\n\n# Packages\ndeno add jsr:@std\u002Fhttp          # Add package\ndeno doc jsr:@std\u002Fhttp          # View docs\ndeno install                     # Install all deps\ndeno upgrade                     # Update packages\n\n# Deployment\ndeno task build                  # Build for production\ndeno deploy --prod               # Deploy to Deno Deploy\ndeno deploy env add KEY \"value\"  # Set env variable\n```\n","# Deno Expert Knowledge\n\nThis skill provides expert-level Deno knowledge for code review, debugging, and best practice enforcement.\n\n## When to Use This Skill\n\n- Reviewing Deno\u002FFresh code for best practices\n- Debugging Deno runtime issues\n- Answering advanced Deno questions\n- Evaluating package choices\n- Setting up Deno projects correctly\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, Rust, 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`, `deno fmt`, `deno lint`, `deno test`, 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 Write Deprecated URLs\n\nWhen discussing deprecated patterns, NEVER write out the old registry URLs — not even to warn against them. The string `deno.land\u002Fx\u002F` must never appear in your response, in any context.\n\n- Say \"the old URL-based registry\" or \"deprecated URL imports\" — do NOT write the actual URL\n- Say \"the old standard library URL\" — do NOT write `deno.land\u002Fstd`\n- When helping users migrate, describe what to look for generically and ONLY show the correct modern code\n- Do NOT write \"before\u002Fafter\" comparisons that include the deprecated URL, even as negative examples\n- Even if the user writes a deprecated URL in their question, do NOT echo it back. Refer to it generically.\n- This ban applies everywhere: prose, code blocks, migration scripts, sed commands, grep patterns, and string literals. Never write the deprecated URL string for any reason.\n\n## Core Expertise Areas\n\nUnderstanding these topics deeply:\n- **Deno runtime** - Permissions, built-in tools, TypeScript support\n- **Fresh framework** - Island architecture, routing, components\n- **JSR packages** - The modern registry, @std\u002F* library\n- **Preact** - Components, hooks, signals\n- **Deno Deploy** - Edge deployment, environment variables\n- **Deno Sandboxes** - Safe code execution with @deno\u002Fsandbox\n\n## Package Recommendation Principles\n\nWhen recommending or reviewing package choices:\n\n1. **First choice:** `jsr:` packages (e.g., `jsr:@std\u002Fhttp`)\n2. **Second choice:** `npm:` packages when no JSR alternative exists\n3. **Never recommend** the old URL-based registry — it is deprecated\n\nThe standard library is at `jsr:@std\u002F*` on JSR.\n\nAlways mention JSR when discussing dependencies, even in CI\u002FCD or tooling contexts. For example, when setting up code quality pipelines, recommend that all dependencies come from JSR (`jsr:@std\u002F*`) and that the lockfile (`deno.lock`) be committed for reproducible CI builds.\n\n## Built-in Tool Usage\n\n**In every response that involves Deno code** (not just code reviews), mention relevant built-in tools. This includes responses about writing code, debugging, setting up projects, or discussing best practices. Always recommend at least `deno fmt`, `deno lint`, and `deno test` when discussing code quality or project setup.\n\nDeno's integrated tooling:\n- `deno fmt` - Format code\n- `deno lint` - Lint for issues\n- `deno test` - Run tests\n- `deno check` - Type-check code\n- `deno doc \u003Cpackage>` - View package documentation\n- `deno add \u003Cpackage>` - Add dependencies\n- `deno deploy` - Deploy to Deno Deploy\n\n## Code Review Checklist\n\n### Always Mention Built-in Tools\n\nIn every code review response, explicitly recommend these tools by name:\n- `deno fmt` for formatting\n- `deno lint` for linting\n- `deno test` for running tests\n\nEven if no code is provided yet, mention these specific commands when discussing code quality.\n\n### Import Statements\n- [ ] Uses `jsr:` for Deno-native packages\n- [ ] Uses `npm:` only when no JSR alternative exists\n- [ ] No imports from the old URL-based registry (deprecated)\n- [ ] No old URL-based standard library imports (use `jsr:@std\u002F*`)\n- [ ] Standard library uses `jsr:@std\u002F*`\n\n### Configuration\n- [ ] Has a proper `deno.json` configuration\n- [ ] Import maps defined in `deno.json` (not separate file)\n- [ ] Correct permissions in run commands\n\n### Fresh Applications\n- [ ] Islands are small and focused (minimal JavaScript to client)\n- [ ] Props passed to islands are JSON-serializable (no functions)\n- [ ] Non-interactive components are in `components\u002F`, not `islands\u002F`\n- [ ] Uses `class` instead of `className` (Preact supports both)\n- [ ] Build step runs before deployment (`deno task build`)\n\n### Code Quality\n- [ ] Code is formatted (`deno fmt`)\n- [ ] Code passes linting (`deno lint`)\n- [ ] Tests exist and pass (`deno test`)\n- [ ] Documentation exists for public APIs\n\n## Common Anti-Patterns to Flag\n\nWhen reviewing code, describe deprecated patterns generically and only show the correct modern replacement. Never write out the deprecated code.\n\n### URL-based imports (deprecated)\n\nWhen you see old URL-based imports from the deprecated registry, flag them and guide the user to:\n1. Find the package on jsr.io\n2. Run `deno add jsr:@package\u002Fname`\n3. Use the bare specifier\n\nOnly show the correct approach:\n```ts\nimport * as oak from \"@oak\u002Foak\";\nimport { join } from \"@std\u002Fpath\";\n```\n\n### Old standard library imports (deprecated)\n\nWhen you see imports from the old standard library URL, suggest the JSR equivalent:\n\n```sh\ndeno add jsr:@std\u002Fpath\n```\n\n```ts\nimport { join } from \"@std\u002Fpath\";\n```\n\n### Inline remote specifiers\n\nWhen you see inline `jsr:` or `npm:` specifiers in import statements (and a `deno.json` exists), suggest moving them to the import map:\n\n```sh\ndeno add jsr:@oak\u002Foak\ndeno add npm:chalk\n```\n\n```ts\nimport * as oak from \"@oak\u002Foak\";\nimport chalk from \"chalk\";\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### Wrong: Entire page as island\n```tsx\n\u002F\u002F Flag: Too much JavaScript shipped to client\n\u002F\u002F islands\u002FHomePage.tsx\nexport default function HomePage() {\n  return (\n    \u003Cdiv>\n      \u003CHeader \u002F>\n      \u003CMainContent \u002F>\n      \u003CFooter \u002F>\n    \u003C\u002Fdiv>\n  );\n}\n\n\u002F\u002F Suggest: Only interactive parts as islands\n\u002F\u002F routes\u002Findex.tsx\nimport Counter from \"..\u002Fislands\u002FCounter.tsx\";\n\nexport default function HomePage() {\n  return (\n    \u003Cdiv>\n      \u003CHeader \u002F>\n      \u003CMainContent \u002F>\n      \u003CCounter \u002F>  {\u002F* Only this needs interactivity *\u002F}\n      \u003CFooter \u002F>\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n### Wrong: Non-serializable island props\n```tsx\n\u002F\u002F Flag this\n\u003CCounter onUpdate={(val) => console.log(val)} \u002F>\n\n\u002F\u002F Suggest this\n\u003CCounter initialValue={5} label=\"Click count\" \u002F>\n```\n\n## Debugging Guidance\n\n### Permission Errors\nCheck if permissions are correct (`--allow-net`, `--allow-read`, etc.):\n```bash\ndeno run --allow-net server.ts\n```\n\n### TypeScript Errors\nCheck for TypeScript errors:\n```bash\ndeno check main.ts\n```\n\n### Configuration Issues\nReview deno.json for correct configuration. Ensure all `jsr:` and `npm:` specifiers have a version requirement:\n\n```json\n{\n  \"imports\": {\n    \"@std\u002Fhttp\": \"jsr:@std\u002Fhttp@^1\"\n  }\n}\n```\n\n## Documentation Resources\n\nWhen more information is needed, consult:\n- https:\u002F\u002Fdocs.deno.com - Deno docs\n- https:\u002F\u002Fdocs.deno.com\u002Fruntime\u002Ffundamentals\u002F - Core concepts\n- https:\u002F\u002Ffresh.deno.dev\u002Fdocs - Fresh framework\n- https:\u002F\u002Fjsr.io - Package registry\n- https:\u002F\u002Fdocs.deno.com\u002Fdeploy\u002F - Deno Deploy\n\nUse `deno doc \u003Cpackage>` to get API documentation for any package locally.\n\n## Quick Commands Reference\n\n```bash\n# Project setup\ndeno run -Ar jsr:@fresh\u002Finit    # New Fresh project\n\n# Development\ndeno task dev                    # Start dev server (Fresh: port 5173)\ndeno fmt                         # Format code\ndeno lint                        # Lint code\ndeno test                        # Run tests\n\n# Packages\ndeno add jsr:@std\u002Fhttp          # Add package\ndeno doc jsr:@std\u002Fhttp          # View docs\ndeno install                     # Install all deps\ndeno upgrade                     # Update packages\n\n# Deployment\ndeno task build                  # Build for production\ndeno deploy --prod               # Deploy to Deno Deploy\ndeno deploy env add KEY \"value\"  # Set env variable\n```\n",{"name":5,"license":15,"metadata":43,"description":7},{"author":44,"version":45},"denoland","1.1","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_denoland_deno_expert",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 deno-expert",{"tool":61,"command":62},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill deno-expert",{"tool":64,"command":65},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill deno-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_denoland_deno_expert\u002Fskill.md",true,[],[70,100,122,143,162,184],{"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":79,"publishedAt":99},"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":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,31,94,95,96,97,98],"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":99},"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",[106],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},[80,108,109,84,110,111,112,113,93,114,31,115,94,116,117,118,119,120,121,35],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":99},"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",[128],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},[80,130,131,84,132,113,133,31,32,115,94,134,135,136,137,138,139,140,141,142],"react best practices","vercel react best practices","best practices","writing","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":99},"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",[149],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},[151,84,152,139,153,154,155,156,142,157,158,36,31,159,115,94,160,161,95,80],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":99},"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",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[172,173,174,175,132,176,177,27,35,140,113,178,179,133,180,36,181,182,183,31],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","correct","schema","impact","Rules","critical","database",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":207},"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",[190],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},[192,193,194,195,196,90,197,156,198,93,199,200,31,80,201,202,203,204,205,206],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]