tools/sage-claude-plugin/skills/flutter/SKILL.md
Flutter patterns — widget architecture, state management, Impeller renderer, platform-adaptive design
npx skillsauth add xoai/sage flutterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Layer 2 — Framework Pack
Flutter patterns for modern development (3.x+). Widget architecture, state management, Impeller renderer, platform-adaptive design, and the common mistakes agents make from outdated tutorials.
Flutter's "everything is a widget" model is simultaneously its greatest strength
and the main source of agent mistakes. Agents build monolithic widget trees with
thousands of lines, misuse setState for everything, nest widgets 15 levels
deep, and ignore the widget lifecycle. This pack establishes clean widget
architecture, proper state management selection, and Impeller-era performance
patterns.
| Type | Files | Coverage | |------|-------|----------| | Patterns | 7 | Widget architecture, state management, async/data, navigation, platform-adaptive, testing, performance | | Anti-patterns | 5 | God widgets, setState everywhere, ignoring dispose, hardcoded dimensions, unnecessary packages | | Constitution | 1 | 5 Flutter-specific principles | | Gate | 1 | Flutter pattern compliance check |
development
Branch-per-initiative git discipline for all delivery workflows. Defines branch naming by workflow, the propose-confirm creation protocol, dirty-tree and detached-HEAD handling, the always user-gated merge protocol, worktree support for parallel sessions, and abandonment cleanup. Activates only in git repositories — silently inactive everywhere else. Use when starting /build, /fix, /architect, or /build-x at Standard+ scope, when resuming an initiative, when offering a merge at a completion checkpoint, or when the user wants a second concurrent initiative.
development
Drives task-by-task execution from an approved plan with quality gates between each task. Reads the plan, finds the next incomplete task, dispatches implementation, validates, updates progress, and continues. Use after a plan is approved and the user says "go", "start building", "execute the plan", or "implement the feature".
testing
Preserves and restores context across agent sessions using plan file checkboxes as source of truth. Use when starting a new session, resuming previous work, ending a session, or when the user says "continue from last time", "what was I doing", or "save progress".
tools
Captures agent mistakes, corrections, and discovered gotchas so they are not repeated. Use when: (1) a command or operation fails unexpectedly, (2) the user corrects the agent, (3) the agent discovers non-obvious behavior through debugging, (4) an API or tool behaves differently than expected, (5) a better approach is found for a recurring task. Also searches past learnings before starting tasks to avoid known pitfalls. Activate alongside the sage-memory skill — they share the same MCP backend but serve different purposes (sage-memory = codebase knowledge, sage-self-learning = agent mistakes and gotchas).