Flutter Feature Delivery

Goal

Ship Flutter features quickly with low risk by using thin vertical slices, explicit state boundaries, and focused verification.

Trigger Conditions

Use this skill when requests involve:

• New Flutter screen/feature
• Widget tree refactor for maintainability
• State management wiring (Bloc/Provider/Riverpod/Notifier)
• Feature implementation from design/spec/Figma
• Domain/repository/data boundary setup

Standard Workflow

1. Clarify target behavior

• Define user-visible outcome and acceptance checks.
• Identify feature folder/module and dependencies.

2. Respect architecture boundaries

• Presentation/widgets -> state/application -> domain -> data/infrastructure.
• Keep IO/network concerns in repositories/services.

3. Plan thin slices

• Slice 1: screen skeleton and route entry.
• Slice 2: visual layout and reusable widgets.
• Slice 3: state model and rendering states.
• Slice 4: interactions and side effects.
• Slice 5: repository wiring + verification.

4. Implement with minimal scope

• Break long build() methods into cohesive widgets.
• Keep business rules out of widgets.
• Keep each patch focused and reversible.

5. Verify before done

• Run targeted tests for touched logic/state.
• Run app and validate one happy path + one edge path.
• Confirm no unrelated files changed.

Flutter Rules

• Prefer explicit immutable state models.
• Keep async errors/loading handled in state layer.
• Avoid hidden side effects in widgets.

Output Contract

Always return:

1. Selected skills (1 line)
2. Slice plan (3-5 steps)
3. Exact files to edit
4. Verification commands/checks
5. Short completion summary with residual risks

Guardrails

• No broad folder/module rewrites unless requested.
• No package upgrades unless requested.
• No speculative architecture changes without evidence.