software-architecture

Topics in the source

• Software Architecture Development Skill
• Code Style Rules
• General Principles
• Best Practices
• Library-First Approach
• Architecture and Design
• Anti-Patterns to Avoid
• Code Quality

This skill provides guidance for quality focused software development and architecture. It is based on Clean Architecture and Domain Driven Design principles. Early return pattern: Always use early returns when possible, over nested conditions for better readability Avoid code duplication through creation of reusable functions and modules Decompose long (more than 80 lines of code) components and functions into multiple smaller components and functions. If they cannot be used anywhere else, keep it in the same file. But if file longer than 200 lines of code, it should be split into multiple files. Use arrow functions instead of function declarations when possible ALWAYS search for existing solutions before writing custom code Check npm for existing libraries that solve the problem Evaluate existing services/SaaS solutions Consider third-party APIs for common functionality Use libraries instead of writing your own utils or helpers. For example, use cockatiel instead of writing your own retry logic. When custom code IS justified: Specific business logic unique to the domain Performance-critical paths with special requirements When external dependencies would be overkill Security-sens

This is an excerpt. Refer to the complete source and its current requirements.