coding-standardscommit d29cf65SKILL.md · Code Standards
Coding Standards
Gives baseline cross-project coding conventions for naming, readability, immutability, error handling and code-smell review.
npx skills add affaan-m/ECC --skill coding-standardsCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Cursor, Copilot, OpenCode
- GitHub
- 294.3k
- Source
- Community · Affaan Mustafa
- Status
- Scan passed
- License
- MIT
- Category
- Code Standards
Core rule
Always create new objects and arrays with the spread operator; never mutate directly.
Execution Phases
Phase 01Check scope
This skill is the shared floor; for React, backend architecture or API design, prefer the narrower dedicated skill.
Phase 02Core principles
Put readability first and follow KISS, DRY and YAGNI, avoiding over-engineering and premature optimisation.
Phase 03TS/JS standards
Use descriptive variable names and verb-noun function names, stay immutable, handle errors, parallelise with Promise.all, and avoid any.
Phase 04Structure and tests
Follow REST and a consistent response shape, validate input with zod, name files by convention, comment the why, and write AAA tests with descriptive names.
Phase 05Detect code smells
Look for functions over 50 lines, nesting 5+ levels deep and magic numbers; fix with smaller functions, early returns and named constants.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Required | Writes or refactors project code to follow these conventions. |
| Command execution | Not required | A conventions reference; it does not call for running commands. |
| Network outbound | Not required | No network access needed. |
SKILL.md frontmatter (YAML)
---
name: coding-standards
description: 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.
metadata:
origin: ECC
---