Prompt Templates

You are a senior software engineer conducting a thorough code review. Review the following {{language}} code with a focus on correctness, performance, security, and maintainability.

Code to review:
```{{language}}
{{code}}
```

Provide structured feedback covering:
1. **Critical Issues** — bugs, security vulnerabilities, or logic errors that must be fixed
2. **Performance** — inefficiencies, unnecessary allocations, or algorithmic improvements
3. **Code Quality** — readability, naming conventions, and adherence to {{language}} best practices
4. **Suggestions** — optional improvements that would enhance the code

For each issue, cite the specific line or block and provide a corrected example.

You are an expert debugger. Diagnose and fix the bug in the following {{language}} code.

**Error / Symptom:**
{{error_message}}

**Code:**
```{{language}}
{{code}}
```

**Context:**
- Runtime/framework: {{runtime}}
- Expected behavior: {{expected_behavior}}

Respond with:
1. **Root Cause** — a concise explanation of why the bug occurs
2. **Fix** — the corrected code with comments on every change
3. **Prevention** — how to avoid this class of bug in the future

Generate comprehensive unit tests for the following {{language}} function using {{test_framework}}.

Function to test:
```{{language}}
{{function_code}}
```

Requirements:
- Cover all happy paths with representative inputs
- Cover all edge cases (empty, null, boundary values, overflow)
- Cover error conditions and expected exceptions
- Each test must have a descriptive name explaining what it verifies
- Follow Arrange-Act-Assert structure
- Aim for ≥90% branch coverage

Return only the test file code with no additional explanation.

Generate professional API documentation in OpenAPI 3.1 / Markdown format for the following endpoint.

**Endpoint:** {{http_method}} {{endpoint_path}}
**Service:** {{service_name}}

Implementation:
```{{language}}
{{handler_code}}
```

Documentation must include:
- Summary and detailed description
- All path, query, and body parameters with types, constraints, and examples
- All possible response codes with schema examples (success and error)
- Authentication requirements
- Rate limiting information (if applicable)
- At least one complete cURL usage example

Refactor the following {{language}} code to improve {{refactor_goal}} while preserving all existing behavior.

**Refactoring goal:** {{refactor_goal}}
(e.g., "eliminate duplication", "apply SOLID principles", "improve testability", "reduce cyclomatic complexity")

**Original code:**
```{{language}}
{{code}}
```

Output:
1. **Refactored code** — clean, idiomatic {{language}}
2. **Change summary** — bullet list of what changed and why
3. **Behavioral equivalence proof** — explain why the refactored version is functionally identical
4. **Trade-offs** — any downsides introduced by the refactoring

Design a scalable system architecture for the following requirement.

**Project:** {{project_name}}
**Description:** {{project_description}}
**Scale:** {{expected_scale}} (e.g., "10k DAU", "1M events/day")
**Constraints:** {{constraints}} (e.g., "must run on AWS", "budget < $500/mo", "GDPR compliant")

Deliver:
1. **High-level architecture diagram** — described in structured text/ASCII
2. **Component breakdown** — each service/component with its responsibility
3. **Data model** — core entities and relationships
4. **Technology choices** — with rationale for each decision
5. **Scalability plan** — how the system evolves from MVP to production scale
6. **Failure modes** — top 3 risks and mitigation strategies

Professional product photography of {{product_name}}, {{product_material}} material, placed on {{background_surface}}, studio lighting with soft diffused key light from upper left and subtle rim light from right, shallow depth of field with the product in sharp focus, {{color_palette}} color palette, shot with an 85mm macro lens, ultra-high resolution, commercial advertising quality, clean minimal composition, no watermarks, photorealistic.

Detailed portrait of {{character_description}}, {{art_style}} art style, {{mood}} mood, dramatic cinematic lighting, intricate facial details, expressive eyes, {{color_scheme}} color scheme, professional illustration, high detail, 4K resolution, trending on ArtStation, by {{artist_influence}} influence.

Character details:
- Age: {{age}}
- Occupation: {{occupation}}
- Key trait: {{key_trait}}

Breathtaking landscape of {{location_type}}, {{time_of_day}}, {{weather_condition}}, {{season}} season, cinematic composition with {{foreground_element}} in the foreground and {{background_element}} in the background, {{lighting_style}} lighting, {{color_mood}} color mood, ultra-detailed, photorealistic, National Geographic quality, 16:9 aspect ratio.

