بنقرة واحدة
dart-flutter-rules
يحتوي dart-flutter-rules على 30 من skills المجمعة من reloveution، مع تغطية مهنية على مستوى المستودع وصفحات skill داخل الموقع.
Skills في هذا المستودع
MCP server usage for Dart MCP, Firecrawl, Hugging Face. Tool priorities, commands, workflows.
Development process rules. Use when planning complex tasks, implementing incrementally, managing packages, or following communication guidelines.
Dart 3 patterns including switch/if-case, pattern matching, sealed classes, and records. Use when writing exhaustive switches, destructuring, pattern matching on types, or returning multiple values with records.
Core code quality rules for Dart/Flutter. Use when formatting, handling async/null safety, organizing classes, or following Dart best practices.
Code review checklist for PRs/MRs. Use when reviewing pull requests, examining code changes, or when the user asks for a code review.
Data handling patterns for Dart/Flutter. Use when implementing serialization, caching, layer separation, DTOs, repositories, offline-first, or data validation.
Dependency injection patterns for Dart/Flutter applications. Use when configuring get_it, registering dependencies, using constructor injection, setting up composition root, and testing with mocks.
Core software design principles for maintainable Dart/Flutter code. Use when applying SOLID, composition over inheritance, polymorphism over switch/case, immutability, abstraction layers, and code reusability.
Complete guide for using drift database library in Dart applications (CLI, server-side, non-Flutter). Use when building Dart apps that need local SQLite database storage or PostgreSQL connection with type-safe queries, reactive streams, migrations, and efficient CRUD operations.
Error handling patterns for Dart/Flutter. Use when implementing Result<T>, exception vs Error, try-catch at boundaries, validation, retry, logging, and resource cleanup.
Defines the AI assistant's role as Senior Dart/Flutter Architect with Clean Architecture, BLoC, SOLID expertise. Use when guiding AI behavior for Dart/Flutter tasks, code review, architecture decisions, or when task type suggests specific competency activation.
Mocktail testing guidelines for Dart/Flutter. Use when creating mocks, fakes, stubbing async/sync, verifying interactions, registerFallbackValue, or avoiding MissingStub errors.
Project naming conventions for Dart/Flutter. Use when naming interfaces (I prefix), implementations (Impl), use cases (Ucs), datasources (Dts), extensions (X), mixins (Mxn), or organizing feature/datasource folders.
Resource lifecycle and disposal for Dart/Flutter. Use when managing Timer, StreamController, subscriptions, animations, network cancellation, file/DB handles, native resources, or preventing memory leaks.
Simplicity and directness for Dart/Flutter. Use when choosing solutions, avoiding over-engineering, preferring readable over clever code, or applying YAGNI.
Build adaptive and responsive Flutter UIs that work beautifully across all platforms and screen sizes. Use when creating Flutter apps that need to adapt layouts based on screen size, support multiple platforms including mobile tablet desktop and web, handle different input devices like touch mouse and keyboard, implement responsive navigation patterns, optimize for large screens and foldables, or use Capability and Policy patterns for platform-specific behavior.
Comprehensive guide for implementing animations in Flutter. Use when adding motion and visual effects to Flutter apps: implicit animations (AnimatedContainer, AnimatedOpacity, TweenAnimationBuilder), explicit animations (AnimationController, Tween, AnimatedWidget/AnimatedBuilder), hero animations (shared element transitions), staggered animations (sequential/overlapping), and physics-based animations. Includes workflow for choosing the right animation type, implementation patterns, and best practices for performance and user experience.
Flutter app architecture — Clean Architecture layers, BLoC/Cubit, feature-first organization, design patterns (Result, Repository, Offline-First).
BLoC/Cubit state management for Flutter — naming, state modeling, widgets, testing, architecture rules.
Guide for drift database in Flutter. Use when building apps with local SQLite storage — type-safe queries, reactive streams, migrations, CRUD. Includes drift_flutter setup, StreamBuilder integration, and cross-platform support.
Guide for internationalizing Flutter apps using gen-l10n and intl packages. Use when adding localization, translating UI text, formatting numbers/dates for locales, or configuring multi-language support.
Flutter navigation and routing: go_router, auto_route, Navigator 2.0, deep linking, data passing, web URL strategies. Use when implementing screen transitions, routing, deep links, or browser history.
Flutter networking — HTTP CRUD, WebSocket, authentication, error handling, performance. Use when implementing HTTP requests, WebSocket connections, authenticated requests, background parsing, or REST API integration.
Performance optimization for Flutter apps. Use when optimizing lists, build methods, const/keys, images, RepaintBoundary, isolates, or profiling with DevTools.
Provider state management for Flutter. Use when exposing values with Provider, ChangeNotifierProvider, FutureProvider, StreamProvider, scoping with context.watch/read/select, ProxyProvider, or testing provider-based state.
Security best practices for Flutter apps. Use when storing credentials, validating input, securing network/API, or preventing XSS.
State management for Flutter. Use when choosing patterns, implementing BLoC/Cubit, built-in (Streams, Futures, ValueNotifier), ChangeNotifier, or Provider.
Flutter testing guidance covering unit tests, widget tests, integration tests, mocktail mocking, and plugin testing. Use when writing tests, mocking dependencies, debugging test errors, or running tests.
Flutter widget patterns. Use when building UI, fixing layout errors, theming, composing widgets, GoRouter, accessibility, or assets.
Mermaid diagram syntax for flowcharts, sequence, class, state, module, ER, GitFlow. Use when generating Mermaid diagrams in documentation, technical designs, or architecture.