Gemini 3.5 Flash Prompt Generator

You are a research agent with access to search and summarization tools. Your goal: compile a structured competitive analysis report for a Series A SaaS startup entering the project management software space. Step 1 — identify the top 7 competitors by market share and search volume. Step 2 — for each, extract: pricing model, key differentiators, primary customer segment, and one publicly documented weakness. Step 3 — synthesize a positioning gap analysis identifying where the startup has the clearest white space. Format: executive summary (3 sentences), competitor table, gap analysis with 3 prioritized opportunities. Source all data points. Target length: 600 words.

Build a complete user authentication feature for a Next.js 15 app using Supabase Auth. Requirements: (1) Email/password signup and login with client-side validation — required fields, email format check, password minimum 8 characters with one uppercase and one number; (2) A server-side session check middleware that redirects unauthenticated users from /dashboard to /login; (3) A logout button component that clears the Supabase session and redirects to /; (4) Error states for wrong credentials, email already in use, and network failure — each with a distinct user-facing message; (5) TypeScript throughout. Provide complete file contents for each file created or modified. Include a short comment only where the logic is non-obvious.

I am attaching a 150-page investor relations document (10-K annual report). Extract and structure the following: (1) Revenue, gross margin, operating margin, and net income for the last 3 fiscal years in a table; (2) The three risk factors the company identifies as most material, with a one-sentence plain-English explanation of each; (3) Management's stated strategic priorities for the next 12 months — bullet list, no more than 6 items; (4) Any forward guidance provided — exact figures stated, clearly attributed to the document; (5) A 100-word plain-language summary of the company's overall financial health as of the report date. Flag anything that appears to be contradicted elsewhere in the document.

Act as an intelligent email triage agent. I will provide you with 20 email subjects and sender names from my inbox. For each email: (1) Assign a priority level — Urgent (needs response today), Normal (respond within 3 days), or Low (FYI / no response needed); (2) Identify the required action — Reply, Forward to [role], Archive, or Schedule meeting; (3) Draft a one-sentence reply template for any email marked Urgent. Output as a structured table: Subject | Sender | Priority | Action | Draft Reply. At the end, list all Urgent items again in a single prioritised action list I can work through top-to-bottom.

Review the following Node.js Express API endpoint for security vulnerabilities and performance issues. For security: check for SQL injection exposure (parameterised queries vs. string concatenation), missing input validation, unprotected routes (missing auth middleware), sensitive data in logs or error responses, and missing rate limiting. For performance: identify synchronous operations that should be async, missing database query indexes (infer from query patterns), N+1 query patterns, and missing response caching opportunities. Output: a prioritised issue list (Critical / High / Medium / Low), each with the exact line or code block, the problem, and a corrected code snippet. [paste code below]

I am uploading an image of a consumer product and its packaging. Analyse the following: (1) Brand identity — describe the visual language, colour palette, typography style, and the emotional register they communicate; (2) Target audience inference — based on visual cues alone, who does this product appear to be targeting? Age range, lifestyle, income bracket; (3) Competitive positioning — does this look premium, mass-market, or challenger brand? What visual choices create that impression? (4) One specific improvement to the packaging design that would increase perceived quality without changing the product itself; (5) Rate the overall packaging effectiveness for shelf impact on a scale of 1–10 with a one-sentence justification.

Generate complete API documentation for the following REST endpoints. For each endpoint produce: (1) A one-sentence description of what the endpoint does; (2) HTTP method and full path with path parameters highlighted; (3) Request body schema in JSON with type annotations and required/optional flags; (4) All possible response codes with their meaning and an example JSON response body; (5) One curl example showing a realistic request with real-looking (but fake) data. Format as clean Markdown suitable for a developer docs site. Endpoints to document: POST /api/v1/users/register, POST /api/v1/auth/login, GET /api/v1/users/:id, PATCH /api/v1/users/:id, DELETE /api/v1/users/:id.

Write the Go-to-Market section of a business plan for a B2B SaaS product that automates accounts payable for mid-market manufacturing companies (50–500 employees, $10M–$200M revenue). The section must cover: (1) Target customer profile — firmographics, pain points, current workflow, budget authority (who signs); (2) Primary sales motion — outbound SDR-led, inbound content-led, or partnership channel — choose one and justify in 3 sentences; (3) First 90-day launch plan — Week 1–4, Week 5–8, Week 9–13, each with 2–3 specific, measurable actions; (4) Key performance indicators — 5 metrics for the first 6 months with realistic targets; (5) Pricing strategy — model, entry price point, and expansion logic. Tone: crisp, investor-ready. Length: 500–600 words.

