Public Prompt Library

#ROLE: Strategic decision-making facilitator. #TASK: Help me make a decision between {{num_options}} options using a weighted decision matrix. #MY OPTIONS: {{options}} #STEP 1: CRITERIA Identify the key criteria for this decision. Ask me: - What matters most? (cost, time, quality, risk, scalability, etc.) - Weight each criterion 1-5 based on importance. #STEP 2: SCORE For each option, score it 1-5 on each criterion. #STEP 3: CALCULATE Multiply score × weight for each cell. Sum rows. Rank options. #STEP 4: STRESS TEST - Which assumption, if wrong, would change the winner? - What's the worst-case scenario for the top option? - Is there a hybrid approach that combines the best of multiple options? #DECISION CONTEXT: {{context}}

#ROLE: Product demo video scriptwriter. #TASK: Write a {{duration}}-second tutorial video script for {{product_name}}. #STRUCTURE: 1. **Hook (0-5s)**: Show the end result. What will users achieve? 2. **Problem (5-10s)**: The pain point this solves. 3. **Steps (10-{{duration-10}}s)**: Walkthrough key steps with screen recording directions. 4. **Outro (last 5s)**: Recap + CTA. #FOR EACH SCENE specify: - **Voiceover**: Exact narration text - **Visual**: What's on screen (UI screenshot, B-roll, text overlay) - **Duration**: Seconds for this scene - **Text overlay**: Any text shown (keep minimal) #PRODUCT: {{product_name}} #FEATURES TO SHOW: {{key_features}} #TARGET USER: {{target_user}}

Minimalist workspace photograph. A clean {{desk_type}} desk (oak / walnut / white lacquer) against a {{wall_color}} wall. On the desk: a {{laptop_type}} laptop slightly open, a ceramic mug with {{beverage}}, a small potted {{plant_type}}, and one hardcover book. Natural window light from the left creating soft shadows. Shot at 35mm, f/2.8, from a 45-degree angle showing depth. Color grade: muted, desaturated, warm whites. Style: Kinfolk magazine, wellness aesthetic. No clutter, no cables visible, no text. 4K resolution.

#ROLE: Technical writer specializing in developer documentation. #TASK: Generate API documentation for the following endpoint. #DOC SECTIONS: 1. **Summary**: One-line description of what the endpoint does. 2. **Endpoint**: Method + URL path 3. **Authentication**: Required? What type? 4. **Parameters**: Table with name, type, required, description 5. **Request Body**: JSON schema with example 6. **Response**: Success (200) with example, Error responses (4xx, 5xx) 7. **Rate Limits**: If applicable 8. **Code Examples**: cURL, JavaScript, Python #FORMAT: Clean Markdown, ready for a docs site. #ENDPOINT SPEC: - Method: {{method}} - Path: {{path}} - Purpose: {{purpose}} - Parameters: {{parameters}}

# RISEN Framework: Character Voice Consistency Checker **R — Role:** You are a senior fiction editor with 15+ years of experience in character voice consistency for publishers like Tor, HarperCollins, and indie serial fiction platforms. You specialize in dialogue diagnostics — catching voice drift before readers do. **I — Instructions:** You will build a comprehensive voice profile from sample dialogue, then audit new dialogue against that profile. Work methodically through each step. Do not skip the profile-building phase even if the dialogue seems straightforward. **S — Steps:** **STEP 1 — BUILD VOICE PROFILE** Analyze the sample dialogue and extract these six dimensions: 1. **Vocabulary Register**: Is the word choice simple, educated, technical, slang-heavy, archaic? Note specific examples and the reading-grade level equivalent. 2. **Sentence Architecture**: Short and punchy? Long and flowing? Mixed? What's the average sentence length? Do they use fragments, run-ons, or perfectly balanced clauses? 3. **Verbal Fingerprints**: Identify repeated words, filler words ("like," "look," "I mean"), catchphrases, or distinctive speech patterns (e.g., answering questions with questions, trailing off, interrupting themselves). 4. **Emotional Register**: Stoic, expressive, sarcastic, earnest, defensive, warm? How does emotion manifest — through word choice, sentence rhythm, or what they DON'T say? 5. **Subtext Patterns**: What do they avoid saying? How do they deflect, lie, or reveal truth indirectly? 6. **Anti-Voice List** (critical): Words, expressions, idioms, and emotional reactions that this character would NEVER use. Be specific — "formal jargon" is less useful than "would never say 'nevertheless' or 'furthermore.'" **STEP 2 — AUDIT NEW DIALOGUE** When new dialogue is provided, score it on a 1-10 consistency scale using these criteria: | Score | Meaning | Action | |-------|---------|--------| | 9-10 | Fully in voice | No changes needed | | 7-8 | Minor deviations | Small word-level fixes | | 5-6 | Noticeable drift | Rewrite suggested lines | | 3-4 | Significantly off | Flag and provide alternatives | | 1-2 | Wrong character | Full rewrite needed | For each deviation, cite the specific profile dimension violated and suggest a fix that brings it back into voice. **E — End Goal:** Deliver a voice profile that a writer can use as a living reference document across multiple chapters, co-writers, or serialized installments — plus a repeatable audit that catches voice drift before publication. **N — Narrowing:** - Do not rewrite entire scenes. Focus only on dialogue lines. - Do not comment on plot, pacing, or description unless it directly affects voice perception. - If the character has a known arc (e.g., becomes more guarded over time), note that voice evolution is expected — flag only inconsistent drift, not intentional character development. - For ensemble casts, build separate profiles per character and note when voices are bleeding into each other. **VARIABLES:** - CHARACTER NAME: {{character_name}} - SAMPLE DIALOGUE: {{sample_dialogue}} - NEW DIALOGUE TO CHECK: {{new_dialogue}}

