@bdayadev/flutter-ultra-mcp 0.0.0 → 1.0.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,23 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "flutter-ultra-mcp",
+  "description": "The ultimate Flutter MCP plugin — 8 specialized servers, 214 tools, cross-platform automation for Claude Code",
+  "owner": {
+    "name": "Bdaya-Dev",
+    "email": "ahmednfwela@digrum.com"
+  },
+  "plugins": [
+    {
+      "name": "flutter",
+      "description": "Durable cross-platform Flutter automation via 8 specialized MCP servers, in-app mixin binding, and an optional DevTools panel. Replaces marionette_mcp and the official dart mcp-server for Claude Code.",
+      "version": "0.0.1",
+      "author": {
+        "name": "Bdaya-Dev",
+        "url": "https://github.com/Bdaya-Dev"
+      },
+      "repository": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
+      "homepage": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
+      "license": "Apache-2.0"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -1,14 +1,14 @@
-{
-  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
-  "name": "flutter",
-  "version": "0.1.0",
-  "description": "Durable cross-platform Flutter automation via 8 specialized MCP servers, in-app mixin binding, and an optional DevTools panel. Replaces marionette_mcp and the official dart mcp-server for Claude Code.",
-  "author": {
-    "name": "Bdaya-Dev",
-    "url": "https://github.com/Bdaya-Dev"
-  },
-  "homepage": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
-  "repository": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
-  "license": "Apache-2.0",
-  "keywords": ["flutter", "dart", "mcp", "automation", "testing", "devtools", "claude-code"]
-}
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "flutter",
+  "version": "0.1.0",
+  "description": "Durable cross-platform Flutter automation via 8 specialized MCP servers, in-app mixin binding, and an optional DevTools panel. Replaces marionette_mcp and the official dart mcp-server for Claude Code.",
+  "author": {
+    "name": "Bdaya-Dev",
+    "url": "https://github.com/Bdaya-Dev"
+  },
+  "homepage": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
+  "repository": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
+  "license": "Apache-2.0",
+  "keywords": ["flutter", "dart", "mcp", "automation", "testing", "devtools", "claude-code"]
+}

package/.mcp.json

@@ -1,67 +1,67 @@
-{
-  "mcpServers": {
-    "flutter-ultra-build": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-build/dist/index.js"],
-      "env": {
-        "FLUTTER_ULTRA_DATA": "${CLAUDE_PLUGIN_DATA}"
-      }
-    },
-    "flutter-ultra-runtime": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-runtime/dist/bin.js"],
-      "env": {
-        "FLUTTER_ULTRA_DATA": "${CLAUDE_PLUGIN_DATA}",
-        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
-      }
-    },
-    "flutter-ultra-gesture": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-gesture/dist/bin.js"],
-      "env": {
-        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
-      }
-    },
-    "flutter-ultra-browser": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-browser/dist/bin.js"],
-      "env": {
-        "PLAYWRIGHT_BROWSERS_PATH": "${CLAUDE_PLUGIN_DATA}/browsers",
-        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
-      }
-    },
-    "flutter-ultra-native-mobile": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-native-mobile/dist/bin.js"],
-      "env": {
-        "FLUTTER_ULTRA_GO_IOS_BIN": "${CLAUDE_PLUGIN_ROOT}/sidecars/go-ios",
-        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
-      }
-    },
-    "flutter-ultra-native-desktop": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-native-desktop/dist/bin.js"],
-      "env": {
-        "FLUTTER_ULTRA_MAC_HELPER": "${CLAUDE_PLUGIN_ROOT}/sidecars/mac-helper/flutter-ultra-mac",
-        "FLUTTER_ULTRA_LINUX_HELPER": "${CLAUDE_PLUGIN_ROOT}/sidecars/linux-helper/at-spi-bridge.py",
-        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
-      }
-    },
-    "flutter-ultra-devtools": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-devtools/dist/index.js"],
-      "env": {
-        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
-      }
-    },
-    "flutter-ultra-patrol": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-patrol/dist/bin.js"],
-      "env": {
-        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state",
-        "FLUTTER_ULTRA_PATROL_FORK": "${CLAUDE_PLUGIN_ROOT}/vendor/patrol",
-        "PATROL_WEB_BROWSER_ARGS": "--enable-unsafe-swiftshader,--disable-renderer-backgrounding,--disable-background-timer-throttling"
-      }
-    }
-  }
-}
+{
+  "mcpServers": {
+    "flutter-ultra-build": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-build/dist/index.js"],
+      "env": {
+        "FLUTTER_ULTRA_DATA": "${CLAUDE_PLUGIN_DATA}"
+      }
+    },
+    "flutter-ultra-runtime": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-runtime/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_DATA": "${CLAUDE_PLUGIN_DATA}",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-gesture": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-gesture/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-browser": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-browser/dist/bin.js"],
+      "env": {
+        "PLAYWRIGHT_BROWSERS_PATH": "${CLAUDE_PLUGIN_DATA}/browsers",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-native-mobile": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-native-mobile/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_GO_IOS_BIN": "${CLAUDE_PLUGIN_ROOT}/sidecars/go-ios",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-native-desktop": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-native-desktop/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_MAC_HELPER": "${CLAUDE_PLUGIN_ROOT}/sidecars/mac-helper/flutter-ultra-mac",
+        "FLUTTER_ULTRA_LINUX_HELPER": "${CLAUDE_PLUGIN_ROOT}/sidecars/linux-helper/at-spi-bridge.py",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-devtools": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-devtools/dist/index.js"],
+      "env": {
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-patrol": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-patrol/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state",
+        "FLUTTER_ULTRA_PATROL_FORK": "${CLAUDE_PLUGIN_ROOT}/vendor/patrol",
+        "PATROL_WEB_BROWSER_ARGS": "--enable-unsafe-swiftshader,--disable-renderer-backgrounding,--disable-background-timer-throttling"
+      }
+    }
+  }
+}

