skills.rest
Derakons
DerakonsCOMMUNITY
Explore all skills by this author →
GitHub

Clean Code Standards

Enforce clean-code standards including SOLID principles, naming conventions, comments, and feature-based file organization.

Updated Jan 10, 2026
Search Tags:#architecture#refactor#coding-standards#naming-conventions#code-review#clean-code#solid-principles
One-click install
npx skills add https://github.com/Derakons/ERP --skill clean-code-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Clean Code Standards
Source: https://github.com/Derakons/ERP/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/Derakons/ERP --skill clean-code-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality can degrade over time, creating maintainability challenges and technical debt. This Skill defines a concise set of guidelines to keep code readable, modular, and maintainable.

Core Features & Use Cases

  • SOLID principles: Single Responsibility, Open/Closed, Liskov, Interface Segregation, Dependency Inversion to improve testability and scalability.
  • Naming conventions: Consistent camelCase for variables/functions, PascalCase for components, and UPPER_SNAKE_CASE for constants.
  • Comments: Explain the why, not the what; document architectural decisions and rationale to aid future developers.
  • Project structure: Organize by feature/domain to improve navigation and collaboration.

Quick Start

Refactor a legacy module into separate feature-based components to improve readability and maintainability.

Frequently Asked Questions about Clean Code Standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce SOLID principles during code refactoring?▼

Enforce SOLID principles during code refactoring by applying structured guidelines for Single Responsibility, Open/Closed, Liskov, Interface Segregation, and Dependency Inversion to improve testability and scalability.

What are the best naming conventions for clean code in frontend and backend projects?▼

The best naming conventions for clean code use consistent camelCase for variables and functions, PascalCase for components, and UPPER_SNAKE_CASE for constants across frontend and backend projects.

Can I use these clean code standards during code reviews?▼

Yes, you can use these clean code standards during code reviews to enforce structured guidelines, reduce technical debt, and improve code readability across modules, components, and services.

When do I need to write comments for architectural decisions?▼

Write comments for architectural decisions during refactors or onboarding to explain the why and document rationale, aiding future developers rather than simply describing what the code does.

Related Skills

Explore More Software Engineering Skills→
getdatasurgegetdatasurge

GSD Codebase Mapper

Analyze codebases to generate ARCHITECTURE.md and STACK.md documentation.

Community
Advanced
Awais16Awais16

code-quality

Enforce SOLID principles and configure ESLint and Prettier for code quality.

Community
Intermediate
ArabelaTsoArabelaTso
142

component-boundary-identifier

Analyze Python codebases to identify component boundaries and detect architectural violations.

Community
Intermediate
tswrtswr
1

refactoring

Restructure C++, Java, Python, and Rust code without altering external behavior.

Community
Advanced