Coding Standards
Skill Verified ActiveBaseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
To establish and enforce consistent, high-quality coding standards across diverse projects and languages, improving maintainability and developer efficiency.
Features
- Cross-project coding convention baseline
- Detailed language-specific standards (TS, JS, Python, Go, Java, PHP, Swift, ArkTS)
- Principles of readability, KISS, DRY, YAGNI
- Guidance on immutability, error handling, and async/await
- Best practices for React components and custom hooks
- API design standards including REST conventions and response formats
- Input validation examples using Zod
- File organization and naming conventions
- Comment and documentation standards (JSDoc)
- Performance best practices (memoization, lazy loading)
- Testing standards (AAA pattern, test naming)
- Code smell detection (long functions, deep nesting, magic numbers)
Use Cases
- Starting new projects or modules with established conventions
- Reviewing code for quality, maintainability, and adherence to standards
- Refactoring existing codebases to improve consistency
- Onboarding new developers to team-specific coding practices
- Setting up project-wide linting, formatting, and type-checking rules
Non-Goals
- Providing framework-specific patterns for React, backend architecture, or database layering
- Replacing detailed framework guides (use specific frontend/backend skills)
- Enforcing domain-specific toolchain guidance when narrower skills exist
Installation
npx skills add affaan-m/everything-claude-codeRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
VerifiedTrust Signals
Similar Extensions
Cleanup Cycles
100Detect and untangle circular dependencies. Runs madge/skott (TS), pycycle (Py), or compiler-only checks (Go/Rust). Auto-fixes leaf-extractable cycles; reports core cycles for human review. Use when the user asks to find circular imports, fix dependency cycles, or untangle module graph. Example queries — "find circular imports", "fix dependency cycles", "untangle our module graph", "why is madge complaining".
Deepinit
100Deep codebase initialization with hierarchical AGENTS.md documentation
Senior Backend Engineer
100Designs and implements backend systems including REST APIs, microservices, database architectures, authentication flows, and security hardening. Use when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs". Covers Node.js/Express/Fastify development, PostgreSQL optimization, API security, and backend architecture patterns.
Dart Matcher Best Practices
100Best practices for using `expect` and `package:matcher`. Focuses on readable assertions, proper matcher selection, and avoiding common pitfalls.
Semgrep Rule Creator
100Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.
Moyu (摸鱼)
100과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: (1) 사용자가 명시적으로 변경을 요청하지 않은 코드나 파일을 수정하는 경우 (2) 요청되지 않은 새로운 추상화 레이어(class, interface, factory, wrapper)를 생성하는 경우 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 어노테이션을 추가하는 경우 (4) 요청되지 않은 새로운 의존성을 도입하는 경우 (5) 최소한의 편집 대신 파일 전체를 다시 작성하는 경우 (6) diff 범위가 사용자의 요청을 명백히 초과하는 경우 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만" 등의 신호를 보내는 경우 (8) 발생할 수 없는 시나리오에 대한 에러 처리, 유효성 검사, 방어적 코드를 추가하는 경우 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성하는 경우