package/CODE_OF_CONDUCT.md

@@ -1,83 +1,83 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall community
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and sexual attention or advances of any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email address, without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at https://github.com/Bdaya-Dev/flutter-ultra-mcp/security/advisories/new. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at https://github.com/Bdaya-Dev/flutter-ultra-mcp/security/advisories/new. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -1,108 +1,108 @@
-# Contributing to flutter-ultra-mcp
-
-Thanks for considering a contribution! This guide covers everything you need to develop, test, and ship changes.
-
-## Prerequisites
-
-- **Node.js** 20 or 22 (LTS)
-- **Flutter** stable channel
-- **Dart** 3.5+
-- Git with submodule support
-- Platform-specific tooling for the server you're working on (e.g. Android SDK + `adb` for `flutter-ultra-native-mobile`)
-
-You do not need any Bdaya internal resources. This plugin is fully self-sufficient — a fresh clone, `npm install`, and `npm test` is enough.
-
-## Clone
-
-```bash
-git clone https://github.com/Bdaya-Dev/flutter-ultra-mcp.git
-cd flutter-ultra-mcp
-git submodule update --init --recursive
-npm install
-```
-
-## Repository layout
-
-```
-.claude-plugin/      Plugin manifest
-.mcp.json            Declares all 8 MCP servers
-packages/            8 MCP server packages + 3 Dart packages
-shared/              TS shared libs (vm-service-client, mcp-runtime, state-store, keyring)
-skills/              Claude Code skills (one folder per skill)
-hooks/               PreToolUse / SessionStart / Stop hook configs
-sidecars/            Bundled native helpers (signed/notarized in CI)
-vendor/              Plugin-owned dependencies (e.g. patrol fork submodule)
-scripts/             Cross-platform helper scripts referenced by hooks
-docs/                Architecture + contracts + platform matrix
-.github/workflows/   GitHub Actions CI (per §18.12 of plan)
-```
-
-## Conventional Commits — mandatory
-
-Every commit must follow [Conventional Commits 1.0](https://www.conventionalcommits.org/).
-
-```
-<type>(<scope>)?: <subject>
-```
-
-| Type                                                        | Effect on version | Example                                            |
-| ----------------------------------------------------------- | ----------------- | -------------------------------------------------- |
-| `feat`                                                      | minor bump        | `feat(gesture): add scroll_until_visible`          |
-| `fix`                                                       | patch bump        | `fix(runtime): handle DDS reconnect race`          |
-| `feat!` / `fix!` / `BREAKING CHANGE:` footer                | major bump        | `feat(api)!: rename screenshot to take_screenshot` |
-| `perf`                                                      | patch bump        | `perf(browser): cache Playwright contexts`         |
-| `refactor`, `docs`, `test`, `chore`, `build`, `ci`, `style` | no version change | `chore(deps): bump zod to 3.25`                    |
-
-`commitlint` runs as a `commit-msg` hook (installed by `husky`) and as a PR-blocking CI check.
-
-## Branches
-
-- **`main`** — production
-- **`next`** — pre-release (prerelease tag `next`)
-- **`alpha`** / **`beta`** — unstable channels
-
-## Adding a new MCP server
-
-1. Copy the layout of an existing `packages/flutter-ultra-*/` package
-2. Add an entry to `.mcp.json` at the repo root
-3. Add a `tsconfig.json` project reference in the root `tsconfig.json`
-4. Implement tools using `@flutter-ultra/mcp-runtime` scaffolding
-5. Add unit + integration tests under `packages/<name>/tests/`
-6. Update `skills/` for any user-facing workflows
-
-## Adding a new skill
-
-Skills are markdown files at `skills/<name>/SKILL.md`. Follow the conventions in plan §16.8.
-
-## Local testing
-
-```bash
-# Build all packages
-npm run build
-
-# Run all unit + integration tests
-npm test
-
-# Run a single package's tests
-npm test --workspace=@flutter-ultra/runtime
-
-# Lint + format
-npm run lint
-npm run format
-```
-
-Use `npx @modelcontextprotocol/inspector --cli node packages/<name>/dist/index.js --method tools/list` to smoke-test a built server.
-
-## Pull requests
-
-1. Add a [changeset](https://github.com/changesets/changesets): `npm run changeset`
-2. All CI gates must pass (lint, unit, integration, contract, coverage thresholds, MCP Inspector smoke).
-3. Squash-merge with a Conventional Commits subject. Reviewers will preserve the conventional commit by editing the merge subject if needed.
-
-## Code of Conduct
-
-This project adopts the [Contributor Covenant 2.1](CODE_OF_CONDUCT.md). By participating you agree to abide by its terms.
-
-## License
-
-Contributions are licensed under Apache-2.0 (see [LICENSE](LICENSE)).
+# Contributing to flutter-ultra-mcp
+
+Thanks for considering a contribution! This guide covers everything you need to develop, test, and ship changes.
+
+## Prerequisites
+
+- **Node.js** 20 or 22 (LTS)
+- **Flutter** stable channel
+- **Dart** 3.5+
+- Git with submodule support
+- Platform-specific tooling for the server you're working on (e.g. Android SDK + `adb` for `flutter-ultra-native-mobile`)
+
+You do not need any Bdaya internal resources. This plugin is fully self-sufficient — a fresh clone, `npm install`, and `npm test` is enough.
+
+## Clone
+
+```bash
+git clone https://github.com/Bdaya-Dev/flutter-ultra-mcp.git
+cd flutter-ultra-mcp
+git submodule update --init --recursive
+npm install
+```
+
+## Repository layout
+
+```
+.claude-plugin/      Plugin manifest
+.mcp.json            Declares all 8 MCP servers
+packages/            8 MCP server packages + 3 Dart packages
+shared/              TS shared libs (vm-service-client, mcp-runtime, state-store, keyring)
+skills/              Claude Code skills (one folder per skill)
+hooks/               PreToolUse / SessionStart / Stop hook configs
+sidecars/            Bundled native helpers (signed/notarized in CI)
+vendor/              Plugin-owned dependencies (e.g. patrol fork submodule)
+scripts/             Cross-platform helper scripts referenced by hooks
+docs/                Architecture + contracts + platform matrix
+.github/workflows/   GitHub Actions CI (per §18.12 of plan)
+```
+
+## Conventional Commits — mandatory
+
+Every commit must follow [Conventional Commits 1.0](https://www.conventionalcommits.org/).
+
+```
+<type>(<scope>)?: <subject>
+```
+
+| Type                                                        | Effect on version | Example                                            |
+| ----------------------------------------------------------- | ----------------- | -------------------------------------------------- |
+| `feat`                                                      | minor bump        | `feat(gesture): add scroll_until_visible`          |
+| `fix`                                                       | patch bump        | `fix(runtime): handle DDS reconnect race`          |
+| `feat!` / `fix!` / `BREAKING CHANGE:` footer                | major bump        | `feat(api)!: rename screenshot to take_screenshot` |
+| `perf`                                                      | patch bump        | `perf(browser): cache Playwright contexts`         |
+| `refactor`, `docs`, `test`, `chore`, `build`, `ci`, `style` | no version change | `chore(deps): bump zod to 3.25`                    |
+
+`commitlint` runs as a `commit-msg` hook (installed by `husky`) and as a PR-blocking CI check.
+
+## Branches
+
+- **`main`** — production
+- **`next`** — pre-release (prerelease tag `next`)
+- **`alpha`** / **`beta`** — unstable channels
+
+## Adding a new MCP server
+
+1. Copy the layout of an existing `packages/flutter-ultra-*/` package
+2. Add an entry to `.mcp.json` at the repo root
+3. Add a `tsconfig.json` project reference in the root `tsconfig.json`
+4. Implement tools using `@flutter-ultra/mcp-runtime` scaffolding
+5. Add unit + integration tests under `packages/<name>/tests/`
+6. Update `skills/` for any user-facing workflows
+
+## Adding a new skill
+
+Skills are markdown files at `skills/<name>/SKILL.md`. Follow the conventions in plan §16.8.
+
+## Local testing
+
+```bash
+# Build all packages
+npm run build
+
+# Run all unit + integration tests
+npm test
+
+# Run a single package's tests
+npm test --workspace=@flutter-ultra/runtime
+
+# Lint + format
+npm run lint
+npm run format
+```
+
+Use `npx @modelcontextprotocol/inspector --cli node packages/<name>/dist/index.js --method tools/list` to smoke-test a built server.
+
+## Pull requests
+
+1. Add a [changeset](https://github.com/changesets/changesets): `npm run changeset`
+2. All CI gates must pass (lint, unit, integration, contract, coverage thresholds, MCP Inspector smoke).
+3. Squash-merge with a Conventional Commits subject. Reviewers will preserve the conventional commit by editing the merge subject if needed.
+
+## Code of Conduct
+
+This project adopts the [Contributor Covenant 2.1](CODE_OF_CONDUCT.md). By participating you agree to abide by its terms.
+
+## License
+
+Contributions are licensed under Apache-2.0 (see [LICENSE](LICENSE)).