project-guidelines

To enforce Flutter Clean Architecture, apply a skill that mandates a feature-first structure with data, domain, and presentation layers. This ensures repository-wide architectural alignment by applying structural rules to feature development and refactoring tasks.

Standardizing Dart naming conventions and linting rules involves enforcing snake_case naming, applying Flutter linting, and ensuring analyzer-clean code. This approach guarantees consistent styling and formatting across all new and refactored code.

Yes, this approach supports BLoC and Cubit state management by mandating immutable states and json_serializable DTOs. It ensures consistent state handling and data serialization across your Flutter application architecture.

To set up Flutter project standards for unit testing, enforce requirements for testing business logic and critical behavior. Reference a GUIDELINES.md file to govern testing expectations and ensure consistent quality across the repository.

Yes, you need a GUIDELINES.md file to apply repository coding standards. This file specifies architecture requirements, naming conventions, tooling standards, and testing expectations, serving as the central governance document for the project.