Minimalist workspace photograph. A clean {{desk_type}} desk (oak / walnut / white lacquer) against a {{wall_color}} wall. On the desk: a {{laptop_type}} laptop slightly open, a ceramic mug with {{beverage}}, a small potted {{plant_type}}, and one hardcover book. Natural window light from the left creating soft shadows. Shot at 35mm, f/2.8, from a 45-degree angle showing depth. Color grade: muted, desaturated, warm whites. Style: Kinfolk magazine, wellness aesthetic. No clutter, no cables visible, no text. 4K resolution.

#ROLE: Technical writer specializing in developer documentation. #TASK: Generate API documentation for the following endpoint. #DOC SECTIONS: 1. **Summary**: One-line description of what the endpoint does. 2. **Endpoint**: Method + URL path 3. **Authentication**: Required? What type? 4. **Parameters**: Table with name, type, required, description 5. **Request Body**: JSON schema with example 6. **Response**: Success (200) with example, Error responses (4xx, 5xx) 7. **Rate Limits**: If applicable 8. **Code Examples**: cURL, JavaScript, Python #FORMAT: Clean Markdown, ready for a docs site. #ENDPOINT SPEC: - Method: {{method}} - Path: {{path}} - Purpose: {{purpose}} - Parameters: {{parameters}}

#ROLE: Fiction editor specializing in character voice consistency. #TASK: I will provide dialogue samples from a character. Create their voice profile, then check new dialogue for consistency. #STEP 1: PROFILE From the sample dialogue, identify: 1. **Vocabulary level**: Simple, educated, technical, slang-heavy? 2. **Sentence length**: Short and punchy? Long and flowing? 3. **Verbal tics**: Any repeated words, phrases, or speech patterns? 4. **Emotional register**: Stoic, expressive, sarcastic, earnest? 5. **What they would NEVER say**: Words/expressions out of character. #STEP 2: CHECK When I provide new dialogue, score it 1-10 for consistency and explain any deviations. #CHARACTER NAME: {{character_name}} #SAMPLE DIALOGUE: {{sample_dialogue}}

# Instagram Carousel Script Writer ## C — CONTEXT You are creating content for **{{brand_name}}**, a brand whose voice is **{{tone}}**. - **Topic:** {{topic}} - **Audience:** {{audience}} _(e.g., "beginner founders on Instagram", "mid-career marketers")_ - **Goal:** {{goal}} _(pick one: awareness / saves / profile visits / DMs — this decides the CTA)_ - **Platform constraints:** Instagram carousel, 4:5 portrait (1080×1350), text-safe margins, 1–10 slides (10 is the cap, not the target — stop sooner if the idea is done). ## R — ROLE You are a senior Instagram content strategist who has written carousels that routinely hit 6-figure reach. You write the way people actually save and share: one sharp idea per slide, scroll-stopping specificity, no generic advice ("be consistent", "add value") unless you can make it concrete in the same sentence. ## A — ACTION Write a complete carousel script for **{{topic}}**, tuned to **{{audience}}** and optimized for **{{goal}}**. **Anti-generic rule:** Every slide must pass the "could a lazy AI have written this?" test. If a line could appear in any brand's carousel about any topic, rewrite it. Specific examples > abstractions. Real numbers > vague claims. Contrarian-but-true > safe consensus. **Slide architecture (do not pad to fill — 7 strong beats beats 10 mediocre ones):** 1. **Hook (Slide 1)** — A pattern interrupt: a counterintuitive claim, a specific number, or a question that names the reader's exact frustration. Under 12 words. Must be readable in <2 seconds. 2. **Context (Slides 2–3)** — Why this matters *to {{audience}}* right now. Name the common mistake before giving the fix. 3. **Value (Slides 4–8)** — 3 to 5 points. **One idea per slide, hard cap 28 words.** Each point must be immediately actionable or genuinely surprising. 4. **Proof (Slide 9)** — One concrete datapoint, named case, or specific personal result. **No fabricated statistics.** If you don't have a source, write "[INSERT: your stat/source]" instead of inventing one. 5. **CTA (Slide 10)** — Choose the CTA from the **Goal** above: - *awareness* → "Share this with someone who needs it" - *saves* → "Save this for later" (save-bait works for educational content) - *profile visits* → "Follow @{{brand_name}} for more on {{topic}}" - *DMs* → "DM me '{{keyword}}' and I'll send you the full guide" ## F — FORMAT For **each slide**, output exactly these four fields (keep the structure rigid — it's what makes the script production-ready): ``` ### Slide N — [role: Hook / Context / Value / Proof / CTA] **Display text:** [exact words to appear on the graphic — respect the word cap] **Visual direction:** [layout, hierarchy, 1 dominant image or graphic idea, color cue aligned to {{brand_name}}'s identity, where the eye lands first] **Alt text:** [accessibility description of the slide — required] ``` After all slides, output **one** post caption block: ``` ### Caption **Hook line (first line, shows in feed):** [≤80 chars, must make someone want to swipe] **Body:** [≤180 chars total, expands the hook, ends on the CTA] **Hashtags:** [5–8 hashtags, mix of 1 broad + 3 niche + 1–4 community. No #like4like-style spam tags. Aligned to {{audience}}.] ``` **Output rules:** - Markdown only. No preamble ("Here's your carousel…"), no postamble. - If any required input is missing, ask for it before writing — do not guess `{{audience}}` or `{{goal}}`. - Word caps are hard. If you exceed one, cut, don't compress into jargon. ## T — TARGET The reader is **{{audience}}** — write at their knowledge level, not yours. A senior strategist reviewing this should think "this would actually perform", not "this is a reasonable first draft." Optimise for **saves and shares** (the signals Instagram's algorithm rewards for educational content), not just likes.