A logistics company operates 340 delivery vehicles across 12 cities. Fuel represents 38% of their variable operating cost. Diesel prices have increased 22% over the last 18 months. The company is evaluating three options: (A) Transition 30% of the fleet to electric vehicles over 24 months at $85,000 per vehicle, financed at 6.2% over 5 years; (B) Implement a route optimisation software at $12,000/month that the vendor claims reduces fuel consumption by 14%; (C) Do nothing and pass the cost increase to customers, risking a projected 8% churn among price-sensitive accounts. Show your reasoning step by step. Calculate the 3-year net cost or saving for each option under realistic assumptions. State your assumptions explicitly. Recommend one option and explain the two strongest objections to your recommendation.

Write a 12-minute podcast script (approximately 1,800 words) for a tech interview show. Guest: a fictional CTO of a mid-stage AI startup. Topic: 'Why most AI integrations fail within 18 months — and what the ones that succeed do differently.' Format: Host intro (30 seconds), 5 interview questions with guest answers of 2–3 paragraphs each, a rapid-fire closing segment (3 short questions, punchy answers), host outro with call to action (30 seconds). The content should be substantive and specific — draw on real patterns (data quality, change management, ROI measurement, build-vs-buy decisions, executive sponsorship). Write both host and guest lines. Tone: informed, direct, occasionally provocative. No filler phrases ('great question', 'absolutely').

I am providing a dataset of 500 customer support tickets from a SaaS product (as a CSV). Analyse the data and provide: (1) The top 5 issue categories by volume — with exact counts and percentage of total; (2) Average time-to-resolution for each category; (3) The 3 issues with the highest repeat contact rate (same user, same issue within 30 days) — these indicate failed resolutions; (4) Tickets that include language suggesting churn risk ('cancel', 'switch', 'frustrated', 'unacceptable', 'competitor') — list count and the top 3 products/features mentioned alongside churn language; (5) A prioritised recommendation list: which 3 issue types, if resolved structurally, would have the greatest impact on customer satisfaction and support volume. [paste CSV data or attach file]

Analyse the pricing pages of the following three SaaS companies and produce a structured teardown: [Company A URL], [Company B URL], [Company C URL]. For each: (1) Pricing model — per seat, usage-based, tiered flat, or hybrid; (2) Price anchoring strategy — what is the 'hero' plan they want most users to buy, and how is it positioned relative to the other tiers; (3) Feature gating — list 3 features used as upgrade triggers and the tier they unlock at; (4) Social proof and trust signals on the pricing page — logos, testimonials, certifications; (5) CTA language analysis — exact copy of the primary CTA button at each tier. Conclude with a one-paragraph synthesis: which company has the most effective pricing page and why, specifically.

