# Somnio Software Somnio AI Tools Flutter Best Practices

> Flutter Micro-Code Audit Plan

- Skill: `tomevault-io/somnio-software-somnio-ai-tools-flutter-best-practices` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/somnio-software-somnio-ai-tools-flutter-best-practices`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/somnio-software-somnio-ai-tools-flutter-best-practices/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/somnio-software-somnio-ai-tools-flutter-best-practices

---


# 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 local standards from
  `agent-rules/rules/` (testing.md, bloc-test.md,
  architecture.md, best-practices.md, dart-model-from-json.md)
- **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 local `.md` standards from
  `agent-rules/rules/flutter/` (testing.md, bloc-test.md, architecture.md,
  best-practices.md, dart-model-from-json.md)
- **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 local standards** - read from
  `agent-rules/rules/flutter/` in the somnio-ai-tools repository
- **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
  Markdown 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 Markdown 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`

## Report Metadata (MANDATORY)

Every generated report MUST include a metadata block at the very end. This is non-negotiable — never omit it.

To resolve the source and version:
1. Look for `.claude-plugin/plugin.json` by traversing up from this skill's directory
2. If found, read `name` and `version` from that file (plugin context)
3. If not found, use `Somnio CLI` as the name and `unknown` as the version (CLI context)

Include this block at the very end of the report:

```
---
Generated by: [plugin name or "Somnio CLI"] v[version]
Skill: flutter-best-practices
Date: [YYYY-MM-DD]
Somnio AI Tools: https://github.com/somnio-software/somnio-ai-tools
---
```

---
> Source: [somnio-software/somnio-ai-tools](https://github.com/somnio-software/somnio-ai-tools) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->