Does this skill help with naming conventions?

Yes, it actively discourages generic names like 'utils' or 'common' and instead promotes domain-specific naming such as 'InvoiceGenerator' or 'UserAuthenticator'.

How does this skill handle the use of third-party libraries?

It enforces a 'library-first' approach, meaning it will always search for existing npm packages or SaaS solutions before recommending custom-written utility code.

Can this be used for both frontend and backend development?

Absolutely. While the principles are rooted in backend patterns like DDD, the rules for modularity, early returns, and separation of concerns apply to any software layer.

What are the code length restrictions implemented by this skill?

To ensure maintainability, the skill encourages keeping functions under 50 lines and splitting files once they exceed 200 lines of code.

What architectural patterns does this skill support?

The skill is built on Clean Architecture and Domain-Driven Design (DDD) principles, focusing on separating business logic from infrastructure and UI concerns.

Software Architecture & Clean Code

Name: Software Architecture & Clean Code
Author: enuno

byenuno

•

개발자 도구

Enforces Clean Architecture and Domain-Driven Design principles to build maintainable, scalable, and high-quality software systems.

소개

This skill serves as a comprehensive architectural compass for Claude, guiding it to implement robust software patterns like Domain-Driven Design (DDD) and Clean Architecture. It prioritizes code quality through strict modularity rules, such as early return patterns and specific file/function length limits, while championing a 'library-first' approach to minimize technical debt. By discouraging generic naming and 'Not Invented Here' syndrome, it ensures that codebases remain decoupled, testable, and aligned with industry best practices for professional software development.

주요 기능

Enforces Clean Architecture and DDD principles for better separation of concerns
Encourages domain-specific naming conventions over generic utility patterns
Implements strict modularity with function and file length constraints
Promotes a library-first approach to leverage existing, battle-tested solutions
Optimizes code readability via early returns and shallow nesting (max 3 levels)
3 GitHub stars

사용 사례

Enforcing consistent code style and architectural boundaries during development
Architecting a new service using Domain-Driven Design and bounded contexts
Refactoring legacy monoliths into modular, domain-specific components

소개

주요 기능

Enforces Clean Architecture and DDD principles for better separation of concerns
Encourages domain-specific naming conventions over generic utility patterns
Implements strict modularity with function and file length constraints
Promotes a library-first approach to leverage existing, battle-tested solutions
Optimizes code readability via early returns and shallow nesting (max 3 levels)
3 GitHub stars

사용 사례

Enforcing consistent code style and architectural boundaries during development
Architecting a new service using Domain-Driven Design and bounded contexts
Refactoring legacy monoliths into modular, domain-specific components