Output preview flutter-dev.preview

---
name: flutter-dev
description: | A practical guide for building cross-platform applications with Flutter 3 and Dart. Focuses on…
category: other
runtime: no special runtime
---

# flutter-dev output preview

## PART A: Task fit
- Use case: | A practical guide for building cross-platform applications with Flutter 3 and Dart. Focuses on proven patterns, state management, and performance optimization. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Quick Reference / Widget Patterns / Performance Patterns” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| A practical guide for building cross-platform applications with Flutter 3 and Dart. Focuses on proven patterns, state management, and performance optimization. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Quick Reference / Widget Patterns / Performance Patterns” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

Choose the trigger

The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.

Provide inputs and boundaries

Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.

Validate with a small run

Start with a small task and check whether the result follows “Quick Reference / Widget Patterns / Performance Patterns”. Inspect diffs, logs, previews, or tests before expanding scope.

Review before delivery

Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.

SKILL.md SKILL.md

---
name: flutter-dev
description: | A practical guide for building cross-platform applications with Flutter 3 and Dart. Focuses on…
category: other
source: MiniMax-AI/skills
---

# flutter-dev

## When to use
- | A practical guide for building cross-platform applications with Flutter 3 and Dart. Focuses on proven patterns, stat…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Quick Reference / Widget Patterns / Performance Patterns” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "flutter-dev" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Quick Reference / Widget Patterns / Performance Patterns
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Purpose	Component
State management (simple)	`StateProvider` + `ConsumerWidget`
State management (complex)	`NotifierProvider` / `Bloc`
Async data	`FutureProvider` / `AsyncNotifierProvider`
Real-time streams	`StreamProvider`
Navigation	`GoRouter` + `context.go/push`
Responsive layout	`LayoutBuilder` + breakpoints
List display	`ListView.builder`
Complex scrolling	`CustomScrollView` + Slivers
Hooks	`HookWidget` + `useState/useEffect`
Forms	`Form` + `TextFormField` + validation

Purpose	Solution
Prevent rebuilds	`const` constructors
Selective updates	`ref.watch(provider.select(...))`
Isolate repaints	`RepaintBoundary`
Lazy lists	`ListView.builder`
Heavy computation	`compute()` isolate
Image caching	`cached_network_image`

Topic	Reference
Widget patterns, const optimization, responsive layout	Widget Patterns
Riverpod providers, notifiers, async state	Riverpod State Management
Bloc, Cubit, event-driven state	Bloc State Management
GoRouter setup, routes, deep linking	GoRouter Navigation
Feature-based structure, dependencies	Project Structure
Profiling, const optimization, DevTools	Performance Optimization
Widget tests, integration tests, mocking	Testing Strategies
iOS/Android/Web specific implementations	Platform Integration
Implicit/explicit animations, Hero, transitions	Animations
Dio, interceptors, error handling, caching	Networking
Form validation, FormField, input formatters	Forms
i18n, flutter_localizations, intl	Localization

flutter-dev

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

Flutter Development Guide

Quick Reference

Widget Patterns

Performance Patterns

Core Principles

Widget Optimization

State Management

Layout

Performance

Checklist

Widget Best Practices

State Management

Navigation

Performance

Testing

References

Discussion