Agent skill · software engineering · affaan-m
coding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.
Why this skill is useful
Codifies naming conventions and code quality principles that the AI could infer but now doesn't have to guess.
What it needs
About 7k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Coding Standards & Best Practices 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. When to Activate 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 Scope Boundaries 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 Quality Principles 1. Readability First Code is read more than written Clear variable and function names Self-documenting code preferred over comments Consistent formatting 2. KISS (Keep It Simple, Stupid) Simplest solution that works Avoid over-engineering No premature optimization Easy to understand > clever code 3. DRY (Don't Repeat Yourself) Extract common logic into functions Create reusable components Share utilities across modules Avoid copy-paste programming 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/coding-standards--1cbd93