💡 How to use these prompts:
Replace everything in [BRACKETS] with your specific details before sending.
Click Copy to copy any prompt to your clipboard instantly.
[GEMINI MULTIMODAL — attach screenshot of the error or UI]
I have attached a screenshot showing [DESCRIBE: error message / unexpected UI / console output]. Debug the issue and fix it.
Code context: [PASTE RELEVANT CODE OR DESCRIBE THE COMPONENT]
Stack: [YOUR TECH STACK]
What should happen: [EXPECTED BEHAVIOUR]
What is happening: [ACTUAL BEHAVIOUR FROM THE SCREENSHOT]
Diagnose the issue from the screenshot, explain what is causing it, and give me the fix.
[GEMINI 3.6 FLASH — use for speed-first prototyping]
Build a working prototype of the following as fast as possible. Prioritise functional over polished.
What to build: [DESCRIBE]
Stack: [FRAMEWORK AND LANGUAGE]
What "working" means: [MINIMUM VIABLE OUTPUT]
What to skip: [STYLING / TESTS / ERROR HANDLING — specify what to cut for speed]
Output working code immediately. No planning, no asking questions. Cut every corner that does not affect the core function.
[USE IN GOOGLE AI STUDIO OR VERTEX AI — Gemini ecosystem]
Write code to integrate the following with Google Workspace APIs.
Integration: [DESCRIBE — e.g. read from Google Sheets and post summary to Slack, create Calendar event from email]
Google APIs needed: [SHEETS / DOCS / GMAIL / CALENDAR / DRIVE]
Auth: [SERVICE ACCOUNT / OAUTH]
Language: [PYTHON / NODE]
Write the complete integration with:
- OAuth or service account setup
- The core API calls
- Error handling for quota limits and auth failures
- A test function that verifies the integration works
Use the official Google API client libraries.
[GEMINI 3.6 FLASH WITH COMPUTER USE]
Review the following code and then test it by running it in a browser or terminal.
Code to review: [PASTE CODE]
What it should do: [DESCRIBE EXPECTED BEHAVIOUR]
Test steps: [DESCRIBE HOW TO VERIFY IT WORKS]
First do a static review (bugs, security, performance). Then execute the code in your environment and report what actually happens vs what should happen. Flag any divergence between the static review findings and the runtime behaviour.
Refactor the following code for deployment on Google Cloud Platform.
Current code: [PASTE CODE]
Current environment: [LOCAL / OTHER CLOUD / ON-PREM]
Target GCP service: [CLOUD RUN / CLOUD FUNCTIONS / GKE / APP ENGINE]
Requirements: [SCALING / LATENCY / COST CONSTRAINTS]
Refactor to:
1. Use GCP-native services where appropriate (Secret Manager, Cloud Storage, Pub/Sub)
2. Add proper health check endpoint
3. Handle GCP-specific env variables and service account auth
4. Add Dockerfile or deployment config if needed
Write the complete refactored code and deployment configuration.
Write a complete, production-ready API client for the following API.
API: [API NAME AND DOCS URL OR DESCRIPTION]
Language: [PYTHON / NODE / GO]
Authentication: [API KEY / OAUTH / BEARER]
Methods to implement: [LIST THE ENDPOINTS TO COVER]
Error handling: [RATE LIMITS / RETRY / TIMEOUT REQUIREMENTS]
Extras: [PAGINATION / STREAMING / WEBHOOK SUPPORT IF NEEDED]
Include:
- Client class with all methods
- Type hints / TypeScript types
- Rate limit handling with exponential backoff
- A simple test for each method
- README snippet showing basic usage