firebase-development
Firebase development guidelines for Firestore, Authentication, Functions, and Storage with TypeScript and Angular.
What this skill does
# Firebase Development You are an expert in Firebase development with Firestore, Authentication, Cloud Functions, and Storage. ## Project Structure - Organize code by feature directories (services, components, pipes) - Use environment variables for development, staging, and production - Structure Firestore collections logically (users, spots, bookings) - Maintain separate Firebase configurations per environment ## Code Organization Best Practices - Use descriptive naming: "getUsers", "calculateTotalPrice" - Keep classes small and focused - Minimize global state usage - Centralize API calls and error handling through services - Manage storage through a single point of entry with centralized key definitions ## Firebase-Specific Patterns ### Firestore - Create dedicated services for each Firestore collection type - Implement centralized Firebase error handling - Use transactions for data consistency - Apply Firebase security rules for data protection ### Cloud Functions - Leverage Firebase Functions for serverless backend logic - Implement proper error handling and logging - Use typed function parameters and responses ### Storage - Handle file uploads/downloads via Firebase Storage - Implement proper access control - Use signed URLs for secure file access ### Authentication - Manage user identity through Firebase Authentication - Implement proper session management - Handle auth state changes reactively ## Naming Conventions - **camelCase**: functions and variables - **kebab-case**: file names (user-service.ts) - **PascalCase**: classes (UserService) - **Boolean prefixes**: should, has, is (shouldLoadData, isLoading) - **Collections**: plural nouns - **Documents**: descriptive IDs ## Performance Optimization - Implement lazy loading and data prefetching - Cache frequently accessed data - Use global error and alert handlers - Implement Firebase offline persistence - Apply query cursors for pagination - Optimize Firestore reads through proper indexing - Use batch operations for bulk updates ## Testing Requirements - Write comprehensive unit tests covering edge cases - Mock native plugins and Firestore services - Test Firebase security rules thoroughly - Validate offline functionality
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.