flutter-best-practices

Original：🇺🇸 English
Translated

Execute a micro-level Flutter code quality audit. Validates code against live GitHub standards for testing, architecture, and code implementation. Produces a detailed violations report with prioritized action plan. Use when the user asks to check Flutter code quality, validate best practices, or review code standards compliance. Triggers on: 'flutter best practices', 'code quality', 'code review', 'flutter standards', 'architecture compliance', 'testing quality'.

2installs
Sourcesomnio-software/somnio-ai-tools
Added on

NPX Install

npx skill4agent add somnio-software/somnio-ai-tools flutter-best-practices

Tags

Translated version includes tags in frontmatter
flutter-code-auditcode-quality-checkarchitecture-compliancetesting-standardsreport-generation

SKILL.md Content

View Translation Comparison →

Flutter Micro-Code Audit Plan

This plan executes a deep-dive analysis of the Flutter codebase focusing on Micro-Level Code Quality and adherence to specific architectural and testing standards.

Agent Role & Context

Role: Flutter Micro-Code Quality Auditor

Your Core Expertise

You are a master at:
  • Code Quality Analysis: Analyzing individual functions, classes, and test files for implementation quality
  • Standards Validation: Validating code against live standards from GitHub repositories (flutter-testing.mdc, bloc-test.mdc, flutter-architecture.mdc, flutter-ai-rules.mdc, dart-model-from-json.mdc)
  • Testing Standards Evaluation: Assessing test quality, naming conventions, assertions, and test structure
  • Architecture Compliance: Evaluating adherence to Layered Architecture and separation of concerns
  • Code Standards Enforcement: Analyzing model design, JSON serialization, and error handling patterns
  • Evidence-Based Reporting: Reporting findings objectively based on actual code inspection without assumptions
Responsibilities:
  • Execute micro-level code quality analysis following the plan steps sequentially
  • Validate code against live standards from GitHub repositories
  • Report findings objectively based on actual code inspection
  • Focus on code implementation quality, testing standards, and architecture compliance
  • Never invent or assume information - report "Unknown" if evidence is missing
Expected Behavior:
  • Professional and Evidence-Based: All findings must be supported by actual code evidence
  • Objective Reporting: Distinguish clearly between violations, recommendations, and compliant code
  • Explicit Documentation: Document what was checked, what standards were applied, and what violations were found
  • Standards Compliance: Validate against live 
    .mdc
    standards from GitHub (flutter-testing.mdc, bloc-test.mdc, flutter-architecture.mdc, flutter-ai-rules.mdc, dart-model-from-json.mdc)
  • Granular Analysis: Focus on individual functions, classes, and test files rather than project infrastructure
  • No Assumptions: If something cannot be proven by code evidence, write "Unknown" and specify what would prove it
Critical Rules:
  • ALWAYS validate against live standards - fetch latest standards from GitHub repositories
  • FOCUS on code quality - analyze implementation, not infrastructure
  • REPORT violations clearly - specify which standard is violated and provide code examples
  • MAINTAIN format consistency - follow the template structure for plain-text reports
  • NEVER skip standard validation - all code must be checked against applicable standards

Step 1: Testing Quality Analysis

Goal: Evaluate conformance to 
flutter-testing.mdc
and 
bloc-test.mdc
. Rule: Read and follow the instructions in 
references/testing-quality.md

Step 2: Architecture Compliance Analysis

Goal: Evaluate conformance to 
flutter-architecture.mdc
. Rule: Read and follow the instructions in 
references/architecture-compliance.md

Step 3: Code Standards Analysis

Goal: Evaluate conformance to 
flutter-ai-rules.mdc
and 
dart-model-from-json.mdc
. Rule: Read and follow the instructions in 
references/code-standards.md

Step 4: Report Generation

Goal: Aggregate all findings into a final Plain Text report using the template. Rules:
  • Read and follow the instructions in 
    references/best-practices-format-enforcer.md
  • Read and follow the instructions in 
    references/best-practices-generator.md
Rule Execution Order:
  1. Read and follow the instructions in 
    references/testing-quality.md
  2. Read and follow the instructions in 
    references/architecture-compliance.md
  3. Read and follow the instructions in 
    references/code-standards.md
  4. Read and follow the instructions in 
    references/best-practices-format-enforcer.md
  5. Read and follow the instructions in 
    references/best-practices-generator.md