Clarify system prompt

[joehan]

Description

Refining the system prompt a bit, per b/489989652

[gemini-code-assist]

Summary of Changes

Hello, 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 system prompt for Firebase Studio exports, enhancing clarity and completeness. The changes aim to provide users with more precise guidance on application deployment, foundational documentation, AI feature integration, and critical security considerations, thereby streamlining development workflows and promoting best practices.

Highlights

• Deployment Instructions: Updated migration guidelines to provide clearer instructions for deploying to Firebase App Hosting, specifying the correct firebase deploy command and explicitly warning against incorrect commands or deploying to Firebase Hosting.
• Documentation Reference: Clarified the role of docs/blueprint.md as describing the app's original intent.
• AI Feature Guidance: Reaffirmed the use of Genkit for AI features, consistent with existing configuration.
• Security Reminder: Added an "Important" section to explicitly warn against displaying, logging, or committing sensitive credentials.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• templates/firebase-studio-export/system_instructions_template.md
  • Clarified migration guidelines for deployment to Firebase App Hosting.
  • Added explicit instructions on which Firebase commands to use and avoid for deployment.
  • Reiterated the use of Genkit for AI features.
  • Included a new section emphasizing the importance of not exposing sensitive credentials.

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 refines the system prompt for the AI agent, providing more specific and clearer instructions for migrating and working with Firebase Studio projects. The changes include more explicit deployment commands, negative constraints to prevent common errors, and an important new section on handling sensitive credentials. My only suggestion is a minor grammatical correction to improve clarity in one of the instructions.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[christhompsongoogle]

If this is a capra workspace AND it was deployed already we expect to see some firebase.json info, otherwise it might be empty. In that case we should instruct the model to re-use these if available or instruct the user to run init apphosting I think