[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWJ0SMFV3DXSWT3D553PRY":3,"skill-same:01M7BWJ0SMFV3DXSWT3D553PRY":75},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7BWJ0SMFV3DXSWT3D553PRY","graphql-schema",null,"Guide for designing GraphQL schemas following industry best practices. Use this skill when: (1) designing a new GraphQL schema or API, (2) reviewing existing schema for improvements, (3) deciding on type structures or nullability, (4) implementing pagination or error patterns, (5) ensuring security in schema design.","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: graphql-schema\ndescription: >\n  Guide for designing GraphQL schemas following industry best practices. Use this skill when:\n  (1) designing a new GraphQL schema or API,\n  (2) reviewing existing schema for improvements,\n  (3) deciding on type structures or nullability,\n  (4) implementing pagination or error patterns,\n  (5) ensuring security in schema design.\nlicense: MIT\ncompatibility: Any GraphQL implementation (Apollo Server, graphql-js, Yoga, etc.)\nmetadata:\n  author: apollographql\n  version: \"1.0.1\"\nallowed-tools: Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep\n---\n\n# GraphQL Schema Design Guide\n\nThis guide covers best practices for designing GraphQL schemas that are intuitive, performant, and maintainable. Schema design is primarily a server-side concern that directly impacts API usability.\n\n## Schema Design Principles\n\n### 1. Design for Client Needs\n\n- Think about what queries clients will write\n- Organize types around use cases, not database tables\n- Expose capabilities, not implementation details\n\n### 2. Be Explicit\n\n- Use clear, descriptive names\n- Make nullability intentional\n- Document with descriptions\n\n### 3. Design for Evolution\n\n- Plan for backwards compatibility\n- Use deprecation before removal\n- Avoid breaking changes\n\n## Quick Reference\n\n### Type Definition Syntax\n\n```graphql\n\"\"\"\nA user in the system.\n\"\"\"\ntype User {\n  id: ID!\n  email: String!\n  name: String\n  posts(first: Int = 10, after: String): PostConnection!\n  createdAt: DateTime!\n}\n```\n\n### Nullability Rules\n\n| Pattern | Meaning |\n|---------|---------|\n| String | Nullable - may be null |\n| String! | Non-null - always has value |\n| [String] | Nullable list, nullable items |\n| [String!] | Nullable list, non-null items |\n| [String]! | Non-null list, nullable items |\n| [String!]! | Non-null list, non-null items |\n\n**Best Practice:** Use **[Type!]!** for lists - empty list over null, no null items.\n\n### Input vs Output Types\n\n```graphql\n# Output type - what clients receive\ntype User {\n  id: ID!\n  email: String!\n  createdAt: DateTime!\n}\n\n# Input type - what clients send\ninput CreateUserInput {\n  email: String!\n  name: String\n}\n\n# Mutation using input type\ntype Mutation {\n  createUser(input: CreateUserInput!): User!\n}\n```\n\n### Interface Pattern\n\n```graphql\ninterface Node {\n  id: ID!\n}\n\ntype User implements Node {\n  id: ID!\n  email: String!\n}\n\ntype Post implements Node {\n  id: ID!\n  title: String!\n}\n```\n\n### Union Pattern\n\n```graphql\nunion SearchResult = User | Post | Comment\n\ntype Query {\n  search(query: String!): [SearchResult!]!\n}\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- [Types](references\u002Ftypes.md) - Type design patterns, interfaces, unions, and custom scalars\n- [Naming](references\u002Fnaming.md) - Naming conventions for types, fields, and arguments\n- [Pagination](references\u002Fpagination.md) - Connection pattern and cursor-based pagination\n- [Errors](references\u002Ferrors.md) - Error modeling and result types\n- [Security](references\u002Fsecurity.md) - Security best practices for schema design\n\n## Key Rules\n\n### Type Design\n\n- Define types based on domain concepts, not data storage\n- Use interfaces for shared fields across types\n- Use unions for mutually exclusive types\n- Keep types focused (single responsibility)\n- Avoid deep nesting - flatten when possible\n\n### Field Design\n\n- Fields should be named from client's perspective\n- Return the most specific type possible\n- Make expensive fields explicit (consider arguments)\n- Use arguments for filtering, sorting, pagination\n\n### Mutation Design\n\n- Use single input argument pattern: `mutation(input: InputType!)`\n- Return affected objects in mutation responses\n- Model mutations around business operations, not CRUD\n- Consider returning a union of success\u002Ferror types\n\n### ID Strategy\n\n- Use globally unique IDs when possible\n- Implement `Node` interface for refetchability\n- Base64-encode compound IDs if needed\n\n## Ground Rules\n\n- ALWAYS add descriptions to types and fields\n- ALWAYS use non-null (**!**) for fields that cannot be null\n- ALWAYS use **[Type!]!** pattern for lists\n- NEVER expose database internals in schema\n- NEVER break backwards compatibility without deprecation\n- PREFER dedicated input types over many arguments\n- PREFER enums over arbitrary strings for fixed values\n- USE `ID` type for identifiers, not `String` or `Int`\n- USE custom scalars for domain-specific values (DateTime, Email, URL)\n","# GraphQL Schema Design Guide\n\nThis guide covers best practices for designing GraphQL schemas that are intuitive, performant, and maintainable. Schema design is primarily a server-side concern that directly impacts API usability.\n\n## Schema Design Principles\n\n### 1. Design for Client Needs\n\n- Think about what queries clients will write\n- Organize types around use cases, not database tables\n- Expose capabilities, not implementation details\n\n### 2. Be Explicit\n\n- Use clear, descriptive names\n- Make nullability intentional\n- Document with descriptions\n\n### 3. Design for Evolution\n\n- Plan for backwards compatibility\n- Use deprecation before removal\n- Avoid breaking changes\n\n## Quick Reference\n\n### Type Definition Syntax\n\n```graphql\n\"\"\"\nA user in the system.\n\"\"\"\ntype User {\n  id: ID!\n  email: String!\n  name: String\n  posts(first: Int = 10, after: String): PostConnection!\n  createdAt: DateTime!\n}\n```\n\n### Nullability Rules\n\n| Pattern | Meaning |\n|---------|---------|\n| String | Nullable - may be null |\n| String! | Non-null - always has value |\n| [String] | Nullable list, nullable items |\n| [String!] | Nullable list, non-null items |\n| [String]! | Non-null list, nullable items |\n| [String!]! | Non-null list, non-null items |\n\n**Best Practice:** Use **[Type!]!** for lists - empty list over null, no null items.\n\n### Input vs Output Types\n\n```graphql\n# Output type - what clients receive\ntype User {\n  id: ID!\n  email: String!\n  createdAt: DateTime!\n}\n\n# Input type - what clients send\ninput CreateUserInput {\n  email: String!\n  name: String\n}\n\n# Mutation using input type\ntype Mutation {\n  createUser(input: CreateUserInput!): User!\n}\n```\n\n### Interface Pattern\n\n```graphql\ninterface Node {\n  id: ID!\n}\n\ntype User implements Node {\n  id: ID!\n  email: String!\n}\n\ntype Post implements Node {\n  id: ID!\n  title: String!\n}\n```\n\n### Union Pattern\n\n```graphql\nunion SearchResult = User | Post | Comment\n\ntype Query {\n  search(query: String!): [SearchResult!]!\n}\n```\n\n## Reference Files\n\nDetailed documentation for specific topics:\n\n- [Types](references\u002Ftypes.md) - Type design patterns, interfaces, unions, and custom scalars\n- [Naming](references\u002Fnaming.md) - Naming conventions for types, fields, and arguments\n- [Pagination](references\u002Fpagination.md) - Connection pattern and cursor-based pagination\n- [Errors](references\u002Ferrors.md) - Error modeling and result types\n- [Security](references\u002Fsecurity.md) - Security best practices for schema design\n\n## Key Rules\n\n### Type Design\n\n- Define types based on domain concepts, not data storage\n- Use interfaces for shared fields across types\n- Use unions for mutually exclusive types\n- Keep types focused (single responsibility)\n- Avoid deep nesting - flatten when possible\n\n### Field Design\n\n- Fields should be named from client's perspective\n- Return the most specific type possible\n- Make expensive fields explicit (consider arguments)\n- Use arguments for filtering, sorting, pagination\n\n### Mutation Design\n\n- Use single input argument pattern: `mutation(input: InputType!)`\n- Return affected objects in mutation responses\n- Model mutations around business operations, not CRUD\n- Consider returning a union of success\u002Ferror types\n\n### ID Strategy\n\n- Use globally unique IDs when possible\n- Implement `Node` interface for refetchability\n- Base64-encode compound IDs if needed\n\n## Ground Rules\n\n- ALWAYS add descriptions to types and fields\n- ALWAYS use non-null (**!**) for fields that cannot be null\n- ALWAYS use **[Type!]!** pattern for lists\n- NEVER expose database internals in schema\n- NEVER break backwards compatibility without deprecation\n- PREFER dedicated input types over many arguments\n- PREFER enums over arbitrary strings for fixed values\n- USE `ID` type for identifiers, not `String` or `Int`\n- USE custom scalars for domain-specific values (DateTime, Email, URL)\n",{"name":5,"license":15,"metadata":24,"description":27,"allowed-tools":28,"compatibility":29},{"author":25,"version":26},"apollographql","1.0.1","Guide for designing GraphQL schemas following industry best practices. Use this skill when: (1) designing a new GraphQL schema or API, (2) reviewing existing schema for improvements, (3) deciding on type structures or nullability, (4) implementing pagination or error patterns, (5) ensuring security in schema design.\n","Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep","Any GraphQL implementation (Apollo Server, graphql-js, Yoga, etc.)","main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill graphql-schema",{"tool":45,"command":46},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill graphql-schema",{"tool":48,"command":49},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill graphql-schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema\u002FSKILL.md",true,[53,59,63,67,71],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Ferrors.md","REFERENCE","参考文档",6668,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Ferrors.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fnaming.md",6847,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Fnaming.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fpagination.md",7178,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Fpagination.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsecurity.md",9364,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Fsecurity.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Ftypes.md",7950,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgraphos-tools\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Ftypes.md",[76,82,89,95,102,109],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"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":88,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","workflow","Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of \"workflow\", \"durable functions\", \"resumable\", \"workflow sdk\", \"queue\", \"event\", \"push\", \"subscribe\", or step-based orchestration.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":90,"name":84,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7BYASGMK935J33E21N5WTW0","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","vercel-storage","Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","vercel-services","Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]