coding-standards

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

Quality

51%

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 ./.kiro/skills/coding-standards/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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

The content is a dense, code-example-driven reference that is highly actionable for TS/JS/React/Node conventions, but it explains principles Claude already knows, lacks any sequenced workflow or validation guidance, and inlines ~530 lines that would benefit from being split into referenced files.

Suggestions

Drop or trim the KISS/DRY/YAGNI axiom explanations and the "Remember" closer — Claude already knows these; keep only the project-specific conventions.

Split large sections (React Best Practices, API Design, Testing Standards) into referenced files (e.g. REACT.md, API.md, TESTING.md) and keep SKILL.md as a concise overview with one-level-deep links.

Complete the illustrative code examples by replacing `// Implementation` placeholders with runnable bodies, or mark them explicitly as signature-only.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean PASS/FAIL code examples with little padding, but it devotes sections to explaining KISS/DRY/YAGNI and axioms like "Code is read more than written" that Claude already knows, placing it at the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	It provides numerous concrete, executable TypeScript/JS/React patterns as copy-oriented PASS/FAIL pairs covering common cases, but several examples end in `// Implementation` placeholders rather than being fully runnable, keeping it just below a 5.	4 / 5
Workflow Clarity	A "When to Activate" list gives activation triggers, but this is a reference standards doc with no sequenced multi-step workflow and no validation checkpoints; the sequence/checkpoint anchor at 3 is the best fit for a non-process skill with no feedback loops.	3 / 5
Progressive Disclosure	The file is well-organized with clear ## / ### headers, but at ~530 lines everything (React, API design, testing, code smells) is inlined in SKILL.md with no bundle files and no one-level-deep references, matching the "some structure but content that should be separate is inline" anchor.	3 / 5
	Total	13 / 20 Passed

Description

45%Weight 40%Scale 1-5

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 names a clear technology stack but describes only generic capabilities ("standards, best practices, and patterns") with no concrete actions and no explicit "when to use" trigger clause. It is distinguishable but risks overlap with broad code-quality skills.

Suggestions

Add concrete actions, e.g. "Enforces naming, formatting, error-handling, and type-safety conventions..." instead of the generic "standards, best practices, and patterns".

Append an explicit trigger clause: "Use when starting a project, reviewing code, refactoring, or setting up linting/type-checking rules for TS/JS/React/Node."

Include natural user phrases ("code review", "refactoring", "linting", "naming conventions") as trigger terms.

Dimension	Reasoning	Score
Specificity	The description names the domain ("TypeScript, JavaScript, React, and Node.js") but the only actions are the generic "standards, best practices, and patterns" — no concrete capabilities like enforcing naming or setting up linting, matching the score-2 anchor that names the domain with minimal/generic actions.	2 / 5
Completeness	It has a clear "what" (universal coding standards for the named stack) but no "Use when..." or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces the stack names (TypeScript, JavaScript, React, Node.js) but omits the natural phrases a user would actually say ("code review", "refactoring", "linting", "naming conventions"), so keyword coverage has relevant terms but misses common variations.	3 / 5
Distinctiveness Conflict Risk	The specific stack naming helps distinguish it, but "universal coding standards, best practices, and patterns" is broad enough to overlap with general code-quality or linting skills, fitting the "somewhat specific but could still overlap" anchor.	3 / 5
	Total	11 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (534 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/everything-claude-code
Path: .kiro/skills/coding-standards/SKILL.md
Commit: d8409a4

Reviewed: 5 days 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.