coding-general

Standardize coding practices across multiple projects by applying universal guidelines that enforce strict rules like early returns, guard clauses, modular design, and explicit abstraction boundaries. This ensures consistent implementation and architectural alignment across all workspace codebases.

Enforce code style rules during code reviews by checking for early returns, avoidance of else statements, a maximum of 20 lines per function, and no inline SVGs. Applying these universal guidelines streamlines reviews and ensures modular, testable design.

Yes, you can use these coding guidelines to refactor existing architecture by applying strict rules such as explicit abstraction boundaries and modular design. Review a current project and refactor components, modules, and architecture to align with the universal practices.

Avoid else statements and inline SVGs to maintain strict implementation discipline and modular, testable design. These coding guidelines enforce early returns and explicit abstraction boundaries to standardize practices and streamline code reviews across teams.

Limitations depend on your existing codebase complexity, as enforcing strict rules like max 20 lines per function and no inline SVGs requires significant refactoring. These universal guidelines apply to any codebase within the workspace but demand implementation discipline to maintain architectural alignment.