What are the code length restrictions enforced by this skill?

It recommends keeping functions under 50 lines and files under 200 lines to ensure code remains focused, readable, and easy to test.

Can this skill help with code readability?

Yes, it mandates the early return pattern over nested conditionals and requires decomposition of complex components into smaller, reusable modules.

Why does this skill discourage names like 'utils' or 'helpers'?

Generic names often become 'dumping grounds' for unrelated logic. This skill enforces domain-specific naming, like 'InvoiceGenerator', to maintain a clear ubiquitous language.

How does the 'library-first' approach work?

It encourages searching for existing npm packages, SaaS solutions, or APIs before writing custom code, reducing the long-term maintenance burden of the project.

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.

Clean Software Architecture

Name: Clean Software Architecture
Author: prof-ramos

byprof-ramos

•

API Development

Implements quality-focused software development principles using Clean Architecture and Domain-Driven Design patterns.

About

This skill provides a comprehensive framework for building scalable, maintainable software by enforcing Clean Architecture and Domain-Driven Design (DDD) principles. It guides developers through professional best practices such as a 'library-first' approach to minimize maintenance debt, strict naming conventions to eliminate ambiguous 'util' files, and mandatory functional decomposition for enhanced readability. By prioritizing domain logic isolation and the early return pattern, this skill ensures that every line of code is purposeful, testable, and aligned with industry-standard architectural patterns, making it ideal for complex enterprise projects and robust API development.

Key Features

Provides domain-specific naming conventions to replace generic 'utils' and 'helpers'.
Implements strict code quality rules including early returns and function size limits.
Identifies and prevents anti-patterns like NIH (Not Invented Here) syndrome.
1 GitHub stars
Enforces Clean Architecture and DDD principles for domain logic isolation.
Promotes a library-first approach to minimize custom code and maintenance liability.

Use Cases

Refactoring legacy monoliths to improve separation of concerns and testability.
Establishing standardized architectural guardrails and coding styles for a development team.
Designing a new microservice or backend system using Domain-Driven Design.

About

Key Features

Provides domain-specific naming conventions to replace generic 'utils' and 'helpers'.
Implements strict code quality rules including early returns and function size limits.
Identifies and prevents anti-patterns like NIH (Not Invented Here) syndrome.
1 GitHub stars
Enforces Clean Architecture and DDD principles for domain logic isolation.
Promotes a library-first approach to minimize custom code and maintenance liability.

Use Cases

Refactoring legacy monoliths to improve separation of concerns and testability.
Establishing standardized architectural guardrails and coding styles for a development team.
Designing a new microservice or backend system using Domain-Driven Design.