go_router_modular

Best practices and project structure for the go_router_modular Flutter package. Use this whenever you scaffold or edit a go_router_modular app — creating a feature's routes, adding a ChildRoute or ModuleRoute, registering a Module's binds/imports, writing navigation code (go/push), setting up main.dart / AppModule / AppWidget, wiring debug logs, or building bottom navigation / tabs / shell layouts (StatefulShellModularRoute, ShellModularRoute) — even if the user doesn't explicitly ask for "best practices". It enforces the project convention — the lib/src/modules/<feature>/ layout, a feature route file per feature, named-only navigation, name on every ChildRoute, synchronous modules with binds via the `..` cascade, Modular.configure logs gated on kDebugMode, and shell routes only for specific cases (tabs with preserved state, or persistent chrome).

Conventions for the event system of the go_router_modular Flutter package — decoupled cross-module communication via EventModule, ModularEvent, and ModularEventMixin. Use this whenever you need modules or widgets to react to something without a direct reference (e.g. "show a snackbar from another module", "notify the cart when an order is placed", "broadcast a login event", emit/listen events, fire/on, EventModule listeners). It is an optional add-on to the go-router-modular skill and assumes its conventions.