Why does it discourage mocking internal services?

It promotes the use of real objects over mocks to ensure integration tests are more reliable and accurately reflect production behavior.

Which programming languages are supported?

While it contains specific rules for Python and TypeScript, the architectural principles like composition and dependency injection apply to most modern languages.

Does it help with performance optimization?

Yes, by strictly prohibiting blocking I/O within async paths, it ensures high-performance, non-blocking execution in web and data services.

How does this skill improve code quality?

It acts as a high-level linter and architectural guide, preventing common errors like using the 'any' type, magic numbers, and bare exception handlers.

Universal Anti-Patterns

Name: Universal Anti-Patterns
Author: kreuzberg-dev

bykreuzberg-dev

•

480

Developer Tools

Enforces high-quality coding standards and architectural best practices by preventing common development pitfalls and technical debt.

About

The Universal Anti-Patterns skill provides a critical set of guardrails for Claude, ensuring it avoids common software engineering mistakes like the use of 'any' types, class-based tests, and blocking I/O in asynchronous code. By mandating structured logging, composition over inheritance, and real object testing, this skill helps developers maintain clean, scalable, and performant codebases across Python, TypeScript, and other major languages.

Key Features

Transition from class-based to modern function-based testing patterns
Standardization of structured key=value logging and specific exception handling
Strict type safety enforcement by prohibiting 'any' and promoting generics
Prevention of blocking I/O operations within asynchronous execution paths
Elimination of magic numbers and global state through dependency injection
480 GitHub stars

Use Cases

Standardizing logging and error handling across multi-language microservices
Automating architectural code reviews to ensure composition-based design
Refactoring legacy codebases to meet modern type-safety and async standards

About

Key Features

Transition from class-based to modern function-based testing patterns
Standardization of structured key=value logging and specific exception handling
Strict type safety enforcement by prohibiting 'any' and promoting generics
Prevention of blocking I/O operations within asynchronous execution paths
Elimination of magic numbers and global state through dependency injection
480 GitHub stars

Use Cases

Standardizing logging and error handling across multi-language microservices
Automating architectural code reviews to ensure composition-based design
Refactoring legacy codebases to meet modern type-safety and async standards