AI Prompts for Gemini for Coding

I want to build [DESCRIBE WHAT YOU ARE BUILDING]. Before writing code, help me design the architecture. Ask me about: scale requirements, existing systems this needs to integrate with, technology constraints, and team expertise. Then propose two or three architectural approaches with trade-offs for each.

I need to implement [SPECIFIC FEATURE] in [TECH STACK]. Give me three different implementation approaches: the simplest possible approach, the most scalable approach, and the most maintainable approach. For each, estimate complexity, list the main risk, and say which scenario it is best suited for.

I am building [DESCRIBE SYSTEM]. Help me design the data model. Propose the entities, their attributes, the relationships between them, and the indexes I will need for the most common queries. Flag any design decisions that will be painful to change later.

I want to build [DESCRIBE FEATURE] using Google Cloud and Firebase. Recommend the specific services to use: which Firebase features, which Cloud services, how they connect, and the estimated cost at [SCALE]. Show the architecture as a service map I can use as a blueprint.

I am going to build [DESCRIBE FEATURE]. Break this into implementation tasks ordered by dependency. For each task, describe: what it builds, what it depends on, the estimated complexity, and potential blockers. Output as a prioritized task list I can work through in order.

Write a complete, runnable implementation of [DESCRIBE FEATURE]. Language: [LANGUAGE]. Framework: [FRAMEWORK]. Include: all necessary imports, type definitions, error handling, and a usage example I can run immediately. Do not use placeholder comments. Every section should be real, working code.

Write code to integrate [SPECIFIC GOOGLE API, e.g. Gmail API / Maps API / Sheets API] into my [LANGUAGE/FRAMEWORK] application. Include: authentication setup, the specific API calls for [WHAT I NEED TO DO], error handling for common API errors, and a working example. Include the OAuth scope list I need.

Write Firebase backend code for [DESCRIBE FEATURE]. Include: Firestore data structure, security rules for [ACCESS PATTERNS], Cloud Functions for [BACKEND LOGIC], and client-side code to call them. Language: [JAVASCRIPT/TYPESCRIPT/PYTHON]. Production-quality with error handling.

Convert this [SOURCE LANGUAGE/FRAMEWORK] code to [TARGET LANGUAGE/FRAMEWORK]. Preserve the logic exactly but use idiomatic patterns for the target. Flag any places where a direct translation would be unidiomatic and explain what you changed: [PASTE CODE].

Write a comprehensive test suite for this function using [TEST FRAMEWORK]. Include tests for: the happy path, edge cases, invalid inputs, and boundary conditions. Use descriptive test names. Mock external dependencies: [PASTE FUNCTION CODE].

I have a bug I cannot resolve. Code: [PASTE]. Error message: [PASTE]. What I expected: [DESCRIBE]. What happened: [DESCRIBE]. What I have tried: [LIST]. Diagnose the root cause and give me the specific fix.

Review this code for: (1) bugs and logic errors, (2) security vulnerabilities, (3) performance problems, (4) maintainability issues. For each finding, rate the severity, explain the problem, and propose the fix: [PASTE CODE].

Review this Google Cloud or Firebase code against best practices: (1) security and IAM configuration, (2) cost efficiency, (3) scalability, (4) error handling and retry logic, (5) observability and logging. Flag any anti-patterns: [PASTE CODE].

Explain this error message in plain language, tell me what causes it, and give me the exact steps to fix it. Also tell me how to prevent it in future code: [PASTE ERROR MESSAGE AND STACK TRACE].

This code is running slower than expected. Identify the performance bottleneck, explain why it is slow, and propose an optimized version. Show the before and after with an explanation of what changed and why it is faster: [PASTE CODE].

Write complete documentation for this code: (1) a module-level overview explaining what it does and when to use it, (2) inline comments for non-obvious logic, (3) function docstrings with parameters, return values, and examples, (4) a usage README section: [PASTE CODE].

Refactor this code to improve maintainability without changing behavior: rename unclear variables and functions, extract repeated logic into helpers, simplify complex conditionals, and break long functions into smaller ones. Show a diff with explanations for each change: [PASTE CODE].

I am preparing this code for production. Review it for: missing error handling, lack of logging or observability, hardcoded values that should be environment variables, missing rate limiting or input validation, and any security issues. Propose specific changes for each finding: [PASTE CODE].

I need to upgrade [LIBRARY/FRAMEWORK/API] from version [OLD VERSION] to [NEW VERSION]. Write a migration guide for this specific codebase: what needs to change, what is backwards-compatible, what will break, and the recommended order to make changes: [PASTE RELEVANT CODE].

Based on this codebase: [DESCRIBE OR PASTE RELEVANT SECTIONS], create a code review checklist specific to our stack and patterns. Include: correctness checks, style checks, security checks, and performance checks. Make it specific enough that a reviewer can use it without knowing the full context of every PR.