tech-flutter
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when building cross-platform apps with Flutter and Dart.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When working with Flutter, focus on widget tree efficiency and robust state management:
- Very specific: line 14
constConstructors: Always use const constructors for widgets that do not change. - Very specific: line 17
Async UI: Use FutureBuilder or StreamBuilder when dealing with asynchronous data to prevent blocking the main UI isolate.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 & Dart Best Practices
Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.
When working with Flutter, focus on widget tree efficiency and robust state management:
- Widget Composition: Build small, single-purpose widgets. Prefer composing widgets over passing multiple boolean flags to a monolithic widget.
constConstructors: Always useconstconstructors for widgets that do not change. This dramatically improves rendering performance.- State Management: Adhere to the project's chosen state management pattern (Provider, Riverpod, Bloc, etc.). Do not mix patterns or abuse
setStatefor global state. - Null Safety: Leverage Dart's sound null safety. Avoid using the
!(bang) operator to force unwrap; handle nulls gracefully. - Async UI: Use
FutureBuilderorStreamBuilderwhen dealing with asynchronous data to prevent blocking the main UI isolate.
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.