graphql-naming-conventions

graphql-naming-conventions is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (445 once invoked), scanned A, original, MIT.

A naming rule for GraphQL queries, mutations, subscriptions, fragments, types, fields, enums, and variables. It defines consistent patterns such as getUser, createUser, and UserFields.

In plain words
What is it for?
Use it when naming GraphQL operations and schema elements, including the casing of types, fields, enum values, and variables.
Why use it?
Consistent names make GraphQL code easier to find, understand, review, and reuse across a project.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when naming GraphQL operations and schema elements, including the casing of types, fields, enum values, and variables.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/graphql-naming-conventions
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for graphql-naming-conventions

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/graphql-naming-conventions/github.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/graphql-naming-conventions)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/graphql-naming-conventions"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/graphql-naming-conventions/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for graphql-naming-conventions

Your own site · 80×15
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/graphql-naming-conventions"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/graphql-naming-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 445 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00445
Opus 5 $0.00000 $0.00222
Sonnet 5 $0.00000 $0.00089
Haiku 4.5 $0.00000 $0.00044

Measured 6d ago against content hash 05aff6af9a4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

graphql-naming-conventions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

docs/rules/frontend/react/apollo-graphql/graphql-naming-conventions.mdc · 31 lines

What it actually says

  • 遵循查询、变更和片段的命名约定
    • 查询(Queries)
      • 使用 getfetch 前缀,后跟实体名称和可选的复数形式。
      • 示例:getUsersgetUserByIdfetchProductDetails
    • 变更(Mutations)
      • 使用动词前缀表示操作类型,后跟实体名称。
      • 示例:createUserupdateProductdeleteComment
    • 订阅(Subscriptions)
      • 使用 on 前缀,后跟事件名称。
      • 示例:onNewMessageonUserUpdated
    • 片段(Fragments)
      • 使用实体名称,后跟 FieldsDetails 后缀。
      • 示例:UserFieldsProductDetails
    • 类型(Types)和字段(Fields)
      • 类型名称使用 PascalCase(大驼峰命名法)。
      • 字段名称使用 camelCase(小驼峰命名法)。
      • 示例:User 类型中的 firstName 字段。
    • 枚举(Enums)
      • 枚举类型名称使用 PascalCase,枚举值使用 ALL_CAPS(全大写)。
      • 示例:OrderStatus 枚举中的 PENDINGCOMPLETED
    • 变量(Variables)
      • 变量名称使用 camelCase。
      • 示例:$userId$input
    • 通用原则
      • 保持命名清晰、简洁、一致,能够直观地表达其用途和所操作的数据。
      • 避免缩写,除非是广为人知的缩写(如 ID)。
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 31 lines · 0 tokens per session scan A 05aff6af9a4f

Subscribe to this mod's changes

graphql-naming-conventions is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (233 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 445 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.