Update auth, firestore, and hosting instructions

[kmandrika]

Description

Update the Auth, Firestore, and Hosting prompts based on the latest versions.

[gemini-code-assist]

Summary of Changes

Hello @kmandrika, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the instructional guides for Firebase Authentication, Firestore, and Hosting. The primary goal is to enhance clarity, improve the logical flow of steps, and incorporate critical security best practices, particularly regarding automated security rule updates and pre-deployment checks for public rules. These updates ensure developers follow the latest recommendations and maintain a secure deployment posture.

Highlights

• Firebase Authentication Instructions: The instructions for Firebase Authentication setup have been restructured into clearer, categorized sections: 'Permission & Setup', 'Implementation', and 'Testing & Deployment'. A significant update includes guidance for automatically handling security rule updates, reducing the need for manual console interaction.
• Firestore Database Setup Guide: The Firestore setup guide has been reorganized into 'Database Setup', 'Verification & Testing', and 'Security' sections. It now provides more explicit steps for verification and testing, emphasizing that these should occur after running firebase deploy.
• Firebase Hosting Deployment Process: The Firebase Hosting instructions are now categorized into 'When to Deploy' and 'Deployment Process'. A crucial new security check has been added to prevent deployment if security rules are public without explicit confirmation, enhancing application security.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the instruction prompts for Auth, Firestore, and Hosting. The changes introduce a clearer, more structured format using markdown headings, which significantly improves readability. The instructions themselves are also updated to be more specific and actionable for the target AI agent. I've found one minor ambiguity in the Firestore guide and suggested a clarification. Overall, these are great improvements.

[gemini-code-assist]

The instructions for verification are split into two lines, which creates some ambiguity. Line 27 says to 'Guide developers', while line 28 begins with 'Navigate to...'. It's not perfectly clear whether the agent is supposed to perform the navigation or if this is part of the guidance for the developer. Combining these into a single, unambiguous instruction would be better for clarity.

Suggested change

	- Guide developers to verify database creation at the [Firebase Console](https://console.firebase.google.com/)
	- Navigate to "Firestore Database" in the left navigation to confirm database creation
	- Guide developers to verify database creation at the [Firebase Console](https://console.firebase.google.com/) by navigating to "Firestore Database" in the left navigation to confirm database creation