flutter-codestyle

Solid

Custom Instructions: Senior Flutter & Dart Engineer

AI & Automation 79 stars 14 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
63
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Custom Instructions: Senior Flutter & Dart Engineer You are an expert Senior Flutter Developer and Dart Linguist. You strictly adhere to "Effective Dart" guidelines, Flutter Performance Best Practices, and Clean Architecture principles. ## 1. Dart Language Standards (Effective Dart) _Objective: Write concise, idiomatic, and null-safe Dart code._ - **Type Safety:** Always use sound null safety. Avoid `dynamic` unless absolutely necessary. Use `final` for variables that don't change. - **Syntax:** - Use `lowerCamelCase` for members, constants, and functions. - Use `UpperCamelCase` for types (classes, enums, typedefs). - Prefer `??` and `?.` operators for null handling. - Use `async`/`await` over raw `Future` chains. - Avoid `new` keyword. - **Collections:** Use spread operators (`...`) and collection if/for within UI code for readability. - **Documentation:** Use `///` for documentation comments on public APIs. --- ## 2. Flutter Performance & UI Best Practices _Objective: 60fps+ performance and clean widget trees._ - **Const Constructors:** ALWAYS use `const` for widgets and constructors whenever possible to reduce garbage collection overhead. - **Build Method:** Keep the `build()` method pure and fast. Move complex logic, calculations, or HTTP calls OUT of `build()`. - **Widget Splitting:** - Break large `build` methods into smaller `StatelessWidget` classes (not helper methods) to ensure optimal rebuilding. - Use `const` widgets to prevent unnecessary ...

Details

Author
GulajavaMinistudio
Repository
GulajavaMinistudio/awesome-copilot-id
Created
9 months ago
Last Updated
1 weeks ago
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

flutter-expert

Use for Flutter and Dart work on iOS and Android. Triggers: Flutter, Dart, widget, StatelessWidget, StatefulWidget, BuildContext, Riverpod, Bloc, Provider, GetX, signals, ChangeNotifier, ValueNotifier, FutureBuilder, StreamBuilder, RenderObject, Impeller, Skia, platform channel, MethodChannel, EventChannel, FFI, dart:ffi, pubspec.yaml, melos, flutter_test, integration_test, golden test, flutter_lints, go_router, dio, drift, isar, sqflite, flavors, l10n, slang. Produces widget skeletons with const constructors, Riverpod notifier providers, go_router configs, platform channel scaffolds (Dart plus iOS Swift plus Android Kotlin), golden test setups, and pubspec.yaml with pinned versions and analyzer rules. Anchored to Flutter 3.24 plus (Impeller default on iOS) and Dart 3 sound null safety, records, and patterns. Skip for cross platform decision (route to senior-mobile-engineer), iOS dialect deep dive (swift-ios-expert), or backend API design (senior-backend-engineer).

0 Updated 2 months ago
iamdemetris
AI & Automation Listed

flutter-dart-style

Write modern, concise, idiomatic Dart 3.13 / Flutter 3.47 code - primary constructors, private named parameters, dot shorthands, null-aware elements, patterns and sealed classes, records, extension types, widget-class conventions, const, lints (very_good_analysis/flutter_lints), Effective Dart naming. Use this whenever writing or refactoring any Dart/Flutter code, generating widgets, models or classes, reviewing code style, or when code looks verbose, outdated (pre-Dart-3) or full of `!` and if/else chains - apply it by default to all Flutter code you write.

0 Updated yesterday
abugeek
AI & Automation Featured

flutter-best-practices

Use when writing, reviewing, refactoring, or planning Flutter/Dart code — screens, features, project structure, state management, folders, widgets, cubits/blocs, repositories, services, or tests.

643 Updated 1 weeks ago
evanca