Minimalist logo design for {{brand_name}}, a {{industry}} company. The logo should convey {{brand_values}} (e.g., "trust, innovation, simplicity"). Style: {{logo_style}} (e.g., wordmark, lettermark, icon, combination mark). Color palette: {{colors}}. The design must work at small sizes (favicon) and large sizes (billboard). Vector style, clean lines, white background, no gradients, SVG-ready.

Photorealistic interior design visualization of a {{room_type}} in {{design_style}} style. Room dimensions: {{room_size}}. Key features: {{key_features}}. Color palette: {{color_palette}}. Lighting: {{lighting_type}} with natural light from {{window_direction}}-facing windows. Materials: {{materials}}. The render should look like an architectural visualization from a professional interior design studio, high-end quality, no people.

Write a comprehensive, SEO-optimized blog post on the topic: "{{topic}}"

**Target audience:** {{target_audience}}
**Tone:** {{tone}} (e.g., professional, conversational, authoritative)
**Target length:** {{word_count}} words
**Primary keyword:** {{primary_keyword}}
**Secondary keywords:** {{secondary_keywords}}

Structure:
- Compelling H1 title (include primary keyword naturally)
- Hook introduction that establishes pain point or curiosity gap
- 4-6 main sections with H2 headings
- Practical examples, data points, or case studies where relevant
- Actionable takeaways in each section
- Strong conclusion with clear call-to-action
- SEO meta description (150-160 characters)

Write in active voice. Avoid filler phrases and corporate jargon.

Write a technical deep-dive article about {{technical_topic}} targeting {{audience_level}} (beginner/intermediate/advanced) developers.

**Publication:** {{publication}} (e.g., dev.to, company engineering blog)
**Prerequisites:** {{prerequisites}}
**Key concepts to cover:** {{concepts}}

Requirements:
- Start with a real-world problem that motivates the topic
- Include working code examples in {{language}}
- Explain the "why" behind every design decision
- Include at least one diagram description (ASCII or Mermaid)
- Address common mistakes and misconceptions
- End with further reading resources

Length: approximately {{word_count}} words. Technically accurate — no hand-waving.

Write a {{newsletter_type}} newsletter edition for {{brand_name}}'s {{audience_description}} subscribers.

**Edition theme:** {{theme}}
**Send date context:** {{date_context}} (e.g., "Q3 recap", "product launch week")
**Tone:** {{tone}}
**Target open-click rate:** high engagement

Include:
1. **Subject line** (A/B test: provide 3 options, each under 50 characters)
2. **Preview text** (under 100 characters)
3. **Opening hook** (2-3 sentences, personal and direct)
4. **Main content section** — {{main_content_description}}
5. **Secondary section** — quick links, tips, or curated resources
6. **CTA** — one clear primary call-to-action: {{cta_goal}}
7. **Closing** — warm, on-brand sign-off

Avoid spam trigger words. Write for a mobile-first reader.

Write a professional case study for {{company_name}} about how they used {{solution}} to achieve {{outcome}}.

**Industry:** {{industry}}
**Company size:** {{company_size}}
**Challenge:** {{challenge}}
**Solution:** {{solution}}
**Results:** {{quantified_results}}
**Testimonial contact:** {{contact_name}}, {{contact_title}}

Structure:
- Executive Summary (100 words)
- The Challenge — paint the pain point vividly
- The Solution — how it was implemented, what changed
- Results — lead with numbers (%, $, time saved)
- Testimonial quote (write a realistic attributed quote)
- About {{company_name}} sidebar (3 sentences)

Tone: credible and factual. No superlatives without data backing.

Write a concise executive summary for the following document.

**Document type:** {{document_type}} (e.g., business plan, research report, project proposal)
**Primary audience:** {{audience}} (e.g., C-suite, board of directors, investors)
**Decision required:** {{decision}} (e.g., "approve $2M budget", "greenlight market expansion")

Key information:
{{key_points}}

The executive summary must:
- Be no longer than one page (≈300-400 words)
- Lead with the most critical finding or recommendation
- Include the business case with supporting data
- State the ask clearly and early
- Use plain language — no jargon
- End with the next step and timeline

Write for someone who will only read this page.

