Skip to content
Skills Library
Programming · Building & coding

flutter-feature

/flutter-feature

Adds or changes a feature, screen, form or list in an existing Flutter project by following the project's own conventions, then regenerates code and runs the analyzer. Use when asked to build, extend or modify app functionality; for bug fixes, refactors and upgrades use flutter-fix, and for plans or flows use flutter-plan.

Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
7
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Adds or changes a feature, screen, form or list in an existing Flutter project by following the project's own conventions, then regenerates code and runs the analyzer. Use when asked to build, extend or modify app functionality; for bug fixes, refactors and upgrades use flutter-fix, and for plans or flows use flutter-plan.

Original author description

Adds or changes a feature, screen, form or list in an existing Flutter project by following the project's own conventions, then regenerates code and runs the analyzer. Use when asked to build, extend or modify app functionality; for bug fixes, refactors and upgrades use flutter-fix, and for plans or flows use flutter-plan.

How it works

  1. Steps
  2. Watch for these (the usual causes of rework)
  3. References
Original SKILL.md headings · 35 lines, 892 words
SKILL.md preview
---
name: flutter-feature
description: Adds or changes a feature, screen, form or list in an existing Flutter project by following the project's own conventions, then regenerates code and runs the analyzer. Use when asked to build, extend or modify app functionality; for bug fixes, refactors and upgrades use flutter-fix, and for plans or flows use flutter-plan.
license: Apache-2.0
---

# Flutter feature

## Steps

1. **Load the project profile and the project's rules.** Read `AGENTS.md` fully (also `CLAUDE.md` and any rules folder the agent tool uses, such as `.cursor/rules` or `.claude/rules`). If there is no profile, run the `flutter-project-profile` skill first. Pick the rules that apply to this task (a short list, at most ten) and follow them. Where a project rule and this skill disagree, the project rule wins. Where a written rule and existing code disagree (for example an older feature that breaks the rule), do not quietly copy the existing code: follow the written rule if that is possible without changing code outside the task; if only the existing pattern fits (a shared contract or base class forces it), use it and record it as a rule conflict (step 6) with the file that forces it.
2. **Open the exemplar feature** named in the profile (if the request is to match a design or to design the look, use `flutter-design` for the visuals and this skill for the code) and the closest existing feature to this request. Plan the new files by mirroring it, layer by layer. For a change touching more than three files, or when the request is ambiguous, show the plan (file, purpose, one line each) and the assumptions before writing code. For a small, clear change, just do it. If the feature needs something outside the repo (Maps or Places keys, Firebase, social login, push, subscriptions or purchases), run the `flutter-service-setup` skill first and show its setup list with the plan.
3. **Reuse before creating.** Search for an existing status type, form field state, result type, validators, shared widgets, string table or localization keys. Use them. Do not introduce a second way of doing something the project already does.
4. **Implement in dependency order:** domain, data, state, cubit or bloc, page, dependency registration, route, strings. Keep business logic out of widgets.
5. **Generate and check.** Run code generation if you touched annotated files, then `flutter analyze` (with the `fvm` prefix when the version is pinned). Fix what the analyzer reports. Format only the files you created or changed (`dart format <files>`), because a project's CI often fails on unformatted code. Never edit generated files. If code generation or the full analyzer cannot run (missing generated files, missing environment values or secrets), do not work around it: do not recreate env files or recover old ones from git history (ask for the current files), and do not hand-write generated files. Analyze only the files you changed (`dart analyze <files>`) and say in the summary exactly what was not checked and why, plus the exact command the developer should run. `flutter analyze` runs `pub get` first, so when packages must not change use `flutter analyze --no-pub`; a private git dependency that cannot be cloned is also a reason to stop and report.
6. **Finish with a short summary:** files added and changed, assumptions made, and anything the developer must still do by hand (native configuration, backend changes, keys, store settings). Add a **Rule conflicts** line: `none`, or each place where your code departs from a written project rule or relies on a precedent that does, with the rule, the file, and why. Never leave a known departure unmentioned.

## Watch for these (the usual causes of rework)

