coding-standards

Topics in the source

• Coding Standards & Best Practices
• When to Activate
• Scope Boundaries
• Code Quality Principles
• 1. Readability First
• 2. KISS (Keep It Simple, Stupid)
• 3. DRY (Don't Repeat Yourself)
• 4. YAGNI (You Aren't Gonna Need It)

Baseline coding conventions applicable across projects. This skill is the shared floor, not the detailed framework playbook. Use frontend-patterns for React, state, forms, rendering, and UI architecture. Use backend-patterns or api-design for repository/service layers, endpoint design, validation, and server-specific concerns. Use rules/common/coding-style.md when you need the shortest reusable rule layer instead of a full skill walkthrough. Starting a new project or module Reviewing code for quality and maintainability Refactoring existing code to follow conventions Enforcing naming, formatting, or structural consistency Setting up linting, formatting, or type-checking rules Onboarding new contributors to coding conventions Activate this skill for: descriptive naming immutability defaults readability, KISS, DRY, and YAGNI enforcement error-handling expectations and code-smell review Do not use this skill as the primary source for: React composition, hooks, or rendering patterns backend architecture, API design, or database layering domain-specific framework guidance when a narrower ECC skill already exists Code is read more than written Clear variable and function names Self-docum

This is an excerpt. Refer to the complete source and its current requirements.