flutter-navigation

SKILL.md

Navigate Flutter apps across mobile and web with Navigator API or go_router, including deep linking and browser history.

Choose Navigator API for simple apps without deep linking; use go_router for production apps requiring deep links, browser history support, and URL-based navigation across platforms

Pass data between screens via constructor arguments (Navigator) or URL query parameters (go_router); return data using Future-based pop with typed results

Configure deep linking through platform-specific files (AndroidManifest.xml, Info.plist) and choose web URL strategy (hash-based or path-based with server configuration)

Avoid named routes due to Flutter team recommendations; instead use imperative Navigator methods or declarative go_router navigation (go, push, pop)

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