coding-standards

TypeScript、JavaScript、React、Node.js 开发的通用编码标准、最佳实践和模式。

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/skills/coding-standards/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, executable code examples, but it is an over-long monolith that re-teaches standard best practices Claude already knows. Splitting it into focused reference files and trimming redundant basics would materially improve it.

Suggestions

Trim or remove sections covering knowledge Claude already has (KISS/DRY/YAGNI, basic naming, Promise.all, useMemo) to respect the token budget, keeping only project-specific conventions.

Split the large single file into one-level-deep references (e.g. react.md, api-design.md, testing.md) with a concise overview in SKILL.md linking to them, improving progressive disclosure.

If any destructive or batch workflow (e.g. migrations, bulk refactors) is implied, add explicit validate-then-proceed checkpoints to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is well-formatted with ✅/❌ code examples rather than prose fluff, but at ~527 lines it largely restates basic concepts Claude already knows (KISS, DRY, YAGNI, naming, immutability, Promise.all, useMemo), so it could be tightened considerably.	2 / 3
Actionability	It provides extensive concrete, executable TypeScript/React code with specific patterns (spread immutability, try/catch fetch, Promise.all, typed components, zod schemas, REST routes), making it copy-paste ready.	3 / 3
Workflow Clarity	This is a topical reference document with no multi-step workflow or validation checkpoints; content is organized by section but lacks the sequenced steps and feedback loops the top anchor requires.	2 / 3
Progressive Disclosure	Sections are clearly organized, but the entire 527-line document is monolithic and inline with no external references or file splitting, which for a doc this size matches 'content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

50%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a specific technology stack and content type but stops short of listing concrete actions, natural trigger terms, or an explicit 'Use when' clause. It is adequately specific but generic enough to risk overlap with similar skills.

Suggestions

Add concrete actions instead of abstract nouns, e.g. 'Reviews, refactors, and generates TypeScript/React/Node.js code against team conventions'.

Append an explicit 'Use when...' clause with natural trigger terms users would say (e.g. 'Use when writing or reviewing TypeScript, JavaScript, React, or Node.js code, or when applying coding standards and best practices').

Narrow the scope or add a distinguishing qualifier to reduce overlap with generic coding-skills.

Dimension	Reasoning	Score
Specificity	The description names a concrete tech stack ("TypeScript、JavaScript、React、Node.js") and content categories ("编码标准、最佳实践和模式"), but the 'actions' are abstract nouns rather than concrete operations, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It clearly states what the skill provides (coding standards/best practices/patterns) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes relevant keywords users would say (TypeScript, JavaScript, React, Node.js), but lacks natural trigger phrasing and common variations, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The named tech stack gives it a niche, but the '通用编码标准' (general coding standards) framing is broad and could overlap with other general coding skills, so it is not a clearly distinct 3.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (528 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/coding-standards/SKILL.md
Commit: dfbf946

Reviewed: 2 months ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.