coding-standards

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

Quality

24%

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

Discovery

14%

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

This description is too vague and broad to be effective for skill selection. It lacks concrete actions, has no 'Use when...' clause, and covers such a wide domain (four major technologies plus 'universal' standards) that it would likely conflict with many other skills. The description reads more like a category label than a functional skill description.

Suggestions

Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks about code style, naming conventions, project structure, or best practices for TypeScript/React/Node.js projects.'

Replace vague terms like 'best practices and patterns' with specific concrete actions, e.g., 'Enforces naming conventions, recommends project folder structure, applies error handling patterns, and guides component composition.'

Narrow the scope or add distinguishing details to reduce conflict risk, e.g., specify whether this is about code review, scaffolding, refactoring, or style enforcement.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'coding standards, best practices, and patterns' without listing any concrete actions. It doesn't specify what it actually does (e.g., 'enforces naming conventions', 'applies linting rules', 'structures project files').	1 / 3
Completeness	The 'what' is vague ('coding standards, best practices, and patterns') and there is no 'when' clause at all. There's no explicit guidance on when Claude should select this skill.	1 / 3
Trigger Term Quality	It 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', 'conventions', 'linting', or 'code quality'.	2 / 3
Distinctiveness Conflict Risk	This description is extremely broad and would conflict with virtually any TypeScript, JavaScript, React, or Node.js skill. 'Best practices and patterns' could overlap with any coding-related skill in those ecosystems.	1 / 3
	Total	5 / 12 Passed

Implementation

35%

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

This skill is essentially a comprehensive but generic coding standards document that teaches Claude things it already knows — TypeScript naming conventions, React best practices, DRY/KISS/YAGNI principles, and common code smells. While the examples are well-structured with clear PASS/FAIL patterns, the content adds minimal value beyond Claude's existing knowledge. The document would benefit greatly from being reduced to only project-specific conventions and standards that deviate from common practices.

Suggestions

Remove all universally-known programming principles (KISS, DRY, YAGNI, basic naming conventions, code smells) and focus only on project-specific standards or conventions that differ from common defaults.

Split the remaining content into focused reference files (e.g., REACT_PATTERNS.md, API_STANDARDS.md) with SKILL.md serving as a brief overview with links.

Add project-specific context: which linter/formatter is used, specific library versions, project-specific patterns or architectural decisions that Claude wouldn't know by default.

Reduce the file to under 50 lines focusing on the few conventions that are genuinely non-obvious or project-specific (e.g., the specific API response format with the ApiResponse<T> interface, or the specific project directory structure).

Dimension	Reasoning	Score
Conciseness	This skill extensively explains fundamental programming concepts Claude already knows well — KISS, DRY, YAGNI, naming conventions, immutability, error handling, React patterns, testing AAA pattern, code smells like magic numbers and deep nesting. Nearly all content is standard knowledge that adds no new project-specific or tool-specific value. The file is ~350 lines of widely-known best practices.	1 / 3
Actionability	The code examples are concrete and executable TypeScript/React snippets with clear PASS/FAIL patterns, which is good. However, the guidance is generic rather than project-specific — it doesn't tell Claude what to do in a specific context, just restates universal coding standards. The examples are illustrative rather than task-oriented.	2 / 3
Workflow Clarity	There is no multi-step workflow or process described. The content is a reference document of coding standards organized by topic. While the sections are logically ordered, there are no sequential steps, validation checkpoints, or feedback loops. For a standards reference skill this is acceptable but not exemplary.	2 / 3
Progressive Disclosure	The content is a monolithic wall of standards with no references to external files for detailed topics. Given the length (~350 lines), topics like React patterns, API design, testing, and performance could be split into separate reference files. The section headers provide some organization but the document is too long for a single SKILL.md.	2 / 3
	Total	7 / 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: 928076c

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.