You are processing a raw meeting transcript. Transform it into structured meeting notes following this format exactly: (1) Meeting metadata: date, attendees, meeting type (decision / update / brainstorm / review); (2) 5-bullet executive summary — what was decided, not what was discussed; (3) Action items table — Owner | Task | Due Date | Priority — extract every commitment made during the meeting, even implicit ones ('let's check on that'); (4) Decisions made — numbered list, each as a one-sentence declarative statement ('The team decided to...'); (5) Open questions — unresolved issues explicitly flagged for follow-up; (6) Next meeting: suggested agenda items based on open questions. Flag any ambiguous commitments where the owner or due date was not stated — mark these as [OWNER TBC] or [DATE TBC]. [paste transcript below]

Build a complete 8-week self-study curriculum for a software engineer transitioning into machine learning engineering. Prerequisites: strong Python, basic statistics (mean, variance, probability). Goal: capable of training, evaluating, and deploying a supervised learning model in a production environment by week 8. For each week provide: (1) Core concept to master — 1 sentence; (2) Primary resource — specific book chapter, course, or tutorial (real, widely available); (3) Hands-on project — a specific, completable mini-project to reinforce the concept; (4) Assessment checkpoint — one question or task to verify understanding before moving on. End with a capstone project specification for week 8. Keep resources free or low-cost. Format as a clean weekly table.

I am uploading an image of a business performance chart. Extract and analyse: (1) Chart type and time period covered; (2) The primary metric displayed — name, unit, and scale; (3) Key data points — highest value (date + value), lowest value (date + value), most recent value; (4) Trend direction — growth, decline, flat, or cyclical — with a one-sentence quantitative description ('Revenue grew approximately X% over the period shown'); (5) Any anomalies — single data points or periods that deviate significantly from the trend, with a possible explanation; (6) A one-paragraph plain-English summary of what this chart tells an executive who has 30 seconds to review it. Be precise — report the actual numbers visible in the chart, do not round unless the scale makes exact reading impossible.

Act as a GDPR compliance reviewer. I will provide the text of a user consent form and a privacy policy. Review both documents and flag: (1) Missing mandatory disclosures under GDPR Article 13 and 14 — for each missing item, cite the specific article and paragraph; (2) Consent mechanisms that do not meet the 'freely given, specific, informed, unambiguous' standard — explain why each fails; (3) Data retention periods — are they stated? Are they justified? Are they proportionate to the stated purpose?; (4) Third-party data sharing — are all processors and sub-processors disclosed with the required information?; (5) Data subject rights — are all 8 rights listed and is the exercise mechanism clearly described? Output: a numbered findings list with severity (Critical / Major / Minor), each with the specific clause or section where the issue appears, and a suggested corrected wording.

Expand the following one-line creative brief into a complete 400-word creative brief suitable for briefing a design agency. Brief: 'Rebrand a 40-year-old regional bank to appeal to millennial and Gen Z customers without alienating existing older customers.' The expanded brief must include: (1) Business context — why this rebrand is happening and what success looks like in business terms; (2) Target audience — primary (new customers) and secondary (existing customers), with specific psychographic and behavioural descriptors for each; (3) Brand positioning statement — complete the template: 'For [audience], [brand] is the [category] that [benefit] because [reason to believe]'; (4) Tone of voice — 3 adjectives, each with a one-sentence definition and an example of it in brand copy; (5) Mandatory elements — what must be retained or respected from the existing brand; (6) Creative mandatories and restrictions — what the work must include or must avoid.

I am uploading a 30-second video clip. Analyse and describe: (1) Scene overview — setting, time of day, number of subjects visible; (2) Action sequence — a timestamped description of the key actions in order (0s, 5s, 10s, 15s, 20s, 25s, 30s); (3) Audio analysis — speech (transcribe any audible dialogue), ambient sound, music (if present, describe tempo and mood); (4) Visual quality assessment — camera movement (static, pan, zoom, handheld), lighting quality, and overall production value (consumer, semi-professional, broadcast); (5) Emotional register — what emotion does the scene communicate, and what specific visual or audio elements create that effect; (6) If this were used as a social media clip, describe the ideal caption and platform in one sentence each.

Write a Product Requirements Document (PRD) for a mobile feature: 'AI-powered receipt scanner that automatically categorises expenses and suggests budget adjustments.' The PRD must follow this structure: (1) Problem statement — who has this problem, how often, and what is the cost of the current solution (manual entry); (2) Success metrics — 3 quantitative targets the feature must hit within 90 days of launch (e.g., adoption rate, accuracy rate, time saved); (3) User stories — 5 stories in 'As a [user], I want to [action], so that [outcome]' format, covering the core loop and two edge cases; (4) Functional requirements — numbered list of must-haves for v1, clearly separated from nice-to-haves; (5) Non-functional requirements — performance (scan-to-result time), accuracy threshold, offline behaviour, data privacy; (6) Out of scope for v1 — 3 items explicitly excluded with a one-sentence rationale each.

Prepare me to debate the following motion: 'AI coding assistants make software engineers less skilled over time.' I will be arguing both sides in a practice session. For the PROPOSITION side: provide 4 arguments with supporting evidence or analogies, ranked by persuasive strength, plus the single strongest counter-argument I should be ready to rebut. For the OPPOSITION side: provide 4 arguments with supporting evidence or analogies, ranked by persuasive strength, plus the single strongest counter-argument I should be ready to rebut. Finally, identify the one empirical question (a factual claim that is currently unresolved) that would most change the debate if answered — and explain why it is pivotal. Format: clearly labelled Proposition / Opposition sections, with numbered arguments and a 'Key rebuttal' subsection for each side.