flutter-ai-starter / rules
Cursor rule0 starsChanged 5 months agoMITView on GitHub
Design system tokens, components, and calm UX
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/000-project.mdcCursor rule
- .cursor/rules/accessibility.mdcCursor rule
- .cursor/rules/api-integration.mdcCursor rule
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/dart-style.mdcCursor rule
- .cursor/rules/flutter-ui.mdcCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/state-management.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- doubt-reviewSkill
- fix-dependenciesSkill
- flutter-componentSkill
- flutter-implementSkill
- generate-mocksSkill
- grind-until-greenSkill
- implement-tddSkill
- monitor-terminalSkill
- plan-featureSkill
- repo-navigatorSkill
- review-codeSkill
- save-contextSkill
- suggest-ruleSkill
- write-commitSkill
- write-readmeSkill
The file
We split this design-system.mdc into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Never raw hex, sizes, radii, or durations in features — always tokens
- Very specific: line 18
Use project prefix consistently (e.g.
- Very specific: line 24
No raw Image.network in features — use design-system image wrapper
- Distinctive: line 29
No ALL CAPS body copy
- Distinctive: line 35
Default Material 3 for both platforms
- Distinctive: line 40
Every design-system component: widget test + golden (light + dark)
- Very specific: line 41
Use flutter-component skill when adding new components
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
--- description: Design system tokens, components, and calm UX globs: ["lib/design_system/**/*.dart", "lib/features/**/presentation/**/*.dart"] alwaysApply: false --- # Design system ## Tokens (`lib/design_system/tokens/`) - `colors`, `typography`, `spacing`, `radii`, `sizes`, `durations` - Never raw hex, sizes, radii, or durations in features — always tokens - Icon sizes use token constants; min touch ≥48dp (Material) / ≥44pt (Cupertino) from `sizes.dart` ## Components (`lib/design_system/components/`) - Reusable primitives only — no feature data shapes or network access - Use project prefix consistently (e.g. `AppButton`, `app_button.dart`) - Variants in separate `*_variant.dart` files when needed - Tappable: `Material` + `InkWell`; always `Semantics` ## Imagery - No raw `Image.network` in features — use design-system image wrapper - Icons via project icon set — not raw `Icons.*` ## Calm UX - No ALL CAPS body copy - Muted error colors — not alarming red for routine errors - Loading/empty copy: specific and helpful ## Platform - Default Material 3 for both platforms - Cupertino only where iOS-native UX is materially better — not mixed on one screen ## Coverage - Every design-system component: widget test + golden (light + dark) - Use `flutter-component` skill when adding new components
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.