thiennc-tesoglobal/flutter-skills
Focused Agent Skills for complete Flutter and Dart app delivery.
72
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
SKILL.mdskills/flutter-app-workflow/
- name:
- flutter-app-workflow
- description:
- Coordinate end-to-end delivery of a complete Flutter app or feature across UI, state, data, tests, and runtime verification. Use for broad vertical-slice ownership; not for data-only sync/cache, one screen or form, or contained work that merely touches multiple files or two domains.
Flutter App Workflow
Deliver a runnable, maintainable result with evidence. Preserve the user's product choices and existing conventions unless migration is explicitly requested.
Preflight
Read project preflight before planning. Treat supplied project facts as preflight evidence; inspect repository constraints (SDK, platforms, packages, architecture, tests, flavors, devices) instead of re-asking. Reuse adequate existing solutions; do not add packages merely for familiarity.
Route specialists
Load only the available specialists needed for the vertical slice:
- Architecture & state:
flutter-architecture,flutter-state-management - UI & visual:
flutter-ui-design,flutter-visual-effects, or matching UI specialist - Data, AI & product:
flutter-networking,flutter-persistence,flutter-authentication,flutter-in-app-purchases,flutter-product-analytics,flutter-ai-integration - Platform & ops:
flutter-package-development,flutter-notifications,flutter-background-execution,flutter-dependency-upgrades,flutter-observability,flutter-runtime-debugging - Language & security:
dart-language,dart-concurrency,flutter-security,flutter-code-review - Quality & delivery: testing, accessibility, performance, CI/CD, release, device specialists
If a specialist is unavailable, continue with this workflow's preflight and vertical-slice rules; do not claim it was loaded or silently install skills. Hand focused work (e.g. form validation, API cache) to dedicated specialists rather than running this workflow.
Deliver in vertical slices
- Define user-visible behavior and acceptance evidence.
- Choose the smallest architectural change fitting the existing project.
- Implement one coherent path through model, data, state, and UI.
- Add focused tests with the behavior, not after an unrelated rewrite.
- Run narrow checks after each slice and follow delivery verification.
Keep files cohesive and domain-oriented. Do not split files solely for line counts.
Stop conditions
Do not claim completion while required checks fail. If credentials, devices, or backends block verification, report what was verified and what remains blocked.
Sources
.tessl-plugin
skills
dart-concurrency
dart-language
flutter-accessibility
flutter-ai-integration
flutter-animation
flutter-app-workflow
flutter-architecture
flutter-authentication
flutter-background-execution
flutter-build-release
flutter-ci-cd
flutter-code-review
flutter-dependency-upgrades
flutter-device-testing
flutter-figma-workflow
flutter-in-app-purchases
flutter-localization
references
flutter-networking
references
flutter-notifications
flutter-observability
flutter-openapi-client
flutter-package-development
flutter-performance
flutter-persistence
references
flutter-platform-integration
flutter-product-analytics
flutter-responsive-layout
flutter-runtime-debugging
flutter-security
flutter-state-management
flutter-testing
flutter-ui-design
flutter-ui-patterns
flutter-visual-effects