Conciseness

The body is lean throughout: every section is a short bullet list or a minimal code snippet with PASS/FAIL labels ('// PASS: recordとfinalフィールドを優先', '// FAIL: 複雑なネストされたストリームを避ける'), with zero padding and no explanation of concepts Claude already knows — every token earns its place.

Actionability

Most guidance is concrete and imitable — real Java snippets for records, Optional chaining ('.map(MarketResponse::from).orElseThrow(...)'), bounded generics, and a project layout tree — but a few sections (フォーマットとスタイル, テストの期待) are bullet-only without a code example, and the exception-wrapping rule is stated without a demonstration, leaving minor gaps.

Workflow Clarity

As a standards reference rather than a multi-step process, the sections are clearly sequenced by concern with unambiguous PASS/FAIL examples and a summarizing takeaway ('覚えておく'), but there is no guidance on how to apply the standards to existing code or check compliance, so it sits just below fully explicit.

Progressive Disclosure

The single file is well-organized into clearly headed sections with no nested or buried references (there are no bundle files at all), which is good structure; however, at roughly 130 lines it exceeds the under-50-line case where well-organized sections alone warrant a 5, and no example-heavy detail is split out to reference files.

Specificity

The description names the domain clearly ('Spring Bootサービス向けのJavaコーディング標準') and enumerates seven topic areas ('命名、不変性、Optional使用、ストリーム、例外、ジェネリクス、プロジェクトレイアウト'), but these are topic labels rather than concrete actions, matching the 'names domain and concrete items but not comprehensive actions' level rather than the action-listing anchors above.

Completeness

It has a clear 'what' (Java coding standards covering named topic areas) but no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

Trigger Term Quality

Good keyword coverage — 'Spring Boot', 'Java', '命名', '不変性', 'Optional', 'ストリーム', '例外', 'ジェネリクス' are all terms a user would naturally mention — but common variations such as 'conventions' ('規約'/'コンベンション'), 'style guide', or 'code review' are missing, so it falls just short of comprehensive synonym coverage.

Distinctiveness Conflict Risk

The niche is specific — Java coding standards specifically for Spring Boot services — and unlikely to fire for unrelated skills, though it could overlap with a general Java or code-review skill since no 'when' phrasing narrows the trigger context.