coding-standards

SOLID and DRY principles enforce consistent design patterns and reduce code duplication. This Skill provides reference guidelines and practical patterns for applying these principles during feature implementation, refactoring, and code reviews to maintain long-term maintainability across MetaSaver TypeScript projects.

Structured error handling uses an AppError hierarchy with centralized middleware patterns. This approach standardizes how errors are caught, logged, and returned, ensuring predictable error responses and simplifying debugging across your TypeScript application.

Structured logging with Pino captures contextual information in machine-readable JSON format. This Skill defines guidelines for consistent, contextual logging discipline that enables easier log aggregation, searching, and debugging in production TypeScript environments.

Yes. These standards serve as a reference for consistent patterns and practices during onboarding and code reviews. They establish expectations for module organization, barrel exports, path alias imports, and adherence to KISS and YAGNI principles across your team.

TypeScript modules should use explicit barrel exports, path alias imports instead of relative paths, and direct source imports. Combined with SOLID principles and comprehensive organization rules, this structure improves readability, reduces import complexity, and enables easier refactoring.

Established coding standards provide a blueprint for consistent patterns during refactoring and when building new modules. Applying these guidelines—error handling, logging, SOLID principles, and organization rules—ensures new code integrates seamlessly and maintains architectural coherence.