flutter/devtools · Archived
Guidelines and step-by-step workflow for debugging DevTools extensions locally, including stub mode, fixed-port launching, browser auto-opening, URL query parameters, target app connection, and human-in-the-loop interaction.
npx skills add flutter/devtools --skill debugging-devtools-extensions
This repository is archived — consider an actively maintained alternative.
Adds user-facing change descriptions to DevTools release notes. Use when documenting improvemen…
17 installsUse when documenting changes in CHANGELOG.md files for devtools_shared, devtools_app_shared, or…
17 installsAdds copyright headers to files based on file type. Use when creating new files or when asked t…
16 installsGuides updating dependency versions in published packages to avoid mono-repo resolution failure…
15 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsOther skills from flutter/devtools.
npx skills add flutter/devtools
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
master
Files included with this skill beyond the listing page.
SKILL.md
3,355 B
SUMMARY.md
320 B
Follow this workflow to test and debug DevTools extensions locally.
When running DevTools in standalone web mode (flutter run -d chrome), DevTools does not run the devtools_server backend by default. To test extensions without a running server backend:
packages/devtoolsapp/lib/src/shared/developmenthelpers.dart](file:///Users/ryjohn/code/github/flutter/devtools/packages/devtoolsapp/lib/src/shared/developmenthelpers.dart#L57).const _debugDevToolsExtensions = true;.[!WARNING]
Never commitdebugDevToolsExtensions = true;to git. A repository unit test (developmenthelpers_test.dart) enforces that this flag remainsfalse.
Activating stub mode registers the following mock extensions:
foo_ext (package:foo)bar_ext (package:bar)provider_ext (package:provider)The agent can automate running DevTools AND launching the browser directly to the target URL:
In packages/devtools_app, launch DevTools specifying a fixed --web-port:
flutter run -d chrome --web-port=52941Use the system OS open command to launch Chrome/browser directly to the desired test URL:
open "http://localhost:52941/foo_ext?embedMode=one";xdg-open "http://localhost:52941/foo_ext?embedMode=one";start "http://localhost:52941/foo_ext?embedMode=one";To test against real pub package extensions:
packages/devtoolsextensions/example/appthatusesfoo:``bash cd packages/devtoolsextensions/example/appthatusesfoo flutter run -d chrome ``
ws://127.0.0.1:8181/xxx=/ws).uri parameter using the appropriate OS command (as described in Step 2b):- macOS: open "http://localhost:52941/fooext?embedMode=one&uri=<VMSERVICEURI>" - Linux: xdg-open "http://localhost:52941/fooext?embedMode=one&uri=<VMSERVICEURI>" - Windows: start "http://localhost:52941/fooext?embedMode=one&uri=<VMSERVICE_URI>"
When an AI agent is performing this workflow:
ask_question or a direct prompt).open, xdg-open, or start as described in Step 2b) to launch the browser automatically.