flutter-directory-tree agent plugin

Teaches AI coding agents the flutter_directory_tree Flutter package: the exact 2.x API, the traps that compile but do nothing, and how to move a project from 1.x. It installs in Claude Code, Codex, and Google Antigravity from this repository.

The plugin contains skills only: markdown instructions, with no hooks, MCP servers, scripts, or network access.

Skills

An agent loads a skill when a request matches it. In Claude Code you can also call one directly, for example /flutter-directory-tree:use-flutter-directory-tree.

Install, update, and remove

Claude Code

In a session:

/plugin marketplace add omar-hanafy/flutter_directory_tree
/plugin install flutter-directory-tree@flutter-directory-tree-tools

Or from a shell:

claude plugin marketplace add omar-hanafy/flutter_directory_tree
claude plugin install flutter-directory-tree@flutter-directory-tree-tools

Run /reload-plugins or start a new session to load it.

• Update: claude plugin marketplace update flutter-directory-tree-tools, then claude plugin update flutter-directory-tree@flutter-directory-tree-tools. Claude Code leaves automatic updates off for third-party marketplaces; to turn them on, run /plugin, open Marketplaces, select flutter-directory-tree-tools, and choose Enable auto-update.
• Remove: claude plugin uninstall flutter-directory-tree@flutter-directory-tree-tools, or claude plugin marketplace remove flutter-directory-tree-tools to remove the marketplace and its plugin together.

Codex

codex plugin marketplace add omar-hanafy/flutter_directory_tree
codex plugin add flutter-directory-tree@flutter-directory-tree-tools

Start a new Codex session; an open session does not pick up new skills.

• Update: codex plugin marketplace upgrade flutter-directory-tree-tools refreshes the marketplace and the installed copy.
• Remove: codex plugin remove flutter-directory-tree@flutter-directory-tree-tools. To drop the marketplace as well, run codex plugin marketplace remove flutter-directory-tree-tools afterwards; on its own, that command leaves the plugin installed.

Where a Codex surface has no plugin support, its $skill-installer skill can install the folders under tooling/ai/flutter-directory-tree/skills/ directly.

Google Antigravity

agy plugin install https://github.com/omar-hanafy/flutter_directory_tree/tree/main/tooling/ai/flutter-directory-tree

The command installs the plugin into ~/.gemini/config/plugins/, which the agy CLI, the Antigravity IDE, and the desktop app all read. Start a new session to load it. Use the full URL above: the plugin lives in a subfolder, so the bare repository URL finds nothing to install.

• Update: run the same install command again; it replaces the installed copy. Antigravity has no third-party marketplace yet, so nothing updates on its own.
• Remove: agy plugin uninstall flutter-directory-tree.

Other agents

The plugin has an Agent Plugins 1.0 manifest (plugin.json), and each skill is a standard Agent Skills folder, so agents that read either format can load this folder directly. Only the three hosts above are tested.

Example prompts

• "Upgrade this project from flutter_directory_tree 1.0.0 to 2 and check the behavior changes that affect us."
• "Add an explorer pane with flutter_directory_tree: search, a context menu with Delete, and the open folders saved between launches."
• "Show my home folder in a lazily loaded tree on desktop with flutter_directory_tree."
• "Let the user pick several folders with flutter_directory_tree and handle cancel."

Permissions and trust

The skills tell the agent to run ordinary Flutter tooling in your project, such as flutter pub get, dart fix --dry-run, flutter analyze, flutter test, and grep, through your agent's usual approval prompts. The plugin itself runs nothing and sends nothing anywhere.

Compatibility

• Documents flutter_directory_tree 2.x; the plugin version always equals the package version it documents. The migration skill covers projects on 1.x.
• Installation is tested with Claude Code 2.1.312, Codex 0.165.0, and the Antigravity CLI 1.4.9 (October 2026). A weekly CI job repeats the test with each host's current release.

For maintainers

tooling/ai/flutter-directory-tree/
  plugin.json                  Agent Plugins 1.0 manifest: Codex, Antigravity, other clients
  .claude-plugin/plugin.json   Claude Code manifest
  .codex-plugin/plugin.json    legacy manifest for Codex releases before Agent Plugins
  assets/icon.png              icon for all three manifests
  skills/<skill>/SKILL.md      one folder per skill
  evals/<case>/                cases for claude plugin eval

The marketplace catalogs live at the repository root: .claude-plugin/marketplace.json for Claude Code and .agents/plugins/marketplace.json for Codex. Antigravity installs the plugin folder itself.

Rules:

• The three manifests share their metadata, and their version equals the pubspec.yaml version; bump them together.
• Codex reads its interface (display name, prompts, icons) from extensions["com.openai"].interface in plugin.json, and older releases read the legacy manifest's interface; keep the two identical.
• Skill facts must match the source. Change a skill in the same pull request as the behavior it describes; test/agent_skill_claims_test.dart compiles every 2.x Dart block of the skills, checks that every API name they mention in inline code or in any other fenced block exists (or is a removed 1.x name, which the use skill may name only as a wrong guess), and asserts their behavioral claims.
• The plugin stays instructions only: tool/validate_agent_plugin.dart allows only the manifests' metadata fields and the manifests, this README, the icon, and Markdown skills and eval cases as files.
• A breaking package release ships its migration hop, as a new migrate-flutter-directory-tree-vX-to-vY skill, before it is tagged.

Checks, run from the repository root:

The host check uses throwaway profiles, so it never touches your own Claude Code, Codex, or Antigravity setup and needs no sign-in. Without --require, it skips any host that is not on PATH.

Keeping it current

Hosts and their plugin formats change every few weeks. When the weekly Agent plugin workflow fails, and before each package release:

1. Read what changed in each host since the versions listed under Compatibility (agy changelog prints Antigravity's notes), and check agent-plugins.org and agentskills.io for new spec versions.
2. Run the checks above, and claude plugin details flutter-directory-tree@flutter-directory-tree-tools after a local install to see the always-on token cost.
3. Run the eval suite and compare it with the last run: the four package cases should pass with the plugin and score higher than without it, and the unrelated case must never load a package skill.
4. Update the tested versions under Compatibility and in the package README.