Coding Standards

researched 2026-05-25· 0 sources · 10 concepts · skill coding-standards

Baseline coding conventions applicable across projects.

Coding Standards & Best Practices

Baseline coding conventions applicable across projects. [source]
This skill is the shared floor, not the detailed framework playbook. [source]
Use frontend-patterns for React, state, forms, rendering, and UI architecture. [source]
Use backend-patterns or api-design for repository/service layers, endpoint design, validation, and server-specific concerns. [source]
Use rules/common/coding-style.md when you need the shortest reusable rule layer instead of a full skill walkthrough. [source]

When to Activate

Starting a new project or module [source]
Reviewing code for quality and maintainability [source]
Refactoring existing code to follow conventions [source]
Enforcing naming, formatting, or structural consistency [source]
Setting up linting, formatting, or type-checking rules [source]
Onboarding new contributors to coding conventions [source]

Scope Boundaries

Activate this skill for: [source]
descriptive naming [source]
immutability defaults [source]
readability, KISS, DRY, and YAGNI enforcement [source]
error-handling expectations and code-smell review [source]
Do not use this skill as the primary source for: [source]
React composition, hooks, or rendering patterns [source]
backend architecture, API design, or database layering [source]
domain-specific framework guidance when a narrower ECC skill already exists [source]

1. Readability First

Code is read more than written [source]
Clear variable and function names [source]
Self-documenting code preferred over comments [source]
Consistent formatting [source]

2. KISS (Keep It Simple, Stupid)

Simplest solution that works [source]
Avoid over-engineering [source]
No premature optimization [source]
Easy to understand > clever code [source]

3. DRY (Don't Repeat Yourself)

Extract common logic into functions [source]
Create reusable components [source]
Share utilities across modules [source]
Avoid copy-paste programming [source]

4. YAGNI (You Aren't Gonna Need It)

Don't build features before they're needed [source]
Avoid speculative generality [source]
Add complexity only when required [source]
Start simple, refactor when needed [source]

Code Smell Detection

Watch for these anti-patterns: [source]

3. Magic Numbers

Remember: Code quality is not negotiable. Clear, maintainable code enables rapid development and confident refactoring. [source]

Children

Naming and Readability Conventions (frontier)
TypeScript and JavaScript Standards (frontier)
React Best Practices (frontier)
File Organization (frontier)
Testing Standards (frontier)

Frontier under this node: File Organization, Naming and Readability Conventions, React Best Practices, Testing Standards, TypeScript and JavaScript Standards

← the whole tree · 3D view· how to read this page