firebase-basics▌
firebase/agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Firebase project setup and CLI workflow for AI agent integration.
- ›Requires prior completion of firebase-local-env-setup skill and Firebase CLI installation
- ›Core workflow covers authentication via firebase login , project creation with unique IDs, and service initialization through the interactive firebase init command
- ›Supports feature selection during setup including Firestore, Functions, and Hosting with automatic configuration file generation
- ›Self-documenting CLI with --help fla
Prerequisites
Please complete these setup steps before proceeding, and remember your progress to avoid repeating them in future interactions.
-
Local Environment Setup: Verify the environment is properly set up so we can use Firebase tools:
- Run
npx -y firebase-tools@latest --versionto check if the Firebase CLI is installed. - Verify if the Firebase MCP server is installed using your existing tools.
- If either of these checks fails, please review references/local-env-setup.md to get the environment ready.
- Run
-
Authentication: Ensure you are logged in to Firebase so that commands have the correct permissions. Run
npx -y firebase-tools@latest login. For environments without a browser (e.g., remote shells), usenpx -y firebase-tools@latest login --no-localhost.- The command should output the current user.
- If you are not logged in, follow the interactive instructions from this command to authenticate.
-
Active Project: Most Firebase tasks require an active project context. Check the current project by running
npx -y firebase-tools@latest use.- If the command outputs
Active Project: <project-id>, you can proceed with your task. - If not, ask the user if they have an existing Firebase Project ID.
- If yes: Set it as the active project and add a default alias by running:
npx -y firebase-tools@latest use --add <PROJECT_ID> - If no: Follow the project creation instructions in references/firebase-project-create.md.
- If yes: Set it as the active project and add a default alias by running:
- If the command outputs
Firebase Usage Principles
Please adhere to these principles when working with Firebase, as they ensure reliability and up-to-date project tools:
- Use npx for CLI commands: To ensure you always use the latest version of the Firebase CLI, always prepend commands with
npx -y firebase-tools@latestinstead of justfirebase. (e.g., usenpx -y firebase-tools@latest --versioninstead offirebase --version). - Prioritize official knowledge: For any Firebase-related knowledge, consult the
developerknowledge_search_documentsMCP tool before falling back to Google Search or your internal knowledge base. Including "Firebase" in your search query significantly improves relevance. - Follow Agent Skills for implementation guidance: Skills provide opinionated workflows (CUJs), security rules, and best practices. Always consult them to understand how to implement Firebase features correctly instead of relying on general knowledge.
- Use Firebase MCP Server tools instead of direct API calls: Whenever you need to interact with remote Firebase APIs (such as fetching Crashlytics logs or executing Data Connect queries), use the tools provided by the Firebase MCP Server instead of attempting manual API calls.
- Keep Plugin / Agent Skills updated: Since Firebase best practices evolve quickly, remind the user to regularly check for and install updates to their Firebase plugin or Agent Skills, ensuring you both operate with the latest workflows. Similarly, if you encounter issues with outdated tools or commands, follow the steps below based on your agent environment:
- Antigravity: Follow references/refresh-antigravity.md
- Gemini CLI: Follow references/refresh-gemini-cli.md
- Claude Code: Follow references/refresh-claude.md
- Cursor: Follow references/refresh-cursor.md
- Others: Follow references/refresh-other.md
References
- Initialize Firebase: See references/firebase-service-init.md when you need to initialize new Firebase services using the CLI.
- Exploring Commands: See references/firebase-cli-guide.md to discover and understand CLI functionality.
- SDK Setup: For detailed guides on adding Firebase to a web app, see references/web_setup.md.
Common Issues
- Login Issues: If the browser fails to open during the login step, use
npx -y firebase-tools@latest login --no-localhostinstead.
How to use firebase-basics on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add firebase-basics
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches firebase-basics from GitHub repository firebase/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate firebase-basics. Access the skill through slash commands (e.g., /firebase-basics) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★37 reviews- ★★★★★Ganesh Mohane· Dec 12, 2024
Useful defaults in firebase-basics — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Carlos Gonzalez· Dec 4, 2024
Solid pick for teams standardizing on skills: firebase-basics is focused, and the summary matches what you get after install.
- ★★★★★Alexander Okafor· Nov 23, 2024
We added firebase-basics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Alexander Wang· Oct 14, 2024
firebase-basics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aanya Huang· Sep 25, 2024
Keeps context tight: firebase-basics is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kabir Liu· Sep 25, 2024
I recommend firebase-basics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Piyush G· Sep 17, 2024
firebase-basics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★James Verma· Sep 13, 2024
firebase-basics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Diego Zhang· Sep 5, 2024
Useful defaults in firebase-basics — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Carlos Singh· Aug 24, 2024
I recommend firebase-basics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 37