[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ECSTNYC3CVB2ZXWRJ2B0N":3,"skill-same:01M71ECSTNYC3CVB2ZXWRJ2B0N":73},{"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":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M71ECSTNYC3CVB2ZXWRJ2B0N","graphql-operations",null,"Guide for writing GraphQL operations (queries, mutations, fragments) following best practices. Use this skill when: (1) writing GraphQL queries or mutations, (2) organizing operations with fragments, (3) optimizing data fetching patterns, (4) setting up type generation or linting, (5) reviewing operations for efficiency.","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_apollographql_graphql_operations\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"GraphQL","operations","graphql operations","for","setting","guide","patterns","urql","data","edit","write","read","linting","efficiency","data fetching","Bash","apollo client","when","writing","up","2026-11-10 10:12:30",false,"---\nname: graphql-operations\ndescription: >\n  Guide for writing GraphQL operations (queries, mutations, fragments) following best practices. Use this skill when:\n  (1) writing GraphQL queries or mutations,\n  (2) organizing operations with fragments,\n  (3) optimizing data fetching patterns,\n  (4) setting up type generation or linting,\n  (5) reviewing operations for efficiency.\nlicense: MIT\ncompatibility: Any GraphQL client (Apollo Client, urql, Relay, etc.)\nmetadata:\n  author: apollographql\n  version: \"1.0.0\"\nallowed-tools: Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep\n---\n\n# GraphQL Operations Guide\n\nThis guide covers best practices for writing GraphQL operations (queries, mutations, subscriptions) as a client developer. Well-written operations are efficient, type-safe, and maintainable.\n\n## Operation Basics\n\n### Query Structure\n\n```graphql\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n    email\n  }\n}\n```\n\n### Mutation Structure\n\n```graphql\nmutation CreatePost($input: CreatePostInput!) {\n  createPost(input: $input) {\n    id\n    title\n    createdAt\n  }\n}\n```\n\n### Subscription Structure\n\n```graphql\nsubscription OnMessageReceived($channelId: ID!) {\n  messageReceived(channelId: $channelId) {\n    id\n    content\n    sender {\n      id\n      name\n    }\n  }\n}\n```\n\n## Quick Reference\n\n### Operation Naming\n\n| Pattern      | Example                                     |\n| ------------ | ------------------------------------------- |\n| Query        | `GetUser`, `ListPosts`, `SearchProducts`    |\n| Mutation     | `CreateUser`, `UpdatePost`, `DeleteComment` |\n| Subscription | `OnMessageReceived`, `OnUserStatusChanged`  |\n\n### Variable Syntax\n\n```graphql\n# Required variable\nquery GetUser($id: ID!) { ... }\n\n# Optional variable with default\nquery ListPosts($first: Int = 20) { ... }\n\n# Multiple variables\nquery SearchPosts($query: String!, $status: PostStatus, $first: Int = 10) { ... }\n```\n\n### Fragment Syntax\n\n```graphql\n# Define fragment\nfragment UserBasicInfo on User {\n  id\n  name\n  avatarUrl\n}\n\n# Use fragment\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    ...UserBasicInfo\n    email\n  }\n}\n```\n\n### Directives\n\n```graphql\nquery GetUser($id: ID!, $includeEmail: Boolean!) {\n  user(id: $id) {\n    id\n    name\n    email @include(if: $includeEmail)\n  }\n}\n\nquery GetPosts($skipDrafts: Boolean!) {\n  posts {\n    id\n    title\n    draft @skip(if: $skipDrafts)\n  }\n}\n```\n\n## Key Principles\n\n### 1. Request Only What You Need\n\n```graphql\n# Good: Specific fields\nquery GetUserName($id: ID!) {\n  user(id: $id) {\n    id\n    name\n  }\n}\n\n# Avoid: Over-fetching\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n    email\n    bio\n    posts {\n      id\n      title\n      content\n      comments {\n        id\n      }\n    }\n    followers {\n      id\n      name\n    }\n    # ... many unused fields\n  }\n}\n```\n\n### 2. Name All Operations\n\n```graphql\n# Good: Named operation\nquery GetUserPosts($userId: ID!) {\n  user(id: $userId) {\n    posts {\n      id\n      title\n    }\n  }\n}\n\n# Avoid: Anonymous operation\nquery {\n  user(id: \"123\") {\n    posts {\n      id\n      title\n    }\n  }\n}\n```\n\n### 3. Use Variables, Not Inline Values\n\n```graphql\n# Good: Variables\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n  }\n}\n\n# Avoid: Hardcoded values\nquery {\n  user(id: \"123\") {\n    id\n    name\n  }\n}\n```\n\n### 4. Colocate Fragments with Components\n\n```tsx\n\u002F\u002F UserAvatar.tsx\nexport const USER_AVATAR_FRAGMENT = gql`\n  fragment UserAvatar on User {\n    id\n    name\n    avatarUrl\n  }\n`;\n\nfunction UserAvatar({ user }) {\n  return \u003Cimg src={user.avatarUrl} alt={user.name} \u002F>;\n}\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Queries (`references\u002Fqueries.md`) - Query patterns and optimization\n- Mutations (`references\u002Fmutations.md`) - Mutation patterns and error handling\n- Fragments (`references\u002Ffragments.md`) - Fragment organization and reuse\n- Variables (`references\u002Fvariables.md`) - Variable usage and types\n- Tooling (`references\u002Ftooling.md`) - Code generation and linting\n\n## Ground Rules\n\n- ALWAYS name your operations (no anonymous queries\u002Fmutations)\n- ALWAYS use variables for dynamic values\n- ALWAYS request only the fields you need\n- ALWAYS include `id` field for cacheable types\n- NEVER hardcode values in operations\n- NEVER duplicate field selections across files\n- PREFER fragments for reusable field selections\n- PREFER colocating fragments with components\n- USE descriptive operation names that reflect purpose\n- USE `@include`\u002F`@skip` for conditional fields\n","# GraphQL Operations Guide\n\nThis guide covers best practices for writing GraphQL operations (queries, mutations, subscriptions) as a client developer. Well-written operations are efficient, type-safe, and maintainable.\n\n## Operation Basics\n\n### Query Structure\n\n```graphql\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n    email\n  }\n}\n```\n\n### Mutation Structure\n\n```graphql\nmutation CreatePost($input: CreatePostInput!) {\n  createPost(input: $input) {\n    id\n    title\n    createdAt\n  }\n}\n```\n\n### Subscription Structure\n\n```graphql\nsubscription OnMessageReceived($channelId: ID!) {\n  messageReceived(channelId: $channelId) {\n    id\n    content\n    sender {\n      id\n      name\n    }\n  }\n}\n```\n\n## Quick Reference\n\n### Operation Naming\n\n| Pattern      | Example                                     |\n| ------------ | ------------------------------------------- |\n| Query        | `GetUser`, `ListPosts`, `SearchProducts`    |\n| Mutation     | `CreateUser`, `UpdatePost`, `DeleteComment` |\n| Subscription | `OnMessageReceived`, `OnUserStatusChanged`  |\n\n### Variable Syntax\n\n```graphql\n# Required variable\nquery GetUser($id: ID!) { ... }\n\n# Optional variable with default\nquery ListPosts($first: Int = 20) { ... }\n\n# Multiple variables\nquery SearchPosts($query: String!, $status: PostStatus, $first: Int = 10) { ... }\n```\n\n### Fragment Syntax\n\n```graphql\n# Define fragment\nfragment UserBasicInfo on User {\n  id\n  name\n  avatarUrl\n}\n\n# Use fragment\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    ...UserBasicInfo\n    email\n  }\n}\n```\n\n### Directives\n\n```graphql\nquery GetUser($id: ID!, $includeEmail: Boolean!) {\n  user(id: $id) {\n    id\n    name\n    email @include(if: $includeEmail)\n  }\n}\n\nquery GetPosts($skipDrafts: Boolean!) {\n  posts {\n    id\n    title\n    draft @skip(if: $skipDrafts)\n  }\n}\n```\n\n## Key Principles\n\n### 1. Request Only What You Need\n\n```graphql\n# Good: Specific fields\nquery GetUserName($id: ID!) {\n  user(id: $id) {\n    id\n    name\n  }\n}\n\n# Avoid: Over-fetching\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n    email\n    bio\n    posts {\n      id\n      title\n      content\n      comments {\n        id\n      }\n    }\n    followers {\n      id\n      name\n    }\n    # ... many unused fields\n  }\n}\n```\n\n### 2. Name All Operations\n\n```graphql\n# Good: Named operation\nquery GetUserPosts($userId: ID!) {\n  user(id: $userId) {\n    posts {\n      id\n      title\n    }\n  }\n}\n\n# Avoid: Anonymous operation\nquery {\n  user(id: \"123\") {\n    posts {\n      id\n      title\n    }\n  }\n}\n```\n\n### 3. Use Variables, Not Inline Values\n\n```graphql\n# Good: Variables\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n  }\n}\n\n# Avoid: Hardcoded values\nquery {\n  user(id: \"123\") {\n    id\n    name\n  }\n}\n```\n\n### 4. Colocate Fragments with Components\n\n```tsx\n\u002F\u002F UserAvatar.tsx\nexport const USER_AVATAR_FRAGMENT = gql`\n  fragment UserAvatar on User {\n    id\n    name\n    avatarUrl\n  }\n`;\n\nfunction UserAvatar({ user }) {\n  return \u003Cimg src={user.avatarUrl} alt={user.name} \u002F>;\n}\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Queries (`references\u002Fqueries.md`) - Query patterns and optimization\n- Mutations (`references\u002Fmutations.md`) - Mutation patterns and error handling\n- Fragments (`references\u002Ffragments.md`) - Fragment organization and reuse\n- Variables (`references\u002Fvariables.md`) - Variable usage and types\n- Tooling (`references\u002Ftooling.md`) - Code generation and linting\n\n## Ground Rules\n\n- ALWAYS name your operations (no anonymous queries\u002Fmutations)\n- ALWAYS use variables for dynamic values\n- ALWAYS request only the fields you need\n- ALWAYS include `id` field for cacheable types\n- NEVER hardcode values in operations\n- NEVER duplicate field selections across files\n- PREFER fragments for reusable field selections\n- PREFER colocating fragments with components\n- USE descriptive operation names that reflect purpose\n- USE `@include`\u002F`@skip` for conditional fields\n",{"name":5,"license":15,"metadata":44,"description":47,"allowed-tools":48,"compatibility":49},{"author":45,"version":46},"apollographql","1.0.0","Guide for writing GraphQL operations (queries, mutations, fragments) following best practices. Use this skill when: (1) writing GraphQL queries or mutations, (2) organizing operations with fragments, (3) optimizing data fetching patterns, (4) setting up type generation or linting, (5) reviewing operations for efficiency.\n","Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep","Any GraphQL client (Apollo Client, urql, Relay, etc.)","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_apollographql_graphql_operations",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill graphql-operations",{"tool":65,"command":66},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill graphql-operations",{"tool":68,"command":69},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill graphql-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_apollographql_graphql_operations\u002Fskill.md",true,[],[74,106,128,146,166,189],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":105},"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",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[86,87,88,89,90,91,92,93,94,95,96,97,98,99,36,100,101,102,103,104],"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":105},"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",[112],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[86,114,115,90,116,117,118,119,99,120,36,121,100,122,123,124,125,126,127,22],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":105},"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",[134],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[86,136,137,90,138,119,37,36,139,121,100,33,140,141,142,27,25,143,144,145],"react best practices","vercel react best practices","best practices","code","react components","next","refactoring","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":105},"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":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[154,90,155,25,156,157,158,159,145,160,161,162,36,163,121,100,164,165,101,86],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":105},"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",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000010","后端与接口",[176,177,178,179,138,180,181,182,22,143,119,183,184,37,185,162,186,187,188,36],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":212},"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",[195],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[197,198,199,200,201,96,202,159,203,99,204,205,36,86,206,207,208,209,210,211],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]