flutter-ai-starter / rules
Cursor rule0 starsChanged 5 months agoMITView on GitHub
API and backend integration — Supabase, dio, Edge Functions
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/architecture.mdcCursor rule
- .cursor/rules/dart-style.mdcCursor rule
- .cursor/rules/design-system.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 api-integration.mdc into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 11
All client access through repositories in lib/features/<feature>/data/repositories/
- Distinctive: line 13
Use typed query builders — no raw SQL from client
- Distinctive: line 20
Never call Gemini, OpenAI, or model SDKs from client
- Very specific: line 33
Verify JWT, validate body (e.g.
- Distinctive: line 44
Verify signature; idempotent handlers.
≈ “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: API and backend integration — Supabase, dio, Edge Functions
globs: ["lib/core/network/**/*.dart", "lib/services/**/*.dart", "lib/features/**/data/**/*.dart", "supabase/**/*"]
alwaysApply: false
---
# API & backend integration
## Supabase from client
- All client access through repositories in `lib/features/<feature>/data/repositories/`
- **Services** in `data/services/` wrap one data source each (Supabase table, REST endpoint, local store) — repositories compose services, not the reverse
- Use typed query builders — no raw SQL from client
- Repositories return `Future<Result<T, Failure>>`
- Map Supabase exceptions in `core/errors/error_mapper.dart` — never expose `PostgrestException` in presentation
- Inject `SupabaseClient` via `Provider` in `app/dependencies.dart` — not `Supabase.instance.client`
## AI calls (when enabled)
- Never call Gemini, OpenAI, or model SDKs from client
- Route through backend Edge Function (e.g. `POST /functions/v1/ai-invoke`)
- Client validates response with freezed models; handle timeout/rate-limit as UI states
## External HTTP (non-Supabase)
- Use `dio`
- Timeout: 15s; retry 5xx max 2 with backoff; honor 429 `Retry-After`
- Map all errors to typed `Failure`s
## Edge Functions
- One folder per function under `supabase/functions/<name>/`
- Verify JWT, validate body (e.g. zod), typed response `{ ok, data } | { ok: false, code, message }`
- Structured logs without PII; CORS to specific origins; rate limit per user
- Secrets via env — never inline
## Storage
- Private buckets; signed URLs for downloads
- Uploads: MIME whitelist, size cap, path sanitization; strip EXIF from photos
## Webhooks
- Verify signature; idempotent handlers; return 200 quickly, queue async work
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.