- Using `BuildContext` after an `await` without checking `context.mounted`.
- Emitting state after a cubit or bloc is closed.
- A load or submit that can never leave the loading state because its error path is missing.
- One shared status for operations that run side by side (load list and delete item need their own).
- Controllers, focus nodes, timers or stream subscriptions that are never disposed or cancelled.
- User-visible text outside the project's string table or localization, or a plural built in code (`count == 1 ? '' : 's'`) instead of an ARB plural.
- A new package added without asking, or a new feature that needs Android or iOS configuration (permissions, manifest, `Info.plist`, entitlements) and does not say so.
- Business logic or data access called straight from a widget.
- A feature that adds API calls, token handling, paging, search or caches without reading the pitfalls list in the `flutter-review` skill (`api-auth-paging-pitfalls.md`, if that skill is installed) first (success codes, error mapping, one refresh at a time, caches cleared on sign-out, paging after cache hydration).

## References

- `references/bloc-freezed-recipe.md`: a complete feature slice for the Cubit, Freezed, injectable and auto_route stack.
- `references/bloc-plain-recipe.md`: a feature slice for `flutter_bloc` with Cubit or Bloc without Freezed or injectable (Equatable state, event transformers, `RepositoryProvider`).
- `references/riverpod-recipe.md`: a complete feature slice for Riverpod 3.
- `references/go-router-recipe.md`: go_router setup, `go` versus `push` (state lost when a screen is rebuilt), `StatefulShellRoute` tabs, redirects and sign-in, type-safe routes.
- `references/graphql-ferry-recipe.md`: Ferry (GraphQL) setup, code generation, repository mapping to `Result`, auth link and cache pitfalls; read it when the project uses Ferry or the feature adds GraphQL.
- `references/localization-recipe.md`: gen-l10n setup, ARB placeholders and plurals, right-to-left, Android and iOS native language settings, and per-language store listings; read it when the project or feature adds a language or user-visible text in an app that has localization.

Read the recipe that matches the project's stack only when the project has no suitable exemplar feature, or when asked to start a feature from scratch.
Files in this package (7)
  • SKILL.md 6 KB
  • references/bloc-freezed-recipe.md 3 KB
  • references/bloc-plain-recipe.md 8 KB
  • references/go-router-recipe.md 5 KB
  • references/graphql-ferry-recipe.md 8 KB
  • references/localization-recipe.md 9 KB
  • references/riverpod-recipe.md 5 KB

Versions

The database has no other skills named flutter-feature.

Database snapshot: 13.11.2026 · package version 2a0f0306dcb0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100flutter-fix
    Finds the root cause of a bug, crash, slowdown or size problem in a Flutter app and fixes it, refactors code without changing behaviour, or upgrades packages, Dart and Flutter (with FVM) one step at a time. Use when asked to debug, fix or investigate an error or crash, find why…
  • 100flutter-testing
    How to verify Flutter work - analyzer, unit, bloc/notifier, widget, and golden tests, using the project's existing test tooling. Use when fixing a bug, adding a feature that has testable logic, writing or repairing tests, or before claiming a Flutter task is done.
  • 100feature
    Build a new Flutter feature end to end in a feature-first, layered structure (domain, data, presentation) with Riverpod 3, loading/error/empty states and tests. Use when the user asks to add a screen, flow or feature to a Flutter app.
  • 100flutter-architecture
    Design, refactor, review, or implement Flutter app architecture using MVVM, layered UI/Data/optional Domain boundaries, feature-first or layer-first project structure, repositories, services, dependency injection, Result and Command patterns, offline-first or optimistic UI…
  • 100dart-n-flutter
    Instructions for writing Dart and Flutter code following the official recommendations. Triggers on: **/*.dart
  • 100flutter-senior-orchestration
    Use to run a Flutter feature or fix end to end — restoring cross-AI context (context/memory/), triaging architecture via PLAN.md, sequencing official flutter-*/dart-* how-to skills, and dispatching parallel or sequential subagents (flutter-architect, flutter-implementer,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.