[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ECCX0KANK8RH7D18Y69WR":3,"skill-same:01M71ECCX0KANK8RH7D18Y69WR":81},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M71ECCX0KANK8RH7D18Y69WR","apollo-mcp-server",null,"Guide for using Apollo MCP Server to connect AI agents with GraphQL APIs. Use this skill when: (1) setting up or configuring Apollo MCP Server, (2) defining MCP tools from GraphQL operations, (3) using introspection tools (introspect, search, validate, execute), (4) troubleshooting MCP server connectivity or tool execution 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\u002F.ai\u002Fskills\u002Fofficial_apollographql_apollo_mcp_server\u002Fskill.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"mcp server","server","apollo mcp server","apollo","MCP","setting","graphql operations","guide","Tools","edit","write","read","ai agents","code","Bash","when","connect","issues","up","search","2026-11-10 10:12:30",false,"---\nname: apollo-mcp-server\ndescription: >\n  Guide for using Apollo MCP Server to connect AI agents with GraphQL APIs.\n  Use this skill when: (1) setting up or configuring Apollo MCP Server,\n  (2) defining MCP tools from GraphQL operations, (3) using introspection\n  tools (introspect, search, validate, execute), (4) troubleshooting\n  MCP server connectivity or tool execution issues.\nlicense: MIT\ncompatibility: Works with Claude Code, Claude Desktop, Cursor.\nmetadata:\n  author: apollographql\n  version: \"1.1.1\"\nallowed-tools: Bash(rover:*) Bash(npx:*) Read Write Edit Glob Grep\n---\n\n# Apollo MCP Server Guide\n\nApollo MCP Server exposes GraphQL operations as MCP tools, enabling AI agents to interact with GraphQL APIs through the Model Context Protocol.\n\n## Quick Start\n\n### Step 1: Install\n\n```bash\n# Linux \u002F MacOS\ncurl -sSL https:\u002F\u002Fmcp.apollo.dev\u002Fdownload\u002Fnix\u002Flatest | sh\n\n# Windows\niwr 'https:\u002F\u002Fmcp.apollo.dev\u002Fdownload\u002Fwin\u002Flatest' | iex\n```\n\n### Step 2: Configure\n\nCreate `config.yaml` in your project root:\n\n```yaml\n# config.yaml\ntransport:\n  type: streamable_http\nschema:\n  source: local\n  path: .\u002Fschema.graphql\noperations:\n  source: local\n  paths:\n    - .\u002Foperations\u002F\nintrospection:\n  introspect:\n    enabled: true\n  search:\n    enabled: true\n  validate:\n    enabled: true\n  execute:\n    enabled: true\n```\n\nStart the server:\n```bash\napollo-mcp-server .\u002Fconfig.yaml\n```\n\nThe MCP endpoint is available at `http:\u002F\u002F127.0.0.1:8000\u002Fmcp` (streamable_http defaults: address `127.0.0.1`, port `8000`). The GraphQL endpoint defaults to `http:\u002F\u002Flocalhost:4000\u002F` — override with the `endpoint` key if your API runs elsewhere.\n\n### Step 3: Connect\n\nAdd to your MCP client configuration:\n\n**Streamable HTTP (recommended):**\n\nClaude Desktop (`claude_desktop_config.json`):\n```json\n{\n  \"mcpServers\": {\n    \"graphql-api\": {\n      \"command\": \"npx\",\n      \"args\": [\"mcp-remote\", \"http:\u002F\u002F127.0.0.1:8000\u002Fmcp\"]\n    }\n  }\n}\n```\n\nClaude Code:\n```bash\nclaude mcp add graphql-api -- npx mcp-remote http:\u002F\u002F127.0.0.1:8000\u002Fmcp\n```\n\n**Stdio (client launches the server directly):**\n\nClaude Desktop (`claude_desktop_config.json`) or Claude Code (`.mcp.json`):\n```json\n{\n  \"mcpServers\": {\n    \"graphql-api\": {\n      \"command\": \".\u002Fapollo-mcp-server\",\n      \"args\": [\".\u002Fconfig.yaml\"]\n    }\n  }\n}\n```\n\n## Built-in Tools\n\nApollo MCP Server provides four introspection tools:\n\n| Tool | Purpose | When to Use |\n|------|---------|-------------|\n| `introspect` | Explore schema types in detail | Need type definitions, fields, relationships |\n| `search` | Find types in schema | Looking for specific types or fields |\n| `validate` | Check operation validity | Before executing operations |\n| `execute` | Run ad-hoc GraphQL operations | Testing or one-off queries |\n\n## Defining Custom Tools\n\nMCP tools are created from GraphQL operations. Three methods:\n\n### 1. Operation Files (Recommended)\n\n```yaml\noperations:\n  source: local\n  paths:\n    - .\u002Foperations\u002F\n```\n\nEach file must contain exactly one operation. Each named operation becomes an MCP tool.\n\n```graphql\n# operations\u002FGetUser.graphql\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n    email\n  }\n}\n```\n\n```graphql\n# operations\u002FCreateUser.graphql\nmutation CreateUser($input: CreateUserInput!) {\n  createUser(input: $input) {\n    id\n    name\n  }\n}\n```\n\n### 2. Operation Collections\n\n```yaml\noperations:\n  source: collection\n  id: your-collection-id\n```\n\nUse GraphOS Studio to manage operations collaboratively.\n\n### 3. Persisted Queries\n\n```yaml\noperations:\n  source: manifest\n  path: .\u002Fpersisted-query-manifest.json\n```\n\nFor production environments with pre-approved operations.\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Tools (`references\u002Ftools.md`) - Introspection tools and minify notation\n- Configuration (`references\u002Fconfiguration.md`) - All configuration options\n- Troubleshooting (`references\u002Ftroubleshooting.md`) - Common issues and solutions\n\n## Key Rules\n\n### Security\n\n- **Never expose sensitive operations** without authentication\n- Use `headers` configuration for API keys and tokens\n- Disable introspection tools in production (they are disabled by default)\n- Set `overrides.mutation_mode: explicit` to require confirmation for mutations\n\n### Authentication\n\n```yaml\n# Static header\nheaders:\n  Authorization: \"Bearer ${env.API_TOKEN}\"\n\n# Dynamic header forwarding\nforward_headers:\n  - x-forwarded-token\n\n# OAuth (streamable_http transport)\ntransport:\n  type: streamable_http\n  auth:\n    servers:\n      - https:\u002F\u002Fauth.example.com\u002F.well-known\u002Fopenid-configuration\n    audiences:\n      - https:\u002F\u002Fapi.example.com\n```\n\n### Token Optimization\n\nEnable minification to reduce token usage:\n\n```yaml\nintrospection:\n  introspect:\n    minify: true\n  search:\n    minify: true\n```\n\nMinified output uses compact notation:\n- **T** = type, **I** = input, **E** = enum\n- **s** = String, **i** = Int, **b** = Boolean, **f** = Float, **d** = ID\n- **!** = required, **[]** = list\n\n### Mutations\n\nControl mutation behavior via the `overrides` section:\n\n```yaml\noverrides:\n  mutation_mode: all       # Execute mutations directly\n  # mutation_mode: explicit  # Require explicit confirmation\n  # mutation_mode: none      # Block all mutations (default)\n```\n\n## Common Patterns\n\n### GraphOS Cloud Schema\n\n```yaml\n# schema.source defaults to uplink — can be omitted when graphos is configured\ngraphos:\n  apollo_key: ${env.APOLLO_KEY}\n  apollo_graph_ref: my-graph@production\n```\n\n### Local Development\n\n```yaml\ntransport:\n  type: streamable_http\nschema:\n  source: local\n  path: .\u002Fschema.graphql\nintrospection:\n  introspect:\n    enabled: true\n  search:\n    enabled: true\n  validate:\n    enabled: true\n  execute:\n    enabled: true\noverrides:\n  mutation_mode: all\n```\n\n### Production Setup\n\n```yaml\ntransport:\n  type: streamable_http\nendpoint: https:\u002F\u002Fapi.production.com\u002Fgraphql\noperations:\n  source: manifest\n  path: .\u002Fpersisted-query-manifest.json\ngraphos:\n  apollo_key: ${env.APOLLO_KEY}\n  apollo_graph_ref: ${env.APOLLO_GRAPH_REF}\nheaders:\n  Authorization: \"Bearer ${env.API_TOKEN}\"\nhealth_check:\n  enabled: true\n```\n\n### Docker\n\n```yaml\ntransport:\n  type: streamable_http\n  address: 0.0.0.0\n  port: 8000\nendpoint: ${env.GRAPHQL_ENDPOINT}\ngraphos:\n  apollo_key: ${env.APOLLO_KEY}\n  apollo_graph_ref: ${env.APOLLO_GRAPH_REF}\nhealth_check:\n  enabled: true\n```\n\n## Ground Rules\n\n- ALWAYS configure authentication before exposing to AI agents\n- ALWAYS use `mutation_mode: explicit` or `mutation_mode: none` in shared environments\n- NEVER expose introspection tools with write access to production data\n- PREFER operation files over ad-hoc execute for predictable behavior\n- PREFER streamable_http transport for remote and multi-client deployments\n- USE stdio only when the MCP client launches the server process directly\n- USE GraphOS Studio collections for team collaboration\n","# Apollo MCP Server Guide\n\nApollo MCP Server exposes GraphQL operations as MCP tools, enabling AI agents to interact with GraphQL APIs through the Model Context Protocol.\n\n## Quick Start\n\n### Step 1: Install\n\n```bash\n# Linux \u002F MacOS\ncurl -sSL https:\u002F\u002Fmcp.apollo.dev\u002Fdownload\u002Fnix\u002Flatest | sh\n\n# Windows\niwr 'https:\u002F\u002Fmcp.apollo.dev\u002Fdownload\u002Fwin\u002Flatest' | iex\n```\n\n### Step 2: Configure\n\nCreate `config.yaml` in your project root:\n\n```yaml\n# config.yaml\ntransport:\n  type: streamable_http\nschema:\n  source: local\n  path: .\u002Fschema.graphql\noperations:\n  source: local\n  paths:\n    - .\u002Foperations\u002F\nintrospection:\n  introspect:\n    enabled: true\n  search:\n    enabled: true\n  validate:\n    enabled: true\n  execute:\n    enabled: true\n```\n\nStart the server:\n```bash\napollo-mcp-server .\u002Fconfig.yaml\n```\n\nThe MCP endpoint is available at `http:\u002F\u002F127.0.0.1:8000\u002Fmcp` (streamable_http defaults: address `127.0.0.1`, port `8000`). The GraphQL endpoint defaults to `http:\u002F\u002Flocalhost:4000\u002F` — override with the `endpoint` key if your API runs elsewhere.\n\n### Step 3: Connect\n\nAdd to your MCP client configuration:\n\n**Streamable HTTP (recommended):**\n\nClaude Desktop (`claude_desktop_config.json`):\n```json\n{\n  \"mcpServers\": {\n    \"graphql-api\": {\n      \"command\": \"npx\",\n      \"args\": [\"mcp-remote\", \"http:\u002F\u002F127.0.0.1:8000\u002Fmcp\"]\n    }\n  }\n}\n```\n\nClaude Code:\n```bash\nclaude mcp add graphql-api -- npx mcp-remote http:\u002F\u002F127.0.0.1:8000\u002Fmcp\n```\n\n**Stdio (client launches the server directly):**\n\nClaude Desktop (`claude_desktop_config.json`) or Claude Code (`.mcp.json`):\n```json\n{\n  \"mcpServers\": {\n    \"graphql-api\": {\n      \"command\": \".\u002Fapollo-mcp-server\",\n      \"args\": [\".\u002Fconfig.yaml\"]\n    }\n  }\n}\n```\n\n## Built-in Tools\n\nApollo MCP Server provides four introspection tools:\n\n| Tool | Purpose | When to Use |\n|------|---------|-------------|\n| `introspect` | Explore schema types in detail | Need type definitions, fields, relationships |\n| `search` | Find types in schema | Looking for specific types or fields |\n| `validate` | Check operation validity | Before executing operations |\n| `execute` | Run ad-hoc GraphQL operations | Testing or one-off queries |\n\n## Defining Custom Tools\n\nMCP tools are created from GraphQL operations. Three methods:\n\n### 1. Operation Files (Recommended)\n\n```yaml\noperations:\n  source: local\n  paths:\n    - .\u002Foperations\u002F\n```\n\nEach file must contain exactly one operation. Each named operation becomes an MCP tool.\n\n```graphql\n# operations\u002FGetUser.graphql\nquery GetUser($id: ID!) {\n  user(id: $id) {\n    id\n    name\n    email\n  }\n}\n```\n\n```graphql\n# operations\u002FCreateUser.graphql\nmutation CreateUser($input: CreateUserInput!) {\n  createUser(input: $input) {\n    id\n    name\n  }\n}\n```\n\n### 2. Operation Collections\n\n```yaml\noperations:\n  source: collection\n  id: your-collection-id\n```\n\nUse GraphOS Studio to manage operations collaboratively.\n\n### 3. Persisted Queries\n\n```yaml\noperations:\n  source: manifest\n  path: .\u002Fpersisted-query-manifest.json\n```\n\nFor production environments with pre-approved operations.\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- Tools (`references\u002Ftools.md`) - Introspection tools and minify notation\n- Configuration (`references\u002Fconfiguration.md`) - All configuration options\n- Troubleshooting (`references\u002Ftroubleshooting.md`) - Common issues and solutions\n\n## Key Rules\n\n### Security\n\n- **Never expose sensitive operations** without authentication\n- Use `headers` configuration for API keys and tokens\n- Disable introspection tools in production (they are disabled by default)\n- Set `overrides.mutation_mode: explicit` to require confirmation for mutations\n\n### Authentication\n\n```yaml\n# Static header\nheaders:\n  Authorization: \"Bearer ${env.API_TOKEN}\"\n\n# Dynamic header forwarding\nforward_headers:\n  - x-forwarded-token\n\n# OAuth (streamable_http transport)\ntransport:\n  type: streamable_http\n  auth:\n    servers:\n      - https:\u002F\u002Fauth.example.com\u002F.well-known\u002Fopenid-configuration\n    audiences:\n      - https:\u002F\u002Fapi.example.com\n```\n\n### Token Optimization\n\nEnable minification to reduce token usage:\n\n```yaml\nintrospection:\n  introspect:\n    minify: true\n  search:\n    minify: true\n```\n\nMinified output uses compact notation:\n- **T** = type, **I** = input, **E** = enum\n- **s** = String, **i** = Int, **b** = Boolean, **f** = Float, **d** = ID\n- **!** = required, **[]** = list\n\n### Mutations\n\nControl mutation behavior via the `overrides` section:\n\n```yaml\noverrides:\n  mutation_mode: all       # Execute mutations directly\n  # mutation_mode: explicit  # Require explicit confirmation\n  # mutation_mode: none      # Block all mutations (default)\n```\n\n## Common Patterns\n\n### GraphOS Cloud Schema\n\n```yaml\n# schema.source defaults to uplink — can be omitted when graphos is configured\ngraphos:\n  apollo_key: ${env.APOLLO_KEY}\n  apollo_graph_ref: my-graph@production\n```\n\n### Local Development\n\n```yaml\ntransport:\n  type: streamable_http\nschema:\n  source: local\n  path: .\u002Fschema.graphql\nintrospection:\n  introspect:\n    enabled: true\n  search:\n    enabled: true\n  validate:\n    enabled: true\n  execute:\n    enabled: true\noverrides:\n  mutation_mode: all\n```\n\n### Production Setup\n\n```yaml\ntransport:\n  type: streamable_http\nendpoint: https:\u002F\u002Fapi.production.com\u002Fgraphql\noperations:\n  source: manifest\n  path: .\u002Fpersisted-query-manifest.json\ngraphos:\n  apollo_key: ${env.APOLLO_KEY}\n  apollo_graph_ref: ${env.APOLLO_GRAPH_REF}\nheaders:\n  Authorization: \"Bearer ${env.API_TOKEN}\"\nhealth_check:\n  enabled: true\n```\n\n### Docker\n\n```yaml\ntransport:\n  type: streamable_http\n  address: 0.0.0.0\n  port: 8000\nendpoint: ${env.GRAPHQL_ENDPOINT}\ngraphos:\n  apollo_key: ${env.APOLLO_KEY}\n  apollo_graph_ref: ${env.APOLLO_GRAPH_REF}\nhealth_check:\n  enabled: true\n```\n\n## Ground Rules\n\n- ALWAYS configure authentication before exposing to AI agents\n- ALWAYS use `mutation_mode: explicit` or `mutation_mode: none` in shared environments\n- NEVER expose introspection tools with write access to production data\n- PREFER operation files over ad-hoc execute for predictable behavior\n- PREFER streamable_http transport for remote and multi-client deployments\n- USE stdio only when the MCP client launches the server process directly\n- USE GraphOS Studio collections for team collaboration\n",{"name":5,"license":15,"metadata":52,"description":55,"allowed-tools":56,"compatibility":57},{"author":53,"version":54},"apollographql","1.1.1","Guide for using Apollo MCP Server to connect AI agents with GraphQL APIs. Use this skill when: (1) setting up or configuring Apollo MCP Server, (2) defining MCP tools from GraphQL operations, (3) using introspection tools (introspect, search, validate, execute), (4) troubleshooting MCP server connectivity or tool execution issues.\n","Bash(rover:*) Bash(npx:*) Read Write Edit Glob Grep","Works with Claude Code, Claude Desktop, Cursor.","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_apollographql_apollo_mcp_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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill apollo-mcp-server",{"tool":73,"command":74},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill apollo-mcp-server",{"tool":76,"command":77},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill apollo-mcp-server","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_apollographql_apollo_mcp_server\u002Fskill.md",true,[],[82,112,135,156,176,197],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":111},"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",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,42,106,107,108,109,110],"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":111},"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",[118],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},[92,120,121,96,122,123,124,125,105,126,42,127,106,128,129,130,131,132,133,134],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":111},"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",[141],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},[92,143,144,96,145,125,146,42,40,127,106,147,148,149,150,151,152,153,154,155],"react best practices","vercel react best practices","best practices","writing","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":111},"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",[162],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},[164,96,165,152,166,167,168,169,155,170,171,172,42,173,127,106,174,175,107,92],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":111},"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",[182],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[184,185,186,187,145,188,189,190,134,153,125,191,192,146,193,172,194,195,196,42],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"publishedAt":218},"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",[203],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},[205,206,207,208,209,102,210,169,44,105,211,212,42,92,213,214,28,215,216,217],"text","portable text serialization","portable","serialization","extracting","strings","frontend","svelte","sanity","astro","markdown","rendering","vue","2026-11-10 10:56:23"]