flutter-control-and-screenshot
Guide on how to control a Flutter app using flutter_driver via MCP and capture screenshots.
What this skill does
# Flutter Driver Control & Screenshot
This skill outlines the process of adding `flutter_driver` support to a Flutter application, launching it via the Dart MCP server, controlling it (tapping, finding widgets), and capturing screenshots (handling Web/Desktop specific constraints).
## Prerequisites
1. **Dart MCP Server**: Ensure the `dart-mcp-server` is active.
2. **Flutter Project**: You need a working Flutter project.
## Step 1: Add Dependency
Add `flutter_driver` to the `dev_dependencies` in your `pubspec.yaml`.
```yaml
dev_dependencies:
flutter_driver:
sdk: flutter
```
Run `dart pub get` or use the `mcp_dart-mcp-server_pub` tool.
## Step 2: Create Driver Entry Point
Create a separate entry point, typically `test_driver/app.dart`, to enable the driver extension without polluting `main.dart`.
> [!IMPORTANT]
> Replace `your_app_package_name` with the actual name of your package as defined in `pubspec.yaml`.
```dart
// test_driver/app.dart
import 'package:flutter_driver/driver_extension.dart';
import 'package:your_app_package_name/main.dart' as app; // Import your main app
void main() {
// Enable the extension
enableFlutterDriverExtension();
// Run the app
app.main();
}
```
## Step 3: Launch App via MCP
Use the `mcp_dart-mcp-server_launch_app` tool.
- `target`: `test_driver/app.dart`
- `device`: `chrome` (or `macos`, `linux`, `windows`)
- `root`: Absolute path to your project root.
**Note**: The tool returns a **DTD URI** (Data Tooling Daemon) and a PID. Save these.
## Step 4: Connect to DTD
Use `mcp_dart-mcp-server_connect_dart_tooling_daemon` with the URI returned from the launch step.
```json
{
"uri": "ws://127.0.0.1:..."
}
```
## Step 5: Web Screenshot Strategy (Browser Subagent)
If running on **Web (Chrome)**, `flutter_driver`'s screenshot command may not work or may not be supported directly in all environments. A robust fallback is to use the `browser_subagent`.
1. **Get App URL**: Use `mcp_dart-mcp-server_get_app_logs` with the app's PID. Look for lines like `A Dart VM Service on Chrome is available at: http://127.0.0.1:XXXXX`. The app logs usually contain the local HTTP URL.
2. **Navigate & Snapshot**: Call `browser_subagent`.
- **Task**: "Navigate to [URL]. Wait for render. Take a screenshot."
## Step 6: Control the App (Flutter Driver)
Use `mcp_dart-mcp-server_flutter_driver` to interact with the app.
- **Get Widget Tree**: `mcp_dart-mcp-server_get_widget_tree` (useful to find keys/labels).
- **Tap**:
```json
{
"command": "tap",
"finderType": "ByText",
"text": "Settings"
}
```
- **Scroll**, **Enter Text**, etc. are also available.
## Step 7: Cleanup
Always stop the app when done to free up ports and resources.
- Use `mcp_dart-mcp-server_stop_app` with the PID.
## Example Workflow
1. **Launch** `test_driver/app.dart`.
2. **Connect** DTD.
3. **Log Check**: Find localhost URL.
4. **Browser Subagent**: Navigate & Screenshot (Home/Dashboard).
5. **Flutter Driver**: Tap "Tasks" tab.
6. **Browser Subagent**: Screenshot (Tasks).
7. **Flutter Driver**: Tap "Settings" tab.
8. **Browser Subagent**: Screenshot (Settings).
9. **Stop App**.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.