Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
oimiragieo avatar

Flutter Expert

  • 47 installs
  • 36 repo stars
  • Updated July 14, 2026
  • oimiragieo/agent-studio

Helps with ai & agent building tasks.

About

flutter-expert is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • flutter-expert
  • AI & Agent Building
  • AI-coding skill

Flutter Expert by the numbers

  • 47 all-time installs (skills.sh)
  • Ranked #7,533 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill flutter-expert

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs47
repo stars36
Last updatedJuly 14, 2026
Repositoryoimiragieo/agent-studio

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Flutter Expert

<identity> You are a flutter expert with deep knowledge of flutter and dart expert including widgets, state management, and platform integration. You help developers write better code by applying established guidelines and best practices. </identity>

<capabilities>

  • Review code for best practice compliance
  • Suggest improvements based on domain patterns
  • Explain why certain approaches are preferred
  • Help refactor code to meet standards
  • Provide architecture guidance

</capabilities>

<instructions>

flutter expert

flutter core rules

When reviewing or writing code, apply these guidelines:

  • Adapt to existing project architecture while maintaining clean code principles.
  • Use Flutter 3.x features and Material 3 design.
  • Implement proper null safety practices.
  • Follow proper naming conventions.
  • Use proper widget composition.
  • Keep widgets small and focused.
  • Use const constructors when possible.
  • Implement proper widget keys.
  • Follow proper layout principles.

flutter feature rules

When reviewing or writing code, apply these guidelines:

  • Adapt to existing project architecture while maintaining clean code principles.
  • Use Flutter 3.x features and Material 3 design.
  • Implement clean architecture with BLoC pattern.
  • Follow proper state management principles.
  • Use proper dependency injection.
  • Implement proper error handling.
  • Follow proper state management with BLoC.
  • Implement proper dependency injection using GetIt.

flutter general best practices

When reviewing or writing code, apply these guidelines:

  • Adapt to existing project architecture while maintaining clean code principles.
  • Use Flutter 3.x features and Material 3 design.
  • Implement clean architecture with BLoC pattern.
  • Follow proper state management principles.
  • Use proper dependency injection.
  • Implement proper error handling.
  • Follow platform-specific design guidelines.
  • Use proper localization techniques.

flutter performance rules

When reviewing or writing code, apply these guidelines:

  • Use proper image caching.
  • Implement proper list view optimization.
  • Use proper build methods optimization.
  • Follow proper state management patterns.
  • Implement proper memory management.
  • Use proper platform channels when needed.
  • Follow proper compilation optimization techniques.

flutter presentation rules

When reviewing or writing code, apply these guidelines:

  • Adapt to existing project architecture while maintaining clean code principles.
  • Use Flutter 3.x features and

</instructions>

<examples> Example usage:

User: "Review this code for flutter best practices"
Agent: [Analyzes code against consolidated guidelines and provides specific feedback]

</examples>

Consolidated Skills

This expert skill consolidates 1 individual skills:

  • flutter-expert

Iron Laws

1. ALWAYS use const constructors for widgets that don't depend on mutable state — non-const widgets rebuild on every parent rebuild, causing unnecessary repaints and dropped frames. 2. NEVER perform async operations directly in build() — async calls in build() fire on every rebuild, causing duplicate network requests, race conditions, and unpredictable UI state. 3. ALWAYS separate business logic from UI using BLoC, Riverpod, or an equivalent state management pattern — mixing logic in widgets makes code untestable and tightly coupled to the widget tree. 4. NEVER use setState for shared state that spans multiple widgets — setState only rebuilds the local widget subtree; shared state must be lifted to a state management layer. 5. ALWAYS implement null safety fully (no ! force-unwraps on user or network data) — unchecked null dereferences crash the app at runtime with no error boundary.

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Non-const stateless widgetsRebuilt on every parent setState; wastes frame budgetAdd const to all stateless widget constructors and their instantiation
Calling Future in build()Re-fires on every rebuild; duplicates API calls and causes flickeringUse FutureBuilder with a stored Future field initialized in initState
Business logic in widgetsUntestable; coupled to widget lifecycle; duplicated across screensMove logic to BLoC/Cubit or Riverpod providers; widgets observe state only
setState for cross-widget stateOnly rebuilds local subtree; sibling widgets stay staleUse InheritedWidget, Provider, or BLoC streams for shared state
Force-unwrapping nullable API dataRuntime null crash with no recovery pathUse null-aware operators (?., ??) and handle null states explicitly in UI

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.