coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
73
48%
Does it follow best practices?
Impact
89%
1.21xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-TW/skills/coding-standards/SKILL.mdQuality
Discovery
32%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 its technology domain but relies heavily on vague terms like 'best practices' and 'patterns' without concrete actions. It critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others. The technology keywords provide some distinctiveness but are insufficient for reliable skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when reviewing code style, enforcing conventions, or asking about TypeScript/React patterns'.
Replace vague terms with concrete actions such as 'Enforces naming conventions, recommends file structure, applies consistent formatting, suggests type patterns'.
Include natural user phrases like 'code review', 'style guide', 'how should I organize', 'naming conventions' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (coding standards) and technologies (TypeScript, JavaScript, React, Node.js), but uses vague terms like 'best practices' and 'patterns' without listing concrete actions like 'enforce naming conventions' or 'apply linting rules'. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks a 'Use when...' clause or any explicit guidance on when Claude should select this skill. The rubric caps completeness at 2 for missing triggers, and this is weaker than that threshold. | 1 / 3 |
Trigger Term Quality | Includes relevant technology keywords (TypeScript, JavaScript, React, Node.js) that users might mention, but lacks natural trigger phrases users would say like 'code review', 'style guide', 'conventions', or 'how should I structure'. | 2 / 3 |
Distinctiveness Conflict Risk | The technology stack (TypeScript, JavaScript, React, Node.js) provides some specificity, but 'coding standards' and 'best practices' are generic enough to potentially conflict with other coding-related skills or general development assistance. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive coding standards reference with excellent actionable code examples and clear good/bad pattern comparisons. However, it's verbose with explanations of concepts Claude already knows (DRY, KISS, YAGNI definitions), and the monolithic structure could benefit from splitting into focused sub-documents. The skill functions more as a reference document than a workflow guide.
Suggestions
Remove or drastically shorten the '程式碼品質原則' section - Claude already knows KISS, DRY, YAGNI principles; just reference them by name if needed
Split into multiple files: TYPESCRIPT.md, REACT.md, API.md, TESTING.md with SKILL.md as a brief overview pointing to each
Remove explanatory text like '程式碼被閱讀的次數遠多於被撰寫的次數' - keep only the actionable patterns and code examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful patterns but includes explanations Claude already knows (KISS, DRY, YAGNI principles, basic concepts like 'code is read more than written'). The code examples are good but the surrounding explanations add unnecessary tokens. | 2 / 3 |
Actionability | Excellent executable code examples throughout - TypeScript/JavaScript patterns, React components, API designs, and test structures are all copy-paste ready with clear good/bad comparisons using ✅/❌ markers. | 3 / 3 |
Workflow Clarity | This is primarily a reference/standards document rather than a workflow skill. While patterns are clearly shown, there's no multi-step process guidance or validation checkpoints. The file organization section lists structure but doesn't guide through creating it. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear headers and sections, but it's a monolithic document (~400 lines) with no references to external files. API reference, testing standards, and React patterns could be split into separate files for better navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
- haniakrim21/everything-claude-code
- Commit
ae2cadd
- Reviewed
Table of Contents
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.