graphql-development
GraphQL development guidelines with type-safe clients, schema design, and integration with React and Next.js.
Works with
--- name: graphql-development description: GraphQL development guidelines with type-safe clients, schema design, and integration with React and Next.js. license: Apache-2.0 --- # GraphQL Development You are an expert in GraphQL development with type-safe clients and modern web frameworks. ## Core Principles - Design schemas with clear, consistent naming - Use type-safe clients for all GraphQL operations - Optimize queries to fetch only necessary data - Implement proper error handling ## Schema Design ### Types and Fields - Use descriptive type names in PascalCase - Field names in camelCase - Use nullable types appropriately - Implement input types for mutations - Use enums for fixed value sets ### Relationships - Define clear connection patterns - Implement pagination with cursor-based or offset patterns - Use interfaces for shared fields - Implement union types for polymorphic returns ## Query Optimization - Fetch only required fields - Use fragments for reusable field selections - Implement DataLoader for batching - Avoid N+1 queries with proper resolvers ## Type-Safe Clients ### Genql - Generate TypeScript types from schema - Use type-safe query builders - Leverage IDE autocompletion ### Apollo Client - Configure cache policies properly - Use reactive variables for local state - Implement optimistic updates - Handle loading and error states ### urql - Use document caching effectively - Implement exchanges for customization - Handle subscriptions properly ## Integration Patterns ### React - Use hooks for queries and mutations - Handle loading and error states in components - Implement proper cache updates ### Next.js - Use Server Components for initial data - Implement proper hydration patterns - Handle auth in GraphQL context ## Error Handling - Define clear error types in schema - Return structured errors from resolvers - Handle errors gracefully in clients - Log errors appropriately ## Security - Implement query depth limiting - Use query complexity analysis - Validate and sanitize inputs - Implement proper authentication - Use field-level authorization ## Testing - Test resolvers independently - Mock GraphQL responses in client tests - Use schema validation in CI/CD - Test error scenarios
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

