agentsclimarketplace

Flutter expert

Skill Poorgramer-Zack/dart-expert-skills/skills/flutter-expert

A comprehensive library of modular Agent Skills for Flutter & Dart development

Install
npx -y skills add Poorgramer-Zack/dart-expert-skills --skill flutter-expert

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Expert-level guidance for Flutter production applications: architecture decisions (Clean/Layered/Hexagonal/Feature-First), advanced state management (BLoC/Riverpod/GetX), performance optimization (eliminating jank, memory profiling, reducing rebuild overhead), code review with design pattern enforcement, scalability assessments, native platform integration (MethodChannel/EventChannel/FFI), complex UI challenges (custom render objects, slivers), testing strategies (unit/widget/integration/golden), CI/CD pipeline architecture, build optimization, and accessibility compliance. Triggers: 'architecture decision', 'design pattern', 'performance issue', 'code review', 'production problem', 'scaling concerns', 'best practices', 'technical debt', 'refactoring strategy'. Essential for complex enterprise apps, critical production debugging, architectural refactors, or when choosing between competing technical approaches.

SKILL.md

4.3 KB, as published. Nobody here has run it

Flutter Expert Guide

Overview

Expert reference for Flutter architecture, UI implementation, native platform integration, and performance optimization across the full application lifecycle.

Process

🚀 High-Level Workflow

Architecting a scalable Flutter application involves the following development phases:

Phase 1: Environment & Architecture Foundations

1.1 Core Architectural Design

Choose between feature-first and layer-first directory structures. Architect Domain, Data, and Presentation layers.

  • References: architecture.md, architecture-decision-matrix.md

Phase 2: Application Navigation & Interactive UI Delivery

2.1 Phenomenal UI Implementation & Theming

Build responsive adaptive UI with accessibility (a11y) and internationalization (i18n) standards.

  • References: layout.md, theming.md, accessibility.md, localization.md

2.2 System UI Control & Immersion

Fine-tune status bar and navigation bar aesthetics. Control full-screen immersive modes while effectively resolving manufacturer-specific layout bugs.

  • Reference: system-ui.md

2.3 Animations & Micro-Interactions

Implement implicit/explicit animations and micro-interactions to improve perceived performance and UX.

  • Reference: animation.md

Phase 3: Data Integration & Systemic Performance

3.1 Advanced Data Architectures

Implement HTTP clients, JSON parsing strategies, and response caching.

  • References: http-and-json.md, caching.md

3.2 Performance & Concurrency Scaling

Move heavy computation to background isolates to prevent UI jank. Optimize compiled app size via tree shaking, deferred loading, and asset compression.

  • References: performance.md, concurrency.md, app-size.md

3.3 Deep Native Platform Integrations

Communicate with native OS APIs via MethodChannel, EventChannel, or dart:ffi.

  • References: native-interop.md, platform-views.md, plugins.md, home-screen-widget.md

Reference Files

📚 Documentation Library

Specialized reference documents for each topic:

Architecture Foundations

Visual Presentation (UI/UX)

Systems, Network & Data

Native Devices & Platform Enhancements

Optimization & Quality Assurance

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.