[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71M3P4MHHS7KXZ5MVD071ST":3,"skill-same:01M71M3P4MHHS7KXZ5MVD071ST":78},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M71M3P4MHHS7KXZ5MVD071ST","apollo-server",null,"Guide for building GraphQL servers with Apollo Server 5.x. Use this skill when: (1) setting up a new Apollo Server project, (2) writing resolvers or defining GraphQL schemas, (3) implementing authentication or authorization, (4) creating plugins or custom data sources, (5) troubleshooting Apollo Server errors or performance issues.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_apollographql_apollo_server\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"server","apollo","apollo server","express","new","when","data sources","implementing","standalone","errors","fastify","sources","writing","project","up","read","Bash","issues","authentication","performance","2026-11-10 10:56:23",false,"---\nname: apollo-server\ndescription: >\n  Guide for building GraphQL servers with Apollo Server 5.x. Use this skill when:\n  (1) setting up a new Apollo Server project,\n  (2) writing resolvers or defining GraphQL schemas,\n  (3) implementing authentication or authorization,\n  (4) creating plugins or custom data sources,\n  (5) troubleshooting Apollo Server errors or performance issues.\nlicense: MIT\ncompatibility: Node.js v20+, TypeScript 4.7+. Works with Express v4\u002Fv5, standalone, Fastify, and serverless.\nmetadata:\n  author: apollographql\n  version: \"1.0.0\"\nallowed-tools: Bash(npm:*) Bash(npx:*) Bash(node:*) Read Write Edit Glob Grep\n---\n\n# Apollo Server 5.x Guide\n\nApollo Server is an open-source GraphQL server that works with any GraphQL schema. Apollo Server 5 is framework-agnostic and runs standalone or integrates with Express, Fastify, and serverless environments.\n\n## Quick Start\n\n### Step 1: Install\n\n```bash\nnpm install @apollo\u002Fserver graphql\n```\n\nFor Express integration:\n\n```bash\nnpm install @apollo\u002Fserver @as-integrations\u002Fexpress5 express graphql cors\n```\n\n### Step 2: Define Schema\n\n```typescript\nconst typeDefs = `#graphql\n  type Book {\n    title: String\n    author: String\n  }\n\n  type Query {\n    books: [Book]\n  }\n`;\n```\n\n### Step 3: Write Resolvers\n\n```typescript\nconst resolvers = {\n  Query: {\n    books: () => [\n      { title: \"The Great Gatsby\", author: \"F. Scott Fitzgerald\" },\n      { title: \"1984\", author: \"George Orwell\" },\n    ],\n  },\n};\n```\n\n### Step 4: Start Server\n\n**Standalone (Recommended for prototyping):**\n\nThe standalone server is great for prototyping, but for production services, we recommend integrating Apollo Server with a more fully-featured web framework such as Express, Koa, or Fastify. Swapping from the standalone server to a web framework later is straightforward.\n\n```typescript\nimport { ApolloServer } from \"@apollo\u002Fserver\";\nimport { startStandaloneServer } from \"@apollo\u002Fserver\u002Fstandalone\";\n\nconst server = new ApolloServer({ typeDefs, resolvers });\n\nconst { url } = await startStandaloneServer(server, {\n  listen: { port: 4000 },\n});\n\nconsole.log(`Server ready at ${url}`);\n```\n\n**Express:**\n\n```typescript\nimport { ApolloServer } from \"@apollo\u002Fserver\";\nimport { expressMiddleware } from \"@as-integrations\u002Fexpress5\";\nimport { ApolloServerPluginDrainHttpServer } from \"@apollo\u002Fserver\u002Fplugin\u002FdrainHttpServer\";\nimport express from \"express\";\nimport http from \"http\";\nimport cors from \"cors\";\n\nconst app = express();\nconst httpServer = http.createServer(app);\n\nconst server = new ApolloServer({\n  typeDefs,\n  resolvers,\n  plugins: [ApolloServerPluginDrainHttpServer({ httpServer })],\n});\n\nawait server.start();\n\napp.use(\n  \"\u002Fgraphql\",\n  cors(),\n  express.json(),\n  expressMiddleware(server, {\n    context: async ({ req }) => ({ token: req.headers.authorization }),\n  }),\n);\n\nawait new Promise\u003Cvoid>((resolve) => httpServer.listen({ port: 4000 }, resolve));\nconsole.log(\"Server ready at http:\u002F\u002Flocalhost:4000\u002Fgraphql\");\n```\n\n## Schema Definition\n\n### Scalar Types\n\n- `Int` - 32-bit integer\n- `Float` - Double-precision floating-point\n- `String` - UTF-8 string\n- `Boolean` - true\u002Ffalse\n- `ID` - Unique identifier (serialized as String)\n\n### Type Definitions\n\n```graphql\ntype User {\n  id: ID!\n  name: String!\n  email: String\n  posts: [Post!]!\n}\n\ntype Post {\n  id: ID!\n  title: String!\n  content: String\n  author: User!\n}\n\ninput CreatePostInput {\n  title: String!\n  content: String\n}\n\ntype Query {\n  user(id: ID!): User\n  users: [User!]!\n}\n\ntype Mutation {\n  createPost(input: CreatePostInput!): Post!\n}\n```\n\n### Enums and Interfaces\n\n```graphql\nenum Status {\n  DRAFT\n  PUBLISHED\n  ARCHIVED\n}\n\ninterface Node {\n  id: ID!\n}\n\ntype Article implements Node {\n  id: ID!\n  title: String!\n}\n```\n\n## Resolvers Overview\n\nResolvers follow the signature: `(parent, args, contextValue, info)`\n\n- **parent**: Result from parent resolver (root resolvers receive undefined)\n- **args**: Arguments passed to the field\n- **contextValue**: Shared context object (auth, dataSources, etc.)\n- **info**: Field-specific info and schema details (rarely used)\n\n```typescript\nconst resolvers = {\n  Query: {\n    user: async (_, { id }, { dataSources }) => {\n      return dataSources.usersAPI.getUser(id);\n    },\n  },\n  User: {\n    posts: async (parent, _, { dataSources }) => {\n      return dataSources.postsAPI.getPostsByAuthor(parent.id);\n    },\n  },\n  Mutation: {\n    createPost: async (_, { input }, { dataSources, user }) => {\n      if (!user) throw new GraphQLError(\"Not authenticated\");\n      return dataSources.postsAPI.create({ ...input, authorId: user.id });\n    },\n  },\n};\n```\n\n## Context Setup\n\nContext is created per-request and passed to all resolvers.\n\n```typescript\ninterface MyContext {\n  token?: string;\n  user?: User;\n  dataSources: {\n    usersAPI: UsersDataSource;\n    postsAPI: PostsDataSource;\n  };\n}\n\nconst server = new ApolloServer\u003CMyContext>({\n  typeDefs,\n  resolvers,\n});\n\n\u002F\u002F Standalone\nconst { url } = await startStandaloneServer(server, {\n  context: async ({ req }) => ({\n    token: req.headers.authorization || \"\",\n    user: await getUser(req.headers.authorization || \"\"),\n    dataSources: {\n      usersAPI: new UsersDataSource(),\n      postsAPI: new PostsDataSource(),\n    },\n  }),\n});\n\n\u002F\u002F Express middleware\nexpressMiddleware(server, {\n  context: async ({ req, res }) => ({\n    token: req.headers.authorization,\n    user: await getUser(req.headers.authorization),\n    dataSources: {\n      usersAPI: new UsersDataSource(),\n      postsAPI: new PostsDataSource(),\n    },\n  }),\n});\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Resolvers (`references\u002Fresolvers.md`) - Resolver patterns and best practices\n- Context and Auth (`references\u002Fcontext_and_auth.md`) - Authentication and authorization\n- Plugins (`references\u002Fplugins.md`) - Server and request lifecycle hooks\n- Data Sources (`references\u002Fdata_sources.md`) - RESTDataSource and DataLoader\n- Error Handling (`references\u002Ferror_handling.md`) - GraphQLError and error formatting\n- Troubleshooting (`references\u002Ftroubleshooting.md`) - Common issues and solutions\n\n## Key Rules\n\n### Schema Design\n\n- Use **!** (non-null) for fields that always have values\n- Prefer input types for mutations over inline arguments\n- Use interfaces for polymorphic types\n- Keep schema descriptions for documentation\n\n### Resolver Best Practices\n\n- Keep resolvers thin - delegate to services\u002Fdata sources\n- Always handle errors explicitly\n- Use DataLoader for batching related queries\n- Return partial data when possible (GraphQL's strength)\n\n### Performance\n\n- Use `@defer` and `@stream` for large responses\n- Implement DataLoader to solve N+1 queries\n- Consider persisted queries for production\n- Use caching headers and CDN where appropriate\n\n## Ground Rules\n\n- ALWAYS use Apollo Server 5.x patterns (not v4 or earlier)\n- ALWAYS type your context with TypeScript generics\n- ALWAYS use `GraphQLError` from `graphql` package for errors\n- NEVER expose stack traces in production errors\n- PREFER `startStandaloneServer` for prototyping only\n- USE an integration with a server framework like Express, Koa, Fastify, Next, etc. for production apps\n- IMPLEMENT authentication in context, authorization in resolvers\n","# Apollo Server 5.x Guide\n\nApollo Server is an open-source GraphQL server that works with any GraphQL schema. Apollo Server 5 is framework-agnostic and runs standalone or integrates with Express, Fastify, and serverless environments.\n\n## Quick Start\n\n### Step 1: Install\n\n```bash\nnpm install @apollo\u002Fserver graphql\n```\n\nFor Express integration:\n\n```bash\nnpm install @apollo\u002Fserver @as-integrations\u002Fexpress5 express graphql cors\n```\n\n### Step 2: Define Schema\n\n```typescript\nconst typeDefs = `#graphql\n  type Book {\n    title: String\n    author: String\n  }\n\n  type Query {\n    books: [Book]\n  }\n`;\n```\n\n### Step 3: Write Resolvers\n\n```typescript\nconst resolvers = {\n  Query: {\n    books: () => [\n      { title: \"The Great Gatsby\", author: \"F. Scott Fitzgerald\" },\n      { title: \"1984\", author: \"George Orwell\" },\n    ],\n  },\n};\n```\n\n### Step 4: Start Server\n\n**Standalone (Recommended for prototyping):**\n\nThe standalone server is great for prototyping, but for production services, we recommend integrating Apollo Server with a more fully-featured web framework such as Express, Koa, or Fastify. Swapping from the standalone server to a web framework later is straightforward.\n\n```typescript\nimport { ApolloServer } from \"@apollo\u002Fserver\";\nimport { startStandaloneServer } from \"@apollo\u002Fserver\u002Fstandalone\";\n\nconst server = new ApolloServer({ typeDefs, resolvers });\n\nconst { url } = await startStandaloneServer(server, {\n  listen: { port: 4000 },\n});\n\nconsole.log(`Server ready at ${url}`);\n```\n\n**Express:**\n\n```typescript\nimport { ApolloServer } from \"@apollo\u002Fserver\";\nimport { expressMiddleware } from \"@as-integrations\u002Fexpress5\";\nimport { ApolloServerPluginDrainHttpServer } from \"@apollo\u002Fserver\u002Fplugin\u002FdrainHttpServer\";\nimport express from \"express\";\nimport http from \"http\";\nimport cors from \"cors\";\n\nconst app = express();\nconst httpServer = http.createServer(app);\n\nconst server = new ApolloServer({\n  typeDefs,\n  resolvers,\n  plugins: [ApolloServerPluginDrainHttpServer({ httpServer })],\n});\n\nawait server.start();\n\napp.use(\n  \"\u002Fgraphql\",\n  cors(),\n  express.json(),\n  expressMiddleware(server, {\n    context: async ({ req }) => ({ token: req.headers.authorization }),\n  }),\n);\n\nawait new Promise\u003Cvoid>((resolve) => httpServer.listen({ port: 4000 }, resolve));\nconsole.log(\"Server ready at http:\u002F\u002Flocalhost:4000\u002Fgraphql\");\n```\n\n## Schema Definition\n\n### Scalar Types\n\n- `Int` - 32-bit integer\n- `Float` - Double-precision floating-point\n- `String` - UTF-8 string\n- `Boolean` - true\u002Ffalse\n- `ID` - Unique identifier (serialized as String)\n\n### Type Definitions\n\n```graphql\ntype User {\n  id: ID!\n  name: String!\n  email: String\n  posts: [Post!]!\n}\n\ntype Post {\n  id: ID!\n  title: String!\n  content: String\n  author: User!\n}\n\ninput CreatePostInput {\n  title: String!\n  content: String\n}\n\ntype Query {\n  user(id: ID!): User\n  users: [User!]!\n}\n\ntype Mutation {\n  createPost(input: CreatePostInput!): Post!\n}\n```\n\n### Enums and Interfaces\n\n```graphql\nenum Status {\n  DRAFT\n  PUBLISHED\n  ARCHIVED\n}\n\ninterface Node {\n  id: ID!\n}\n\ntype Article implements Node {\n  id: ID!\n  title: String!\n}\n```\n\n## Resolvers Overview\n\nResolvers follow the signature: `(parent, args, contextValue, info)`\n\n- **parent**: Result from parent resolver (root resolvers receive undefined)\n- **args**: Arguments passed to the field\n- **contextValue**: Shared context object (auth, dataSources, etc.)\n- **info**: Field-specific info and schema details (rarely used)\n\n```typescript\nconst resolvers = {\n  Query: {\n    user: async (_, { id }, { dataSources }) => {\n      return dataSources.usersAPI.getUser(id);\n    },\n  },\n  User: {\n    posts: async (parent, _, { dataSources }) => {\n      return dataSources.postsAPI.getPostsByAuthor(parent.id);\n    },\n  },\n  Mutation: {\n    createPost: async (_, { input }, { dataSources, user }) => {\n      if (!user) throw new GraphQLError(\"Not authenticated\");\n      return dataSources.postsAPI.create({ ...input, authorId: user.id });\n    },\n  },\n};\n```\n\n## Context Setup\n\nContext is created per-request and passed to all resolvers.\n\n```typescript\ninterface MyContext {\n  token?: string;\n  user?: User;\n  dataSources: {\n    usersAPI: UsersDataSource;\n    postsAPI: PostsDataSource;\n  };\n}\n\nconst server = new ApolloServer\u003CMyContext>({\n  typeDefs,\n  resolvers,\n});\n\n\u002F\u002F Standalone\nconst { url } = await startStandaloneServer(server, {\n  context: async ({ req }) => ({\n    token: req.headers.authorization || \"\",\n    user: await getUser(req.headers.authorization || \"\"),\n    dataSources: {\n      usersAPI: new UsersDataSource(),\n      postsAPI: new PostsDataSource(),\n    },\n  }),\n});\n\n\u002F\u002F Express middleware\nexpressMiddleware(server, {\n  context: async ({ req, res }) => ({\n    token: req.headers.authorization,\n    user: await getUser(req.headers.authorization),\n    dataSources: {\n      usersAPI: new UsersDataSource(),\n      postsAPI: new PostsDataSource(),\n    },\n  }),\n});\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Resolvers (`references\u002Fresolvers.md`) - Resolver patterns and best practices\n- Context and Auth (`references\u002Fcontext_and_auth.md`) - Authentication and authorization\n- Plugins (`references\u002Fplugins.md`) - Server and request lifecycle hooks\n- Data Sources (`references\u002Fdata_sources.md`) - RESTDataSource and DataLoader\n- Error Handling (`references\u002Ferror_handling.md`) - GraphQLError and error formatting\n- Troubleshooting (`references\u002Ftroubleshooting.md`) - Common issues and solutions\n\n## Key Rules\n\n### Schema Design\n\n- Use **!** (non-null) for fields that always have values\n- Prefer input types for mutations over inline arguments\n- Use interfaces for polymorphic types\n- Keep schema descriptions for documentation\n\n### Resolver Best Practices\n\n- Keep resolvers thin - delegate to services\u002Fdata sources\n- Always handle errors explicitly\n- Use DataLoader for batching related queries\n- Return partial data when possible (GraphQL's strength)\n\n### Performance\n\n- Use `@defer` and `@stream` for large responses\n- Implement DataLoader to solve N+1 queries\n- Consider persisted queries for production\n- Use caching headers and CDN where appropriate\n\n## Ground Rules\n\n- ALWAYS use Apollo Server 5.x patterns (not v4 or earlier)\n- ALWAYS type your context with TypeScript generics\n- ALWAYS use `GraphQLError` from `graphql` package for errors\n- NEVER expose stack traces in production errors\n- PREFER `startStandaloneServer` for prototyping only\n- USE an integration with a server framework like Express, Koa, Fastify, Next, etc. for production apps\n- IMPLEMENT authentication in context, authorization in resolvers\n",{"name":5,"license":15,"metadata":49,"description":52,"allowed-tools":53,"compatibility":54},{"author":50,"version":51},"apollographql","1.0.0","Guide for building GraphQL servers with Apollo Server 5.x. Use this skill when: (1) setting up a new Apollo Server project, (2) writing resolvers or defining GraphQL schemas, (3) implementing authentication or authorization, (4) creating plugins or custom data sources, (5) troubleshooting Apollo Server errors or performance issues.\n","Bash(npm:*) Bash(npx:*) Bash(node:*) Read Write Edit Glob Grep","Node.js v20+, TypeScript 4.7+. Works with Express v4\u002Fv5, standalone, Fastify, and serverless.","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_apollographql_apollo_server",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill apollo-server",{"tool":70,"command":71},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill apollo-server",{"tool":73,"command":74},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill apollo-server","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_apollographql_apollo_server\u002Fskill.md",true,[],[79,108,130,151,171,192],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":88,"publishedAt":107},"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",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[89,90,91,92,93,94,95,96,97,98,99,100,101,31,29,102,103,104,105,106],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":107},"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",[114],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[89,116,117,93,118,119,120,43,31,121,29,122,102,123,124,125,126,127,128,129],"react native","native","vercel react native skills","react native skills","modules","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":107},"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",[136],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[89,138,139,93,140,43,36,29,141,122,102,142,143,144,145,146,147,148,149,150],"react best practices","vercel react best practices","best practices","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":107},"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",[157],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[159,93,160,147,161,162,163,164,150,165,166,167,29,168,122,102,169,170,103,89],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":107},"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",[177],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[179,180,181,182,140,183,184,185,129,148,43,186,187,36,188,167,189,190,191,29],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":44},"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",[198],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[200,201,202,203,204,99,205,164,41,31,206,207,29,89,208,209,24,210,211,212],"text","portable text serialization","portable","serialization","extracting","strings","frontend","svelte","sanity","astro","markdown","rendering","vue"]