code-standards

Enforce SOLID principles and Clean Code patterns across classes and modules.

14|1|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/marcioaltoe/claude-craftkit --skill code-standards-marcioaltoe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-standards
Source: https://github.com/marcioaltoe/claude-craftkit/tree/main/plugins/architecture-design/skills/code-standards
Command: npx skills add https://github.com/marcioaltoe/claude-craftkit --skill code-standards-marcioaltoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers to design simple, robust, and clean code, applying SOLID, DRY, KISS, and pragmatic design patterns to reduce complexity and maintenance costs.

Core Features & Use Cases

  • SOLID Application: Apply SOLID principles in class/module design.
  • Clean Code Guidelines: Enforce readability, naming, and testability.
  • Code Review Aid: Provide quick checks to spot anti-patterns and complexity.

Quick Start

Describe a simple class or function that adheres to SOLID principles in a minimal, well-structured example.

Frequently Asked Questions about code-standards

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

FAQPage Schema
How do I apply SOLID principles to improve code maintainability?

SOLID principles guide design by enforcing Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. They reduce complexity, separate concerns, and make code easier to test and evolve across any software context.

What's the best way to refactor code to follow clean code standards?

Start by identifying violations of DRY, KISS, and YAGNI patterns, then apply SOLID principles incrementally. Prioritize separation of concerns and simplicity over premature abstraction, and validate changes through code review.

When should I enforce design standards during development?

Apply design standards during feature design, refactors, bug fixes, and code reviews. Early enforcement prevents architectural decay and maintains simplicity throughout the development lifecycle rather than fixing problems after they accumulate.

How do SOLID principles differ from other design approaches?

SOLID emphasizes separation of concerns and flexible module interfaces over coupled systems. It pairs with pragmatic patterns like DRY and YAGNI to prevent over-engineering while maintaining testability and long-term maintainability.

Can I use clean code standards with existing codebases?

Yes. Clean code guidelines and SOLID principles apply during refactors and bug fixes in any existing codebase. They help arrest maintainability drift without requiring a full rewrite.

What anti-patterns should I watch for in code reviews?

Watch for violations of Single Responsibility, tight coupling, duplication, unnecessary complexity, and over-abstraction. Code review checklists based on SOLID and Clean Code patterns help spot these quickly.