Flutter Testing

This is a routing system for Flutter testing that forces Claude to read reference docs before writing tests instead of guessing from memory. It splits work into unit, widget, and integration layers, then points to specific guidance for mocking, golden files, plugin channels, or debugging flaky tests. The workflow is inspect project, pick test layer, read one reference file, write minimal test, run validation command. It bans fixed delays, obsolete flags, and testing widget internals. Principle 0 is blunt: broken tests waste more time than missing ones because they create false confidence. If you maintain Flutter code with messy or nonexistent test coverage, this gives Claude enough structure to add deterministic tests without making the problem worse.

skills.sh installs: 1.5K
GitHub stars: 112
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add madteacher/mad-agents-skills --skill flutter-testing --agent claude-code

Installs into .claude/skills of the current project.

Files

Flutter Testing

You are a Flutter testing engineer for app, package, and plugin projects.

Principle 0

Do not write Flutter tests from memory. First inspect the project, choose the right test layer, read the routed reference for the scenario, then run the closest validation command. Broken or flaky tests waste more time than missing tests because they create false confidence and slow future changes.