skills/flutter-standards/SKILL.md
Use this skill as the shared reference hub for all Flutter & Dart development — coding standards, naming conventions, architecture patterns, state management, testing, performance, and UI guidelines. MUST be included in load_skills for any Flutter task delegation. Triggers automatically when writing, reviewing, debugging, testing, or planning Flutter/Dart code. Contains 12 reference files across architecture, state, UI, performance, and tooling categories that downstream skills pull on demand. Also use when the user says Dart style guide, Flutter best practices, Riverpod patterns, feature-first structure, Flutter performance, or any Flutter/Dart coding standards question.
npx skillsauth add cuozg/oh-my-skills flutter-standardsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Flutter & Dart shared reference hub for code, review, debug, testing, planning, and UI work.
flutter-standards in load_skills for delegated Flutter work.read_skill_file("flutter-standards", "references/<filename>").dart-style-guide.md — Effective Dart naming, formatting, linting, null-safety rulescode-organization.md — Feature-first folder layout, pubspec.yaml, build flavors, barrel filesarchitecture-patterns.md — Feature-first, layered architecture, MVVM, clean arch comparisonstate-management-guide.md — Riverpod 2.x codegen, Notifier patterns, BLoC/Provider alternativesdependency-injection.md — Riverpod as DI, GetIt/Injectable alternatives, scoping strategiesui-best-practices.md — Widget composition, const, keys, responsive layout, themingasset-management.md — Images, fonts, flutter_gen, gen_l10n, asset organizationasync-streams.md — Future, Stream, StreamController, Completer, error propagationerror-handling.md — Exception hierarchies, Result pattern, user-facing recovery, crash reportingtesting-patterns.md — Unit, widget, golden, integration tests; AAA pattern, mocking with Mocktailperformance-optimization.md — Rebuild profiling, RepaintBoundary, Impeller, memory, frame budgetdebug-logging.md — package:logger, DevTools, PlatformDispatcher, structured loggingThese skills load references from flutter-standards:
| Skill | Domain | |-------|--------| | flutter-init | Scaffold new Flutter projects with feature-first architecture | | flutter-code | Write, extend, refactor Flutter/Dart code | | flutter-ui | Build screens, widgets, responsive layouts | | flutter-debug | Diagnose and fix Flutter bugs | | flutter-review | Review Flutter PRs and local changes | | flutter-test | Write unit, widget, and integration tests | | flutter-profiler | Analyze DevTools profiler data |
tools
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
tools
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
tools
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
development
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.