[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EC5EARD8906HF2AS6VQ8N":3,"skill-same:01M71EC5EARD8906HF2AS6VQ8N":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},"01M71EC5EARD8906HF2AS6VQ8N","apollo-federation",null,"Guide for authoring Apollo Federation subgraph schemas. Use this skill when: (1) creating new subgraph schemas for a federated supergraph, (2) defining or modifying entities with @key, (3) sharing types\u002Ffields across subgraphs with @shareable, (4) working with federation directives (@external, @requires, @provides, @override, @inaccessible), (5) troubleshooting composition errors, (6) any task involving federation schema design patterns.","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_apollo_federation\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"federation","apollo federation","apollo","new","design","when","directives","errors","types","authoring","across","patterns","design patterns","edit","write","read","Bash","Composition","server","library","2026-11-10 10:12:30",false,"---\nname: apollo-federation\ndescription: >\n  Guide for authoring Apollo Federation subgraph schemas. Use this skill when:\n  (1) creating new subgraph schemas for a federated supergraph,\n  (2) defining or modifying entities with @key,\n  (3) sharing types\u002Ffields across subgraphs with @shareable,\n  (4) working with federation directives (@external, @requires, @provides, @override, @inaccessible),\n  (5) troubleshooting composition errors,\n  (6) any task involving federation schema design patterns.\nlicense: MIT\ncompatibility: Works with any Federation 2.x compatible subgraph library (Apollo Server, GraphQL Yoga, etc.)\nmetadata:\n  author: apollographql\n  version: \"1.0.0\"\nallowed-tools: Bash(rover:*) Read Write Edit Glob Grep\n---\n\n# Apollo Federation Schema Authoring\n\nApollo Federation enables composing multiple GraphQL APIs (subgraphs) into a unified supergraph.\n\n## Federation 2 Schema Setup\n\nEvery Federation 2 subgraph must opt-in via `@link`:\n\n```graphql\nextend schema\n  @link(url: \"https:\u002F\u002Fspecs.apollo.dev\u002Ffederation\u002Fv2.12\",\n        import: [\"@key\", \"@shareable\", \"@external\", \"@requires\", \"@provides\"])\n```\n\nImport only the directives your subgraph uses.\n\n## Core Directives Quick Reference\n\n| Directive | Purpose | Example |\n|-----------|---------|---------|\n| `@key` | Define entity with unique key | `type Product @key(fields: \"id\")` |\n| `@shareable` | Allow multiple subgraphs to resolve field | `type Position @shareable { x: Int! }` |\n| `@external` | Reference field from another subgraph | `weight: Int @external` |\n| `@requires` | Computed field depending on external fields | `shippingCost: Int @requires(fields: \"weight\")` |\n| `@provides` | Conditionally resolve external field | `@provides(fields: \"name\")` |\n| `@override` | Migrate field to this subgraph | `@override(from: \"Products\")` |\n| `@inaccessible` | Hide from API schema | `internalId: ID! @inaccessible` |\n| `@interfaceObject` | Add fields to entity interface | `type Media @interfaceObject` |\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Directives (`references\u002Fdirectives.md`) - All federation directives with syntax, examples, and rules\n- Schema Patterns (`references\u002Fschema_patterns.md`) - Multi-subgraph patterns and recipes\n- Composition (`references\u002Fcomposition.md`) - Composition rules, error codes, and debugging\n\n## Key Patterns\n\n### Entity Definition\n\n```graphql\ntype Product @key(fields: \"id\") {\n  id: ID!\n  name: String!\n  price: Int\n}\n```\n\n### Entity Contributions Across Subgraphs\n\n```graphql\n# Products subgraph\ntype Product @key(fields: \"id\") {\n  id: ID!\n  name: String!\n  price: Int\n}\n\n# Reviews subgraph\ntype Product @key(fields: \"id\") {\n  id: ID!\n  reviews: [Review!]!\n  averageRating: Float\n}\n```\n\n### Computed Fields with @requires\n\n```graphql\ntype Product @key(fields: \"id\") {\n  id: ID!\n  size: Int @external\n  weight: Int @external\n  shippingEstimate: String @requires(fields: \"size weight\")\n}\n```\n\n### Value Types with @shareable\n\n```graphql\ntype Money @shareable {\n  amount: Int!\n  currency: String!\n}\n```\n\n### Entity Stub (Reference Without Contributing)\n\n```graphql\ntype Product @key(fields: \"id\", resolvable: false) {\n  id: ID!\n}\n```\n\n## Ground Rules\n\n- ALWAYS use Federation 2.x syntax with `@link` directive\n- ALWAYS import only the directives your subgraph uses\n- NEVER use `@shareable` without ensuring all subgraphs return identical values for that field\n- PREFER `@key` with single ID field for simple entity identification\n- USE `rover supergraph compose` to validate composition locally\n- USE `rover subgraph check` to validate against production supergraph\n","# Apollo Federation Schema Authoring\n\nApollo Federation enables composing multiple GraphQL APIs (subgraphs) into a unified supergraph.\n\n## Federation 2 Schema Setup\n\nEvery Federation 2 subgraph must opt-in via `@link`:\n\n```graphql\nextend schema\n  @link(url: \"https:\u002F\u002Fspecs.apollo.dev\u002Ffederation\u002Fv2.12\",\n        import: [\"@key\", \"@shareable\", \"@external\", \"@requires\", \"@provides\"])\n```\n\nImport only the directives your subgraph uses.\n\n## Core Directives Quick Reference\n\n| Directive | Purpose | Example |\n|-----------|---------|---------|\n| `@key` | Define entity with unique key | `type Product @key(fields: \"id\")` |\n| `@shareable` | Allow multiple subgraphs to resolve field | `type Position @shareable { x: Int! }` |\n| `@external` | Reference field from another subgraph | `weight: Int @external` |\n| `@requires` | Computed field depending on external fields | `shippingCost: Int @requires(fields: \"weight\")` |\n| `@provides` | Conditionally resolve external field | `@provides(fields: \"name\")` |\n| `@override` | Migrate field to this subgraph | `@override(from: \"Products\")` |\n| `@inaccessible` | Hide from API schema | `internalId: ID! @inaccessible` |\n| `@interfaceObject` | Add fields to entity interface | `type Media @interfaceObject` |\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Directives (`references\u002Fdirectives.md`) - All federation directives with syntax, examples, and rules\n- Schema Patterns (`references\u002Fschema_patterns.md`) - Multi-subgraph patterns and recipes\n- Composition (`references\u002Fcomposition.md`) - Composition rules, error codes, and debugging\n\n## Key Patterns\n\n### Entity Definition\n\n```graphql\ntype Product @key(fields: \"id\") {\n  id: ID!\n  name: String!\n  price: Int\n}\n```\n\n### Entity Contributions Across Subgraphs\n\n```graphql\n# Products subgraph\ntype Product @key(fields: \"id\") {\n  id: ID!\n  name: String!\n  price: Int\n}\n\n# Reviews subgraph\ntype Product @key(fields: \"id\") {\n  id: ID!\n  reviews: [Review!]!\n  averageRating: Float\n}\n```\n\n### Computed Fields with @requires\n\n```graphql\ntype Product @key(fields: \"id\") {\n  id: ID!\n  size: Int @external\n  weight: Int @external\n  shippingEstimate: String @requires(fields: \"size weight\")\n}\n```\n\n### Value Types with @shareable\n\n```graphql\ntype Money @shareable {\n  amount: Int!\n  currency: String!\n}\n```\n\n### Entity Stub (Reference Without Contributing)\n\n```graphql\ntype Product @key(fields: \"id\", resolvable: false) {\n  id: ID!\n}\n```\n\n## Ground Rules\n\n- ALWAYS use Federation 2.x syntax with `@link` directive\n- ALWAYS import only the directives your subgraph uses\n- NEVER use `@shareable` without ensuring all subgraphs return identical values for that field\n- PREFER `@key` with single ID field for simple entity identification\n- USE `rover supergraph compose` to validate composition locally\n- USE `rover subgraph check` to validate against production supergraph\n",{"name":5,"license":15,"metadata":44,"description":47,"allowed-tools":48,"compatibility":49},{"author":45,"version":46},"apollographql","1.0.0","Guide for authoring Apollo Federation subgraph schemas. Use this skill when: (1) creating new subgraph schemas for a federated supergraph, (2) defining or modifying entities with @key, (3) sharing types\u002Ffields across subgraphs with @shareable, (4) working with federation directives (@external, @requires, @provides, @override, @inaccessible), (5) troubleshooting composition errors, (6) any task involving federation schema design patterns.\n","Bash(rover:*) Read Write Edit Glob Grep","Works with any Federation 2.x compatible subgraph library (Apollo Server, GraphQL Yoga, etc.)","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_apollographql_apollo_federation",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 apollo-federation",{"tool":65,"command":66},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill apollo-federation",{"tool":68,"command":69},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill apollo-federation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_apollographql_apollo_federation\u002Fskill.md",true,[],[74,105,128,149,168,191],{"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":104},"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,27,96,97,98,24,99,100,101,102,103],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":104},"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",[111],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[86,113,114,90,115,116,117,118,98,119,24,120,99,121,122,123,124,125,126,127],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"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":104},"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,118,139,24,140,120,99,141,142,143,144,145,30,146,147,148],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","Optimization","guidelines","triggers",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":104},"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",[155],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[36,90,157,30,158,159,160,161,148,162,163,164,24,165,120,99,166,167,100,86],"composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":104},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000010","后端与接口",[178,179,180,181,138,182,183,184,127,146,118,185,186,139,187,164,188,189,190,24],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":213},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[197],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[199,200,201,202,203,27,204,161,205,98,206,207,24,86,208,209,37,210,211,212],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","markdown","rendering","vue","2026-11-10 10:56:23"]