coding-standards

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

Quality

19%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-TW/skills/coding-standards/SKILL.md

Quality

Content

14%

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

This skill is an extensive catalog of generic TypeScript/React/Node.js coding standards that Claude already knows well. It violates the core principle of token efficiency by spending hundreds of lines teaching fundamental concepts like DRY, KISS, YAGNI, naming conventions, and early returns. The content would only be valuable if it contained project-specific conventions that deviate from standard practices, but instead it restates universal best practices.

Suggestions

Remove all generic programming principles (KISS, DRY, YAGNI, early returns, magic numbers, etc.) that Claude already knows—focus only on project-specific conventions that differ from standard practices.

Add a workflow section with sequenced steps for common development tasks (e.g., creating a new feature, adding an API endpoint) with validation checkpoints.

Split content into a concise SKILL.md overview with references to separate files for React patterns, API standards, and testing conventions.

Replace the broad best-practices catalog with project-specific configuration details (linter rules, specific library versions, custom patterns unique to this codebase).

Dimension	Reasoning	Score
Conciseness	This skill extensively explains fundamental programming concepts (KISS, DRY, YAGNI, naming conventions, early returns, magic numbers) that Claude already knows thoroughly. The vast majority of content is basic software engineering knowledge that adds no new information for Claude. At ~350+ lines, it's extremely verbose for what amounts to standard coding practices.	1 / 3
Actionability	The code examples are concrete and executable, which is good. However, the skill is more of a reference document of general best practices than actionable task-specific guidance. It tells Claude to follow patterns Claude already follows by default, rather than providing project-specific configurations, commands, or workflows.	2 / 3
Workflow Clarity	There are no multi-step workflows, no sequenced processes, and no validation checkpoints. The content is a flat list of coding conventions and patterns with no procedural guidance on when or how to apply them in a development workflow.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no layered structure. All content—from basic naming conventions to API design to testing—is dumped into a single file with no navigation aids or separation of concerns.	1 / 3
	Total	5 / 12 Passed

Description

25%

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 is too broad and vague to effectively differentiate this skill from other coding-related skills. It names technologies but fails to specify concrete actions or provide explicit trigger guidance. The combination of four major technologies with generic terms like 'best practices and patterns' creates high conflict risk with other skills.

Suggestions

Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks about coding conventions, style guidelines, naming patterns, or best practices for TypeScript, JavaScript, React, or Node.js projects.'

List specific concrete actions instead of 'best practices and patterns', e.g., 'Enforces naming conventions, applies design patterns, recommends project structure, defines error handling strategies, and guides type safety practices.'

Narrow the scope or add distinguishing details to reduce conflict risk with other coding skills, e.g., specify whether this covers linting rules, architectural patterns, or code review standards.

Dimension	Reasoning	Score
Specificity	Names the domain (coding standards) and technologies (TypeScript, JavaScript, React, Node.js), but 'best practices and patterns' is vague — it doesn't list specific concrete actions like 'enforce naming conventions, apply design patterns, lint code'.	2 / 3
Completeness	Describes 'what' at a high level (coding standards and best practices) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant technology keywords (TypeScript, JavaScript, React, Node.js) that users might mention, but 'coding standards' and 'best practices' are somewhat generic. Missing natural trigger terms like 'code review', 'style guide', 'linting', 'conventions', 'code quality'.	2 / 3
Distinctiveness Conflict Risk	Very broad scope covering four major technologies with generic terms like 'best practices' and 'patterns' — this would easily conflict with any TypeScript, JavaScript, React, or Node.js skill, as well as general coding or code review skills.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: affaan-m/everything-claude-code
Commit: ec92b52

Reviewed: 3 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.