# ROLE You are a Senior Product Manager with 10+ years of experience shipping software at fast-moving product companies. You write PRDs that are clear, actionable, and unambiguous — documents that an engineering team can implement without follow-up meetings. You think in user outcomes first, scope second, and solutions third. # INSTRUCTIONS Write a complete Product Requirements Document (PRD) for the feature described below. The document must be self-contained, decision-ready, and structured so a newly onboarded engineer could start building from it. Do not invent user research — if research is not provided, state clearly what assumption you are making and flag it in the Open Questions section. Use Markdown throughout. Keep each section tight: every sentence should earn its place. Avoid filler, motivational language, and AI-isms like "In today's fast-paced world" or "It's important to note that." # STEPS Produce the document in this exact order. Do not skip, merge, or reorder sections. ## 1. Problem Statement - State the user problem in 2-3 sentences. - Quantify impact where possible (users affected, frequency, revenue/support cost). - If user research is provided, quote it directly. If not, write a labeled ASSUMPTION and flag it in §8. ## 2. Proposed Solution - Describe what we are building at a high level (1 paragraph, no implementation detail). - Explain why this approach over the obvious alternatives. ## 3. User Stories Write each in the form: *As a {{user_type}}, I want to {{action}} so that {{benefit}}.* - Group by user type. - Mark the primary story with ⭐. ## 4. Requirements Split into three tiers, each as a checklist: - **Must-have (MVP)** — required for launch. - **Should-have (Phase 2)** — important but not blocking. - **Could-have (Phase 3)** — nice-to-have, defer if time-constrained. Each requirement must be testable: "User can export CSV" ✓, "Better UX" ✗. ## 5. Success Metrics List 3-5 measurable outcomes with a target and a measurement method. Format: `Metric — Target — How measured (instrument/source)`. ## 6. Technical Considerations - API changes (new endpoints, breaking changes). - Data model / schema impact. - Performance, security, privacy, and accessibility notes. - Dependencies on other teams or systems. ## 7. Timeline & Milestones Propose phased delivery with estimated dates relative to a kick-off (T+0, T+2w, etc.). Include a one-line scope per milestone. State that these are estimates pending engineering review. ## 8. Open Questions List every unresolved decision, missing input, or cross-team dependency that must be resolved before build. Format as a numbered list of questions, each tagged with an owner role (e.g., `[Design]`, `[Eng]`, `[Legal]`). # END GOAL The reader — an engineer, designer, or stakeholder — should finish this document knowing: (1) what problem we're solving and for whom, (2) exactly what's in and out of scope for each phase, (3) how success will be measured, and (4) what decisions still need to be made. The document should be good enough to base a sprint plan on. # NARROWING (constraints) - **Length**: Aim for 800-1,500 words. Cut rather than pad. - **Tone**: Direct, professional, opinionated. No hedging. - **No fabrication**: Never invent metrics, quotes, or dates. Use `[TBD]` or `[ASSUMPTION: ...]` instead. - **Scope discipline**: If the feature idea is vague, narrow it to a reasonable MVP interpretation rather than trying to cover every possible direction. - **Output**: Markdown only. No preamble ("Sure, here's your PRD...") and no postamble ("Hope this helps!"). Start immediately with `# PRD: {{feature_name}}`. # INPUT - **Feature name**: {{feature_name}} - **Product name**: {{product_name}} - **Current problem / context**: {{current_problem}} - **Affected users**: {{affected_users}} - **(Optional) User research or quotes**: {{user_research}} - **(Optional) Known constraints** (deadline, budget, tech stack): {{constraints}}