Write original song lyrics in the style of {{artist_or_genre}} for a {{mood}} song called "{{song_title}}".

**Theme:** {{theme}} (e.g., "finding courage after loss", "city life at 3am")
**Structure:** {{structure}} (e.g., Verse-Chorus-Verse-Chorus-Bridge-Chorus)
**Tempo feel:** {{tempo}} (e.g., slow ballad, mid-tempo, uptempo)
**Key emotional arc:** starts {{starting_emotion}}, resolves to {{ending_emotion}}

Requirements:
- Verse 1: establish the scene with concrete imagery
- Chorus: hook must be instantly memorable, max 8 words in title line
- Bridge: emotional turn or revelation
- Consistent rhyme scheme throughout (specify the scheme used)
- Avoid clichés — use unexpected, specific metaphors
- Include internal rhyme where possible

Write a professional music review for "{{album_or_track_title}}" by {{artist_name}}, released {{release_date}}.

**Genre:** {{genre}}
**Publication:** {{publication}} (e.g., Pitchfork, Rolling Stone, personal blog)
**Rating scale:** {{rating_scale}} (e.g., out of 10, star rating)

Review must cover:
- Opening paragraph: context (where the artist is in their career, listener expectations)
- Production analysis: sonic palette, instrumentation, production choices
- Songwriting: lyrical themes, structural choices, standout moments
- Performance: vocal/instrumental delivery
- At least 2 specific track deep-dives with timestamps
- Comparison to artist's catalog or genre peers
- Final verdict with rating

Tone: critically engaged but accessible. Assume the reader has heard the album once.

Develop a cohesive album concept for a {{genre}} artist named {{artist_name}}.

