flutter-isar
Implement local data persistence with Isar database and offline-first architecture. Use when building cache-first data strategies, reactive queries, schema migrations, or secure local storage with flutter_secure_storage.
What this skill does
# Isar Database - Use **Isar** as the primary local database for structured data persistence - Define collections using `@collection` annotation with `Id` field - Place collection definitions in the `data/local/` directory of the relevant feature - Run `dart run build_runner build --delete-conflicting-outputs` after modifying collections ## Schema Design - Keep collections focused — one collection per domain entity - Use `@Index` annotations for fields queried frequently - Use `@enumerated` for enum fields - Use `Links` and `Backlinks` for relationships between collections - NEVER store derived/computed values — compute them in the domain layer ## Migrations - Isar handles additive schema changes automatically (new fields, new collections) - For breaking changes (renamed fields, removed fields), write migration logic in the repository - Version your database schema and check version on app startup # Repository Pattern for Local Data - Local DataSource wraps all Isar `put`, `get`, `delete`, `watch` calls - Repositories orchestrate between remote and local DataSources - Repositories decide cache-first vs network-first strategy per use case # Offline-First Patterns - **Cache-First**: Read from Isar first, fetch from network in background, update Isar on success - **Network-First**: Fetch from network, fall back to Isar on failure - **Write-Behind**: Write to Isar immediately, sync to server asynchronously (queue pending changes) - Always show cached data immediately while refreshing in background # Reactive Queries - Use Isar's `watchLazy()` or `watch()` to stream changes to the UI via BLoC - Wrap Isar watch streams in the repository and expose as `Stream<List<DomainModel>>` - Dispose stream subscriptions properly in BLoC `close()` method # Secure Storage - Use `flutter_secure_storage` for sensitive key-value data (tokens, encryption keys) - Use `SharedPreferences` ONLY for non-sensitive user preferences (theme, locale, onboarding flags) - NEVER store passwords, tokens, or secrets in `SharedPreferences` or plain Isar
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.