#ROLE: Customer insights analyst. #TASK: Analyze the following {{num_reviews}} product reviews and extract actionable insights. #ANALYSIS: 1. **Overall Sentiment**: What % are positive, neutral, negative? 2. **Top 5 Praises**: What do happy customers love most? (rank by frequency) 3. **Top 5 Complaints**: What frustrates unhappy customers? (rank by severity) 4. **Feature Requests**: What do customers wish existed? 5. **Customer Segments**: Can you identify distinct user types from the reviews? 6. **Competitor Mentions**: Do any reviews mention alternatives? 7. **Action Items**: 5 specific recommendations for the product team #OUTPUT: Structured report with data tables and bullet points. #REVIEWS: {{reviews}}

#WORKFLOW: Generate a complete 10-slide pitch deck structure for {{startup_name}}. #STEP 1: STRUCTURE Create the slide-by-slide outline: 1. Title (name + tagline) 2. Problem (3 pain points with evidence) 3. Solution (how you solve it, with a visual) 4. Market (TAM/SAM/SOM with sources) 5. Product (key features, demo screenshots) 6. Traction (metrics, growth chart, key wins) 7. Business Model (how you make money) 8. Competition (2x2 matrix positioning) 9. Team (why YOU are the right people) 10. Ask (how much, what for, milestones) #STEP 2: CONTENT For each slide, write: - Headline (under 8 words) - Body text (under 30 words) - Visual direction (what image/chart goes here) #STEP 3: REFINEMENT Review for: - Narrative flow (does it tell a story?) - Clarity (can a non-expert understand?) - Credibility (are claims backed by data?) #STARTUP DETAILS: - Industry: {{industry}} - Stage: {{stage}} (pre-seed / seed / Series A) - Key differentiator: {{differentiator}}

Aerial drone cinematography shot plan for {{location_type}} (mountain range / city skyline / coastal area / forest / desert). Time of day: {{time_of_day}} (golden hour / blue hour / midday / night). Mood: {{mood}} (epic, serene, mysterious, energetic). Create a 5-shot sequence: 1. **Establishing shot**: Wide reveal of the landscape, slow ascending orbit 2. **Approach shot**: FPV-style dive toward a key feature, {{speed}} speed 3. **Detail shot**: Low-altitude flyover highlighting texture 4. **Transition shot**: Smooth climb revealing scale, looking back 5. **Closing shot**: High-altitude panoramic pullaway at {{altitude}}m For each shot specify: camera movement, altitude, speed, duration, and the visual story it tells. Style: cinematic, color-graded with {{color_grade}}. No text overlays.

Professional logo design brief for {{company_name}}. The company operates in the {{industry}} industry. Core values: {{values}} (e.g., trust, innovation, speed). The logo should feel {{personality}} (minimalist, bold, playful, luxurious). Style references: {{style_references}} (e.g., Stripe, Nike, Apple). Color preference: {{colors}} or open to suggestions. Must work at sizes from 16x16 favicon to billboard. Generate 5 distinct concept directions, each as a detailed visual description suitable for an AI image generator or human designer. Include typography recommendations for each concept. No clipart, no generic stock illustrations.

#ROLE You are an expert meeting analyst and executive assistant with years of experience distilling complex, fast-paced meetings into clear, actionable intelligence for busy teams. #CONTEXT The user has just attended {{meeting_type}} (e.g., "weekly engineering sync," "client kickoff call," "quarterly planning session") and needs to transform their raw, unstructured notes or transcript into a polished, shareable meeting debrief. Meeting participants: {{participants}} Meeting objective: {{meeting_objective}} #INSTRUCTIONS Analyze the following raw meeting notes and produce a comprehensive meeting debrief. The debrief must be structured, scannable, and immediately actionable. Do not omit any decisions, commitments, or risks mentioned. Raw meeting notes: --- {{meeting_notes}} --- #STEPS 1. **Executive Summary** — Write a 3-4 sentence overview of what was discussed and the key outcomes. 2. **Decisions Made** — List every decision agreed upon during the meeting. Use a bullet list. If no clear decision was reached on a topic, note it as "Unresolved." 3. **Action Items** — Extract every task or follow-up. Format each as: **[Owner]** — [Task description] — **Due:** [Deadline or "TBD"]. If an owner isn't specified, mark as **[Unassigned]**. 4. **Risks & Blockers** — Identify any risks, concerns, or blockers raised during the meeting. Include who raised them if known. 5. **Open Questions** — List any questions that were raised but not answered during the meeting. 6. **Parking Lot** — Capture any topics that were deferred, tabled, or acknowledged but not discussed in depth. 7. **Follow-up Email Draft** — Write a concise, professional email to all participants summarizing the meeting, highlighting decisions, and listing action items with owners. Use an appropriate subject line. Tone: {{email_tone}} (default: professional and friendly). #END GOAL Produce a single, well-structured debrief document that the user can immediately share with their team — no further editing required. #NARROWING CONSTRAINTS - Do not invent decisions, tasks, or information that is not present in the raw notes. - If a section has no relevant content (e.g., no risks were discussed), write "None identified" rather than omitting the section. - Use plain language. Avoid corporate jargon unless it appears in the source notes. - Keep the follow-up email under 200 words. - Preserve any specific dates, numbers, metrics, or names mentioned in the notes.

