coding_standareds

What problem does it solve?

This Skill eliminates fragile, tangled codebases by enforcing a production-grade project structure, unidirectional dependencies, and strict type safety so your system scales without becoming unmaintainable.

Core Features & Use Cases

• Clean Architecture dependency flow: Enforces an import direction where config/schema/helpers/core/providers/services/routers have clear boundaries and no circular or implicit dependencies.
• Structural blueprint for maintainability: Prescribes a src/-centered layout (config, schema, helpers, core, providers, services, routers) aligned to SRP and framework-like readability.
• Safety, performance, and security guardrails: Requires Pydantic models and type hints, async-first I/O, robust error handling, parameterized safety practices, and secret management via environment variables.
• Refactoring verification mindset: Mandates regression/approval testing strategies (golden masters, mutation testing, performance and integration validation) to preserve behavior while improving design.

Use Case: When onboarding a new feature, you apply the rules to introduce new layers (e.g., a new provider or service) without modifying existing code, preventing spaghetti growth and dependency breakage.

Quick Start

Ask an AI agent to rewrite your proposed project/module structure so it follows the Skill’s clean-architecture dependency table, SRP directory responsibilities, and type-safe Pydantic-first interfaces.