How does this skill manage code complexity?

It enforces rules for early returns, limits function and file length, and restricts nesting depth to a maximum of three levels to ensure readability.

What is the Library-First approach in this skill?

It is a strategy that prioritizes using established third-party libraries over writing custom utility code to reduce the maintenance liability of the codebase.

When should I activate the software-architecture skill?

You should use it whenever you are designing system architecture, writing new features, or performing code analysis to ensure best practices are followed.

Does this skill help with naming conventions?

Yes, it strictly discourages generic names like 'utils' and 'helpers' in favor of domain-specific, descriptive names that follow bounded context patterns.

Software Architecture Guide

Name: Software Architecture Guide
Author: ShunmeiCho

byShunmeiCho

0•

Herramientas para Desarrolladores

Implements Clean Architecture and Domain-Driven Design principles to ensure high-quality, maintainable codebases.

This skill acts as an architectural consultant for Claude, enforcing high standards for software development. It promotes the 'Library-First' approach to reduce maintenance overhead, utilizes Clean Architecture and Domain-Driven Design (DDD) to isolate business logic, and applies strict code quality rules such as early returns and modular decomposition. By preventing 'Not Invented Here' syndrome and ensuring domain-specific naming, it helps developers build scalable systems that are easy to test and maintain over time.

Características Principales

01Strict separation of concerns between logic and infrastructure

02Clean Architecture and DDD implementation guidance

030 GitHub stars

04Library-First approach to minimize custom code maintenance

05Automatic code decomposition and length management rules

06Domain-specific naming convention enforcement

Casos de Uso

01Refactoring a monolithic codebase into a modular DDD structure

02Conducting architectural reviews to identify 'Not Invented Here' anti-patterns

03Establishing high-quality code style standards for new projects

Características Principales

01Strict separation of concerns between logic and infrastructure

02Clean Architecture and DDD implementation guidance

030 GitHub stars

04Library-First approach to minimize custom code maintenance

05Automatic code decomposition and length management rules

06Domain-specific naming convention enforcement

Casos de Uso

01Refactoring a monolithic codebase into a modular DDD structure

02Conducting architectural reviews to identify 'Not Invented Here' anti-patterns

03Establishing high-quality code style standards for new projects