#ROLE: Learning experience designer who creates skill-building curricula. #TASK: Design a {{duration}}-week learning path for {{skill}}. #INPUTS: - Current level: {{current_level}} (beginner / intermediate / advanced) - Goal: {{learning_goal}} - Time available: {{hours_per_week}} hours/week - Learning style: {{learning_style}} (visual, hands-on, reading, mixed) #OUTPUT: 1. **Week-by-week plan** with: - Core concept to learn - Recommended resource (book, course, video) - Practical exercise or project - Milestone/checkpoint 2. **Resource list** ranked by priority (free first) 3. **Portfolio project** to build by the end 4. **Self-assessment rubric** for each phase

#ROLE: UX writer who creates clear, human microcopy for digital products. #TASK: Write microcopy for the following UI elements in a {{app_type}} app. #ELEMENTS: 1. **Empty state**: When user has no {{items}} yet 2. **Loading state**: While {{data}} is being fetched 3. **Error state**: When {{action}} fails 4. **Success state**: After {{action}} completes 5. **Delete confirmation**: Before removing {{item}} 6. **Onboarding tooltip**: First time seeing {{feature}} #FOR EACH ELEMENT: - Primary text (action-oriented, under 40 chars) - Secondary text (helpful context, under 80 chars) - Button label (verb-first, under 20 chars) #BRAND VOICE: {{voice}} (e.g., friendly, professional, playful)

#ROLE: Database performance engineer. #TASK: Analyze the following SQL query and optimize it. #ANALYSIS NEEDED: 1. **Execution Plan Prediction**: How will the database likely execute this? Full scan? Index usage? 2. **Bottlenecks**: What makes this query slow? 3. **Index Recommendations**: Which indexes should exist? 4. **Rewritten Query**: Provide an optimized version 5. **Expected Improvement**: Why is the new version faster? #DATABASE: {{database_type}} (PostgreSQL / MySQL / SQLite) #TABLE SIZES: {{table_sizes}} #QUERY: ```sql {{sql_query}} ```

#ROLE: Newsletter editor who writes welcome sequences that convert subscribers into loyal readers. #TASK: Write a 3-email welcome sequence for {{newsletter_name}}. #EMAIL 1 (Immediate): The Welcome - Deliver the lead magnet/freebie promised - Set expectations: what they'll get, how often - Share your origin story in 3 sentences - CTA: Hit reply and tell me about yourself #EMAIL 2 (Day 2): The Best Of - Link to 3 must-read past issues - Explain why each matters - CTA: Forward this to a friend #EMAIL 3 (Day 4): The Feedback Ask - Share a contrarian take related to {{topic}} - Ask: What's your biggest challenge with {{topic}}? - CTA: Reply with your answer #TONE: {{tone}} (conversational, expert, witty)

#ROLE: B2B sales copywriter specializing in cold email openers that get replies. #TASK: Write 5 cold email openers for reaching out to {{target_persona}} about {{product_or_service}}. #CONSTRAINTS: - Under 75 words each - No "I hope this finds you well" - No "My name is..." - Must reference something specific about THEIR situation (research-driven) - End with a low-friction question (not a demo request) #CONTEXT: - Sender: {{sender_name}} from {{company}} - Value prop: {{value_prop}} - Trigger event: {{trigger}} (e.g., funding round, new hire, product launch)

#WORKFLOW: Multi-step prompt chain for turning research into published content. ## STEP 1: RESEARCH Topic: {{topic}} Research latest developments, statistics, and expert opinions. Compile a fact sheet with 10 key data points with sources. ## STEP 2: ANGLE Based on research, identify 3 unique content angles that have not been overdone. For each, explain why it is interesting and who would care. ## STEP 3: DRAFT Selected angle: {{chosen_angle}} Write a {{content_format}} (800-1200 words). Hook in first 2 sentences. Include data points naturally. End with clear CTA. ## STEP 4: OPTIMIZE Review draft for SEO, readability (grade 8), engagement, and CTA effectiveness. Provide revised version with tracked changes. #USAGE: Run each step sequentially, using previous output as next input.

Cinematic product reveal video of {{product}}. Ultra slow-motion, dark seamless background, single dramatic spotlight. Product on reflective black surface. Camera slowly orbits 180 degrees. Volumetric light rays interact with product edges. Subtle particles drift through beam. Depth of field shifts. Color grade: high contrast, cool shadows, warm highlights. Duration: 5 seconds. Style: Apple product reveal. No text overlays.

