flutter-navigation
Skill16 starsChanged 2 months agoBSD-3-ClauseView on GitHub
Implement, review, or verify Flutter routing, deep-link destinations, back-stack behavior, nested navigation, restoration, redirects, and URL synchronization. Use for route correctness; pair with flutter-device-testing on a concrete runtime, and do not introduce a routing package by default.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- thienqo/flutter-skillsword for word, first seen Nov 1, 2026
- MADTeacher/mad-agents-skillstheir own version, first seen May 1, 2026
Other versions2 projects use a version of this.
Word for word · 1
- thienqo/flutter-skills★ 16100% same
Edited · 0
None found.
Wrote their own version · 1
- MADTeacher/mad-agents-skills★ 106same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dart-concurrencySkill
- dart-languageSkill
- flutter-accessibilitySkill
- flutter-ai-integrationSkill
- flutter-animationSkill
- flutter-app-workflowSkill
- flutter-architectureSkill
- flutter-authenticationSkill
- flutter-background-executionSkill
- flutter-build-releaseSkill
- flutter-ci-cdSkill
- flutter-code-reviewSkill
- flutter-dependency-upgradesSkill
- flutter-device-testingSkill
- flutter-figma-workflowSkill
- flutter-in-app-purchasesSkill
- flutter-localizationSkill
- flutter-mediaSkill
- flutter-networkingSkill
- flutter-notificationsSkill
- flutter-observabilitySkill
- flutter-openapi-clientSkill
- flutter-package-developmentSkill
- flutter-performanceSkill
- flutter-persistenceSkill
- flutter-platform-integrationSkill
- flutter-product-analyticsSkill
- flutter-responsive-layoutSkill
- flutter-runtime-debuggingSkill
- flutter-securitySkill
- flutter-state-managementSkill
- flutter-testingSkill
- flutter-text-renderingSkill
- flutter-ui-designSkill
- flutter-ui-patternsSkill
- flutter-visual-effectsSkill
- flutter-webviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Keep route names, path parameters, and argument decoding typed or centrally validated.
- Distinctive: line 19
Use nested navigation only for independent histories such as tab shells.
- Very specific: line 21
Keep navigation side effects outside widget build.
- Distinctive: line 22
Do not place large domain objects directly in URLs or restoration state.
- Distinctive: line 26
Test cold deep links, warm links, back/forward behavior, authentication redirects, invalid parameters, restoration where required, and each …
- Distinctive: line 30
When tab shell patterns or independent back histories are in scope, follow the nested shell navigation reference.
- Distinctive: line 31
When handling deep links or state restoration, follow the deep link and restoration reference.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flutter Navigation
Model navigation as application state when URLs, deep links, restoration, or multiple navigators require it; use simpler imperative navigation for genuinely local flows.
Inspect first
Identify the current router, route ownership, authentication flow, tab/shell structure, supported platforms, URL requirements, and state restoration expectations. Preserve the existing routing package unless migration is requested.
Rules
- Keep route names, path parameters, and argument decoding typed or centrally validated.
- Make redirect logic deterministic and free of redirect loops.
- Preserve intended back behavior across Android system back, browser history, iOS gestures, nested navigators, and modals.
- Use nested navigation only for independent histories such as tab shells.
- Parse deep links into domain-safe state and define behavior for unknown or unauthorized destinations.
- Keep navigation side effects outside widget
build. - Do not place large domain objects directly in URLs or restoration state.
Verification
Test cold deep links, warm links, back/forward behavior, authentication redirects, invalid parameters, restoration where required, and each supported shell/tab history.
References
When tab shell patterns or independent back histories are in scope, follow the nested shell navigation reference. When handling deep links or state restoration, follow the deep link and restoration reference.
Sources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.