flutteryard

Plugin flutteryard from marketplace flutteryard in KarimEbrahemAbdelaziz/FlutterYard. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• architecture

  Design or review the layering and module boundaries of a Flutter app — feature slices, data/domain/presentation separation, dependency direction, and package splits. Use when structuring a new app, adding a feature that crosses boundaries, reviewing whether the architecture still holds, or when impo

• code-review

  Review Flutter/Dart changes for correctness, rebuild cost, design-system compliance, accessibility, and test coverage — where every finding must be reproducible. Use when reviewing a diff, a PR, or a branch of Flutter code, or when asked to check work before merge.

• design-system

  Sync the project's live design tokens into .flutteryard/design-system.md — a Figma-variable-to-Dart-accessor map the agent uses instead of hardcoding colors, spacing, radii, or text styles. Use before building any widget from a design, when tokens are stale (>14 days), when the designer changed vari

• feature

  Scaffold a complete vertical feature slice in a Flutter app — data, domain, presentation, state, routing, stories, and tests — following the project's existing conventions. Use when adding a new feature or screen to an app, or when asked to set up the structure for one.

• figma-to-screen

  Build a complete Flutter screen from a Figma frame — decompose it into components, reuse what the design system already has, build only what is missing into the feature's presentation/widgets/, compose the screen, and verify it against the design. Use when asked to build or implement a screen or pag

• figma-to-widget

  Build a Flutter widget from a Figma design using the project's live design tokens, catalogue it in Widgetbook, and verify it against the design. Use when asked to implement a design, build a component from Figma, turn a design node/link into a widget, or match a screen to its mockup. Handles the ful

• golden-tests

  Write and maintain Flutter golden (visual regression) tests driven off Widgetbook stories, including accessibility matchers and CI determinism. Use when adding golden coverage, when goldens are failing or flaky, when goldens differ between machines and CI, or when deciding whether to regenerate them

• maestro

  Drive and verify a Flutter app on a real simulator/emulator via the Maestro MCP server — the mandatory Gate 3 surface for animations, gestures, transitions, and multi-screen flows. Use when verifying an interaction actually works on device, recording motion for review, authoring .maestro flows, or w

• motion-from-video

  Build a Flutter animation, transition, or interaction from a reference video (or Figma motion), then verify it on a real simulator via Maestro and iterate with the user until they approve. Use when given a video/screen-recording of an animation to replicate, when asked to build a transition, gesture

• onboard

  Profile a Flutter project and write .flutteryard/profile.md — detect state management, routing, DI, codegen, Widgetbook version, design tokens, test setup, and Maestro. Run this first in any Flutter repo, or when FlutterYard skills seem to be guessing about the project's conventions. Also use to ref

• perf-audit

  Diagnose and fix Flutter performance problems with measurements — jank, dropped frames, excessive rebuilds, slow scrolling, shader compilation stutter, memory growth, and startup time. Use when the app feels slow or janky, when a list scrolls poorly, when an animation stutters, or when asked to opti

• release

  Prepare and verify a Flutter release build for the App Store or Play Store — versioning, flavors, signing, obfuscation, size, and the pre-ship checklist. Use when cutting a release, building a release artifact, bumping a version, or checking whether a build is ready to ship.

• state-management

  Design and review Flutter state management — Riverpod, Bloc, or whatever the project already uses — including provider/bloc structure, rebuild scope, async state modelling, and testability. Use when adding state to a feature, when a widget rebuilds too much, when async loading/error states are handl

• test-strategy

  Decide what to test in a Flutter codebase and write those tests — unit, widget, golden, and integration — with the right balance and no redundancy. Use when adding test coverage, when asked how something should be tested, when tests are slow or flaky, or when coverage is low on code that matters.

• widget-craft

  Improve existing Flutter widget code — composition, const correctness, rebuild scope, directional layout, semantics, and removing hardcoded design values — while proving the refactor changed nothing visually. Use when asked to clean up, refactor, simplify, or optimise widget code, when a build metho

• widgetbook

  Author and verify Widgetbook stories/use-cases for Flutter widgets — the mandatory Gate 1 surface. Use when creating or changing any widget, when a widget needs a use-case or story, when setting up Widgetbook in a project, when wiring designLink to Figma, or when running golden and accessibility che

Subagents (7)

• flutter-architect

  Designs Flutter app structure — feature slices, layer boundaries, dependency direction, state management approach, and package splits — with a mechanical check for the boundaries it defines. Use when structuring a new app or feature, reviewing whether the architecture holds, or deciding on a package

• flutter-engineer

  Builds Flutter features end to end — data, domain, presentation, state, routing, and tests — following the project's existing conventions. Use for implementing a feature, adding a screen with logic, wiring a repository, or general Flutter build work that isn't purely visual or motion.

• flutter-motion-engineer

  Builds and verifies Flutter animations, transitions, gestures, and micro-interactions from a reference video or Figma motion — implementing them, then running and recording them on a real simulator via Maestro. Use for "build this animation", "replicate this transition", or "the motion feels off".

• flutter-perf-engineer

  Diagnoses and fixes Flutter performance problems with before/after measurements — jank, dropped frames, excessive rebuilds, slow lists, shader stutter, memory growth, startup time. Use when the app feels slow, a list scrolls poorly, an animation stutters, or an optimisation needs verifying.

• flutter-reviewer

  Independent reviewer for Flutter/Dart changes — correctness, rebuild cost, design-system compliance, accessibility, and verification gaps. Every finding must reproduce. Use to review a diff, PR, or branch before merge. Never used to review work the same session authored.

• flutter-test-engineer

  Writes and repairs Flutter tests — unit, widget, golden, and integration — at the cheapest level that catches the bug, plus Maestro flows for device-level behaviour. Use for adding coverage, fixing flaky or failing tests, or deciding how something should be tested.

• flutter-ui-engineer

  Builds Flutter widgets from designs — Figma nodes, mockups, or design-system specs — using project tokens, catalogued in Widgetbook, verified with goldens and accessibility matchers. Use for "implement this design", "build this component", or "make this screen match the mockup".

Hooks (8)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/block-generated-edit.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/dart-format-analyze.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/require-story-for-widget.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/widget-structure.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/observe-command.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-profile-check.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/stop-gate.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/widget-gate.sh

Similar plugins