Clean isometric 3D illustration of {{object}}, modern tech-startup style. Soft pastel palette with {{accent_color}} accent. Matte clay-render with subtle ambient occlusion. Clean white background. 30-degree isometric angle. Soft studio lighting from top-left. Minimal geometric details. Style: Stripe illustrations, Spline 3D. 2048x2048, sharp edges. No text.

Cinematic portrait photograph of {{subject}}, shot during golden hour. Subject positioned near a large window with warm amber light streaming through, casting soft directional shadows. Shallow depth of field (f/1.4), 85mm lens. Background: blurred bokeh of minimal studio with dust particles in light beams. Color grade: warm teal and orange, film grain, Kodak Portra 400 emulation. Subject expression: {{expression}}. Subtle rim light. Hyperrealistic, 8K. No text overlays.

#ROLE: Direct-response copywriter optimized for CTR and conversion. #TASK: Write {{num_variants}} ad copy variants for {{product_or_service}}. #PLATFORM: {{platform}} #VARIANTS (different psychological angles): 1. **Pain-Agitate-Solve**: Lead with the problem 2. **Aspirational**: Lead with the dream outcome 3. **Social Proof**: Lead with credibility 4. **Curiosity Gap**: Lead with unexpected claim 5. **Scarcity/Urgency**: Lead with time-sensitivity #FOR EACH: Headline (<40 chars), Primary text (<125 chars), CTA, Why it works. #CONSTRAINT: No buzzwords. Specific numbers over adjectives.

#ROLE: Social media strategist building engagement-driven content calendars. #TASK: Create a {{timeframe}} content calendar for {{brand_or_product}}. #INPUTS: - Platform: {{platform}} - Audience: {{target_audience}} - Brand voice: {{brand_voice}} - Goal: {{goal}} - Frequency: {{frequency}} posts/week #OUTPUT: Week-by-week table: | Day | Post Type | Hook/Caption | Visual Direction | CTA | Hashtags | #POST TYPES: Educational, Entertaining, Promotional, Engagement, Storytelling #CONSTRAINT: No generic posts. Every post needs a specific hook.

#ROLE: Staff-level software architect documenting technical decisions. #TASK: Write an Architecture Decision Record (ADR) for: {{decision_summary}} #ADR FORMAT: 1. **Title**: Short noun phrase 2. **Status**: Proposed | Accepted | Deprecated 3. **Context**: What is the issue? 4. **Decision**: What change are we making? 5. **Alternatives Considered**: 2-3 alternatives with pros/cons 6. **Consequences**: Positive, negative, neutral 7. **Compliance**: How to verify #INPUTS: - System: {{system_name}} - Constraint: {{key_constraint}} - Team size: {{team_size}}

#ROLE: Senior software engineer performing a thorough code review. #REVIEW CHECKLIST: 1. **Bugs & Logic Errors**: Runtime errors, edge cases, logic flaws 2. **Security**: Injection, XSS, auth issues, secret leaks 3. **Performance**: N+1 queries, allocations, complexity 4. **Readability**: Naming, structure, dead code 5. **Testing**: Missing test cases 6. **Architecture**: Separation of concerns #FORMAT: Severity levels (Critical/Warning/Suggestion/Nitpick). Show line, problem, fix. #LANGUAGE: {{language}} #CODE: ```{{language}} {{code}} ```

#ROLE: Business strategy consultant specializing in competitive intelligence. #CONTEXT: Analyze the competitive landscape for: {{company_or_product}} #FRAMEWORK: Analyze each competitor across: Product/Service, Pricing, Target Market, Strengths, Weaknesses, Strategy. #OUTPUT: 1. **Competitor Matrix** (comparison table) 2. **SWOT** for top 3 competitors 3. **White Space Opportunities**: Gaps no one serves 4. **Strategic Recommendations**: 3 actionable moves #COMPETITORS: {{competitor_list}}

#ROLE: Research analyst skilled at synthesizing multiple sources. #CONTEXT: I will provide {{num_sources}} sources. Synthesize them into a coherent overview. #TASK: 1. **Key Findings**: 5-7 bullet points of collective insights 2. **Areas of Consensus**: Where sources agree 3. **Areas of Conflict**: Where they disagree 4. **Methodology Notes**: Strength of evidence 5. **Gaps**: Unanswered questions 6. **Implications**: Why this matters for {{field}} #OUTPUT: Structured Markdown. Cite source numbers. #SOURCES: {{sources}}

#ROLE: Master storyteller specializing in narrative hooks. #TASK: Generate 10 compelling story hooks for a {{genre}} story with the theme of "{{theme}}". #HOOK TYPES to include: - **Action**: Start mid-scene - **Dialogue**: Start with a striking line - **Mystery**: Pose an irresistible question - **Character**: Introduce through a telling detail - **World**: Drop into a vivid setting - **Contradiction**: State something impossible #FORMAT: Numbered list, 2-4 sentences each. No cliches. No dream sequences.

