# Flutter > Coding conventions for Flutter and Dart development in this project. Use when this capability is needed. - Skill: `tomevault-io/flutter-8` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/flutter-8` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/flutter-8/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/flutter-8 --- # Flutter & Dart Conventions ## General Principles - **Clean & Explicit**: Write readable and maintainable Dart code. - **Safety First**: Avoid `any` types; prefer strict typing and sound null safety. - **Consistency**: Follow existing patterns in the codebase for widgets and state management. ## Widget Guidelines - Use `const` constructors whenever possible to improve performance. - Favor composition over inheritance. - Large widget trees should be split into smaller, focused widgets. - Prefer `StatelessWidget` unless internal state is absolutely necessary. ## Localization - Use the localized strings from the defined `l10n` setup. - Do not hardcode user-facing strings in widget trees. ## Testing - Ensure new features have corresponding unit or widget tests when applicable. - Run tests regularly using `flutter test`. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jamesoidian) — claim your Tome and manage your conversions.