graphql-docs
>
Works with
--- name: graphql-docs description: > license: MIT --- # GraphQL GraphQL is a query language for APIs and a runtime for fulfilling those queries with existing data. It provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need, makes it easier to evolve APIs over time, and enables powerful developer tools. **Specification**: [spec.graphql.org/draft](https://spec.graphql.org/draft/) --- ## Quick Reference | Topic | File | |------|------| | Introduction & Core Concepts (type system, queries, versionless evolution) | `introduction.md` | | Schemas & Types (SDL, object types, scalars, enums, interfaces, unions, input types, directives) | `schema.md` | | Queries (fields, arguments, aliases, variables, fragments, inline fragments, directives) | `queries.md` | | Mutations (create, update, delete, input objects, serial execution) | `mutations.md` | | Subscriptions (real-time, pub/sub, WebSocket transport, scaling) | `subscriptions.md` | | Validation (validation rules, error detection, common invalid queries) | `validation.md` | | Execution (resolvers, context, async, scalar coercion, list resolvers) | `execution.md` | | Response Format (data, errors, extensions, request vs field errors, status codes) | `response.md` | | Introspection (__schema, __type, querying the schema itself) | `introspection.md` | | Best Practices (thinking in graphs, HTTP serving, auth, pagination, errors, caching, security, federation, schema governance) | `best-practices.md` | --- ## Core Concepts - **Schema**: The type system that describes all available data and operations - **Query**: Read operation that traverses fields to fetch exactly what's needed - **Mutation**: Write operation that modifies data (executed serially) - **Subscription**: Long-lived operation for real-time data updates - **Resolver**: Function that provides data for each field - **Type System**: Scalars, objects, enums, interfaces, unions, input types, lists, non-null - **SDL**: Schema Definition Language — language-agnostic way to describe schemas - **Introspection**: Ability to query the schema itself via `__schema` and `__type` --- ## Official Documentation - [GraphQL Learn](https://graphql.org/learn/) - [GraphQL Specification](https://spec.graphql.org/draft/) - [GraphQL Code](https://graphql.org/code/) - [GraphQL FAQ](https://graphql.org/faq/)
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 时使用。