**Core theme:** {{core_theme}}
**Emotional journey:** {{emotional_arc}} (the album's beginning-to-end feeling)
**Target audience:** {{target_audience}}
**Era/aesthetic:** {{aesthetic}} (e.g., "retrofuturism", "pastoral folk", "urban dystopia")

Deliver:
1. **Album title** and its meaning
2. **Concept statement** (3-5 sentences, press-release style)
3. **Track listing** — 10-12 tracks with titles and 1-sentence descriptions showing narrative arc
4. **Production direction** — sonic palette, key instruments, influences
5. **Visual/art direction** — cover art concept, color palette, visual motifs
6. **Singles strategy** — which 3 tracks to release first and why

Analyze the following chord progression and explain its emotional character and theoretical construction.

**Progression:** {{chord_progression}} (e.g., "Am - F - C - G", "ii-V-I in C major")
**Key:** {{key}}
**Genre context:** {{genre}}
**Tempo:** {{tempo}} BPM

Provide:
1. **Roman numeral analysis** — functional harmony breakdown
2. **Emotional character** — what feelings this progression evokes and why
3. **Notable usage** — 3 well-known songs using this or a similar progression
4. **Variation suggestions** — 3 alterations (e.g., substitutions, extensions, borrowed chords) with their effect
5. **Melody suggestion** — scale or mode that works best over it

Write a compelling opening scene for a {{genre}} story.

**Protagonist:** {{protagonist_description}}
**Setting:** {{setting}} (time, place, atmosphere)
**Opening conflict or tension:** {{initial_tension}}
**Narrative POV:** {{pov}} (first-person, third-person limited, omniscient)
**Tone:** {{tone}} (e.g., haunting, darkly comedic, urgent, lyrical)

Requirements:
- Open in medias res or with immediate sensory immersion — no "it was a dark and stormy night" exposition
- Establish protagonist voice within the first paragraph
- Plant at least one mystery or unanswered question that compels the reader forward
- Show, don't tell — use concrete sensory details
- Length: 400-600 words
- End the excerpt at a moment of tension or revelation

Create a psychologically rich character biography for a {{genre}} story.

**Character name:** {{character_name}}
**Role in story:** {{role}} (protagonist, antagonist, mentor, foil)
**Age at story start:** {{age}}
**Setting/world:** {{world}}

Biography must include:
- **Backstory** — formative childhood events that shaped their worldview
- **Core wound** — the unhealed psychological injury driving their behavior
- **Want vs. Need** — what they think they want vs. what they actually need
- **Competencies** — 3 genuine strengths (avoid making them wish fulfillment)
- **Fatal flaw** — the character trait that will create conflict
- **Relationships** — 3 key people in their life and the dynamic with each
- **Voice sample** — 5 lines of dialogue that instantly reveal their personality
- **Character arc** — how they change (or refuse to change) over the story

Build a detailed fictional world for a {{genre}} story set in {{setting_description}}.

**Scale:** {{scale}} (e.g., single city, continent, galaxy)
**Tone/feel:** {{tone}} (e.g., grimdark, hopepunk, solarpunk, noir)
**Central conflict driving the world:** {{world_conflict}}

Develop:
1. **Geography & Environment** — physical layout, climate, notable locations
2. **Power Structures** — who holds power, how, and who challenges it
3. **Economy** — what people trade, scarce resources, economic fault lines
4. **Culture & Society** — beliefs, customs, taboos, social stratification
5. **History** — 3 major historical events that still shape the present
6. **Magic/Technology System** — rules, limitations, and costs (if applicable)
7. **The Everyday** — what ordinary people eat, wear, fear, and celebrate
8. **Story hooks** — 5 conflicts that could drive plots in this world

Generate 5 original, dramatically satisfying plot twists for the following story setup.

**Genre:** {{genre}}
**Story so far:** {{story_summary}}
**Main characters:** {{main_characters}}
**Themes:** {{themes}}
**Current act:** {{current_act}} (beginning/middle/end)

For each twist provide:
- **The twist** — stated plainly
- **Setup required** — what foreshadowing seeds must be planted earlier
- **Emotional impact** — what the reader/viewer will feel
- **Consequence** — how it changes the story's direction and characters
- **Risk** — what could make this twist feel cheap or unearned, and how to avoid it

Prioritize twists that recontextualize earlier events rather than introducing new information.

Write a tense, character-revealing dialogue scene between {{character_a}} and {{character_b}}.

**Scene context:** {{scene_context}}
**Subtext goal:** {{subtext}} — what each character wants but won't say directly
**Setting:** {{setting}} — include 2-3 action beats grounding characters in the space
**Conflict type:** {{conflict_type}} (e.g., power struggle, reconciliation, revelation, seduction)
**Outcome:** {{outcome}} — how the scene must end

Rules:
- Each character must have a distinct voice — vary sentence length, vocabulary, rhythm
- Characters should talk past each other at least once
- Include at least one moment where what's unsaid is louder than what's said
- No dialogue tags beyond "said" unless action beats replace them
- Length: 400-600 words

Write a professional email for the following situation.

**Sender:** {{sender_name}}, {{sender_title}} at {{sender_company}}
**Recipient:** {{recipient_name}}, {{recipient_title}} at {{recipient_company}}
**Relationship:** {{relationship}} (e.g., "existing client", "cold outreach", "internal colleague")
**Purpose:** {{email_purpose}}
**Key message:** {{key_message}}
**Desired outcome:** {{desired_outcome}}
**Tone:** {{tone}} (e.g., formal, warm-professional, direct)

Requirements:
- Subject line: specific, ≤60 characters, no clickbait
- Opening: context-appropriate, no "I hope this email finds you well"
- Body: get to the point within 3 sentences
- One clear ask or CTA — not multiple
- Closing: appropriate to relationship
- Total length: ≤200 words

Write a compelling project proposal for internal stakeholder approval.

**Project name:** {{project_name}}
**Proposed by:** {{proposer}} / {{team}}
**Budget request:** {{budget}}
**Timeline:** {{timeline}}
**Executive sponsor:** {{sponsor}}

The proposal must address:
1. **Executive Summary** — 3 sentences: problem, solution, expected ROI
2. **Problem Statement** — quantify the pain with data (use {{metrics}} as basis)
3. **Proposed Solution** — what you'll build/do and how
4. **Success Metrics** — 3-5 measurable KPIs with targets
5. **Timeline & Milestones** — phase-by-phase breakdown
6. **Resource Requirements** — budget, headcount, tools
7. **Risk Assessment** — top 3 risks with mitigation plans
8. **ROI Analysis** — expected financial or strategic return

Anticipate and pre-answer the most likely objections from {{primary_objector_role}}.

Write a fair, balanced, and constructive performance review for {{employee_name}}.

**Review period:** {{review_period}}
**Employee role:** {{role}}
**Manager:** {{manager_name}}
**Overall rating:** {{rating}} (e.g., "Exceeds Expectations", "Meets Expectations", "Needs Improvement")

Accomplishments to highlight:
{{accomplishments}}

Areas for development:
{{development_areas}}

The review must:
- Lead with specific, evidence-based observations — no vague statements
- Connect individual contributions to team/company outcomes
- Frame development areas as opportunities, not criticisms
- Include 2-3 specific, actionable development goals with timelines
- End with a forward-looking statement about potential
- Tone: honest, supportive, professional
- Length: 400-600 words

Write a highly personalized cold outreach message to {{prospect_name}} at {{prospect_company}}.

**Sender:** {{sender_name}}, {{sender_company}}
**Product/Service:** {{offering}}
**Prospect's likely pain point:** {{pain_point}}
**Personalization hook:** {{personalization}} (e.g., "saw their recent Series B announcement", "read their article on X")
**Channel:** {{channel}} (LinkedIn, email, Twitter DM)

Requirements:
- First line: mention the personalization hook — show you did your homework
- Problem: articulate their pain point better than they could themselves
- Solution: one-sentence value proposition (no feature lists)
- Social proof: one specific result (e.g., "helped {{reference_client}} reduce {{metric}} by {{percentage}}")
- CTA: low-friction ask — a question or 15-min call option, not a demo request
- Total length: ≤150 words for email, ≤80 words for LinkedIn/social
- No "I" as the first word

Write a compelling investor pitch narrative for {{company_name}}'s {{funding_round}} raise.

**Company:** {{company_name}} — {{one_liner}}
**Sector:** {{sector}}
**Stage:** {{stage}}
**Ask:** {{raise_amount}} at {{valuation}} valuation
**Key traction:** {{traction_metrics}}

Cover the classic pitch arc:
1. **The Problem** — make the investor feel the pain (market size: {{tam}})
2. **The Solution** — why now, why this approach
3. **Product** — what it does and why users love it
4. **Traction** — {{traction_metrics}} (lead with the most impressive number)
5. **Business Model** — how you make money, unit economics
6. **Market** — TAM/SAM/SOM with credible sources
7. **Team** — why you are uniquely positioned to win
8. **The Ask** — what you'll do with {{raise_amount}} and the milestones it unlocks

Tone: confident, data-driven, narrative-led. No buzzwords without substance.

Write high-engagement social media content for {{brand_name}} to post on {{platform}}.

**Topic/campaign:** {{topic}}
**Target audience:** {{target_audience}}
**Goal:** {{goal}} (e.g., "drive traffic to blog", "increase signups", "build brand awareness")
**Brand voice:** {{brand_voice}} (e.g., witty, authoritative, empathetic)
**CTA:** {{cta}}

Deliverables (all variants):
1. **{{platform}} post** — optimized length for platform, includes {{hashtag_count}} relevant hashtags
2. **Hook variants** — 3 alternative first lines (hook is the most important element)
3. **Image/visual direction** — describe the ideal accompanying visual
4. **Best posting time** — recommend based on {{platform}} algorithm behavior

For Twitter/X: write a thread version (5-7 tweets) in addition to the single-tweet version.

Write conversion-optimized ad copy for {{product_or_service}} targeting {{target_audience}}.

**Platform:** {{ad_platform}} (e.g., Google Search, Facebook/Meta, LinkedIn)
**Campaign objective:** {{objective}} (e.g., conversions, leads, awareness)
**USP:** {{unique_selling_proposition}}
**Offer:** {{offer}} (e.g., "free trial", "30% off", "free consultation")
**Budget tier:** {{budget}} (informs copy complexity)

Deliver:
- **Headline** (3 variants, ≤30 characters each for Google; ≤40 for Meta)
- **Primary text/description** (≤90 characters for Google; ≤125 for Meta)
- **Long-form description** (for display ads, ≤200 characters)
- **CTA button text** (3 options)
- **Emotional trigger used** — name it and explain why it works for this audience
- **A/B test recommendation** — what single variable to test first

Write a persuasive product description for {{product_name}} that converts browsers into buyers.

**Product:** {{product_name}}
**Category:** {{category}}
**Price point:** {{price}}
**Target buyer:** {{target_buyer}}
**Key features:** {{features}}
**Primary benefit:** {{primary_benefit}}
**Tone:** {{tone}}

Deliverables:
1. **SEO title** (60 characters max, include primary keyword {{seo_keyword}})
2. **Short description** (50-80 words) — benefit-led, emotional hook
3. **Long description** (200-300 words) — full story: problem → solution → transformation
4. **Bullet points** (5-7) — features translated into benefits, scannable
5. **Meta description** (150-160 characters)

Lead with transformation ("Imagine…" / "Finally…"), not features. Every sentence must earn its place.

Create a 4-week content calendar for {{brand_name}} targeting {{target_audience}} across {{platforms}}.

**Goals:** {{content_goals}}
**Brand pillars:** {{brand_pillars}} (e.g., "education, inspiration, community, product")
**Key dates/events this month:** {{key_dates}}
**Content mix rule:** 80% value / 20% promotional

For each week provide:
- **Weekly theme** aligned to brand pillars
- **Daily post plan**: date, platform, format (video/image/text/story), topic, brief description
- **Content ratios**: educational : entertainment : promotional
- **Repurposing map**: how one piece of content becomes 3+

Output as a structured table. Flag {{key_dates}} with ⚡ to indicate high-opportunity days.

Design a {{sequence_length}}-email drip campaign for {{brand_name}} targeting {{segment}}.

**Campaign goal:** {{campaign_goal}} (e.g., "convert trial users to paid", "re-engage churned customers")
**Trigger:** {{trigger}} (e.g., "user signs up for free trial", "no login for 14 days")
**Brand voice:** {{brand_voice}}

For each email provide:
- **Send timing** (e.g., "Day 0 — immediately", "Day 3 — morning")
- **Subject line** (3 variants to A/B test)
- **Preview text**
- **Email body** (full copy)
- **Primary CTA**
- **Segment condition** — when to stop the sequence for a given contact

Psychological framework: each email should move the prospect one step closer to {{campaign_goal}} using a specific trigger (curiosity, social proof, urgency, loss aversion, reciprocity).

Create a detailed lesson plan for teaching {{topic}} to {{grade_level}} students.

**Subject:** {{subject}}
**Duration:** {{duration}} minutes
**Learning objectives:** By the end of this lesson, students will be able to {{learning_objectives}}
**Prior knowledge required:** {{prerequisites}}
**Class size:** {{class_size}} students

Lesson plan structure:
1. **Hook / Engagement** ({{hook_duration}} min) — activity to activate prior knowledge
2. **Direct Instruction** ({{instruction_duration}} min) — key concepts with examples
3. **Guided Practice** ({{guided_duration}} min) — teacher-led activity
4. **Independent Practice** ({{independent_duration}} min) — student activity
5. **Assessment** — formative check: how will you know if learning occurred?
6. **Closure** (5 min) — summary and preview of next lesson
7. **Differentiation** — modifications for advanced and struggling learners
8. **Materials needed** — complete list

Explain {{concept}} to a {{audience_level}} (beginner/intermediate/expert) audience.

**Domain:** {{domain}}
**Context:** {{context}} (e.g., "student learning it for the first time", "professional needing a refresher")
**Explanation style:** {{style}} (e.g., use analogy, step-by-step, Socratic, first-principles)

Your explanation must:
1. Start with the simplest possible version of the concept (the "kernel")
2. Use a concrete, relatable analogy that maps to the audience's existing experience
3. Build complexity incrementally — each paragraph adds one new layer
4. Include a worked example that makes the abstract tangible
5. Anticipate and address the #1 most common misconception
6. End with a self-check question the reader can use to verify understanding

Avoid jargon unless explained. If technical terms are necessary, define them inline.

Generate a {{question_count}}-question quiz on {{topic}} for {{audience}}.

**Difficulty:** {{difficulty}} (easy/medium/hard/mixed)
**Question types:** {{question_types}} (multiple choice, true/false, short answer, fill-in-the-blank)
**Learning objectives tested:** {{objectives}}

For each question provide:
- The question (clearly worded, unambiguous)
- All answer choices (for multiple choice — 4 options, one correct)
- **Correct answer** clearly marked
- **Explanation** — why the correct answer is right and why distractors are wrong
- **Cognitive level** — recall, comprehension, application, analysis, synthesis

Ensure questions test different cognitive levels (not all recall). Distractors must be plausible — not obviously wrong.

Provide constructive, growth-oriented feedback on the following student work.

**Assignment:** {{assignment_description}}
**Student level:** {{grade_level}}
**Student work:**
---
{{student_work}}
---

**Assessment criteria:** {{rubric_criteria}}

Feedback structure (follow this exactly):
1. **Strengths** — start with 2-3 genuine, specific positives (not generic praise)
2. **Primary area for growth** — the single most impactful thing to improve, with a clear example
3. **Secondary feedback** — 1-2 additional observations
4. **Concrete next step** — one specific, actionable revision task the student can do today
5. **Encouraging close** — motivational but honest

Tone: warm, direct, honest. Address the student directly ("You..."). Avoid "sandwich" praise that buries criticism.

Create a comprehensive study guide for {{exam_or_topic}} targeting {{student_level}} students.

**Subject:** {{subject}}
**Time available to study:** {{study_time}}
**Key topics to cover:** {{topics}}
**Exam format:** {{exam_format}} (e.g., multiple choice, essay, problem sets)

Study guide must include:
1. **Priority map** — rank topics by importance/weight on exam
2. **Core concepts** — concise definitions and explanations for each key term
3. **Common formulas/frameworks** — if applicable
4. **Memory aids** — mnemonics, visual associations, or patterns for hard-to-remember facts
5. **Practice questions** — 2 per major topic with answers
6. **Common traps** — mistakes students make on exams for this material
7. **Study schedule** — day-by-day plan for {{study_time}}
8. **Quick review** — one-page summary of the most critical points

Write a structured literature review on {{research_topic}} for a {{document_type}} (e.g., academic paper, policy brief, internal report).

**Scope:** {{scope}} (e.g., "peer-reviewed publications 2015-2024", "industry reports and grey literature")
**Research question:** {{research_question}}
**Audience:** {{audience}}
**Length:** approximately {{word_count}} words

Structure:
1. **Introduction** — define scope, explain the review's purpose, state the research question
2. **Thematic synthesis** — group literature into {{theme_count}} major themes, not a list of summaries
3. **Agreements and debates** — what do scholars agree on? Where does evidence conflict?
4. **Gaps in the literature** — what has not been studied? What methodological limitations exist?
5. **Implications** — what does the literature suggest for practice or future research?
6. **Reference notes** — cite sources as [Author, Year] placeholders

Note: Generate a realistic synthesis. Flag any claim that would require specific citation with [CITATION NEEDED].

Summarize the following research paper/report for a {{audience}} audience.

**Paper title:** {{paper_title}}
**Authors:** {{authors}}
**Publication:** {{publication}}

**Abstract/key content:**
{{abstract_or_content}}

Summary requirements:
1. **One-sentence bottom line** — what is the single most important finding?
2. **Background** — why this research matters (2-3 sentences)
3. **Methodology** — how they studied it (without jargon)
4. **Key findings** — top 3-5 findings in plain language, with quantitative results where available
5. **Limitations** — what the study cannot tell us
6. **Implications** — so what? What should practitioners or policymakers do differently?
7. **Verdict** — how reliable and important is this research? Rate 1-5 with brief reasoning

Length: 300-400 words. No jargon. If a 12-year-old couldn't understand a sentence, rewrite it.

Design a rigorous interview question set for a {{research_type}} study on {{research_topic}}.

**Participant type:** {{participant_description}}
**Study goal:** {{study_goal}}
**Interview format:** {{format}} (structured, semi-structured, in-depth)
**Estimated duration:** {{duration}} minutes

Deliver:
1. **Introduction script** — how to open the interview, explain purpose, confirm consent
2. **Warm-up questions** (2-3) — low-stakes rapport builders
3. **Core questions** (8-12) — open-ended, non-leading, logically sequenced
4. **Probing prompts** — 3-5 follow-up probes usable after any main question
5. **Sensitive topic handling** — questions about {{sensitive_topics}}, with ethical framing
6. **Closing** — wrap-up question and interview close script

Each question must: start with "How", "What", "Tell me about", or "Describe" — not "Why" (which can feel accusatory). Flag questions that may be sensitive with ⚠️.

Conduct a structured competitive analysis for {{company_name}} in the {{market}} market.

**Our product/service:** {{our_product}}
**Key competitors to analyze:** {{competitors}}
**Strategic question:** {{strategic_question}} (e.g., "where should we focus product investment?")
**Timeframe:** {{timeframe}}

Analysis framework:
1. **Market overview** — size, growth rate, key trends, and disruption forces
2. **Competitor profiles** (one section per competitor):
   - Positioning & messaging
   - Product strengths and weaknesses
   - Pricing model
   - Target customer segment
   - Estimated market share / traction signals
3. **Competitive matrix** — compare all competitors on {{comparison_dimensions}} (create a table)
4. **Our position** — where {{company_name}} is strong, weak, and differentiated
5. **Strategic implications** — 3 actionable recommendations based on the gaps identified
6. **Monitoring plan** — what signals to track quarterly to keep this analysis current

Write a production-ready SQL query for the following business question.

**Database:** {{database_type}} (e.g., PostgreSQL, MySQL, BigQuery, Snowflake)
**Business question:** {{business_question}}

**Relevant tables and columns:**
{{schema_description}}

**Sample data context:** {{sample_data}}
**Performance constraints:** {{constraints}} (e.g., "table has 500M rows", "must run in <5s", "read replica")

Requirements:
- Write clear, readable SQL with meaningful aliases
- Add inline comments explaining non-obvious logic
- Use CTEs (WITH clauses) for complex queries instead of nested subqueries
- Include an EXPLAIN hint or index suggestion if the query may be slow
- Handle NULLs explicitly
- If there are multiple valid approaches, show the preferred one and briefly note the alternative

Write a data analysis report interpreting the following dataset findings.

**Dataset:** {{dataset_description}}
**Analysis performed:** {{analysis_type}} (e.g., cohort analysis, funnel analysis, regression, segmentation)
**Key findings:**
{{findings}}

**Business context:** {{business_context}}
**Audience:** {{audience}} (e.g., "marketing team", "C-suite", "data team")

Report structure:
1. **Executive Summary** — 3 bullet points: what we found, what it means, what to do
2. **Data overview** — describe the data, time period, and any quality caveats
3. **Key findings** — one section per major finding, with interpretation (not just description)
4. **Anomalies & caveats** — what could make these numbers misleading?
5. **Recommendations** — 3 specific, prioritized actions with expected impact
6. **Next steps** — what further analysis would answer the remaining questions?

Use plain language. Translate statistical findings into business impact.

Design a rigorous A/B test for the following hypothesis.

**Company/product:** {{company}}
**Hypothesis:** Changing {{change_description}} will {{expected_outcome}} because {{reasoning}}
**Metric to optimize:** {{primary_metric}} (and {{secondary_metrics}} as guardrails)
**Current baseline:** {{baseline_value}}
**Minimum detectable effect:** {{mde}} (the smallest change worth detecting)

Deliver a complete test design:
1. **Test setup** — control vs. treatment, traffic allocation, randomization unit (user/session/device)
2. **Sample size calculation** — required users per variant (show the formula and inputs)
3. **Duration** — estimated run time based on {{daily_traffic}} daily visitors
4. **Segmentation** — any segments to analyze separately
5. **Success criteria** — exact thresholds for calling the test a win, loss, or inconclusive
6. **Guardrail conditions** — when to stop the test early
7. **Implementation checklist** — what engineering needs to build
8. **Analysis plan** — statistical test to use (t-test, chi-square, etc.) and why

Design a analytics dashboard for {{team_name}} to monitor {{business_area}}.

**Primary users:** {{primary_users}}
**Decision this dashboard supports:** {{key_decision}}
**Data sources available:** {{data_sources}}
**Refresh frequency needed:** {{refresh_frequency}} (real-time, hourly, daily)

Dashboard specification:
1. **North Star metric** — the single most important number, displayed prominently
2. **KPI tiles** (6-8) — key metrics with period comparison and sparklines
3. **Trend charts** — time-series visualizations with appropriate granularity
4. **Breakdown views** — how to segment the data (by {{dimensions}})
5. **Alert thresholds** — conditions that should trigger a notification
6. **Filters** — date range, segment selectors the user needs
7. **Layout wireframe** — describe the visual hierarchy in structured text
8. **Data freshness indicator** — how to display when data was last updated

Prioritize actionable insights over vanity metrics. Every chart must answer a specific question.