implementing▌

Use the steps below to plan or implement a new mode. A mode is a way to manage the context of the agent and inject tools, prompts, and mode-related behavior relevant to a product, use case, JTBD, etc. The agent has the switch_mode tool that allows it to switch itself to another mode, which might change tools, prompt, and executables, preserving the current context. Some previously created tools are contextual, meaning they're injected on particular pages of the frontend. The modes change the app

Imperative and declarative routing patterns for Flutter screen transitions and deep linking. \n \n Covers both Navigator (imperative, stack-based) and Router (declarative, URL-synchronized) approaches with guidance on when to use each \n Supports deep linking on iOS, Android, and Web; includes data passing via constructors, route arguments, and return values \n Implements nested navigation for multi-step flows (e.g., setup wizards) with independent sub-navigators and back-button interception \n