coding-standards

You can enforce cross-project coding standards by applying framework-agnostic guidelines for descriptive naming, immutability, and error handling. This establishes a shared baseline for readability and maintainability across different languages like C# and Python.

Best practices for reviewing code quality involve checking for descriptive naming, immutability, consistent error handling, and type safety. Use these baseline conventions during refactoring sessions to identify code smells and align modules with structural standards.

Yes, the coding standards skill provides concrete framework-agnostic examples in both C# and Python. These examples illustrate best practices for naming conventions, readability, and type safety specific to these language stacks.

Set up baseline code hygiene for onboarding by codifying requirements for descriptive naming, structure enforcement, and type safety. This gives new contributors a shared floor of coding conventions to follow when starting new modules.

Use cross-project coding conventions for baseline code quality, naming, and structure across languages. Defer to stack-specific skills like python-development or VSTO-development when you need framework-specific patterns and language-level playbooks.

Apply guidelines that emphasize immutability and strict type safety when creating new modules. These cross-project conventions improve code readability and maintainability while preventing structural inconsistencies across your codebase.