flutter-ai-integration
Skill16 starsChanged 3 months agoBSD-3-ClauseView on GitHub
Build or review provider-neutral AI features in Flutter, including streaming responses, conversation state, structured output, tool calls, attachments, cancellation, and safe service boundaries. Use when model behavior is part of the product; do not use for ordinary APIs, product analytics, or generic chat between people.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- thienqo/flutter-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- thienqo/flutter-skills★ 16100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dart-concurrencySkill
- dart-languageSkill
- flutter-accessibilitySkill
- flutter-animationSkill
- flutter-app-workflowSkill
- flutter-architectureSkill
- flutter-authenticationSkill
- flutter-background-executionSkill
- flutter-build-releaseSkill
- flutter-ci-cdSkill
- flutter-code-reviewSkill
- flutter-dependency-upgradesSkill
- flutter-device-testingSkill
- flutter-figma-workflowSkill
- flutter-in-app-purchasesSkill
- flutter-localizationSkill
- flutter-mediaSkill
- flutter-navigationSkill
- flutter-networkingSkill
- flutter-notificationsSkill
- flutter-observabilitySkill
- flutter-openapi-clientSkill
- flutter-package-developmentSkill
- flutter-performanceSkill
- flutter-persistenceSkill
- flutter-platform-integrationSkill
- flutter-product-analyticsSkill
- flutter-responsive-layoutSkill
- flutter-runtime-debuggingSkill
- flutter-securitySkill
- flutter-state-managementSkill
- flutter-testingSkill
- flutter-text-renderingSkill
- flutter-ui-designSkill
- flutter-ui-patternsSkill
- flutter-visual-effectsSkill
- flutter-webviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- could be automatic: a setting could enforce it
- Distinctive: line 10
Do not add a provider SDK, account setup, credential, or backend merely because this skill was selected.
- Very specific: line 14
Read pubspec.yaml, SDK constraints, existing AI or API adapters, backend boundary, authentication, model configuration, state ownership, …
- Distinctive: line 16
Keep model and provider details behind a narrow application-owned interface.
- Distinctive: line 20
Read service boundary and secrets when selecting client versus backend responsibilities, credentials, provider abstraction, safety, …
- Distinctive: line 21
Read streaming, tools, and state when implementing streamed output, conversations, attachments, structured responses, or tool/function …
- Distinctive: line 22
Read Flutter AI Toolkit and GenUI only when the project uses or is considering those Flutter packages.
- Distinctive: line 36
Verify the visible stream and state transitions on affected platforms, including restart or restoration when required.
≈ “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 AI Integration
Integrate model behavior as an unreliable, asynchronous external capability with an explicit product contract. Preserve the project's provider, backend, networking client, state management, persistence, and UI architecture unless the user requests a migration.
Do not add a provider SDK, account setup, credential, or backend merely because this skill was selected.
Preflight
Read pubspec.yaml, SDK constraints, existing AI or API adapters, backend boundary, authentication, model configuration, state ownership, persistence, privacy requirements, tests, and platform targets. Clarify the intended capability and failure behavior before choosing a model, provider, SDK, or UI toolkit.
Keep model and provider details behind a narrow application-owned interface. Treat output, tool arguments, citations, and structured data as untrusted input. Define cancellation, timeout, retry, partial-result, quota, offline, and unsupported-capability behavior.
Load references conditionally
- Read service boundary and secrets when selecting client versus backend responsibilities, credentials, provider abstraction, safety, privacy, or model configuration.
- Read streaming, tools, and state when implementing streamed output, conversations, attachments, structured responses, or tool/function calls.
- Read Flutter AI Toolkit and GenUI only when the project uses or is considering those Flutter packages. Do not introduce them by default.
Boundaries
flutter-networkingowns generic HTTP, WebSocket, SSE, authentication refresh, and transport reliability; this skill owns model-specific semantics on top.dart-concurrencyowns general stream races, cancellation primitives, and isolate behavior.flutter-persistenceowns durable storage and offline synchronization; this skill defines what conversation or model state may be retained.flutter-securityowns a broad threat review; this skill enforces the model boundary, credential placement, untrusted output handling, and least-privilege tools.flutter-ui-patternsandflutter-accessibilityown general interface composition and accessibility.
Verification
Use a deterministic fake model or recorded adapter for ordinary automated tests. Cover partial chunks, cancellation, timeout, malformed structured output, tool denial and failure, repeated or reordered events, quota errors, and provider unavailability. Use a real provider only when credentials, cost, network access, and environment are explicitly in scope; keep such tests separate and non-destructive.
Verify the visible stream and state transitions on affected platforms, including restart or restoration when required. Report which behavior was fake-tested, which was exercised end to end, the exact provider/model configuration when relevant, and any cost, safety, or backend boundary not verified.
Sources
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.