flutter-interactive-design
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
Design and implement distinctive Flutter interfaces with responsive composition, reusable components, gesture-driven interaction, purposeful 2D animation, custom painting and shaders, and bounded interactive 3D experiences. Use when creating or redesigning Flutter screens, design systems, onboarding, visualizations, games, immersive product moments, microinteractions, navigation transitions, or accessible high-performance motion.
In this repository11 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- android-verifySkill
- app-store-listing-creatorSkill
- expo-android-performanceSkill
- expo-interactive-designSkill
- flutter-android-performanceSkill
- release-checkSkill
- reproduce-firstSkill
- seo-geo-optimizerSkill
- ship-smallSkill
- toris-flutter-play-store-releaseSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 16 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create an intentional product-specific visual system, then implement only the motion and 2D/3D technology that serves the interaction.
- Very specific: line 12
Read execution defaults and select execute, review, or plan.
- Distinctive: line 17
add purposeful 2D/3D interaction using the smallest capable technology plus reduced-motion and constrained-device fallbacks.
- Distinctive: line 23
Follow the user's explicit art direction.
- Distinctive: line 25
Do not add a package, shader, runtime, WebView/native integration, or asset pipeline without checking maintenance, license, platform …
- Distinctive: line 28
Read evidence and verification before claiming performance or usability outcomes.
- Distinctive: line 36
If the user asked for implementation but the visual direction is materially ambiguous, present two or three concise directions and obtain …
- Distinctive: line 56
Prefer a single orchestrated transition to scattered entrances.
- Distinctive: line 60
Read motion and 3D decisions.
- Distinctive: line 70
add gestures and state transitions.
- Distinctive: line 71
add the signature 2D/3D moment behind a stable interface.
- Distinctive: line 72
add reduced-motion, assistive-technology, loading, error, and low-performance fallbacks.
- Distinctive: line 74
test each slice before expanding.
- Distinctive: line 76
Keep widgets/components focused, state ownership explicit, and animation controllers/resources disposed.
- Distinctive: line 82
Remove one unnecessary decorative element or motion if the result feels overworked.
- Distinctive: line 86
Use a production-representative Flutter build and physical devices.
- Distinctive: line 88
Test reduced motion, screen reader/semantics, text scale, contrast, touch targets, keyboard/pointer where targeted, interruption, …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flutter Interactive Design
Create an intentional product-specific visual system, then implement only the motion and 2D/3D technology that serves the interaction. Treat accessibility, lifecycle, and frame performance as design constraints.
Quick start
Read execution defaults and select execute, review, or plan. In the default execute mode:
- inspect the Flutter project or brief, routes/state, existing visual system, dependencies, assets, target devices, and the screen's single job;
- state an intentional direction tied to the product; ask for a choice only when competing directions would materially change the result;
- implement one complete vertical slice with real content and all relevant states;
- add purposeful 2D/3D interaction using the smallest capable technology plus reduced-motion and constrained-device fallbacks;
- critique the rendered result and validate accessibility, lifecycle, and production-representative frame behavior.
Operating rules
- Inspect the product, audience, screen job, existing design system, Flutter version, routes/state architecture, dependencies, assets, target platforms, and device floor before designing.
- Follow the user's explicit art direction. Where it is open, derive choices from the product's subject and content rather than a reusable AI aesthetic.
- Spend visual boldness in one justified signature element; keep supporting UI disciplined.
- Do not add a package, shader, runtime, WebView/native integration, or asset pipeline without checking maintenance, license, platform support, build impact, and user authorization.
- Motion must explain hierarchy, causality, continuity, progress, manipulation, or meaningful delight. Remove motion that only decorates.
- Preserve unrelated changes and current project conventions.
- Read evidence and verification before claiming performance or usability outcomes.
Workflow
1. Ground the brief
State the product/feature, audience, one primary screen job, target devices/platforms, input methods, accessibility requirements, performance floor, content/data states, and desired emotional quality. Inventory existing colors, type, spacing, shapes, icons, imagery, motion, components, and brand constraints.
If the user asked for implementation but the visual direction is materially ambiguous, present two or three concise directions and obtain approval before making a strong aesthetic commitment.
2. Create an intentional design plan
Define:
- a named visual concept tied to the subject;
- four to six semantic colors with contrast intent;
- typography roles, scale, weight, line height, and fallback behavior;
- spacing, grid, breakpoints/adaptive behavior, shape, elevation/material, icon, and imagery rules;
- one signature interaction or visual element;
- a content hierarchy and plain-language interface vocabulary;
- loading, empty, error, success, disabled, offline, and permission states.
Sketch the composition in prose or a compact wireframe. Critique it against the brief: replace any choice that could be dropped unchanged into an unrelated app.
3. Model interaction and motion
For every animated interaction document trigger, user intent, start/end state, duration or physics, interruption/reversal, gesture ownership, focus/semantics behavior, reduced-motion alternative, low-performance fallback, and completion condition.
Prefer a single orchestrated transition to scattered entrances. Keep actions consistently named and make errors explain recovery.
4. Select the smallest capable technology
Read motion and 3D decisions. Start with Flutter SDK primitives. Move to custom paint, fragment shaders, authored animation runtimes, a maintained 2D engine, or bounded 3D only when the design requires it and the project supports it.
Inspect installed packages and current official/project documentation. Do not prescribe a remembered package or version as universally correct.
5. Implement in vertical slices
When authorized:
- establish tokens/theme and responsive scaffold;
- implement semantic static states with real content;
- add gestures and state transitions;
- add the signature 2D/3D moment behind a stable interface;
- add reduced-motion, assistive-technology, loading, error, and low-performance fallbacks;
- integrate navigation/lifecycle and cleanup;
- test each slice before expanding.
Keep widgets/components focused, state ownership explicit, and animation controllers/resources disposed. Do not restructure unrelated routes or state management merely to fit an effect.
6. Critique visually and behaviorally
Review captures on representative sizes and themes. Check hierarchy, alignment, typography, contrast, density, safe areas, text scaling, localization expansion, keyboard/pointer/focus behavior where supported, semantics, gesture conflicts, state transitions, and whether the signature element still serves the product.
Remove one unnecessary decorative element or motion if the result feels overworked.
7. Profile and verify
Use a production-representative Flutter build and physical devices. Inspect frame pacing, UI/raster work, rebuild scope, layout churn, image/texture and shader cost, memory, asset/package weight, startup/loading, energy/thermal behavior, and lifecycle cleanup relevant to the design.
Test reduced motion, screen reader/semantics, text scale, contrast, touch targets, keyboard/pointer where targeted, interruption, background/foreground, route changes, loading failure, and low-end fallback. Report measured evidence and remaining limits; do not claim smoothness from visual inspection alone.
Deliverable
Provide design intent and tokens, responsive/state map, interaction specification, technology decision and risks, implemented files when authorized, accessibility/fallback behavior, visual evidence, performance evidence, and remaining tradeoffs.
Definition of done
- The visual direction, tokens, hierarchy, and signature interaction are specific to the product brief.
- A working vertical slice covers real content plus loading, empty, error, and disabled states as applicable.
- Gestures and motion handle interruption, lifecycle, and navigation without decorative excess.
- Reduced motion, semantics/screen reader, text scale, and constrained-device fallbacks remain usable.
- Representative screenshots or rendered evidence and relevant frame/resource checks are reviewed.
- The handoff lists implemented files, visual/performance evidence, remaining platform gaps, and any user-only release step.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