#ROLE: You are a content strategist and SEO specialist. #TASK: Create a detailed blog post outline for the topic: "{{topic}}" #REQUIREMENTS: 1. **Target keyword**: {{primary_keyword}} 2. **Search intent**: {{search_intent}} 3. **Target audience**: {{audience}} 4. **Word count goal**: {{word_count}} words #DELIVERABLES: 1. **Title options** (5 variations, each under 60 characters) 2. **Meta description** (under 155 characters) 3. **Outline** with H2/H3 headers and brief descriptions 4. **Internal linking suggestions** 5. **FAQ section**: 4-5 common questions

#CONTEXT: You are an Email Triage Assistant. I will paste emails below. For each email, classify and draft a response. #RULES: 1. **Classify**: [URGENT / ACTION NEEDED / FYI / SPAM / NEWSLETTER] 2. **Summarize**: One sentence on what the email wants. 3. **Draft Reply**: Professional, concise (under 100 words). Use {{my_name}} as sender. 4. **Suggested Action**: What I should do after sending. #TONE: Professional but warm. Match the sender's formality level. #EMAILS TO PROCESS: {{email_content}}

#ROLE: You are a productivity strategist who designs focused work schedules using deep work principles. #CONTEXT: I need a structured plan for my work {{timeframe}}. My inputs: - Available hours: {{available_hours}} - Top priorities: {{priorities}} - Meetings/existing commitments: {{commitments}} - Energy peaks: {{energy_pattern}} #TASK: 1. Design a daily schedule blocking out deep work sessions (90-min blocks minimum). 2. Assign each priority to specific time slots based on energy level. 3. Add buffer time between tasks (15 min). 4. Include a shutdown ritual at end of day. 5. Flag anything that can't fit and suggest what to cut. #OUTPUT FORMAT: Hour-by-hour table for each day.

#CONTEXT: You are a Meeting Intelligence Assistant. I will paste raw meeting transcripts, notes, or rough summaries. Your job is to extract structured, actionable output. #TASK: 1. **Summary** (3-5 sentences): What was discussed, decided, and why it matters. 2. **Decisions Made**: Bullet list of all decisions agreed upon. 3. **Action Items**: Table with columns [Owner, Task, Deadline, Priority]. 4. **Risks & Blockers**: Anything flagged as a concern or delay. 5. **Parking Lot**: Topics deferred for later discussion. #FORMAT: Clean Markdown with headers and a table for action items. #TRANSCRIPT: {{meeting_notes}}

#CONTEXT: I need you to complete multiple related tasks in a single response. Process all sections below and output each one clearly labeled. #ROLE: [INSERT ROLE - e.g., "You are a senior content strategist with 10 years of B2B SaaS experience"] #TASKS (complete all in one response): ## Task 1: [LABEL] [Specific instructions for task 1] ## Task 2: [LABEL] [Specific instructions for task 2] ## Task 3: [LABEL] [Specific instructions for task 3] #CONSTRAINTS: - [Constraint 1 - e.g., "Keep each section under 200 words"] - [Constraint 2 - e.g., "Use casual tone, no jargon"] - [Constraint 3 - e.g., "Include one specific example per task"] #OUTPUT FORMAT: Label each task clearly with the ## header. Separate sections with a line break. Complete ALL tasks before stopping.

#CONTEXT: You are a Conversation Compression Specialist. Your job is to extract all critical context from this conversation and compress it into a briefing document that can be pasted into a new chat without losing any important details. #ROLE: You are an expert at identifying what matters and discarding what doesn't. You preserve decisions, preferences, constraints, deliverables, and progress. You discard small talk, failed attempts, and redundant exchanges. #TASK: Analyze this entire conversation and produce a compressed briefing that includes: 1. Project Context: What we're working on and why 2. Decisions Made: Every choice or direction confirmed 3. Current Progress: What's been completed so far 4. Active Constraints: Rules, preferences, and specs 5. Next Steps: What needs to happen next 6. Key Outputs: Any finalized content (copy exact text) #FORMAT: Output a single briefing document. Use headers and bullets. Keep it under 500 words. Prioritize specifics over summaries. If exact wording was approved, include it verbatim. #TASK CRITERIA: - Do NOT summarize vaguely ("we discussed marketing") - DO include specifics ("Subject line approved: 'Free guide'", target audience: B2B SaaS founders, tone: casual") - If files or data were referenced, note what they contained - Flag anything unresolved or needing a decision

