[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERNPF4PB4XSNZ82SGPY05K":3,"skill-same:01M7ERNPF4PB4XSNZ82SGPY05K":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7ERNPF4PB4XSNZ82SGPY05K","graphql-schema",null,"Guide for designing and changing GraphQL schemas following industry best practices. Use this skill whenever you create or edit GraphQL SDL, such as a `schema.graphql` file or `typeDefs`, including when: (1) designing a new GraphQL schema or API, (2) adding or changing types, fields, arguments, mutations, or descriptions in an existing schema, (3) reviewing existing schema for improvements, (4) deciding on type structures or nullability, (5) implementing pagination or error patterns, (6) ensuring security in schema design.","ga-arnez\u002Fhabii-base","ga-arnez","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171380296?v=4","01M7ERN055RRZGC541T4VJPWAP","01M7ERN05V02WTNTBGR3QYNYFK",0,"MIT","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: graphql-schema\ndescription: >\n  Guide for designing and changing GraphQL schemas following industry best practices. Use this skill\n  whenever you create or edit GraphQL SDL, such as a `schema.graphql` file or `typeDefs`, including when:\n  (1) designing a new GraphQL schema or API,\n  (2) adding or changing types, fields, arguments, mutations, or descriptions in an existing schema,\n  (3) reviewing existing schema for improvements,\n  (4) deciding on type structures or nullability,\n  (5) implementing pagination or error patterns,\n  (6) 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.2\"\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- Give every new argument or input field a default value, or make it nullable. Existing clients don't send it, so a required field without a default makes their requests fail validation.\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- ALWAYS paginate lists that can grow without limit, such as `Query.users` or `Post.comments`: return a connection and give `first` a default page size\n- NEVER expose database internals in schema\n- NEVER break backwards compatibility without deprecation\n- NEVER add a required argument or input field without a default value\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- Give every new argument or input field a default value, or make it nullable. Existing clients don't send it, so a required field without a default makes their requests fail validation.\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- ALWAYS paginate lists that can grow without limit, such as `Query.users` or `Post.comments`: return a connection and give `first` a default page size\n- NEVER expose database internals in schema\n- NEVER break backwards compatibility without deprecation\n- NEVER add a required argument or input field without a default value\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":14,"metadata":23,"description":26,"allowed-tools":27,"compatibility":28},{"author":24,"version":25},"apollographql","1.0.2","Guide for designing and changing GraphQL schemas following industry best practices. Use this skill whenever you create or edit GraphQL SDL, such as a `schema.graphql` file or `typeDefs`, including when: (1) designing a new GraphQL schema or API, (2) adding or changing types, fields, arguments, mutations, or descriptions in an existing schema, (3) reviewing existing schema for improvements, (4) deciding on type structures or nullability, (5) implementing pagination or error patterns, (6) 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","673b9947a5ae59be5e46a590b2dddb529b8461ba","plugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base","https:\u002F\u002Fgithub.com\u002Fga-arnez","2026-11-13 05:04:20",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ga-arnez\u002Fhabii-base --skill graphql-schema",{"tool":41,"command":42},"bunx","bunx skills add ga-arnez\u002Fhabii-base --skill graphql-schema",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ga-arnez\u002Fhabii-base --skill graphql-schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema\u002FSKILL.md",true,[49,55,59,63,67],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ferrors.md","REFERENCE","参考文档",6668,"https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Ferrors.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fnaming.md",6839,"https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Fnaming.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fpagination.md",7178,"https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Fpagination.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fsecurity.md",9364,"https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Fsecurity.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Ftypes.md",7995,"https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-core\u002Fskills\u002Fgraphql-schema\u002Freferences\u002Ftypes.md",[72,79,86,93,100,109],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7ERS7Y51EDYAWW4NVTXH722","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\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7ERS2YQMAPNHTXQ011SZEPF","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\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7ERREG7BR55CZYE944RKBK3","prisma-client-api","Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on \"prisma query\", \"findMany\", \"create\", \"update\", \"delete\", \"$transaction\".","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fprisma-client-api\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M7ERRAMGZJ0W08Y98D6ZC6WV","prisma-cli","Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Fprisma-cli\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M7ERR7K7RJR1CW1SB7RW769B","frontend-design","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-ts\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M7ERQMMESXB742C1RD1139DP","security-check","Use when auditing a Rails app for XSS, CSRF, SQLi, IDOR, secrets, or auth bypass. Never print secrets. Trigger words: security, audit, XSS, CSRF, SQL injection, vulnerability.","https:\u002F\u002Fgithub.com\u002Fga-arnez\u002Fhabii-base\u002Fblob\u002Fmain\u002Fplugins\u002Fhabii-rails\u002Fskills\u002Fsecurity-check\u002FSKILL.md",[],[]]