feature-route

A set of rules for tab-based navigation in a Flutter app, including a navigation shell, separate navigation history for each tab, back-button handling, and screen tracking.

In plain words
What is it for?
Use it when setting up iOS-style tabs, returning an active tab to its root, handling system back actions, keeping tab navigation separate, or adding Firebase and PostHog route tracking.
Why use it?
It shows which navigation pieces are already implemented so developers do not rebuild them. It also identifies features the package does not provide, such as deep links and tab badges.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/sampaio-tech/flutter-core-modules/feature-route
Clone the repo
git clone --depth 1 https://github.com/sampaio-tech/flutter-core-modules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,122 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01122
Opus 5 $0.00000 $0.00561
Sonnet 5 $0.00000 $0.00224
Haiku 4.5 $0.00000 $0.00112

Measured yesterday against content hash e2b8cbe5c71d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feature-route scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/feature-route.mdc · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature: Route — Rules

What Is Already Implemented — Check Before Building

Capability Status
iOS tab scaffold (CupertinoTabScaffold) ShellRouteWidget
Pop-to-root on active tab double-tap ✅ Built into ShellRouteWidget
System back handling PopScope in ShellRouteWidget
Per-tab isolated navigator CupertinoTabView per tab
Stable GlobalKey<NavigatorState> per tab navigatiorKeyProvider (family provider)
Analytics screen tracking (Firebase + PostHog) defaultNavigatorObservers()
Deep-link / go_router integration ❌ Not in package — implement in consuming app
Bottom tab badge / notification dot ❌ Not in package — extend NavigationTab
Custom tab bar beyond activeColor ❌ Uses CupertinoTabBar — only activeColor is configurable

Before building navigation infrastructure, verify whether ShellRouteWidget already covers the requirement.


Layer Structure

lib/src/features/route/
└── presentation/
    ├── utils/navigation_observers.dart     # defaultNavigatorObservers()
    └── widgets/shell_route_widget.dart     # ShellRouteWidget, NavigationTab, navigatiorKeyProvider

This feature is presentation-only — no domain or data layers.


Implementing a Tab

class HomeTab extends NavigationTab {
  const HomeTab() : super(
    name: 'home',          // unique string identifier
    icon: CupertinoIcons.house_fill,
    initialTab: true,      // only one tab should have initialTab: true
  );

  @override
  String label(BuildContext context) => AppLocalizations.of(context)!.home;

  @override
  Map<String, Widget Function(BuildContext)>? get routes => {
    '/': (context) => const HomeScreen(),
    '/detail': (context) => const DetailScreen(),
  };

  @override
  List<NavigatorObserver> navigatorObservers(BuildContext context) =>
      defaultNavigatorObservers(context); // always include for analytics
}

Rules for NavigationTab subclasses:

  • name must be unique across all tabs in the app
  • Only one tab per ShellRouteWidget should have initialTab: true
  • Always override navigatorObservers to return defaultNavigatorObservers(context) unless you have a specific reason not to track screen views

Read the full file on GitHub · 131 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 131 lines · 0 tokens per session scan A e2b8cbe5c71d

Subscribe to this mod's changes

feature-route is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,122 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.