# Overview High-speed FPV Drone POV following a dynamically {{moving_object}} through a futuristic cyberpunk megacity at night, dominated by deep blue and red neon tones. ## Genre/Style * Cyberpunk Noir * High-Action Cinematic Realism ## Camera Movement/Action * Opening: The FPV drone races forward at high speed, initially positioned above an elevated highway. * Descent & Weaving: Swiftly descends, weaving dynamically between towering skyscrapers. * Low Dive: Dives low over highway lanes, with headlights streaking beneath. * Ascent & Wide Shot: Pulls up rapidly, ascending through a canyon of skyscrapers. The camera tilts slightly to capture a vast horizon of endless neon towers. * Stabilization: Stabilizes high above the city, providing a breathtaking wide shot of the glowing cyberpunk metropolis fading into mist. * Precision Maneuvers: Executes sharp, precise turns, banking close to glass facades. * Subject Focus: The drone continuously follows a fast-moving {{moving_object}} along its path, capturing its dynamic jumps and speed changes. ## Environment Setting Details ### Cityscape Towering, architecturally diverse skyscrapers forming a dense urban canyon. ### Highways/Traffic Elevated highways with fluid streams of autonomous vehicles. Roads are wet and highly reflective from rain. ### Advertising Numerous glowing digital billboards and large, animated holographic advertisements (futuristic brands, bars, virtual AI companions). Sleek holograms of women wave or interact with passersby, their neon colors refracting in the drizzle. ### Pedestrian Areas Glowing pedestrian sky bridges filled with silhouettes of people and holographic vendors. ## Atmosphere/Lighting ### Atmospheric Density Dense cinematic haze, rain mist, and ambient fog. ### Weather Heavy rain and drizzle, with raindrops streaking across the drone lens. ### Color Palette Dominant deep blue and red neon lighting throughout the cityscape. ### Light Effects Significant neon bloom and glow, especially reflecting on wet surfaces. Cinematic volumetric lighting. Realistic motion blur trails. ### Dynamic Lighting Rhythmic pulse of red signage and digital flicker from megatowers. Headlights streaking on the highway. ### Lens Effects Subtle lens flare. ## Visual Fidelity/Realism ### Textures Ultra-realistic textures across all surfaces. ### Shadows Deep, dramatic shadows. ### Reflections Vibrant neon reflections shimmering on all wet and reflective surfaces (glass facades, wet roads). ### Drone Simulation Subtle camera shake, aerodynamic motion, and g-force simulation to mimic a real FPV drone's thrust and movement. ## Looping Requirement The final shot should be a smooth upward pan into the skyline, designed to seamlessly transition back to the opening shot for a perfect, continuous loop.

A wide-angle, cinematic architectural photograph of a sophisticated content creator studio at dusk, rendered in photorealistic 8k resolution. The composition is anchored by a large industrial-style window on the left wall, admitting warm, golden-hour natural light that rakes across a bespoke solid walnut desk. The desk features a minimalist, high-end PC setup with dual color-calibrated monitors displaying creative software, a mechanical keyboard, and a professional audio interface. A textured grey fabric ergonomic office chair (resembling a Herman Miller Embody) is positioned at the station. The primary lighting is a cozy, ambient warm glow provided by strategically placed vintage-style standing floor lamps with exposed Edison bulbs and an articulating warm-toned desk lamp, creating inviting pools of orange light. Contrasting sharply with this warmth are precise cyan-blue LED strip accents hidden behind the monitors, under floating wooden shelves housing plants, camera gear, books, and washing over a textured concrete back wall, establishing a professional blue and orange cinematic color grade. The room is rich in tangible textures: reclaimed hardwood floors covered by a thick woven wool rug, acoustic felt wall panels, and leather desktop accessories. The image is captured with a professional DSLR aesthetic (e.g., 35mm lens, f/2.8 aperture), exhibiting a shallow depth of field focused on the desk equipment, natural lens flare from the window, and incredible micro-detail in wood grain, fabric fibers, and brushed metal surfaces. No cartoonish gamer aesthetics; the mood is elegant, focused, and inviting.

A wide-angle, cinematic architectural photograph of a sophisticated content creator studio at dusk, rendered in photorealistic 8k resolution. The composition is anchored by a large industrial-style window on the left wall, admitting warm, golden-hour natural light that rakes across a bespoke solid walnut desk. The desk features a minimalist, high-end PC setup with dual color-calibrated monitors displaying creative software, a mechanical keyboard, and a professional audio interface. A textured grey fabric ergonomic office chair (resembling a Herman Miller Embody) is positioned at the station. The primary lighting is a cozy, ambient warm glow provided by strategically placed vintage-style standing floor lamps with exposed Edison bulbs and an articulating warm-toned desk lamp, creating inviting pools of orange light. Contrasting sharply with this warmth are precise cyan-blue LED strip accents hidden behind the monitors, under floating wooden shelves housing plants, camera gear, books, and washing over a textured concrete back wall, establishing a professional blue and orange cinematic color grade. The room is rich in tangible textures: reclaimed hardwood floors covered by a thick woven wool rug, acoustic felt wall panels, and leather desktop accessories. The image is captured with a professional DSLR aesthetic (e.g., 35mm lens, f/2.8 aperture), exhibiting a shallow depth of field focused on the desk equipment, natural lens flare from the window, and incredible micro-detail in wood grain, fabric fibers, and brushed metal surfaces. No cartoonish gamer aesthetics; the mood is elegant, focused, and inviting.