Install
$ agentstack add skill-musabekisakov-imj-flutter-design-engineer-flutter-implementation ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Flutter UI Implementation
Implement the approved experience inside the host project's conventions.
Before Editing
- Confirm the visual direction, behavior, state matrix, and acceptance criteria. If absent and choices are material, return to
$flutter-design. - Inspect neighboring screens, theme, routing, state management, generated code rules, test style, and current worktree changes.
- Read only the relevant references:
references/flutter-architecture.md,references/adaptive-layouts.md,references/navigation-and-input.md, andreferences/states-and-feedback.md.
Read references/connected-product-workflows.md when one surface combines multiple domains or data sources.
Implement
- Separate orchestration, domain state, and presentational widgets at boundaries that remain understandable in one file view.
- Prefer constraints and layout primitives over device-name checks or fixed coordinates.
- Reuse semantic theme roles and established components.
- Preserve callbacks, validation, analytics, navigation, persistence, and backend contracts.
- Implement all applicable loading, empty, partial, error, offline, disabled, destructive, and success states.
- Make focus, semantics, keyboard behavior, touch targets, text scaling, RTL, and reduced motion part of the implementation.
- Keep animations interruptible and avoid expensive work inside build/layout/paint paths.
- Preserve unrelated user changes in a dirty worktree.
Verify
- Run the project's formatter, analyzer, and relevant unit/widget/golden tests.
- Render representative compact and expanded layouts, supported themes, and critical states.
- Invoke
$flutter-accessibilityand$flutter-visual-qafor visually important work. - Refine material findings, then rerun affected checks.
Deliver
Lead with what changed for the user. List key files, behavior preserved, checks run, rendered combinations inspected, and remaining environmental limitations.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: musabekisakov-imj
- Source: musabekisakov-imj/flutter-design-engineer
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.