Can it identify architectural issues?

Yes, it specifically scans for 'Feature Envy' (where a method uses another class's data more than its own) and tight coupling via hidden dependencies.

Will it help me rename my variables?

Yes, it identifies and suggests replacements for generic names like 'data', 'utils', or 'manager' with domain-specific, intention-revealing terms.

What is Object Calisthenics in this context?

It is a set of 9 rules, such as 'one level of indentation' and 'no else keyword', designed to improve code readability, maintainability, and modularity.

How does this skill handle TypeScript errors?

It strictly forbids type escape hatches like 'any' or 'as' and promotes the use of Zod for runtime validation to keep types and data in sync.

Software Design Principles

Name: Software Design Principles
Author: NTCoding

byNTCoding

•

Developer Tools

Enforces professional object-oriented design patterns and type-safe principles to create maintainable, self-documenting codebases.

About

This skill equips Claude with a rigorous set of software engineering best practices, ranging from Object Calisthenics and Dependency Inversion to Type-Driven Design. It focuses on eliminating technical debt by enforcing fail-fast error handling, removing generic naming conventions, and making illegal states unrepresentable via TypeScript’s type system. Ideal for refactoring legacy modules, performing deep architectural reviews, or ensuring high-quality standards during the development of new features, it transforms code from simply 'functional' to architecturally sound.

Key Features

Intention-revealing naming standards to replace generic jargon like 'utils' or 'data'
Object Calisthenics enforcement (one level of indentation, no 'else' keyword, etc.)
Fail-fast error handling and Zod-based runtime validation for external data
Dependency Inversion and Loose Coupling through mandatory constructor injection
Type-Driven Design to make illegal states unrepresentable without 'any' or 'as'
94 GitHub stars

Use Cases

Designing type-safe domain models to ensure business logic integrity
Refactoring complex legacy methods into small, cohesive classes and entities
Conducting automated code reviews to detect 'Feature Envy' and tight coupling

About

Key Features

Intention-revealing naming standards to replace generic jargon like 'utils' or 'data'
Object Calisthenics enforcement (one level of indentation, no 'else' keyword, etc.)
Fail-fast error handling and Zod-based runtime validation for external data
Dependency Inversion and Loose Coupling through mandatory constructor injection
Type-Driven Design to make illegal states unrepresentable without 'any' or 'as'
94 GitHub stars

Use Cases

Designing type-safe domain models to ensure business logic integrity
Refactoring complex legacy methods into small, cohesive classes and entities
Conducting automated code reviews to detect 'Feature Envy' and tight coupling