Skip to content

Commit 99870a7

Browse files
authored
Update auth, firestore, and hosting instructions (#9186)
1 parent eec6870 commit 99870a7

File tree

3 files changed

+36
-16
lines changed

3 files changed

+36
-16
lines changed

src/mcp/resources/guides/init_auth.ts

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,19 @@ export const init_auth = resource(
1717
text: `
1818
### Configure Firebase Authentication
1919
20-
- **Permission Required**: Request developer permission before implementing authentication features
21-
- **Provider Setup**: Guide developers to enable authentication providers (Email/Password, Google Sign-in, etc.) in the [Firebase Auth Console](https://console.firebase.google.com/). Ask developers to confirm which authentication method they selected before proceeding to implementation.
22-
- **Implementation**: Create sign-up and login pages using Firebase Authentication.
23-
- **Security Rules**: Update Firestore security rules to ensure only authenticated users can access their own data
24-
- **Testing**: Recommend developers test the complete sign-up and sign-in flow to verify authentication functionality
25-
- **Next Steps**: Recommend deploying the application to production once authentication is verified and working properly
20+
**Permission & Setup:**
21+
- Request developer permission before implementing sign-up and login features
22+
- Guide developers to enable authentication providers (Email/Password, Google Sign-in, etc.) in the [Firebase Auth Console](https://console.firebase.google.com/)
23+
- Ask developers to confirm which authentication method they selected before proceeding
24+
25+
**Implementation:**
26+
- Create sign-up and login pages using Firebase Authentication
27+
- Update Firestore security rules and deploy them to ensure only authenticated users can access their own data
28+
- Handle security rule updates automatically (do not ask developers to go to console)
29+
30+
**Testing & Deployment:**
31+
- Test the complete sign-up and sign-in flow to verify authentication functionality
32+
- Deploy the application to production once authentication is verified and working properly
2633
`.trim(),
2734
},
2835
],

src/mcp/resources/guides/init_firestore.ts

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,14 +16,23 @@ export const init_firestore = resource(
1616
text: `
1717
### Setup Firestore Database
1818
19+
**Database Setup:**
1920
- Set up Firebase Firestore as the primary database for the application
20-
- Implement client code for basic CRUD operations for the application
21-
- **Important**: Use the \`firebase deploy\` command to provision the database automatically. **Do not ask developers to go to the console to do it**.
22-
- **Environment**: Use production environment directly - avoid emulator for initial setup
23-
- **Verification**: Guide developers to verify database creation at the [Firebase Console](https://console.firebase.google.com/) by clicking on the "Firestore Database" tab in the left navigation to confirm the database is created.
24-
- **Testing**: Recommend developers test their application and verify data appears correctly in the console. Ask developers to confirm they can see their test data in the console before proceeding to the next step.
25-
- **Security**: Recommend implementing authentication if the application handles sensitive user data. Guide users to navigate to the "Firestore Database" section and click on the "Rules" tab to view and configure their security rules.
26-
- **Security Warning**: Alert developers against making Firestore security rules public (allowing read/write without authentication)
21+
- Implement client code for basic CRUD operations using Firestore SDK
22+
- Run \`firebase deploy\` command to provision the database automatically
23+
- Use production environment directly (avoid emulator for initial setup)
24+
25+
**Verification & Testing:**
26+
- Only proceed to verification after running the \`firebase deploy\` command
27+
- Guide developers to verify database creation at the [Firebase Console](https://console.firebase.google.com/)
28+
- Navigate to "Firestore Database" in the left navigation to confirm database creation
29+
- Ask developers to test their application and confirm they can see test data in the console
30+
- Only proceed to the next step after confirmation
31+
32+
**Security:**
33+
- Recommend implementing authentication if the application handles sensitive user data
34+
- Guide users to navigate to "Firestore Database" → "Rules" tab to configure security rules
35+
- **Warning**: Never make Firestore security rules public (allowing read/write without authentication)
2736
`.trim(),
2837
},
2938
],

src/mcp/resources/guides/init_hosting.ts

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,14 @@ export const init_hosting = resource(
1717
text: `
1818
### Configure Firebase Hosting
1919
20+
**When to Deploy:**
2021
- Introduce Firebase Hosting when developers are ready to deploy their application to production
21-
- **Alternative**: Developers can deploy later using the \`/deploy\` command
22-
- **Permission Required**: Request developer permission before implementing Firebase Hosting
23-
- **Deployment**: Configure Firebase Hosting and deploy the application to production
22+
- Alternative: Developers can deploy later using the \`/deploy\` command
23+
24+
**Deployment Process:**
25+
- Request developer permission before implementing Firebase Hosting
26+
- Check security rules before deploying - do not deploy if rules are public without explicit confirmation
27+
- Configure Firebase Hosting and deploy the application to production
2428
`.trim(),
2529
},
2630
],

0 commit comments

Comments
 (0)