java-enum-static-constants-naming

A Java naming rule for enum values and static constants. It requires PascalCase, such as `Pending` or `MaxRetries`, while ordinary variables and methods keep camelCase.

In plain words
What is it for?
Reviewing or writing Java code where enum values and `static final` constants must follow this naming convention.
Why use it?
It gives constant-like names one consistent style and separates them visually from other Java identifiers.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/xc404/kiwi/java-enum-static-constants-naming
Clone the repo
git clone --depth 1 https://github.com/xc404/kiwi

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 280 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00280
Opus 5 $0.00000 $0.00140
Sonnet 5 $0.00000 $0.00056
Haiku 4.5 $0.00000 $0.00028

Measured yesterday against content hash b633ef4f0956, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

java-enum-static-constants-naming 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 yesterday.

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.

.cursor/rules/java-enum-static-constants-naming.mdc · 39 lines

What it actually says

Enum 与 static 常量命名

在本仓库的 Java 代码中,枚举常量static 常量(尤其 static final)采用 PascalCase:每个单词首字母大写,无下划线分隔。

约定

  • 枚举常量PendingCompletedInProgress,而非 PENDINGpending
  • 类内 static final 常量:与枚举一致,使用 PascalCase,例如 DefaultTimeoutMaxRetries

示例

// 推荐
public enum JobStatus {
    Pending,
    Running,
    Completed,
    Failed
}

private static final Duration DefaultPollInterval = Duration.ofSeconds(30);

// 不推荐(全大写下划线、或小驼峰用于“常量”语义)
public enum JobStatus {
    PENDING,
    running
}

private static final Duration defaultPollInterval = ...;

与局部变量、方法、实例字段的 camelCase 区分:常量级命名统一为 PascalCase。

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. yesterday First seen · 39 lines · 0 tokens per session scan A b633ef4f0956

Subscribe to this mod's changes

java-enum-static-constants-naming is a cursor rule published in the GitHub repository xc404/kiwi (7 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 280 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-08-31.