skills/stack-flutter-firebase/SKILL.md
Integration patterns for Flutter + Firebase + Riverpod — auth, Firestore, Cloud Functions, project structure
npx skillsauth add xoai/sage stack-flutter-firebaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Layer 3 — Stack Composition
Integration patterns for the most common Flutter fullstack combination: Flutter + Firebase (Auth, Firestore, Cloud Functions, Storage) + Riverpod.
Firebase documentation explains each service in isolation. Riverpod docs explain state management in isolation. Neither explains: how Firebase Auth state feeds into Riverpod providers, how Firestore streams compose with Riverpod's reactive model, how to structure a project where Firebase is the backend and Riverpod manages the entire state tree.
These seams are where this pack provides value.
| Type | Files | Coverage | |------|-------|----------| | Integration | 4 | Firebase Auth + Riverpod, Firestore + Riverpod, Cloud Functions patterns, project structure | | Anti-patterns | 3 | Direct Firebase in widgets, unstructured Firestore, no security rules | | Constitution | 1 | 4 stack integration principles |
tools
Captures agent mistakes, corrections, and discovered gotchas so they are not repeated. Use when: (1) a command or operation fails unexpectedly, (2) the user corrects the agent, (3) the agent discovers non-obvious behavior through debugging, (4) an API or tool behaves differently than expected, (5) a better approach is found for a recurring task. Also searches past learnings before starting tasks to avoid known pitfalls. Activate alongside the sage-memory skill — they share the same MCP backend but serve different purposes (sage-memory = codebase knowledge, sage-self-learning = agent mistakes and gotchas).
development
Typed knowledge graph stored in sage-memory. Use when creating or querying structured entities (Person, Project, Task, Event, Document), linking related objects, checking dependencies, planning multi-step actions as graph transformations, or when skills need to share structured state. Trigger on "remember that X is Y", "what do I know about", "link X to Y", "show dependencies", "what blocks X", entity CRUD, cross-skill data access, or any request involving structured relationships between things.
tools
Integrates sage-memory into Sage workflows. Teaches the agent when to remember (store findings during work), when to recall (search memory at session start and task start), and how to learn (structured knowledge capture via sage learn). Use when the user mentions memory, remember, recall, learn, capture knowledge, onboard to codebase, or when starting any session where sage-memory MCP tools are available.
tools
Captures agent mistakes, corrections, and discovered gotchas so they are not repeated. Use when: (1) a command or operation fails unexpectedly, (2) the user corrects the agent, (3) the agent discovers non-obvious behavior through debugging, (4) an API or tool behaves differently than expected, (5) a better approach is found for a recurring task. Also searches past learnings before starting tasks to avoid known pitfalls. Activate alongside the sage-memory skill — they share the same MCP backend but serve different purposes (sage-memory = codebase knowledge, sage-self-learning = agent mistakes and gotchas).