Build Flutter Features
Build and refactor Flutter features with layered architecture, robust state management, Dart MCP analysis, and optional Figma MCP UI implementation.
Install
$ agentstack add skill-wreos-flutter-cursor-plugin-build-flutter-features ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-wreos-flutter-cursor-plugin-build-flutter-features) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Build Flutter Features
Use this skill for non-test Flutter development tasks.
Workflow
- Understand the target behavior and constraints.
- Map changes by layer: presentation -> domain -> data.
- Keep dependency flow one-directional and injectable.
- Implement feature changes in small increments.
- Use Dart MCP to validate diagnostics and apply safe fixes.
- If Figma source exists, follow
figma-to-flutter.md. - Add/update tests using
../write-flutter-tests/SKILL.md.
Architecture defaults
- Keep widgets focused on rendering and interaction.
- Choose state management based on existing project conventions first.
- If the project already uses Riverpod/Bloc/Cubit/GetX, stay consistent with that choice.
- If no convention exists, choose the simplest viable option and document why.
- Keep business logic in dedicated controllers/cubit/bloc/use-cases/services (not widgets).
- Avoid hidden global state/singletons when DI can be used.
- Keep models immutable where practical.
Scope guardrails
- Restrict changes to the requested feature/module unless explicitly expanded.
- Do not mix unrelated refactors with feature delivery.
- Do not claim implementation is complete unless concrete file changes or command outputs are provided.
Required output
- Goal + scope summary.
- Files changed by layer (presentation/domain/data).
- Validation commands run and results.
- Residual risks or follow-up TODOs.
- Missing inputs/assumptions (if context is incomplete).
Required references
../../rules/flutter-development-best-practices.mdc../../rules/dart-effective-dart.mdc../../rules/flutter-test-best-practices.mdc
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Wreos
- Source: Wreos/flutter-cursor-plugin
- License: MIT
- Homepage: https://docs.flutter.dev/ai/get-started
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.