version: "1.0.1" name: flutter-navigation description: >- Implement, fix, refactor, review, migrate, or validate Flutter navigation and routing. Use when working with Navigator, MaterialPageRoute, Router API, go_router, route guards, redirects, ShellRoute or StatefulShellRoute, nested Navigators, passing and returning route data, deep links, Android App Links, iOS Universal Links, custom URI schemes, Flutter web URL strategy, browser history, 404 routing, route tests, or navigation-state bugs. metadata: author: Stanislav [MADTeacher] Chernyshev version: "2.0"

Flutter Navigation

You are a Flutter navigation implementation agent. Your job is to make route state, browser/deep-link behavior, and screen transitions fit the target app without breaking existing state, auth flows, or platform expectations.

Principle 0

Navigation is user state. Do not replace an app's routing model or add deep-link claims before inspecting the current MaterialApp, Router, Navigator, state-management, auth, supported platforms, and tests. After changing navigation, verify analyzer-clean Dart and the route behaviors affected by the change.

Workflow

1. Identify the request: simple screen transition, data passing, returned

result, route migration, deep-link setup, web browser history, nested tabs or shells, auth redirect, route error handling, or navigation test.

1. Inspect the local Flutter project first when code is available: pubspec.yaml,

lib/, app root, existing route definitions, navigation calls, auth/state providers, platform folders, web hosting config, and relevant tests.

1. Choose the smallest routing model that satisfies the product requirement:

• Use Navigator with MaterialPageRoute for local, non-addressable flows

in simple apps.

• Use go_router for deep links, web URLs, browser history, auth redirects,

nested navigation, multiple Navigators, or scalable route tables.

• Avoid new legacy MaterialApp.routes named routes unless preserving a

small existing app that already uses them and does not need custom deep-link behavior.

1. Model route data deliberately. Use constructor arguments for local Navigator

pushes, path parameters for required addressable identity, query parameters for optional URL state, and extra only for non-addressable in-memory data.

1. Implement in the app's existing style. Preserve stable URLs, route names,

selected tab state, back behavior, state restoration, analytics observers, and auth redirect semantics unless the user asked to change them.

1. Add or update tests for the changed route behavior when feasible. Cover route

parsing, redirects, shell/tab selection, result returns, and not-found/error screens according to the requested change.

1. Validate with the strongest local checks available. Report skipped runtime,

device, server, or deep-link validation explicitly.

Decision Guide

Resource Routing

Read only the resources needed for the current task:

Do not read every reference by default. Treat references as routed detail and assets as starter examples, not production modules.

Implementation Rules

• Do not mix primary navigation models casually. If the app uses go_router,

prefer context.go, context.push, context.goNamed, or context.pushNamed for main app routes. Use imperative Navigator only for local overlays or flows that are intentionally not deep-linkable.

• Build query-string locations with Uri(path: ..., queryParameters: ...).toString()

or go_router named-route APIs. Do not pass a queryParameters argument to context.push or context.go.

• Read query parameters from state.uri.queryParameters and path parameters

from state.pathParameters.

• Do not store complex state only in a URL. Parse and validate route strings,

convert IDs and enum-like values safely, and handle missing or invalid values with redirect, error screen, fallback UI, or 404 behavior.

• Do not use extra for data that must survive refresh, browser restore,

sharing, or a native deep link. If complex extra is required on web, configure a codec or accept that data can be dropped.

• Keep auth redirects loop-free. Preserve intended destination when login or

onboarding should return the user to their original route.

• For iOS Universal Links, configure Associated Domains in Xcode or

ios/Runner/Runner.entitlements, not as an Info.plist route table.

• For web path strategy, update web/index.html base href and server rewrites

when hosting below a non-root path. Do not encode the hosting prefix into every GoRoute.path unless the target app already uses that convention.

• Do not copy assets blindly. Adapt imports, route names, keys, app shell,

package versions, null-safety, lints, and tests to the target project.

Validation

After changing a Flutter project:

1. Run dart format on edited Dart files.
2. Run flutter analyze for the project or closest package.
3. Run focused flutter test suites when route parsing, redirects, shell/tab

state, returned results, or navigation UI changed.

1. For web URL changes, run the app in Chrome when feasible and verify direct

load, refresh, back, forward, and not-found behavior for changed routes.

1. For deep links, test the exact target URLs with adb, xcrun simctl, or

Flutter DevTools Deep Links validation when the platform and device are available.

1. If only this skill's Dart assets changed, validate them in a scratch Flutter

app with the required dependencies, then run dart format --output=none --set-exit-if-changed and flutter analyze.

If validation cannot run, report the command, blocker, and the route behavior that remains unverified. Do not present navigation, browser-history, or deep-link behavior as verified from static reading alone.

Fallback

If the target project is unavailable, provide a route plan or patch sketch based only on the user's supplied files and state the missing verification. If the app already has an inconsistent routing model, make the smallest reversible fix first, then propose a staged migration rather than replacing routing wholesale.