400 ChatGPT Prompts
The Ultimate Free Library

Write a professional email: **Subject/Topic:** [[TOPIC]] **Recipient:** [[RECIPIENT]] (role/relationship) **Tone:** [[TONE]] (formal / friendly-professional / urgent) **Core message:** [[CORE_MESSAGE]] **Desired reaction:** [[REACTION]] Requirements: - Concise subject line (max. 50 characters) - Situationally appropriate greeting - Main text: clear, structured, no filler sentences - Concrete next step / CTA - Professional sign-off Also provide 2 alternative subject lines.

List [Number] ideas for blog posts about [Topic].

Schreibe den ersten Absatz von [Text] völlig neu. Starte mit einer konkreten Szene, einer Provokation oder dem Ergebnis. Lösche langweilige Einleitungen wie 'Es ist wichtig zu wissen...'.

Bitte stelle mir eine Liste mit den besten SEO-optimierten Blogtiteln für eine Website zur Verfügung, die [dein Produkt] verkauft.

Explain the following complex topic so that an interested layperson understands it immediately: **Topic:** [[TOPIC]] **Target audience:** [[AUDIENCE]] (prior knowledge: [[PRIOR_KNOWLEDGE]]) **Format:** [[FORMAT]] (article / email / social post / FAQ) Rules: - No technical terms without immediate explanation - Use at least 2 everyday analogies - Summarize core message in one sentence - Take the "Why does this matter to me?" perspective - At the end: clarify 3 common misconceptions

Write a converting product description: **Product:** [[PRODUCT]] **Target audience:** [[AUDIENCE]] **Main features:** [[FEATURES]] **Main problem it solves:** [[PROBLEM]] **Price point:** [[PRICE]] Structure: - Headline with strongest benefit - Subheadline addressing the main problem - 3 feature-benefit pairs ("[Feature] → so you can [benefit]") - Social proof placeholder ("As our customers say...") - Objection handling (most common purchase barriers) - CTA with urgency

Generate 10 different headlines for: **Topic:** [[TOPIC]] **Target audience:** [[AUDIENCE]] **Goal:** [[GOAL]] (clicks / leads / awareness) 2 headlines per style: 1. **Curiosity gap** ("What happens when...") 2. **Number/List** ("7 Ways to...") 3. **Direct benefit** ("How to achieve X in Y time") 4. **Question** (provocative, directly addressing the reader) 5. **Counter-intuitive** (surprising perspective) Mark what you consider the strongest variant and explain why.

Write a compelling story using the classic 3-act structure: **Theme/Message:** [[THEME]] **Protagonist:** [[PROTAGONIST]] **Target audience:** [[AUDIENCE]] **Format:** [[FORMAT]] (Blog, speech, social post, case study...) Structure: - **Act 1 – Setup:** Introduce protagonist and status quo, introduce problem - **Act 2 – Conflict:** Challenge, turning point, emotional climax - **Act 3 – Resolution:** Transformation, outcome, transferable lesson Use concrete details, dialogue elements, and sensory descriptions.

Help me design notifications/toasts for my product. WHAT EVENTS TRIGGER THEM: [[EVENTS]] PRODUCT TYPE: [[PRODUCT]] Deliver: 1. Notification types and the right pattern for each (toast, banner, inline, badge, modal) 2. When to interrupt vs stay passive 3. Content rules: what happened + what to do next, kept short 4. Duration, dismissal, and stacking behavior 5. Severity styling (success/info/warning/error) and accessibility (not color-only) 6. How to avoid notification fatigue Respect the user's attention.

Build a translation/localization prompt. FROM → TO LANGUAGE: [[LANGUAGES]] CONTENT TYPE: [[CONTENT_TYPE]] (marketing, UI, legal, casual…) TONE TO PRESERVE: [[TONE]] LOCALE NOTES: [[LOCALE]] (region, formality, audience) Produce a prompt that: 1. Translates for meaning and natural flow, not literally 2. Adapts idioms, units, dates, currency, and cultural references 3. Preserves tone, brand voice, and intent 4. Flags untranslatable terms or things needing a human decision 5. Keeps formatting/placeholders/variables intact 6. Offers a more formal vs casual variant where relevant Localize, don't just translate.

Build a prompt that makes AI write in a specific style. WHOSE STYLE / WHAT STYLE: [[STYLE]] (an author, a brand voice, "punchy and casual"…) SAMPLE OF THE STYLE (if I have one): """ [[SAMPLE]] """ WHAT I'LL WRITE WITH IT: [[USE_CASE]] Produce: 1. An analysis of what defines that style (sentence length, tone, vocabulary, rhythm, devices) 2. A reusable prompt that conditions the AI on those traits 3. How to use a sample as a style reference effectively 4. Guardrails so it captures voice without copying content/plagiarizing 5. A quick test to check if the output actually matches Capture the voice, not a caricature.

Help me design a button/CTA system. CONTEXT: [[PRODUCT]] BRAND COLORS: [[COLORS]] BUTTON USES: [[USES]] (primary actions, destructive, secondary, links…) Deliver: 1. A button hierarchy (primary/secondary/tertiary/destructive) and when to use each 2. Sizing, padding, radius, and state styles (hover/focus/active/disabled/loading) 3. CTA label rules (verb-first, specific, length) 4. Placement and "one primary action per view" guidance 5. Accessibility (contrast, focus, touch target size) 6. Common mistakes (too many primaries, vague labels)

Rewrite my content in an "answer-first" structure for AI overviews and featured snippets. TARGET QUESTION/KEYWORD: [[QUERY]] CURRENT CONTENT: """ [[CONTENT]] """ Deliver: 1. A direct, self-contained answer to the query in the first 1–3 sentences 2. Supporting structure (definition, steps/list, then depth) 3. Quotable, standalone statements a machine can lift cleanly 4. A concise summary box / TL;DR 5. Clear headings phrased as the questions people ask Keep it genuinely useful for humans first — the AI/snippet wins follow.

Help me create a local landing page. SERVICE: [[SERVICE]] CITY/AREA: [[CITY]] WHAT MAKES US RELEVANT HERE: [[LOCAL_RELEVANCE]] Deliver: 1. A title, meta, H1, and URL slug 2. A page outline with genuinely local, useful content (not just find-replace of the city name) 3. Local proof to include (projects, reviews, area knowledge) 4. Internal links and schema (LocalBusiness) 5. A clear CTA 6. How to avoid thin "doorway page" penalties when making many city pages

Help me pitch a guest post to a site. TARGET SITE: [[TARGET_SITE]] — what they publish: [[THEIR_CONTENT]] MY EXPERTISE: [[MY_EXPERTISE]] WHAT I'D LINK TO: [[MY_LINK]] Deliver: 1. 3 guest-post topic ideas tailored to their audience (not self-promotional) 2. Why each fits gaps in their existing content 3. A short, personalized pitch email 4. How to work in a natural, valuable link (not spammy) 5. A polite follow-up Lead with value to them and their readers.

Generate an SEO FAQ section for my page. PAGE TOPIC / KEYWORD: [[KEYWORD]] AUDIENCE: [[AUDIENCE]] PRODUCT/SERVICE (if relevant): [[OFFER]] Deliver: 1. 6–10 real questions people ask (search-style, not invented) 2. Concise, helpful answers (snippet-friendly length) 3. Which questions target featured snippets / PAA 4. FAQPage JSON-LD schema for them 5. A note on Google's current rules for FAQ rich results Answers should genuinely help, not just chase schema.

Help me refresh an old, underperforming piece of content. THE PAGE & TARGET KEYWORD: [[PAGE_AND_KEYWORD]] WHEN PUBLISHED / LAST UPDATED: [[DATE]] HOW IT'S PERFORMING NOW: [[PERFORMANCE]] CURRENT CONTENT (optional): """ [[CONTENT]] """ Deliver: 1. What's likely outdated or thin 2. New sections/subtopics to add (intent + freshness) 3. Title/meta updates for CTR 4. Internal links and schema to add 5. What to cut 6. Whether to update-in-place vs rewrite vs consolidate Prioritize changes by likely ranking impact.

Give me an on-page SEO checklist for a specific page. PAGE TOPIC / TARGET KEYWORD: [[KEYWORD]] PAGE TYPE: [[PAGE_TYPE]] (blog, product, landing, service) CURRENT CONTENT (optional): """ [[CONTENT]] """ Check and advise on: 1. Title tag & meta description 2. URL slug 3. H1 + heading structure 4. Keyword & semantic coverage (without stuffing) 5. Internal & external links 6. Images (alt, filename, size) 7. Intent match & content depth vs what ranks 8. Schema opportunities Give a checklist + the 3 highest-impact fixes for THIS page.

Optimize the heading structure of my content. TARGET KEYWORD: [[KEYWORD]] CURRENT HEADINGS / OUTLINE: """ [[HEADINGS]] """ Deliver: 1. A corrected H1–H3 hierarchy (one H1, logical nesting) 2. Headings rewritten to match search intent and include semantic terms naturally 3. Sections to add or merge for better topical coverage 4. Which headings could win featured snippets if phrased as questions 5. Accessibility/readability notes Make it scannable for humans AND clear for search engines.

Help me optimize this existing page to rank for a keyword. TARGET KEYWORD: [[KEYWORD]] SEARCH INTENT: [[INTENT]] CURRENT PAGE CONTENT: """ [[CONTENT]] """ Deliver: 1. How well the current page matches intent (gap analysis vs what ranks) 2. A revised title, meta, and H1 3. Heading/structure changes and sections to add 4. Subtopics/entities to cover that are missing 5. Internal links to add 6. The single biggest reason it's not ranking and how to fix it Keep my existing strengths — improve, don't gut it.

Generate the questions people actually ask about my topic. TOPIC / TARGET KEYWORD: [[KEYWORD]] AUDIENCE: [[AUDIENCE]] Provide: 1. 15–20 real-style questions (who/what/why/how/can/is/best/vs…) 2. Grouped by sub-intent (informational, comparison, troubleshooting, buying) 3. Which deserve their own section vs a quick FAQ answer 4. 5 questions competitors probably aren't answering well 5. How to format answers to win featured snippets / PAA boxes These should read like real searches, not keyword-stuffed phrases.

Help me plan a podcast episode and its show notes. EPISODE TOPIC: [[TOPIC]] FORMAT: [[FORMAT]] (solo, interview, co-host) GUEST (if any): [[GUEST]] TARGET LENGTH: [[LENGTH]] AUDIENCE: [[AUDIENCE]] Deliver: 1. A hook/cold-open idea 2. A segment-by-segment outline with rough timings 3. Key talking points or interview questions 4. A strong closing + call to action 5. Show notes: episode summary, timestamps, links section, and 3 pull-quotes for promo

Outline a 5-day email course on [[TOPIC]] for [[AUDIENCE]]. GOAL: [[GOAL]] (build trust, sell [[OFFER]], grow list) For each of the 5 days give: - The single lesson/outcome - The hook/subject line - Key points to teach - A small action for the reader - The soft CTA Plus: a welcome email (day 0) and how the sequence builds toward [[GOAL]]. Keep each day focused on one win.

Write a "getting started" setup guide for my project. PROJECT: [[PROJECT]] STACK & TOOLS: [[STACK]] HOW IT RUNS LOCALLY: [[RUN_INFO]] COMMON SETUP GOTCHAS: [[GOTCHAS]] Deliver: 1. Prerequisites (versions, accounts, tools) 2. Step-by-step setup (copy-paste commands) 3. Environment variables needed (with a sample .env) 4. How to run, test, and verify it works 5. Troubleshooting for the common gotchas 6. Who/where to ask for help Optimize for "new dev productive in under an hour".

Rewrite this so it doesn't read as AI-generated. TEXT: """ [[TEXT]] """ TARGET VOICE: [[VOICE]] AUDIENCE: [[AUDIENCE]] Remove the AI tells: - Overused phrases ("delve", "in today's fast-paced world", "it's important to note") - Robotic symmetry and listy padding - Empty hedging and over-explaining Add: natural rhythm variation, specificity, a real point of view, and a human imperfection or two. Keep the meaning. Then list the specific changes you made.

Write alt text for these images. CONTEXT (where they appear): [[CONTEXT]] IMAGE DESCRIPTIONS: """ [[IMAGE_LIST]] """ For each image: - Concise, meaningful alt text (what matters, not "image of") - Mark any that are decorative and should get empty alt="" - Note where longer description is needed instead Keep each under ~125 characters. Convey purpose, not just appearance. Explain the one rule people get wrong.

Help me respond to a threatening / legal-sounding letter. WHAT THEY SENT: """ [[THEIR_LETTER]] """ THE ACTUAL SITUATION: [[FACTS]] MY GOAL: [[GOAL]] Help me: 1. Understand what they're actually claiming and how serious it is 2. Whether to respond, stay quiet, or get a lawyer 3. A calm, factual draft reply that doesn't admit fault or escalate 4. What NOT to say or do 5. What to document now DISCLAIMER: general info, not legal advice. For real legal threats, consult a lawyer.

Help me have a money conversation with my partner. THE TOPIC: [[TOPIC]] (budgeting, a big purchase, debt, different habits…) MY GOAL: [[GOAL]] WHERE WE CLASH: [[TENSION]] Give me: 1. A calm, non-blaming way to open it 2. How to share my view using "I" not "you" 3. Questions to understand their side 4. A fair framework to decide together 5. What to avoid saying Aim for teamwork, not winning.

Help me formally request a repair from my landlord. THE PROBLEM: [[PROBLEM]] HOW LONG IT'S BEEN: [[DURATION]] PRIOR REQUESTS: [[PRIOR_REQUESTS]] URGENCY/SAFETY: [[URGENCY]] Write a letter/email that: - Describes the issue and its impact clearly - References any habitability/repair obligation where relevant - Requests a fix by a reasonable deadline - Creates a paper trail (dates, prior contact) - Stays professional, not hostile DISCLAIMER: general info, not legal advice.

Help me push back on extra work / unrealistic scope. WHAT'S BEING ASKED: [[REQUEST]] WHY IT'S A PROBLEM: [[CONSTRAINT]] (time, priorities, capacity) WHAT I CAN OFFER INSTEAD: [[ALTERNATIVE]] Write a response that: - Shows I want to help (not just refusing) - Makes the tradeoff visible ("if I do X, then Y slips — which matters more?") - Proposes a realistic alternative or timeline - Stays collaborative and calm Give me the message + the one line that makes the tradeoff clear.

Help me write a status update for my manager. WHAT I'M WORKING ON: [[PROJECTS]] PROGRESS / WINS: [[PROGRESS]] BLOCKERS OR RISKS: [[BLOCKERS]] WHAT I NEED FROM THEM: [[ASKS]] Write an update that: - Leads with the headline (on track / at risk) - Focuses on outcomes, not a task diary - Surfaces blockers early with a proposed solution - Is scannable in 20 seconds Keep it concise and confident.

Write a README for my project. PROJECT NAME: [[NAME]] WHAT IT DOES: [[PURPOSE]] TECH / REQUIREMENTS: [[STACK]] HOW TO RUN IT: [[RUN_STEPS]] Include: - A one-line description + what problem it solves - Features (bulleted) - Installation & setup (copy-paste commands) - Usage example - Configuration / env vars if any - Contributing & license placeholders Keep it clean and scannable. Match the depth to the project size.

Help me decline or push back on a meeting invite. THE MEETING: [[MEETING]] WHY I WANT TO SKIP / CHANGE IT: [[REASON]] WHAT I'D PREFER: [[PREFERENCE]] (async, shorter, someone else, different time) Write a reply that: - Is respectful of the organizer - Proposes a useful alternative (async update, agenda first, delegate) - Protects my time without sounding dismissive - Keeps things collaborative Give a soft version and a firmer version.

Help me reply to this work chat message. THEIR MESSAGE: [[THEIR_MESSAGE]] WHAT I WANT TO CONVEY: [[MY_POINT]] RELATIONSHIP / FORMALITY: [[CONTEXT]] Write a reply that: - Matches the casual-but-professional tone of chat - Is clear and to the point (no essay) - Is friendly without overusing emojis - Includes a clear answer or next step Give a quick version and a slightly more careful version.

Help me reply to comments on my post. THE POST WAS ABOUT: [[POST_TOPIC]] MY BRAND VOICE: [[VOICE]] THE COMMENTS: """ [[COMMENTS]] """ For each comment, give me a reply that: - Matches my voice (friendly/professional/playful) - Adds value or warmth, not just "thanks!" - Handles any criticism gracefully (don't get defensive) - Encourages more engagement where it fits Flag any comment I should NOT engage with and why.

Help me answer "Tell me about yourself" for an interview. ROLE I'M APPLYING FOR: [[ROLE]] MY BACKGROUND: [[BACKGROUND]] KEY STRENGTHS: [[STRENGTHS]] WHY THIS ROLE: [[MOTIVATION]] Craft a 60–90 second answer that: - Follows present → past → future (or a better structure) - Connects my background to THIS role - Highlights 1–2 relevant wins - Ends on why I'm excited about this job Give the script + 3 delivery tips. Sound natural, not memorized.

Help me write a recommendation for someone. WHO: [[PERSON]] — our relationship: [[RELATIONSHIP]] FOR WHAT: [[PURPOSE]] (job, school, etc.) THEIR STRENGTHS: [[STRENGTHS]] A SPECIFIC EXAMPLE: [[EXAMPLE]] Write a letter that: - Opens with a confident endorsement - Backs it with the specific example, not just adjectives - Connects their strengths to what they're applying for - Sounds sincere and credible Avoid generic praise. Make it clearly about THIS person.

Help me write a resignation letter. MY ROLE: [[ROLE]] LAST DAY: [[LAST_DAY]] REASON (how much to share): [[REASON_LEVEL]] HOW I FEEL ABOUT LEAVING: [[SENTIMENT]] Write a letter that: - States I'm resigning and my last day clearly - Keeps it gracious and professional (no venting, even if I want to) - Offers a smooth handover - Thanks them genuinely if warranted Keep it short. Give a warm version and a neutral version.

Help me reach out to someone for a coffee chat / advice. WHO: [[PERSON]] — what they do: [[THEIR_ROLE]] HOW I FOUND THEM / OUR CONNECTION: [[CONNECTION]] WHAT I WANT TO LEARN: [[GOAL]] Write a message that: - Is short and respects their time - Gives a genuine, specific reason I'm reaching out to them - Makes the ask small (15 min, a question or two) - Is easy to say yes to No "pick your brain". Give a LinkedIn version and an email version.

Summarize this email thread for me. THREAD: """ [[EMAIL_THREAD]] """ Give me: 1. The TL;DR (what's this about, where it stands) 2. Key decisions made 3. Open questions / what's unresolved 4. Action items — who owes what, by when 5. Anything that needs MY response Keep it tight. Flag anything urgent.

Schlage mir kostengünstige Möglichkeiten vor, wie ich mein [dein Unternehmen] mit/ohne Nutzung von [dein Medienkanal] bewerben kann.

Schreibe benutzerfreundliche URLs für dieses Schlüsselwort auf der Domain [deine Domain] für die folgenden Keywords [deine Keywords].

Create an SEO content brief: **Main keyword:** [[KEYWORD]] **Website/Niche:** [[WEBSITE]] **Target audience:** [[AUDIENCE]] Deliver: 1. **Search intent** – informational / navigational / transactional / commercial? 2. **Semantic field** – 10 related keywords and LSI terms 3. **Content type** – which format ranks for this keyword? 4. **Recommended structure** – H1, H2, H3 suggestions 5. **Key questions** the article must answer (People Also Ask) 6. **Internal linking** – suggestions for related pages 7. **Meta title + meta description** (2 variants each)

Help me optimize a form for completion. FORM PURPOSE: [[FORM]] (signup, checkout, contact, survey…) CURRENT FIELDS: [[FIELDS]] WHERE PEOPLE DROP OFF (if known): [[DROPOFF]] Deliver: 1. Which fields to cut, combine, or defer (every field has a cost) 2. Field order and grouping for momentum 3. Labels, placeholders, and helpful microcopy 4. Inline validation and error-message approach 5. Mobile and accessibility considerations 6. The single change most likely to lift completion Reduce effort and anxiety, not just field count.

Help me design the hero section of a page. WHAT WE OFFER: [[OFFER]] AUDIENCE: [[AUDIENCE]] PRIMARY ACTION: [[PRIMARY_CTA]] BRAND VIBE: [[VIBE]] Deliver: 1. The visual hierarchy (what the eye should hit 1st, 2nd, 3rd) 2. Layout options (text/image split, centered, video bg…) with tradeoffs 3. Headline + subhead direction and CTA placement 4. What imagery/visual would reinforce the message 5. Mobile treatment 6. What to remove so the message isn't diluted It should pass the "5-second clarity test".

Help me brief a print design. PIECE: [[PIECE]] (flyer, poster, business card, menu…) PURPOSE & AUDIENCE: [[PURPOSE]] MUST-INCLUDE CONTENT: [[CONTENT]] BRAND: [[BRAND]] Deliver: 1. Recommended size/format and orientation 2. Visual hierarchy and layout direction 3. Copy structure (headline → key info → CTA) 4. Print-ready specs to specify (bleed, margins, CMYK, resolution, fonts) 5. What to avoid for legibility at a glance 6. A short brief I can hand to a designer or printer

Help me respond to a journalist request (HARO-style) to earn a backlink. THE REQUEST / TOPIC: [[REQUEST]] MY EXPERTISE: [[EXPERTISE]] WHO I AM (credentials): [[CREDENTIALS]] Write: 1. A concise, quotable expert response (journalists want ready-to-use quotes) 2. A credibility line that makes me worth citing 3. Why my angle is more useful/original than generic answers 4. Formatting that makes it easy to publish 5. What NOT to do (pitching my product, being vague, going long) Make it genuinely insightful so it gets picked.

Help me run a broken-link-building campaign. MY NICHE: [[NICHE]] A RESOURCE I CAN OFFER AS A REPLACEMENT: [[MY_RESOURCE]] Deliver: 1. How to find broken links worth targeting in my niche (where/how to look) 2. How to qualify which are worth the outreach 3. A short outreach email that helps them first (here's a broken link → here's a fix) 4. When my resource is a fair replacement vs when not to push it 5. Realistic conversion expectations + follow-up Keep it genuinely helpful, not opportunistic.

Help me optimize an e-commerce category page for SEO. CATEGORY: [[CATEGORY]] TARGET KEYWORD: [[KEYWORD]] PRODUCTS IN IT: [[PRODUCT_TYPES]] Deliver: 1. Title, meta, H1, and URL recommendations 2. Where and how to add useful intro/supporting copy (without burying products) 3. Filtering/faceted-navigation SEO handling (avoid index bloat) 4. Internal linking to/from the category 5. Schema opportunities 6. How to compete with marketplaces ranking for the same term Balance SEO content with a clean shopping experience.

Help me optimize my content to get cited by AI search engines (ChatGPT, Perplexity, Google AI Overviews, Gemini). TOPIC / PAGE: [[TOPIC]] WHAT I WANT TO BE CITED FOR: [[TARGET_CLAIM]] CURRENT CONTENT (optional): """ [[CONTENT]] """ Deliver: 1. How AI answer engines pick sources, and what that means for my content 2. Structure changes: clear answers up front, definitions, stats, quotable lines 3. How to add citation-worthy specifics (data, examples, unique insight) 4. Entity/topical clarity and schema that helps machines understand it 5. Authoritativeness signals that increase the chance of being cited 6. The biggest difference between classic SEO and answer-engine optimization Make my page the easiest, most trustworthy source to quote.

Help me find and fix keyword cannibalization. PAGES THAT MIGHT COMPETE: [[PAGES]] THE KEYWORD/TOPIC THEY OVERLAP ON: [[KEYWORD]] Deliver: 1. How to confirm cannibalization (what to check in Search Console) 2. Which page should be the "winner" for the keyword and why 3. The fix for each other page (consolidate/redirect, differentiate, de-optimize, or canonical) 4. Internal links to reinforce the chosen page 5. How to prevent it going forward Explain the tradeoffs of merging vs differentiating.

Help me plan redirects for a site change/migration. WHAT'S CHANGING: [[CHANGE]] (new domain, URL structure, CMS, HTTPS, consolidation) KEY PAGES / URL PATTERNS: [[URL_PATTERNS]] Deliver: 1. A redirect strategy (old → new mapping logic) 2. Rules for handling patterns at scale (not one-by-one) 3. What must be 301 (not 302) and why 4. Redirect chains/loops to avoid 5. A pre-launch and post-launch checklist to preserve rankings 6. What to monitor for the first weeks Flag the migration mistakes that most often cause traffic loss.

Build a local SEO action plan for my business. BUSINESS: [[BUSINESS]] TARGET AREA(S): [[AREAS]] COMPETITION LEVEL: [[COMPETITION]] Cover: 1. Google Business Profile optimization 2. Local keyword targeting and on-page (location pages, homepage) 3. NAP consistency & citations 4. Reviews strategy 5. Local link building / partnerships 6. A prioritized 90-day plan Tell me the 3 things that matter most for ranking in my area.

Help me build a realistic link-building strategy. SITE/NICHE: [[NICHE]] CURRENT AUTHORITY: [[AUTHORITY]] RESOURCES: [[RESOURCES]] (time, budget, content, outreach skill) Deliver: 1. The tactics that fit MY situation (digital PR, guest posts, linkable assets, broken-link, partnerships, listings) 2. Which to start with for fastest realistic results 3. The kind of content that earns links in my niche 4. Outreach targets and how to find them 5. White-hat guardrails (what to avoid that risks penalties) 6. How to measure link quality, not just quantity

Help me control what gets indexed on my site. SITE TYPE: [[SITE_TYPE]] PAGES I WANT INDEXED: [[INDEX_THESE]] PAGES I DON'T: [[EXCLUDE_THESE]] (admin, thank-you, filters, duplicates, staging) Deliver: 1. The right tool for each case: robots.txt vs noindex vs canonical vs password 2. Exact directives/tags to implement 3. The dangerous mistakes (blocking JS/CSS, noindexing money pages, robots-blocking a noindex page) 4. How to verify in Search Console 5. A quick reference of "use X when Y" Keep me from accidentally hiding pages I want ranked.

Help me set up hreflang for my multi-language/region site. LANGUAGES & REGIONS: [[LANGUAGES_REGIONS]] URL STRUCTURE: [[URL_STRUCTURE]] (subfolders, subdomains, ccTLDs) PLATFORM: [[PLATFORM]] Deliver: 1. The right hreflang setup for my structure (with examples) 2. x-default handling 3. Common hreflang mistakes (missing return tags, wrong codes) and how to avoid them 4. How it interacts with canonical tags 5. How to validate it Give me copy-paste examples for my exact case.

Help me optimize my Google Business Profile. BUSINESS TYPE: [[BUSINESS_TYPE]] LOCATION: [[LOCATION]] SERVICES & USP: [[SERVICES_USP]] Deliver: 1. Category selection (primary + secondary) advice 2. A keyword-aware business description 3. What to add (services, products, attributes, hours, photos) 4. A review-generation + response strategy 5. Posts/updates to keep it active 6. The signals that most influence local map-pack ranking Focus on what actually moves local visibility.

Help me fix duplicate content / canonicalization issues. THE SITUATION: [[SITUATION]] (e.g., www vs non-www, params, print pages, similar products, pagination) PLATFORM/CMS: [[PLATFORM]] Deliver: 1. Where duplication is likely happening and why it hurts 2. The correct canonical strategy for each case 3. When to use canonical vs 301 vs noindex vs parameter handling 4. The exact tags/config to implement 5. How to verify it worked in Search Console Keep me from accidentally de-indexing the wrong pages.

Help me analyze the SERP for a keyword so I can outrank it. TARGET KEYWORD: [[KEYWORD]] WHAT'S RANKING (describe top results if known): [[TOP_RESULTS]] MY ANGLE/RESOURCES: [[MY_ANGLE]] Analyze: 1. The dominant search intent and content format (the SERP is telling us what Google wants) 2. Common elements across the top pages (depth, structure, media, schema) 3. What they all do well — so I match the baseline 4. Gaps/weaknesses I can beat them on 5. A content brief to create something better If I can't see the SERP, tell me exactly what to look for.

Find content gaps for my target topic. TARGET KEYWORD / TOPIC: [[TOPIC]] WHAT MY CONTENT COVERS NOW: [[CURRENT_COVERAGE]] AUDIENCE: [[AUDIENCE]] Deliver: 1. Subtopics, questions, and entities that comprehensive content on this topic should cover 2. Which ones I'm missing 3. Related topics to build supporting content around 4. The gaps most likely to be hurting my rankings 5. A prioritized list of what to add first Aim for topical completeness, not keyword stuffing.

Help me improve Core Web Vitals / page speed. PAGE: [[PAGE]] PLATFORM/STACK: [[PLATFORM]] CURRENT SCORES/SYMPTOMS: [[SYMPTOMS]] (LCP, CLS, INP, slow load…) Deliver: 1. The likely culprits for each metric (LCP, CLS, INP) 2. Prioritized fixes by impact vs effort 3. Specific tactics (images, fonts, JS, render-blocking, caching, CDN) 4. Platform-specific quick wins for [[PLATFORM]] 5. How to measure before/after Explain which fixes actually move rankings vs just the score.

Help me improve E-E-A-T (Experience, Expertise, Authoritativeness, Trust) for my site. SITE/NICHE: [[NICHE]] IS IT "YMYL" (health/finance/legal/safety)? [[YMYL]] CURRENT SIGNALS: [[CURRENT_SIGNALS]] (about page, authors, reviews, citations…) Deliver: 1. Concrete ways to show real experience and expertise 2. Author/bio and credential improvements 3. Trust signals to add (reviews, sources, transparency, contact) 4. Content changes that demonstrate first-hand experience 5. The highest-impact fixes for my niche (extra strict if YMYL) Practical actions, not vague advice.

Help me find SEO gaps vs my competitors. MY SITE/NICHE: [[NICHE]] COMPETITORS: [[COMPETITORS]] WHAT I SELL/OFFER: [[OFFER]] Analyze: 1. Topics/keywords they likely rank for that I'm missing 2. Content formats they use that I don't 3. Where I could realistically outrank them (and where not to bother) 4. Their likely weak spots (thin content, poor UX, outdated info) 5. A prioritized "steal this" opportunity list Tell me what data to pull (from an SEO tool) to confirm each gap.

Help me find keyword gaps against specific competitors. MY NICHE: [[NICHE]] COMPETITORS: [[COMPETITORS]] MY EXISTING STRONG TOPICS: [[MY_TOPICS]] Deliver: 1. Likely keyword themes they cover that I don't 2. For each, the intent and the content type I'd need 3. Which gaps are worth pursuing (demand vs difficulty vs relevance to my offer) 4. Quick-win gaps vs long-term plays 5. What tool data to pull to validate (and the exact report to run) Prioritize relevance to what I actually sell.

Help me judge if I can realistically rank for this keyword. TARGET KEYWORD: [[KEYWORD]] MY SITE: [[SITE_INFO]] (age, authority, niche relevance) WHAT'S CURRENTLY RANKING (if I can describe it): [[CURRENT_SERP]] Assess: 1. What the top results have in common (authority, content depth, format) 2. Whether my site can realistically compete, and in what timeframe 3. An easier long-tail alternative to start with 4. What it would take to actually rank (content + links + signals) 5. A go / wait / pick-a-different-keyword verdict Be honest, not optimistic.

Act as an SEO consultant and audit my site. SITE: [[SITE_URL]] WHAT IT DOES / NICHE: [[NICHE]] KNOWN ISSUES: [[KNOWN_ISSUES]] WHAT I CAN SHARE (data/pages): [[AVAILABLE_INFO]] Audit across: 1. Technical (crawlability, indexing, speed, mobile, structured data) 2. On-page (titles, headings, content quality, internal links) 3. Content (depth, intent match, gaps, cannibalization) 4. Off-page (authority, backlinks) 5. UX signals Output: findings by category, each rated impact (High/Med/Low) × effort, then a prioritized top-10 action list. Tell me what to check in Search Console/analytics to confirm each.

Generate long-tail keywords for my topic. SEED TOPIC: [[TOPIC]] WHAT I OFFER: [[OFFER]] AUDIENCE: [[AUDIENCE]] SITE AUTHORITY: [[AUTHORITY]] (new/low/medium/high) Produce: 1. 25+ long-tail keyword ideas grouped by sub-theme 2. The likely search intent for each group 3. Which are realistic for my authority level to target first 4. Question-based variants (great for FAQ/voice) 5. 5 "low competition, real demand" picks to prioritize Flag any you suspect have little real search volume.

Help me optimize images on a page for SEO. PAGE TOPIC / KEYWORD: [[KEYWORD]] IMAGES (describe them): [[IMAGES]] For each image, advise on: 1. A descriptive, keyword-aware filename 2. Useful alt text (accessible, not stuffed) 3. Caption (if it adds value) 4. Format & compression recommendation for speed 5. Whether it qualifies for image-sitemap/structured data Plus: general rules for image SEO and the mistakes that hurt page speed.

Cluster my keyword list into content groups. KEYWORDS: """ [[KEYWORD_LIST]] """ For the list: 1. Group keywords that share search intent (and should target ONE page) 2. Name each cluster and pick the primary keyword 3. Recommend a content type per cluster (blog, landing, product, FAQ) 4. Flag keywords that need their own separate page vs. should be merged 5. Suggest a logical publishing priority order Goal: stop me creating 5 pages that all compete for the same thing.

Give me an SEO launch checklist for a new website. SITE TYPE: [[SITE_TYPE]] (blog, store, SaaS, local business…) PLATFORM/CMS: [[PLATFORM]] TARGET AUDIENCE & REGION: [[AUDIENCE_REGION]] Cover: 1. Technical setup (indexing, sitemap, robots, HTTPS, structured data) 2. Site architecture & URL structure 3. Core pages and on-page basics 4. Analytics & Search Console setup 5. Mobile & speed baseline 6. Pre-launch vs post-launch tasks Give it as a checklist with the 5 things people most often forget flagged.

Do local keyword research for my business. BUSINESS TYPE: [[BUSINESS_TYPE]] LOCATION(S): [[LOCATIONS]] SERVICES: [[SERVICES]] Provide: 1. "Service + location" keyword variations 2. "Near me" and implicit-local terms 3. Neighborhood/landmark-level long-tails 4. Question and emergency/urgent intent terms 5. Which to put on the homepage vs service pages vs blog 6. Seasonal local terms if relevant Focus on terms with real buying intent.

Build a 6-month SEO roadmap for my site. SITE & NICHE: [[NICHE]] CURRENT STATE: [[CURRENT_STATE]] (traffic, rankings, authority) GOAL: [[GOAL]] RESOURCES: [[RESOURCES]] (time, budget, team) Deliver: 1. The 3 highest-leverage focus areas for my situation 2. A month-by-month plan (technical fixes → content → links → refinement) 3. Quick wins to do in week 1 4. KPIs to track each month 5. What to deliberately NOT do yet Be realistic about how long SEO takes to show results.

Help me plan internal links for my content. THE PAGE I WANT TO BOOST: [[TARGET_PAGE]] (and its keyword) OTHER PAGES/POSTS I HAVE: [[OTHER_PAGES]] Deliver: 1. Which existing pages should link TO my target page (and why they're relevant) 2. Natural anchor-text suggestions (varied, not exact-match spam) 3. Which pages my target should link out to 4. A simple hub-and-spoke structure for the topic 5. Orphan-page risks to fix Explain how internal linking helps rankings here.

My organic traffic dropped. Help me diagnose it. WHEN IT DROPPED: [[WHEN]] HOW MUCH: [[MAGNITUDE]] WHAT CHANGED AROUND THEN: [[RECENT_CHANGES]] PAGES/KEYWORDS HIT HARDEST: [[AFFECTED]] Walk me through a diagnosis: 1. Likely causes ranked (algorithm update, technical issue, lost links, SERP change, seasonality, manual action…) 2. For each, exactly what to check (Search Console, analytics, rankings) to confirm or rule out 3. The single most likely cause given my clues 4. A recovery action plan 5. How to tell if it's recovering Be systematic — don't jump to conclusions.

Help me create a lead magnet for my audience. WHO I SERVE: [[AUDIENCE]] THEIR BIG PROBLEM: [[PROBLEM]] WHAT I SELL: [[OFFER]] Deliver: 1. 3 lead-magnet ideas (checklist, template, mini-guide, etc.) matched to the problem 2. For my best pick: a clear outline/structure 3. A title that promises a specific quick win 4. The "aha" it should deliver so they trust me 5. How it naturally leads toward [[OFFER]] Make it high-value but quick to create and consume.

Give me thumbnail concepts for my video. VIDEO TITLE/TOPIC: [[TITLE]] PLATFORM: [[PLATFORM]] THE EMOTION OR CURIOSITY TO TRIGGER: [[HOOK]] MY FACE/BRAND ELEMENTS: [[ELEMENTS]] Deliver: 1. 3 distinct thumbnail concepts (composition, focal point, text overlay) 2. The ≤4-word text for each 3. Color/contrast direction so it pops in feed 4. What to avoid (clutter, tiny text, misleading) 5. Which concept best matches the title and why Stop-the-scroll, but honest.

Write hook options for the first 10 seconds of my video. PLATFORM: [[PLATFORM]] VIDEO TOPIC: [[TOPIC]] THE PAYOFF / WHAT THEY'LL LEARN: [[PAYOFF]] AUDIENCE: [[AUDIENCE]] Give me 5 hook variants using different angles: - Bold claim / contrarian - Curiosity gap / open loop - Relatable problem - Quick result preview - Question Each ≤2 sentences, spoken-word natural. Mark your top pick and explain why it'll retain viewers.

Help me write my creator media kit content. WHO I AM / NICHE: [[NICHE]] PLATFORMS & AUDIENCE SIZE: [[PLATFORMS]] AUDIENCE DEMOGRAPHICS: [[DEMOGRAPHICS]] BEST RESULTS / SOCIAL PROOF: [[RESULTS]] WHAT I OFFER BRANDS: [[OFFERINGS]] Produce: 1. A punchy intro/bio 2. Audience snapshot (the stats that matter to brands) 3. Services/packages with what each includes 4. Past results / testimonials section 5. A clear contact + CTA Make brands see ROI, not just follower counts.

Help me pitch a brand for a sponsorship/collaboration. MY CHANNEL/PLATFORM: [[PLATFORM]] — audience: [[AUDIENCE_STATS]] THE BRAND: [[BRAND]] WHY WE FIT: [[FIT]] WHAT I'M PROPOSING: [[PROPOSAL]] Write a pitch that: - Opens with why I'm reaching out to THEM specifically - Leads with the value to them (audience, fit, results) - Proposes a concrete collaboration + rough deliverables - Includes social proof / relevant numbers - Has a clear, low-friction next step Confident, concise, not desperate. Add a short follow-up too.

Help me repurpose my long video into short clips. VIDEO TOPIC: [[TOPIC]] KEY MOMENTS / TRANSCRIPT NOTES: """ [[HIGHLIGHTS]] """ TARGET PLATFORMS: [[PLATFORMS]] Deliver: 1. 5–8 clip ideas, each with: the moment, why it works standalone, and a hook 2. A caption + on-screen text suggestion per clip 3. Which clips fit which platform 4. The single best clip to post first 5. How to make each work without the full context Maximize reach from one recording.

Let's play a quiz on the topic [Insert Topic]. Ask me questions with increasing difficulty. If I answer a question incorrectly, please give me hints so I can figure out the correct answer myself.

Please summarize the following text [Insert Text] into about 5 bullet points and highlight the key concepts and terms. Create clear notes from this that will help me in studying and reviewing the material.

You are a travel organization expert who ensures nothing is forgotten before departure. Create my pre-departure checklist: DESTINATION: [WHERE?] TRAVEL DURATION: [HOW LONG?] TRAVEL TYPE: [PACKAGE/INDIVIDUAL/BUSINESS] LIVING SITUATION: [APARTMENT/HOUSE/SHARED] PETS: [YES/NO] PLANTS: [YES/NO] CAR: [STAYS AT HOME?] Provide a time-staged checklist: === 1 MONTH BEFORE === DOCUMENTS: [ ] Check passport validity (6 months!) [ ] Apply for visa if needed [ ] International driver's license [ ] Take out travel health insurance [ ] Check/update vaccinations BOOKINGS: [ ] Book flights [ ] Reserve accommodations [ ] Book rental car [ ] Pre-book important activities [ ] Reserve seats on the flight FINANCES: [ ] Check credit card for abroad [ ] Inform bank about foreign use [ ] Order travel currency [ ] Plan budget === 1-2 WEEKS BEFORE === HEALTH: [ ] Assemble travel pharmacy

Build a prompt to ask questions about a long document. DOCUMENT TYPE: [[DOC_TYPE]] (contract, report, manual, research, transcript…) WHAT I NEED FROM IT: [[GOAL]] Produce a prompt that: 1. Answers ONLY from the document (no outside facts) and says so when the answer isn't there 2. Quotes/cites the relevant section for each answer 3. Handles "find/extract/summarize/compare" style questions 4. Flags ambiguity or contradictions in the source 5. Keeps answers concise and grounded 6. Works for follow-up questions in the same session Plus: how to paste the document and the best way to ask multi-part questions.

Help me organize a personal/team prompt library. WHAT I USE PROMPTS FOR: [[USE_CASES]] HOW MANY / HOW MESSY NOW: [[CURRENT_STATE]] SOLO OR TEAM: [[SOLO_OR_TEAM]] Deliver: 1. A category/folder structure that fits my use cases 2. A naming convention so prompts are findable 3. A template for documenting each prompt (purpose, variables, example, model) 4. How to handle variants and versions 5. Tagging for quick retrieval 6. A maintenance habit so it doesn't rot Optimize for "find and reuse the right prompt in seconds".

Build a prompt that makes the AI interview me to gather what it needs. WHAT WE'RE TRYING TO PRODUCE AT THE END: [[GOAL]] (a brief, a plan, a spec, a decision…) WHAT I KNOW vs DON'T: [[CONTEXT]] Produce a prompt that makes the AI: 1. Ask focused questions ONE or two at a time (not a giant form) 2. Adapt follow-ups based on my answers 3. Not assume — clarify when something's unclear 4. Track what it still needs before it can deliver 5. Summarize back and confirm before producing the final output 6. Then produce [[GOAL]] from everything gathered Make it feel like a smart consultant, not an interrogation.

Build me a reusable summarization prompt. WHAT I SUMMARIZE: [[CONTENT_TYPE]] (articles, meetings, papers, threads…) DESIRED LENGTH: [[LENGTH]] FOCUS/ANGLE: [[FOCUS]] (key decisions, action items, arguments, ELI5…) OUTPUT FORMAT: [[FORMAT]] (bullets, paragraph, TL;DR + detail) Produce: 1. A clean, reusable prompt with [[placeholders]] for the input 2. Instructions that control length and focus precisely 3. A rule to flag what it's uncertain about or what was cut 4. A "don't add information not in the source" guardrail 5. An optional variant for a different length/format Make it consistent across different inputs.

Give me a design QA checklist for a feature before it ships. FEATURE: [[FEATURE]] PLATFORM: [[PLATFORM]] Produce a checklist covering: 1. Visual fidelity vs design (spacing, type, color, alignment) 2. All states (empty, loading, error, success, disabled) 3. Responsive behavior across sizes 4. Interaction & animation correctness 5. Accessibility (contrast, focus, labels, touch targets, keyboard) 6. Edge cases (long text, no data, slow network, RTL) 7. Cross-browser/device spot checks Tailor it to this feature. Flag the items most often missed.

Help me design a multi-step prompt chain for a complex task. THE OVERALL GOAL: [[GOAL]] INPUT I START WITH: [[INPUT]] DESIRED FINAL OUTPUT: [[OUTPUT]] Deliver: 1. The logical steps to break this into (each a focused prompt) 2. The prompt for each step, and what it passes to the next 3. Where a step should verify/check before continuing 4. Where human review belongs 5. How to handle errors or bad intermediate output 6. Whether any steps can run in parallel Each step should do one thing well. Show the data flow.

Help me design a pricing table. PLANS: [[PLANS]] WHAT VARIES BETWEEN THEM: [[DIFFERENCES]] THE PLAN I WANT MOST PEOPLE TO PICK: [[TARGET_PLAN]] Deliver: 1. Layout and how many tiers to show 2. How to visually steer toward the recommended plan (anchor, highlight, "most popular") 3. Feature comparison: what to list vs hide, and ordering 4. Handling annual/monthly toggle and currency 5. Microcopy that reduces hesitation (CTA, guarantees, FAQ) 6. Mobile layout for comparison tables Make the choice easy, not overwhelming.

Help me organize my Figma (or design tool) file/project. WHAT'S IN IT: [[CONTENTS]] TEAM SIZE / WHO USES IT: [[TEAM]] CURRENT MESS: [[PROBLEM]] Deliver: 1. A page/file structure (e.g., cover, components, WIP, archive) 2. Naming conventions for layers, frames, and components 3. How to organize components, variants, and styles/tokens 4. Handling versions, WIP vs final, and handoff 5. Collaboration rules to prevent chaos 6. A cleanup plan for the current file Optimize for findability and safe collaboration.

Give me a self-review checklist for my change before I open a PR. WHAT THE CHANGE DOES: [[CHANGE]] LANGUAGE/STACK: [[STACK]] RISK AREAS: [[RISK_AREAS]] Produce a checklist covering: - Correctness & edge cases - Tests added/updated - Error handling & logging - Security (input validation, secrets, auth) - Performance red flags - Readability & naming - Docs/comments and migration notes - Anything to call out for reviewers Tailor it to this change, not generic boilerplate. End with the one thing most likely to be wrong here.

Draft Terms of Service for my [[PRODUCT]]. WHAT IT DOES: [[DESCRIPTION]] PAID OR FREE: [[PRICING_MODEL]] KEY RULES FOR USERS: [[USER_RULES]] REGION: [[REGION]] Include sections for: acceptance, accounts, acceptable use, payment/refunds (if paid), intellectual property, user content, disclaimers & limitation of liability, termination, changes, and governing law. Plain language with placeholders. DISCLAIMER: template only, not legal advice — review before publishing.

Help me write a Statement of Work for a project. PROVIDER & CLIENT: [[PARTIES]] THE PROJECT: [[PROJECT]] DELIVERABLES: [[DELIVERABLES]] TIMELINE & FEE: [[TIMELINE_FEE]] Include: - Scope (and explicitly what's OUT of scope) - Deliverables with acceptance criteria - Milestones, timeline, and payment schedule - Change-request process for scope creep - Assumptions and dependencies - Sign-off section Flag the parts that prevent the most disputes. DISCLAIMER: not legal advice.

Help me clean up a messy slide. WHAT'S ON THE SLIDE NOW: """ [[SLIDE_CONTENT]] """ THE ONE POINT IT SHOULD MAKE: [[KEY_MESSAGE]] AUDIENCE: [[AUDIENCE]] Give me: 1. The single takeaway as a headline 2. What to cut (kill the clutter) 3. A cleaner layout suggestion (what goes where) 4. A visual/data-viz idea if there are numbers 5. Speaker-note content moved off the slide Less text, more clarity. One idea per slide.

Help me create an invoice that gets paid on time. CLIENT: [[CLIENT]] WORK DONE: [[WORK]] AMOUNT: [[AMOUNT]] MY PAYMENT TERMS: [[TERMS]] Deliver: 1. A clean invoice layout (all the fields that prevent "I didn't get it" excuses) 2. Clear payment terms and due date wording 3. Accepted payment methods + late-fee line 4. A friendly note that nudges prompt payment 5. The 3 things that most often delay payment, and how to avoid them

Help me set up sinking funds for irregular/annual expenses. KNOWN BIG OR IRREGULAR COSTS: [[IRREGULAR_COSTS]] (car, gifts, insurance, travel…) WHEN EACH IS DUE: [[TIMING]] MONTHLY BUDGET FOR THIS: [[MONTHLY_AMOUNT]] Deliver: 1. A list of sinking funds with monthly amount to set aside for each 2. The total monthly commitment (and whether it fits the budget) 3. Which to prioritize if money is tight 4. A simple way to track them 5. What to do when one comes due Show the math clearly.

Help me save up for a big purchase. WHAT: [[ITEM]] COST: [[COST]] WHEN I WANT IT: [[TARGET_DATE]] WHAT I CAN SAVE MONTHLY: [[MONTHLY]] Deliver: 1. Whether the timeline is realistic at my savings rate (the math) 2. Monthly target to hit the date 3. Ways to close the gap (save more, wait, cheaper option) 4. Whether to pay cash vs finance, and why 5. A check: is this worth it vs alternatives? Encouraging but honest.

Help me figure out what to charge as a freelancer. WHAT I DO: [[SERVICE]] TARGET ANNUAL INCOME: [[TARGET_INCOME]] BILLABLE HOURS REALISTIC PER WEEK: [[BILLABLE_HOURS]] BUSINESS COSTS / TAXES TO COVER: [[COSTS]] EXPERIENCE LEVEL: [[LEVEL]] Deliver: 1. The hourly rate I need to hit my target (show the math, accounting for non-billable time) 2. A project/value-based pricing alternative 3. How my rate compares to typical for [[SERVICE]] (flag if you're unsure) 4. How to present the price confidently 5. When to raise it Not financial advice — a starting framework.

Give me a spreadsheet formula for what I describe. WHAT I WANT TO DO: [[GOAL]] TOOL: [[EXCEL_OR_SHEETS]] MY DATA LAYOUT: [[LAYOUT]] (which columns/rows hold what) Deliver: 1. The exact formula to paste 2. What each part does, briefly 3. How to adjust it for my cell ranges 4. A common mistake to avoid 5. A simpler alternative if one exists If there are multiple good approaches, recommend one.

Help me run a family meeting. WHO'S INVOLVED: [[FAMILY]] WHAT WE NEED TO SORT OUT: [[TOPICS]] PAST PROBLEM: [[WHAT_USUALLY_GOES_WRONG]] Give me: 1. A short agenda with time limits 2. Ground rules to keep it calm 3. A fair way to let everyone be heard (incl. kids) 4. How to turn complaints into decisions/chores 5. A positive way to close Keep it light and constructive, not a tribunal.

Turn my messy meeting notes into something useful. NOTES: """ [[NOTES]] """ Produce: 1. A 3-bullet summary of what was discussed 2. Decisions made 3. Action items: task — owner — due date (mark "owner TBD" if unclear) 4. Open questions to follow up on 5. A short recap message I can paste to the team Don't invent details that aren't in the notes.

Help me plan a surprise for someone special. WHO: [[PERSON]] — what they love: [[THEIR_INTERESTS]] OCCASION: [[OCCASION]] BUDGET: [[BUDGET]] HOW MUCH TIME I HAVE: [[TIME]] Give me: 1. 3 surprise ideas matched to them (not generic) 2. For my favorite: a step-by-step plan and timeline 3. How to keep it secret 4. A backup if something falls through 5. A personal touch that makes it meaningful Prioritize thoughtful over expensive.

Help me build a self-care plan I'll actually follow. WHAT'S DRAINING ME: [[STRESSORS]] TIME I REALISTICALLY HAVE: [[TIME]] WHAT RECHARGES ME: [[WHAT_HELPS]] Deliver: 1. Daily micro-habits (5–10 min) 2. A weekly recharge activity 3. Boundaries to protect my energy 4. Warning signs I'm running on empty + what to do 5. The one thing to start this week Keep it doable, not another to-do list that stresses me out.

I'm feeling stuck/demotivated. Give me a real pep talk. WHAT I'M FACING: [[SITUATION]] WHAT I'M FEELING: [[FEELING]] WHAT I'M WORKING TOWARD: [[GOAL]] Give me: - An honest acknowledgement (don't dismiss it) - A reframe that actually helps - A reminder of why this matters to me - The single smallest next step - One sentence to carry with me today Be warm and direct, like a coach who believes in me. No clichés.

Make me a grocery list. MEALS / RECIPES I WANT THIS WEEK: [[MEALS]] PEOPLE TO FEED: [[SERVINGS]] WHAT I PROBABLY ALREADY HAVE: [[HAVE]] Deliver: 1. A consolidated list (combine shared ingredients, with quantities) 2. Grouped by store section (produce, dairy, pantry…) 3. Flag anything I likely already own to double-check 4. Optional swaps to save money Keep it tight so I'm not buying things I won't use.

I'm overwhelmed/anxious right now and need to calm down fast. WHAT'S GOING ON: [[SITUATION]] WHERE I AM: [[LOCATION]] (so the technique fits) Give me a 5-minute routine: 1. A breathing pattern with simple timing 2. A grounding exercise I can do here 3. One thought to steady me 4. A tiny first action once I'm calmer Keep instructions calm, short, and easy to follow. (Not medical advice — seek help if it's severe.)

Give me kid activity ideas. AGE(S): [[AGES]] TIME AVAILABLE: [[TIME]] INDOORS OR OUT: [[SETTING]] WHAT WE HAVE: [[MATERIALS]] ENERGY LEVEL WANTED: [[CALM_OR_ACTIVE]] Provide: 1. 5 activity ideas matched to age and setting 2. For 2 favorites: quick setup and any prep 3. A mess-free option 4. A learning-disguised-as-fun option Keep prep minimal and instructions clear.

I need to vent and then get some perspective. WHAT HAPPENED: """ [[WHAT_HAPPENED]] """ First: just acknowledge how this feels — don't rush to fix it. Then, gently: 1. Reflect back what I'm actually upset about 2. Offer a fair outside perspective (including any blind spot) 3. Separate what I can control from what I can't 4. Suggest one constructive next step if I want it Be a good listener first, advisor second.

Help me reframe a thought that's stressing me out (CBT-style, not therapy). THE THOUGHT: [[THOUGHT]] THE SITUATION: [[SITUATION]] Walk me through: 1. What kind of thinking trap this might be (catastrophizing, mind-reading, all-or-nothing…) 2. The evidence for and against the thought 3. A more balanced, realistic way to see it 4. A small action that would help right now Be kind and grounded. Not toxic positivity. (Not a substitute for professional help.)

Help me host a dinner without losing my mind. GUESTS: [[GUEST_COUNT]] VIBE: [[VIBE]] (casual, fancy, cozy…) DIETARY NEEDS: [[DIETARY]] MY COOKING SKILL: [[SKILL_LEVEL]] TIME TO COOK: [[PREP_TIME]] Deliver: 1. A balanced menu (starter/main/side/dessert) that mostly preps ahead 2. A backwards timeline ending when guests arrive 3. What to make the day before 4. A simple drink option 5. One thing to skip to lower stress Match the menu to my skill level.

Help me weigh a big decision (job, move, relationship, money, etc.). THE DECISION: [[DECISION]] OPTIONS: [[OPTIONS]] TIME HORIZON: [[TIMEFRAME]] Guide me through: - My core values that should drive this: [[VALUES]] - Best case / worst case / most likely for each option - The regret test: which would I regret more at [[FUTURE_POINT]]? - What's reversible vs permanent - A small experiment or info-gathering step before deciding End with a framework, not a command.

Here's everything swirling in my head. Organize it for me. BRAIN DUMP: """ [[BRAIN_DUMP]] """ Turn it into: 1. Actionable next-steps (each starting with a verb) 2. Grouped by project/area 3. Flagged: urgent / important / can wait / delegate / delete 4. The top 3 to do first 5. Anything that's actually a worry, not a task (named separately) Make the list feel lighter, not heavier.

I keep avoiding this task. Help me actually start. THE TASK: [[TASK]] WHY I THINK I'M AVOIDING IT: [[SUSPECTED_REASON]] DEADLINE: [[DEADLINE]] Help me: 1. Diagnose the real block (boring, scary, unclear, too big?) 2. Shrink it to a 2-minute first step 3. Remove the top friction point 4. Set a tiny reward and a "good enough" bar 5. Give me the exact first action to take right now Keep it short and kick me into motion.

Design a morning routine that fits my real life. WAKE TIME: [[WAKE_TIME]] TIME AVAILABLE BEFORE I START: [[TIME_AVAILABLE]] MY GOALS: [[GOALS]] (energy, focus, calm, fitness…) WHAT TRIPS ME UP: [[OBSTACLES]] Deliver: 1. A minute-by-minute routine I can actually keep 2. A 5-minute "bare minimum" version for bad days 3. The night-before prep that makes it work 4. One keystone habit to start with first Keep it realistic — no 4 a.m. ice-bath fantasy unless I asked for it.

I have these ingredients. Tell me what to cook. INGREDIENTS I HAVE: [[INGREDIENTS]] STAPLES ON HAND: [[STAPLES]] (oil, spices, rice, pasta…) TIME I HAVE: [[TIME]] DIET / DISLIKES: [[DIET_NOTES]] Give me: 1. 3 meal ideas using mostly what I have 2. For my top pick: simple steps and rough timing 3. What to add if I can grab 1–2 things 4. A way to use anything about to go off Keep it beginner-friendly.

Help me declutter without burning out. SPACE: [[SPACE]] HOW MUCH TIME I HAVE: [[TIME]] MY STRUGGLE: [[STRUGGLE]] (sentimental, too much, no time, decision fatigue…) Give me: 1. An order to tackle it in (quick wins first) 2. A simple keep/donate/toss decision rule 3. Time-boxed mini-sessions ([[SESSION_LENGTH]] each) 4. How to handle the sentimental pile 5. A "done for today" stopping point so I don't spiral Encouraging, not preachy.

Build me a moving checklist. MOVE DATE: [[MOVE_DATE]] FROM → TO: [[FROM_TO]] SITUATION: [[RENT_OR_OWN_SOLO_OR_FAMILY]] Organize tasks by timeline: - 8 weeks out, 4 weeks, 2 weeks, week of, moving day, after Include: admin (address changes, utilities, contracts), packing strategy, and the things people always forget. Flag the 5 most-forgotten items. Keep it scannable.

Help me think through a decision I'm stuck on. THE DECISION: [[DECISION]] OPTIONS: [[OPTIONS]] WHAT I'M AFRAID OF: [[FEARS]] WHAT MATTERS MOST: [[VALUES]] Don't just pick for me. Instead: 1. Reflect back what's really at stake 2. Lay out each option's likely outcome 3. Ask me 3 sharp questions that would unlock the choice 4. Name the decision's reversibility (easy to undo or not?) 5. Then give your honest lean and why Be a thoughtful friend, not a yes-man.

Help me plan a realistic week. MUST-DOS THIS WEEK: [[MUST_DOS]] WANT-TO-DOS: [[WANT_TO_DOS]] FIXED COMMITMENTS: [[FIXED]] ENERGY/TIME REALITY: [[CONSTRAINTS]] Deliver: 1. The 3 priorities that actually matter this week 2. A day-by-day rough plan (don't overload it) 3. What to drop or defer if the week gets tight 4. One buffer day/slot for overflow Be honest if I'm trying to fit too much.

Analyze the following code and the described misbehavior: **Error/Symptom:** [[ERROR_DESCRIPTION]] **Expected behavior:** [[EXPECTED_BEHAVIOR]] **Language/Framework:** [[LANGUAGE]] ``` [[SELECTED_TEXT]] ``` Proceed as follows: 1. Identify the root cause 2. Explain why the error occurs 3. Show the corrected code 4. Name measures to prevent similar bugs in the future

Help me reduce token usage and cost in my AI prompt/workflow. THE PROMPT OR WORKFLOW: """ [[PROMPT]] """ HOW IT'S USED: [[USAGE]] (volume, model) Deliver: 1. Where tokens are being wasted (redundant instructions, bloated context, verbose output) 2. A tightened version that keeps quality 3. Output-length controls to add 4. Context strategies (summarize, retrieve only what's needed, cache) 5. Where a cheaper model or fewer steps would work 6. Estimated savings and any quality risk to watch Trim fat, not muscle.

Help me add a dark mode to my product. CURRENT (light) PALETTE: [[PALETTE]] PRODUCT TYPE: [[PRODUCT]] Deliver: 1. A dark-mode color system (surfaces, elevation, text, borders) — not pure black 2. How to remap brand and semantic colors for contrast 3. Accessibility: contrast ratios to hit and pairings to avoid 4. Handling images, shadows, and illustrations in dark 5. Implementation approach (tokens, CSS variables, theme switching) 6. Common dark-mode mistakes Aim for comfortable, legible, and on-brand in both themes.

Help me spec a reusable component for our design system. COMPONENT: [[COMPONENT]] (button, input, card, dropdown…) BRAND/STYLE CONTEXT: [[STYLE]] WHERE IT'S USED: [[USAGE]] Define: 1. Anatomy (parts) and variants (e.g., primary/secondary, sizes) 2. All states: default, hover, focus, active, disabled, loading, error 3. Spacing, sizing, and the design tokens it uses 4. Behavior & interaction rules 5. Accessibility requirements (focus, contrast, labels, keyboard) 6. Do/don't usage examples Make it precise enough to build consistently across the product.

Help me plan responsive behavior for a layout. THE LAYOUT/PAGE: [[LAYOUT]] KEY ELEMENTS: [[ELEMENTS]] Deliver: 1. Sensible breakpoints (content-driven, not just device sizes) 2. How key elements reflow at each (nav, columns, images, tables) 3. What to hide, stack, or reprioritize on small screens 4. Touch vs pointer considerations 5. Fluid vs fixed strategy (and where each fits) 6. The element most likely to break responsively + how to handle it Design mobile-first where it makes sense.

Help me add the edge-case tests my code is missing. CODE / FUNCTION: ``` [[CODE]] ``` TEST FRAMEWORK: [[FRAMEWORK]] EXISTING TESTS COVER: [[EXISTING_COVERAGE]] Deliver: 1. The edge cases I'm probably not testing (empty, null, huge, boundary, malformed, concurrent…) 2. A prioritized list (most likely to break first) 3. Written tests for the top cases 4. Any input that suggests a real bug in the code itself 5. What's still risky and worth a manual check

Refactor this code to be more readable — same behavior. CODE: ``` [[CODE]] ``` LANGUAGE: [[LANGUAGE]] CONSTRAINTS: [[CONSTRAINTS]] Deliver: 1. The refactored version (clear names, smaller functions, less nesting) 2. A short note on each meaningful change and why 3. Anything that hints at a deeper design issue 4. Confirmation that behavior is unchanged (or flag any risk) 5. What I deliberately left alone and why Prioritize clarity over cleverness. Don't over-engineer.

Help me debug a failing test. THE TEST: ``` [[TEST_CODE]] ``` THE FAILURE OUTPUT: ``` [[FAILURE]] ``` CODE UNDER TEST (if relevant): ``` [[CODE]] ``` Walk me through: 1. What the failure actually tells us 2. Is the bug in the code or the test itself? 3. The most likely cause 4. The fix (and which file it belongs in) 5. Whether this points to other untested cases

Help me integrate the [[API_NAME]] API into my [[STACK]] app. WHAT I WANT IT TO DO: [[GOAL]] AUTH TYPE (if known): [[AUTH]] Deliver: 1. The integration steps in order 2. Auth setup and how to keep keys safe 3. Example request/response code 4. Error handling and rate-limit strategy 5. What to cache vs fetch live 6. The 3 things that most often go wrong with API integrations Note where I should check their docs for specifics.

Help me add proper logging and error handling to this code. CODE: ``` [[CODE]] ``` LANGUAGE/STACK: [[STACK]] WHERE IT RUNS: [[ENVIRONMENT]] Deliver: 1. Where to add error handling (and what to catch vs let bubble up) 2. What to log, at what level (debug/info/warn/error) — and what NOT to log (secrets/PII) 3. User-facing vs internal error messages 4. Retry/fallback where it makes sense 5. The refactored code Avoid noisy logs and swallowing errors silently.

Draft a privacy policy for my [[SITE_OR_APP]]. WHAT DATA I COLLECT: [[DATA_COLLECTED]] WHY / HOW I USE IT: [[USAGE]] THIRD PARTIES / TOOLS: [[THIRD_PARTIES]] (analytics, payments, email…) AUDIENCE REGION: [[REGION]] Include plain-language sections for: what I collect, why, legal basis, sharing, cookies, data rights (access/deletion), retention, security, children, contact, and changes. Use bracketed placeholders for specifics. DISCLAIMER: a starting template, not legal advice — have it reviewed, especially for GDPR/CCPA.

Turn this bug into a clear brief for an AI coding agent. THE BUG: [[BUG]] EXPECTED vs ACTUAL: [[EXPECTED_VS_ACTUAL]] WHERE (files/area): [[LOCATION]] HOW TO REPRODUCE: [[REPRO]] CONSTRAINTS: [[CONSTRAINTS]] Produce a brief with: 1. A one-line problem statement 2. Reproduction steps 3. Acceptance criteria (how we know it's fixed) 4. Scope guardrails (what NOT to touch) 5. Relevant files/context to load 6. A verification step Make it unambiguous so the agent doesn't guess.

Build a prompt that extracts structured data from text. WHAT I'M EXTRACTING FROM: [[SOURCE_TYPE]] (emails, reviews, resumes, receipts…) FIELDS I NEED: [[FIELDS]] OUTPUT FORMAT: [[FORMAT]] (JSON, CSV, table) Produce: 1. A precise extraction prompt with the schema/fields defined 2. Rules for missing or ambiguous data (null vs skip vs best-guess) 3. 1–2 examples (input → desired output) 4. Handling for multiple records in one input 5. A note on validating the output Make it reliable enough to run in a loop.

Help me understand and fix this error. ERROR MESSAGE: ``` [[ERROR]] ``` WHAT I WAS DOING: [[CONTEXT]] STACK / LANGUAGE: [[STACK]] RELEVANT CODE (if any): ``` [[CODE]] ``` Give me: 1. What the error actually means in plain English 2. The most likely cause here 3. The exact fix to try first 4. 1–2 other things to check if that doesn't work 5. How to avoid it next time

Explain this code so I actually understand it. CODE: ``` [[CODE]] ``` MY LEVEL: [[LEVEL]] Walk me through: 1. What it does overall, in one sentence 2. A line-by-line (or block-by-block) explanation in plain language 3. Any non-obvious trick, gotcha, or assumption 4. What would break it 5. One thing I could improve Match the depth to my level. No condescension.

Explain this terminal command before I run it. COMMAND: ``` [[COMMAND]] ``` Break down: 1. What it does overall 2. Each part/flag, explained 3. Is it safe? Anything destructive or irreversible? ⚠️ 4. What I should check or back up first 5. A safer or simpler alternative if relevant Be especially clear about anything that deletes or overwrites.

Tell me the git commands to do this safely. WHAT I WANT TO DO: [[GOAL]] CURRENT SITUATION: [[STATE]] (uncommitted changes, wrong branch, etc.) Give me: 1. The exact commands, in order 2. What each one does 3. Anything destructive flagged with a ⚠️ and a safer alternative 4. How to undo it if it goes wrong 5. The one thing to double-check before running Assume I can lose work if I'm careless — keep me safe.

Write the SQL for what I describe. WHAT I WANT: [[REQUEST]] DATABASE TYPE: [[DB]] TABLES & KEY COLUMNS: [[SCHEMA]] Deliver: 1. The query, formatted and commented 2. A plain-English explanation of what each part does 3. Any assumption I should verify (table/column names, joins) 4. A note on performance if the data is large 5. An alternative if there's a simpler/safer way

Be my rubber-duck debugging partner. THE BUG: [[BUG_DESCRIPTION]] EXPECTED vs ACTUAL: [[EXPECTED_VS_ACTUAL]] WHAT I'VE TRIED: [[TRIED]] RELEVANT CODE: ``` [[CODE]] ``` Don't just hand me the answer. Instead: 1. Ask me targeted questions to narrow it down 2. Point out assumptions worth checking 3. Suggest what to log/test next 4. Only after we've narrowed it, propose the likely fix Help me find it so I learn. One step at a time.

ROLE: Retrieval engineer. TASK: Design a query-rewriting prompt for a RAG system over [[KNOWLEDGE_BASE]]. The rewriter should take a raw user question and produce: 1. A cleaned, decontextualized standalone query (resolve pronouns/"it" using chat history: [[HISTORY]]) 2. 2–3 alternative phrasings / sub-queries to widen recall 3. Extracted key entities/filters for metadata search 4. A note on intent (lookup / comparison / how-to / troubleshooting) Also specify how to handle: vague questions, multi-part questions, and questions outside the knowledge base. Output format should be JSON the retriever can consume.

ROLE: Prompt engineer building a reliable API-style call. TASK: Write a prompt that makes a model return JSON matching this need: [[DATA_NEED]]. DELIVER: 1. A precise schema (fields, types, which are required, allowed enums) 2. The instruction block that enforces "return ONLY valid JSON, no prose/markdown" 3. Rules for missing/uncertain data (null vs omit vs default) 4. 1–2 examples of correct output 5. An edge-case instruction (what to do when input is unparseable) 6. A validation note: what to check on the receiving side Make malformed output as unlikely as possible.

ROLE: Problem-set author. TASK: Generate practice problems for [[TOPIC]] at increasing difficulty for [[AUDIENCE]]. PRODUCE [[NUMBER]] problems, each with: - The problem statement (clear, unambiguous) - Difficulty tag (warm-up / standard / challenge) - A hint (revealed separately) - A full worked solution with the reasoning, not just the answer - A common mistake to avoid Order easy → hard so each builds confidence for the next. Make at least one a real-world applied problem in [[CONTEXT]].

ROLE: Product designer handing off to engineering. TASK: Write handoff notes for "[[COMPONENT_OR_SCREEN]]". COVER: - Layout & spacing logic (and how it reflows on mobile/desktop) - Component states (default, hover, active, focus, disabled, loading, error) - Responsive behavior & breakpoints - Interactions/animations (trigger, duration, easing) - Edge cases (long text, no data, RTL, accessibility/focus order) - Tokens used (color, type, spacing) — reference, don't hardcode - Assets to export and naming End with the 3 details most likely to be missed if not called out.

ROLE: Privacy practitioner. TASK: Produce a GDPR compliance checklist for [[PRODUCT_OR_PROCESS]] that handles [[DATA_TYPES]] for users in the EU. COVER: - Lawful basis for each processing purpose - Consent mechanics (where required) and records - Data subject rights (access, deletion, portability) — how each is fulfilled - Data minimization & retention policy - Processor/sub-processor agreements & transfers - Security measures & breach response (72h) - Privacy notice contents - DPIA: is one needed here? For each item: ✅ what "done" looks like and a common failure. DISCLAIMER: not legal advice.

ROLE: Engineer writing a clear async update. TASK: Turn my raw notes into a standup update for [[TEAM]]. FORMAT: - Yesterday: what moved (outcomes, not activity) - Today: the 1–3 things I'll finish - Blockers: specific, with what I need and from whom (or "none") Keep it scannable, ≤120 words, no status-theater. Flag anything at risk with ⚠️. RAW NOTES: [[NOTES]]

ROLE: Technical SEO. TASK: Generate JSON-LD structured data for a [[SCHEMA_TYPE]] page (e.g., Article, Product, FAQPage, HowTo, LocalBusiness). INPUTS: [[PAGE_DETAILS]] DELIVER: 1. Complete, valid JSON-LD with all recommended + relevant optional properties filled from the inputs (use clear placeholders where data is missing) 2. A note on which properties Google actually uses for rich results 3. Common mistakes to avoid for this type 4. How to validate before shipping Output the script tag ready to paste in <head>.

ROLE: Senior DevOps Engineer. TASK: Optimize the Dockerfile below for [[APP_TYPE]] running on [[BASE_IMAGE]]. Improve for: 1. Image size — multi-stage build, minimal base, no build tools in final layer 2. Build cache — order layers so [[CHANGE_FREQUENCY]] code invalidates the least 3. Security — non-root user, pinned versions, no secrets, drop capabilities 4. Startup — healthcheck, correct ENTRYPOINT/CMD, signal handling OUTPUT: - The rewritten Dockerfile (commented) - A short table: what changed and why - Estimated size/security impact DOCKERFILE: ``` [[DOCKERFILE]] ```

ROLE: On-call engineer doing incident triage. CONTEXT: Stack: [[TECH_STACK]]. Environment: [[ENVIRONMENT]]. TASK: Analyze the log/stack trace and produce a triage report. DELIVER: 1. Root cause hypothesis (most likely first) with the evidence line(s) from the log 2. Blast radius — who/what is affected 3. Immediate mitigation (stop the bleeding) 4. Proper fix with code/config sketch 5. Prevention — test, alert, or guard to add LOG: ``` [[ERROR_LOG]] ```

ROLE: Shell scripting expert. TASK: Write a [[SHELL]] script that: [[GOAL]]. REQUIREMENTS: - Start with strict mode (set -euo pipefail or equivalent) - Validate inputs and required tools; clear error messages - Idempotent where possible; dry-run flag if it mutates anything - Comments on each non-obvious block - Usage/help text INPUTS/ARGS: [[INPUTS]] TARGET OS: [[TARGET_OS]] Output the full script, then a 2-line "how to run" note.

ROLE: Database architect. TASK: Design a relational schema for: [[REQUIREMENTS]]. TARGET DB: [[DB_ENGINE]]. Expected scale: [[SCALE]]. DELIVER: 1. ER overview (entities + relationships in plain text) 2. DDL for each table: columns, types, PK/FK, NOT NULL, UNIQUE, CHECK 3. Indexes — justify each by the queries it serves: [[KEY_QUERIES]] 4. Normalization notes (which normal form, any deliberate denormalization + why) 5. Migration & seeding considerations Flag any modeling decision with a tradeoff worth the team discussing.

ROLE: Performance engineer. TASK: Design a caching strategy for "[[FEATURE]]". INPUTS: - Read pattern: [[READ_PATTERN]] - Write pattern: [[WRITE_PATTERN]] - Consistency requirement: [[CONSISTENCY_NEED]] - Stack/tools available: [[STACK]] DELIVER: 1. Where to cache (client, CDN, app, DB) and why 2. Cache key design + TTL recommendation 3. Invalidation approach (TTL vs write-through vs event-based) with the failure modes of each 4. Stampede/thundering-herd protection 5. Metrics to watch to confirm it's working Be explicit about what you would NOT cache and why.

ROLE: API architect. TASK: Design REST endpoints for the resource "[[RESOURCE]]" in a [[DOMAIN]] system. For each endpoint provide: method + path, purpose, request body/params, success response (status + JSON), error responses (status + shape), auth requirement, idempotency note. Cover the lifecycle: list (with filtering/pagination over [[FILTER_FIELDS]]), get, create, update (PATCH semantics), delete. Also define: - A consistent error envelope - Pagination strategy - Versioning approach CONSTRAINTS: [[CONSTRAINTS]]. Output as a clean spec table + JSON examples.

ROLE: Developer advocate who writes tutorials people finish. TASK: Write a tutorial: "How to [[GOAL]] with [[TOOL_OR_STACK]]". READER LEVEL: [[SKILL_LEVEL]]. Prerequisites: [[PREREQS]]. STRUCTURE: - What you'll build (1 paragraph + the end result) - Prerequisites & setup - Numbered steps — each with: the action, the exact code/command, expected output, and a "why this works" aside - A common-pitfall callout where readers usually get stuck - "Verify it works" check - Next steps / further reading Code blocks must be copy-paste runnable. No skipped steps.

ROLE: Engineer optimizing for fast, high-quality review. TASK: Write a PR description for "[[PR_TITLE]]". INPUT: - What changed: [[SUMMARY_OF_CHANGES]] - Why: [[MOTIVATION]] - Risk areas / files reviewers should focus on: [[RISK_AREAS]] - How it was tested: [[TESTING]] OUTPUT (markdown): ## Summary ## Motivation & Context ## Changes (bulleted) ## How to test / verify ## Screenshots or logs (placeholder) ## Risk & rollback ## Checklist (lint, tests, docs, migration) Keep it scannable. Bold the one thing a reviewer must not miss.

ROLE: Disciplined engineer who writes excellent git history. TASK: Write a Conventional Commits message for the change below. RULES: - Format: type(scope): summary — type ∈ feat|fix|refactor|perf|docs|test|chore|build|ci - Summary ≤ 72 chars, imperative mood, no trailing period - Body: WHY the change was made (not just what), wrapped at 72 chars - Footer: BREAKING CHANGE: … and issue refs like "Closes [[ISSUE_ID]]" if relevant CHANGE: [[CHANGE_DESCRIPTION]] SCOPE/AREA: [[SCOPE]] DIFF (optional): ``` [[DIFF]] ``` Output only the commit message.

Upload : Screenshot of your code or a rough system sketch for OAuth 2.0. Turn this into a clean OAuth 2.0 flow diagram for technical documentation. Include these exact components: - User - Client App - Authorization Server - Resource Server Use color coding: - User actions: blue (#2196F3) - Successful responses: green (#4CAF50) - Authorization steps: orange (#FF9800) Add labeled arrows: 1) Authorization Request 2) Authorization Grant 3) Access Token Request 4) Access Token 5) Protected Resource Request 6) Protected Resource Use a modern, minimalist design with plenty of white space. Include small code snippet callouts in monospace font near key arrows. Export at 2000×2000, optimized for embedding in documentation.

Erstelle eine htaccess Rewrite-Regel, die eine 301-Umleitung verwendet, um [URL] nach [URL] umzuleiten.

Erstelle eine gültige XML-Sitemap, die die folgenden URLs enthält: [Deine Liste mit URLs]

Erstelle eine robots.txt-Regel, um den Zugriff auf das angegebene Website-Verzeichnis [Verzeichnis] zu verbieten.

I'm facing the following architectural problem and am looking for the right design pattern: **Problem:** [[PROBLEM_DESCRIPTION]] **Context/Language:** [[CONTEXT]] **Existing structure:** [[STRUCTURE]] Please: 1. Recommend 2-3 suitable design patterns with justification 2. Explain for each: pros and cons in my context 3. Show a concrete code example for the best option 4. Name anti-patterns I should avoid

Please explain the concept [Insert Concept] to me as if I were a fifth grader. Use simple language, analogies, and examples to make it easier for me to understand.

Set up an AI roleplay/simulation for me. THE SCENARIO: [[SCENARIO]] (job interview, sales call, language practice, difficult convo, negotiation…) THE ROLE THE AI PLAYS: [[AI_ROLE]] THE ROLE I PLAY: [[MY_ROLE]] DIFFICULTY/REALISM: [[DIFFICULTY]] Produce a setup prompt that: 1. Defines the AI's character, goals, and behavior 2. Sets realistic constraints (stays in character, reacts to me) 3. Specifies how/when to give feedback (during vs after) 4. Includes a way for me to pause or adjust difficulty 5. Defines a clear end + debrief Make it immersive but genuinely useful for practice.

Help me understand this investment before I decide anything. THE INVESTMENT: [[INVESTMENT]] WHAT I THINK IT IS: [[MY_UNDERSTANDING]] Explain: 1. What it actually is, in plain terms 2. How it makes (or loses) money 3. The real risks and what could go wrong 4. Fees and costs to watch for 5. The questions I should answer before buying 6. Common ways beginners get burned here Educational only — NOT financial advice. Encourage me to verify and consider a professional.

Explain my payslip / paycheck line by line. PAYSLIP DETAILS: """ [[PAYSLIP]] """ COUNTRY/REGION: [[REGION]] Explain: 1. Gross vs net and where the difference goes 2. What each deduction is (tax, social, pension, insurance…) 3. Anything that looks unusual or worth checking 4. What I could potentially adjust (allowances, contributions) Plain language. General info, not tax advice.

Be my debate practice partner. MY POSITION: [[MY_POSITION]] THE TOPIC: [[TOPIC]] DIFFICULTY: [[LEVEL]] Do this: 1. Take the opposing side and argue it well 2. Push back on my weakest points 3. After a few exchanges, tell me where my argument was strong vs shaky 4. Suggest stronger evidence or framing I could use Go one point at a time and wait for my response. Be challenging but fair.

Explain [[CONCEPT]] at two levels. LEVEL 1 — Explain Like I'm 5: a simple analogy a child would get. LEVEL 2 — Explain Like I'm in the field: the accurate, nuanced version with the real mechanisms and terms. Then: - Bridge them: what the simple version leaves out - One common misconception - A question to test if I really get it Context for why I'm asking: [[CONTEXT]].

Recommend what I should [[READ_OR_WATCH]] next. WHAT I LOVED RECENTLY: [[LIKED]] WHAT I DIDN'T VIBE WITH: [[DISLIKED]] MOOD I'M IN: [[MOOD]] TIME/COMMITMENT: [[LENGTH]] Give me: 1. 5 picks matched to my taste, each with one line on WHY I'd like it (based on what I loved) 2. A safe bet and a wildcard 3. One "if you only pick one" recommendation 4. Where to find it if you know No spoilers. Skip the obvious blockbusters unless they truly fit.

Help me build my vocabulary in [[LANGUAGE_OR_FIELD]]. MY LEVEL: [[LEVEL]] GOAL / CONTEXT: [[GOAL]] (exam, work, fluency…) HOW MANY WORDS: [[COUNT]] For each word give: - The word + simple definition - An example sentence in context - A memory hook or mnemonic - A common mistake or false friend Pick useful, real words for my goal — not obscure ones. End with a 3-question self-check.

Explain this news topic to me clearly and neutrally. TOPIC: [[TOPIC]] WHAT I ALREADY KNOW: [[BACKGROUND]] Give me: 1. What's happening, in plain terms 2. The key background needed to understand it 3. The main perspectives — fairly stated, no strawmen 4. What's fact vs opinion vs unknown 5. Good questions to keep in mind as it develops Stay balanced. Flag where reasonable people disagree and why.

Steelman both sides of this debate so I understand it properly. THE QUESTION: [[QUESTION]] For EACH side: 1. The strongest, most charitable version of the argument 2. The best evidence/reasoning behind it 3. The value or fear underneath the position 4. Its weakest point Then: where the real disagreement actually lies, and what would change minds. Don't tell me what to think — make me think better.

Help me explain something to a child. THE TOPIC: [[TOPIC]] CHILD'S AGE: [[AGE]] WHAT THEY ASKED / WHY IT CAME UP: [[CONTEXT]] OUR VALUES / ANYTHING TO INCLUDE OR AVOID: [[NOTES]] Give me: 1. A simple, honest explanation at their level 2. Words to use and words to avoid 3. How to answer likely follow-up questions 4. A reassuring way to close 5. Signs they need a break from the topic Keep it calm, truthful, and age-appropriate.

Help my child with homework by guiding, not giving answers. SUBJECT & TOPIC: [[SUBJECT]] GRADE LEVEL: [[GRADE]] THE QUESTION THEY'RE STUCK ON: [[QUESTION]] Do this: 1. Explain the underlying concept simply 2. Ask a leading question to get them thinking 3. Give a worked EXAMPLE with different numbers/wording 4. Offer a hint if still stuck — never the final answer 5. A way to check their own work Encourage effort. Keep it patient and positive.

Rewrite the text below in plain, clear language a [[AUDIENCE]] would understand. TEXT: """ [[TEXT]] """ - Replace jargon and acronyms with plain words (define any that must stay) - Use shorter sentences and concrete examples - Keep it accurate — don't dumb down the meaning, just the wording Then give me a one-line "explain it like I'm new here" summary.

Rewrite the text below for a [[READING_LEVEL]] reading level (e.g., 8-year-old, high-schooler, general adult, expert). TEXT: """ [[TEXT]] """ - Match vocabulary and sentence length to the level - Keep all key information accurate - Adjust examples to suit the audience Note any concept that's genuinely hard to simplify and why.

ROLE: Expert educator who knows where learners go wrong. TASK: Identify and fix the common misconceptions about [[TOPIC]] for [[AUDIENCE]]. For each of the top [[NUMBER]] misconceptions: 1. The wrong belief (stated as a learner would say it) 2. Why it's intuitive but wrong 3. The accurate model, explained simply 4. A quick test/example that exposes the difference 5. A memory hook to keep the correct version End with one "if you only remember one thing" correction.

ROLE: Assessment designer. TASK: Create a quiz on [[TOPIC]] at [[DIFFICULTY]] level for [[AUDIENCE]]. PRODUCE [[NUMBER]] questions mixing formats: multiple choice, true/false with justification, short answer, and 1–2 applied/scenario questions. Spread across Bloom levels (recall → apply → analyze). For each: the question, options (if MC), the correct answer, and a one-line explanation of why (and why common wrong answers are tempting). Avoid trick questions; test understanding, not reading speed. SOURCE MATERIAL (optional): [[SOURCE]]

ROLE: Mentor who's coached many learners in [[SKILL]]. TASK: Build a learning roadmap for [[SKILL]] from [[CURRENT_LEVEL]] to [[TARGET_LEVEL]]. Time available: [[WEEKLY_HOURS]]/week. DELIVER stages, each with: - The capability you'll have at the end of the stage - Core concepts to learn (in order — respect prerequisites) - A concrete practice project to prove it - A milestone test ("you're ready to move on when…") - Common trap that stalls people here End with the single highest-leverage thing to do first, and what to deliberately skip for now.

ROLE: Socratic tutor. TASK: Teach me [[CONCEPT]] at a [[LEVEL]] level by asking, not telling. RULES: - Ask one focused question at a time and wait for my answer - Build on my responses; correct gently by asking a sharper question - When I'm stuck, give the smallest possible hint, not the answer - Periodically ask me to explain it back in my own words - End when I can explain it correctly and apply it to a new example: [[APPLICATION_CONTEXT]] Start by checking what I already know about [[CONCEPT]]. Keep it conversational.

ROLE: Learning scientist. TASK: Build a spaced-repetition study schedule to master [[SUBJECT]] by [[EXAM_DATE]]. INPUTS: Available study time: [[TIME_PER_DAY]]. Current level: [[CURRENT_LEVEL]]. Topics: [[TOPICS]]. DELIVER: 1. A topic breakdown with priority (weight by difficulty × exam relevance) 2. A review schedule using expanding intervals (1d, 3d, 7d, etc.) 3. Daily plan mixing new learning + scheduled reviews 4. Active-recall and self-test checkpoints (not re-reading) 5. A weekly adjustment rule based on what you're getting wrong Front-load the hard/foundational topics. Build in rest.

ROLE: Knowledge-management coach. TASK: Design a note/knowledge system for someone who [[CURRENT_PAIN]] and uses [[TOOLS]]. DELIVER: 1. Top-level structure (Projects / Areas / Resources / Archive or an alternative — justify the choice) 2. Naming + tagging conventions that stay consistent 3. A capture-to-organize workflow (where things land, when they get filed) 4. A weekly review routine to prevent rot 5. Migration plan from their current mess Optimize for retrieval and low maintenance, not collecting.

Create a worksheet with 10 math problems on the topic [Topic] for the class level [Class Level]. The problems should have varying levels of difficulty and include both calculation and word problems.

Plan a lesson on the topic [Topic] for the class level [Class Level]. The plan should include an introduction, main activities, and a closing discussion. Also, add materials and resources needed for the lesson.

Create a worksheet on the topic [Topic] for the class level [Class Level]. The worksheet should include multiple-choice questions, fill-in-the-blank exercises, and a brief summary of the topic.

Summarize the following YouTube transcript into bullet points and answer the following questions: Question 1 Question 2 Question 3 [YouTube Transcript]

Here are two translations of the same text from [Source Language] to [Target Language]: Translation 1: [Translation 1] Translation 2: [Translation 2] Compare the two translations and provide an evaluation of which is the more accurate and natural translation. Justify your choice.

I will enter a sentence in [Source Language] and you will do three things: Translate the sentence. Explain any differences between a literal and a comprehensible translation that might be confusing. Revise the sentence to use more natural language, a casual style, and a creative tone, referring to other sentences in this conversation. [Source Language] = [Language] [Target Language] = [Language] Here is the sentence: [Text].

You are a translation assistant that translates texts from [Language] to [Language].

You are a cultural anthropologist and experienced tour guide for [COUNTRY]. Give me comprehensive cultural tips so I can act as a respectful tourist and avoid faux pas. Cover: 1) GREETING ETIQUETTE: Handshake? Bow? Kiss? Eye contact? 2) DOS - What is appreciated and opens doors? 3) DON'TS - Absolute taboos that are offensive, 4) DRESS CODE: Formal/informal, religious sites, beach, 5) TIPPING: How much, when, how to give? 6) FOOD CULTURE: Table manners, alcohol, invitations to eat, 7) BARGAINING: Is haggling expected? How to do it right? 8) RELIGION & POLITICS: Topics to avoid or address? 9) BODY LANGUAGE: Gestures that mean something different than here, 10) BUSINESS: If I'm there for work. Give concrete examples and explain the WHY behind the rules.

You are an experienced language teacher and travel expert. Create the 30 most important travel phrases for [COUNTRY/LANGUAGE] that I will actually need as a tourist. Organized by situation: GREETINGS & POLITENESS (5 phrases): Hello, Thank you, Please, Sorry, Goodbye - with cultural nuances, RESTAURANT & FOOD (6 phrases): Order, Pay, Allergy warnings, Vegetarian/Vegan, Bill, TRANSPORT (5 phrases): Buy ticket, Where does this go? Get off here, EMERGENCY & HEALTH (4 phrases): Help, Police, Hospital, Pharmacy, SHOPPING (5 phrases): Price, Too expensive, Sizes, Payment, ORIENTATION (5 phrases): Where is? Left/Right, Nearby. For each phrase: Local language, phonetic pronunciation for Germans, literal translation, cultural context when to use it.

Stell mir 10 tiefgründige Reflexionsfragen über meine beruflichen Ziele, sachlich und ohne Esoterik.

Erkläre mir [TOPIC] in einfachen Worten, so als wär ich 12 Jahre alt.

Fasse mir das Buch [Book] von [NAME] in einfachen Worten zusammen.

Agiere als Sprachtrainer. Ich bin [Level] in [LANGUAGE]. Ich möchte die Sprache in [Time] lernen. Ich habe Montag bis Freitag je eine Stunde lang Zeit dafür. Könntest du bitte einen strukturierten Lernplan erstellen, der das Pareto-Prinzip nutzt, um mir zu helfen, Englisch zu lernen?.

Erstelle mir einen Trainingsplan für Anfänger, 3x die Woche, Ziel: mehr Ausdauer und Rückenmuskulatur.

Erstelle 20 Prüfungsfragen unterschiedlicher Schwierigkeitsgrade (leicht/mittel/schwer) zum Thema '[dein Thema]'. Variiere zwischen Multiple Choice, offenen Fragen und Fallstudien. Gib auch Musterlösungen an.

Analysiere folgenden Textabschnitt meiner Bachelorarbeit und gib mir spezifisches Feedback zu: 1) Wissenschaftlichkeit des Stils, 2) Logik der Argumentation, 3) Klarheit der Formulierungen. Mache konkrete Verbesserungsvorschläge: [hier deinen Text einfügen]

Entwickle eine detaillierte Gliederung für eine 60-seitige Bachelorarbeit zum Thema '[dein Thema]'. Berücksichtige dabei: 1) Einleitung (10%), 2) Theoretischer Teil (40%), 3) Empirischer Teil (40%), 4) Fazit (10%). Gib zu jedem Hauptkapitel 3-4 Unterkapitel mit kurzen Beschreibungen an.

Du bist ein erfahrener Wissenschaftler im Bereich [dein Fachgebiet]. Erstelle mir eine strukturierte Liste mit 15 relevanten wissenschaftlichen Suchbegriffen für das Thema '[dein Thema]'. Unterteile sie in Hauptkategorien und gib zu jedem Begriff 2-3 alternative englische/deutsche Suchvarianten an.

Ich bin Schüler:in der x. Klasse. Ich muss eine [Englischarbeit über modale Verben] schreiben. Tu so, als wärest du ein geduldiger [Englisch-Lehrer]. Frage mich alles zum Thema der Arbeit. Stelle mir eine Frage und warte ab, bis ich geantwortet habe. Gib mir dann Feedback auf meine Antwort. Stelle die nächste Frage erst, wenn ich geantwortet habe.

Was sind die häufigsten Missverständnisse in Bezug auf [dein Thema]?

Build a prompt to analyze sentiment and themes in feedback. WHAT THE FEEDBACK IS: [[SOURCE]] (reviews, survey responses, support chats, comments…) WHAT I WANT TO LEARN: [[GOAL]] Produce a prompt that: 1. Classifies overall sentiment (and intensity) per item 2. Extracts recurring themes/topics (not just positive/negative) 3. Surfaces the most common complaints and praises with example quotes 4. Spots emerging or surprising signals 5. Quantifies roughly how often each theme appears 6. Recommends what to act on first Output a structured, skimmable summary I could share with a team.

Help me choose the right AI model for a task. THE TASK: [[TASK]] PRIORITIES: [[PRIORITIES]] (quality, speed, cost, context length, privacy) VOLUME: [[VOLUME]] (one-off vs high-volume/API) CONSTRAINTS: [[CONSTRAINTS]] Deliver: 1. What this task actually demands from a model (reasoning, creativity, long context, structured output…) 2. The tradeoffs to weigh for MY priorities 3. A recommendation: a stronger model vs a cheaper/faster one — and when to use each 4. Whether one model for everything vs routing by task makes sense 5. How to test/compare candidates on my real inputs 6. Cost-saving tactics without tanking quality Be practical; recommend by capability tier, not hype.

Build a prompt to fact-check content (mine or another AI's output). CONTENT TO CHECK: """ [[CONTENT]] """ DOMAIN: [[DOMAIN]] Produce a prompt that makes the AI: 1. Extract the checkable factual claims 2. Rate each: likely true / uncertain / likely false / unverifiable 3. Explain its reasoning and flag where it's not confident 4. Identify claims that need a primary source to confirm 5. Catch subtle issues (outdated info, missing context, overgeneralization) 6. NOT bluff — say "I can't verify this" instead of guessing Then tell me which claims I should independently verify before publishing.

Build a prompt to classify text reliably. WHAT I'M CLASSIFYING: [[ITEMS]] (support tickets, reviews, leads, content…) CATEGORIES/LABELS: [[LABELS]] EDGE CASES: [[EDGE_CASES]] Produce: 1. A precise prompt with each label clearly defined (and boundaries between them) 2. Rules for ambiguous items (multi-label? "other"? confidence?) 3. 2–3 examples per tricky label (few-shot) 4. A structured output format (JSON) for easy processing 5. A consistency rule so the same input always gets the same label 6. How to handle inputs that don't fit any label Optimize for running on many items consistently.

Build a prompt to analyze a dataset with AI. WHAT THE DATA IS: [[DATA_DESCRIPTION]] COLUMNS/FIELDS: [[FIELDS]] THE QUESTION I'M TRYING TO ANSWER: [[QUESTION]] Produce a prompt that asks the AI to: 1. Summarize the data and its quality/limits first 2. Answer my specific question with the evidence 3. Surface the 3 most important patterns or anomalies 4. Separate correlation from causation honestly 5. Recommend concrete next actions 6. Say clearly what the data does NOT support Plus: how to format/paste my data, and what to double-check in the output.

Critique my design and tell me how to improve it. WHAT IT IS: [[DESIGN]] GOAL OF THE DESIGN: [[GOAL]] AUDIENCE: [[AUDIENCE]] DESCRIPTION (or paste details): """ [[DESCRIPTION]] """ Give me: 1. First impression — what works 2. Issues by area: hierarchy, layout, typography, color/contrast, spacing, copy, usability 3. Severity for each (nitpick → blocker) 4. The top 3 changes that would most improve it 5. One thing I should NOT change (it's working) Be specific and honest, like a senior designer in a crit.

Help me design the information architecture for my [[SITE_OR_APP]]. WHAT IT CONTAINS: [[CONTENT]] MAIN USER GOALS: [[USER_GOALS]] AUDIENCE: [[AUDIENCE]] Deliver: 1. A logical top-level navigation structure 2. A sitemap (pages/sections and how they nest) 3. Grouping/labeling based on how users think (not internal org charts) 4. Primary vs secondary vs utility navigation 5. Where search, filters, or cross-links are needed 6. The riskiest IA decision worth user-testing Name things the way users would, not the way we do internally.

Help me design a dashboard. WHO USES IT: [[USERS]] DECISIONS IT SHOULD SUPPORT: [[DECISIONS]] KEY METRICS/DATA: [[METRICS]] Deliver: 1. The 3–5 things that deserve top-of-screen priority (and why) 2. The right chart type for each metric (and what to avoid) 3. A layout/grid: hierarchy, grouping, scan path 4. How to show change/context (not just current value) 5. Filters and drill-down approach 6. What to cut to avoid a cluttered "data dump" Optimize for "answer a question in 5 seconds".

My prompt is producing made-up / wrong info. Help me fix it. THE PROMPT: """ [[PROMPT]] """ WHAT IT GETS WRONG: [[PROBLEM]] Diagnose and patch: 1. Where the prompt invites guessing or overconfidence 2. Add instructions to say "I don't know" when unsure 3. Require it to cite/ground claims in provided context only 4. Add a self-check or confidence step 5. Constrain scope so it can't wander Return the patched prompt + what you changed and why.

Help me think through renting vs buying. CURRENT RENT: [[RENT]] TARGET PURCHASE PRICE: [[PRICE]] DOWN PAYMENT AVAILABLE: [[DOWN_PAYMENT]] HOW LONG I'D STAY: [[YEARS]] REGION/NOTES: [[NOTES]] Walk me through: 1. The real monthly cost of buying (mortgage + taxes + maintenance + insurance) 2. The "how long until buying wins" breakeven, roughly 3. The non-financial factors (flexibility, stress, lifestyle) 4. The biggest risk in each direction 5. An honest lean for MY situation Show assumptions. Not financial advice.

Review this lease/rental agreement and flag what I should worry about. LEASE TEXT: """ [[LEASE_TEXT]] """ MY SITUATION: [[SITUATION]] Give me: 1. A plain-language summary of key terms (rent, term, deposit, notice) 2. Clauses that are unusual, one-sided, or risky for me 3. What's missing that should be there 4. Questions to ask or changes to request before signing 5. The 3 things I should NOT sign without clarifying DISCLAIMER: not legal advice — consult a professional for anything significant.

Compare these two options so I can choose. OPTION A: [[OPTION_A]] OPTION B: [[OPTION_B]] WHAT I'LL USE IT FOR: [[USE_CASE]] WHAT MATTERS MOST TO ME: [[PRIORITIES]] Deliver: - A side-by-side on the criteria I care about - Where each one wins - Hidden costs or downsides of each - "Best for X / best for Y" verdict - Your pick for MY use case, and why If you're unsure on a spec, say so rather than guessing.

I'm about to do this. Argue the other side so I don't fool myself. MY PLAN: [[PLAN]] WHY I LIKE IT: [[MY_REASONS]] Play devil's advocate: 1. The strongest reasons this is a bad idea 2. What I'm probably underestimating 3. Who this could affect that I'm not considering 4. The cheapest way to test it before going all-in 5. What would have to be true for this to actually work Be tough but fair. If it's actually a good plan, say that too.

Help me decide whether to buy this. ITEM: [[ITEM]] PRICE: [[PRICE]] WHY I WANT IT: [[REASON]] MY BUDGET SITUATION: [[BUDGET_CONTEXT]] Walk me through: 1. Need vs want — which is this, honestly? 2. Cost per use / will I actually use it? 3. Cheaper or free alternatives 4. The "wait 48 hours" test result 5. A clear recommendation: buy, wait, or skip — with the one deciding factor Be honest, not a cheerleader.

ROLE: Prompt reviewer. TASK: Critique and improve the prompt below. Its goal is: [[PROMPT_GOAL]]. It currently fails because: [[OBSERVED_PROBLEM]]. EVALUATE against: clarity of task, role/context, specificity, output format, constraints, examples, and failure handling. Score each 1–5 with a one-line reason. THEN: 1. Diagnose the top 2 weaknesses actually causing the bad output 2. Provide a rewritten prompt that fixes them 3. Explain what you changed and why 4. Suggest one test input that would reveal if it's fixed PROMPT: """ [[PROMPT_TEXT]] """

ROLE: Analytics partner who drives action. TASK: Interpret the data below about [[CONTEXT]] and tell me what to do. DATA: [[DATA]] DELIVER: 1. The 3 most important findings (lead with the surprising one) 2. What's likely driving each (hypotheses, flagged as such) 3. What the data does NOT tell us (limits, confounders, sample issues) 4. 2–3 concrete recommended actions, ranked 5. The single follow-up question or cut of the data that would sharpen the decision Avoid restating obvious numbers. Tie every insight to a "so what".

ROLE: Red-team critical thinker. TASK: Audit the reasoning below for hidden assumptions, biases, and weak links. INPUT: """ [[ARGUMENT_OR_PLAN]] """ DELIVER: 1. The load-bearing assumptions (the ones that, if false, collapse the whole thing) 2. Cognitive biases likely at play (confirmation, sunk cost, survivorship, etc.) with where you see them 3. The weakest link in the logic 4. What evidence would change the conclusion 5. A steel-manned version of the opposing view Be a candid skeptic, not a contrarian. Goal: make the thinking stronger.

ROLE: Research methodologist. TASK: Design a survey to learn [[RESEARCH_GOAL]] from [[RESPONDENTS]]. DELIVER: 1. The decisions this survey should inform (so every question earns its place) 2. [[NUMBER]] questions with the right type each (scale, MC, ranking, open) — ordered to reduce fatigue and bias 3. Flag and fix any leading, double-barreled, or ambiguous phrasing 4. Required demographic/segmentation questions (only what you'll actually use) 5. Estimated completion time + how to boost response rate 6. How you'll analyze each question Keep it as short as the goal allows. Cut vanity questions.

ROLE: Decision analyst. TASK: Compare these options for the decision "[[DECISION]]": [[OPTIONS]]. DELIVER: 1. A weighted criteria table — criteria: [[CRITERIA]], with weights reflecting what matters most here 2. Score each option per criterion (with a one-line justification, not just a number) 3. Pros/cons summary per option 4. The weighted result + the option it points to 5. A gut-check: does the winner feel right, and what would make you override the math? 6. The reversible-vs-irreversible nature of this choice Surface any criterion that's doing too much of the deciding.

ROLE: Goal-setting coach. TASK: Refine this goal into a SMART goal: [[VAGUE_GOAL]]. Timeframe: [[TIMEFRAME]]. Constraints/resources: [[CONSTRAINTS]]. DELIVER: 1. The rewritten SMART goal (Specific, Measurable, Achievable, Relevant, Time-bound) 2. The single metric that proves success + its target number 3. 3 leading indicators to track weekly (not just the lagging outcome) 4. The first concrete action to take this week 5. The most likely reason this goal fails — and a pre-commitment to counter it Challenge me if the goal is unrealistic for the timeframe.

ROLE: Operations analyst running a blameless RCA. TASK: Find the root cause of: [[PROBLEM]]. CONTEXT: [[CONTEXT]]. What we know so far: [[KNOWN_FACTS]]. DELIVER: 1. A 5-Whys chain (challenge each "why" — don't stop at the convenient answer) 2. A fishbone grouping of contributing factors (People, Process, Tools, Environment, etc.) 3. The most likely root cause(s) + the evidence and what would disconfirm it 4. A systemic fix (not a band-aid) and how to verify it worked 5. The "why didn't we catch this earlier" gap to close Separate symptoms from causes explicitly. Stay blameless.

ROLE: Senior UX designer running a heuristic evaluation. TASK: Critique [[SCREEN_OR_FLOW]] for [[PRODUCT]] used by [[USER]] trying to [[USER_GOAL]]. Evaluate against Nielsen's 10 heuristics. For each issue found: - Heuristic violated - What's wrong (specific) - Severity (cosmetic / minor / major / catastrophic) - A concrete fix Then prioritize: the top 3 fixes by impact-to-effort. End with one thing the design already does well. (Describe the screen below if no image.) SCREEN DESCRIPTION: [[DESCRIPTION]]

ROLE: Lawyer-translator who explains contracts to normal people. TASK: Explain the clause(s) below in plain language. For each clause provide: 1. What it says in one sentence 2. What it means for ME specifically as the [[YOUR_ROLE]] 3. Best case / worst case if this clause is triggered 4. Is this standard, or unusually favorable to the other side? 5. A suggested question or redline if it's risky CLAUSE(S): """ [[CLAUSE_TEXT]] """ DISCLAIMER: Informational only, not legal advice.

ROLE: Market analyst. TASK: Size the market for [[PRODUCT]] sold to [[CUSTOMER]] in [[GEOGRAPHY]]. Use a bottom-up approach where possible: 1. TAM — total demand; state the formula and each input 2. SAM — the slice you can realistically serve (segment/geo filters) 3. SOM — obtainable in [[TIMEFRAME]] given your channels/capacity 4. List every assumption + a source-type or sanity check for each 5. Sensitivity: which assumption moves the number most Be explicit when you're estimating vs guessing. Show the math.

ROLE: Revenue operations analyst. TASK: Run a win/loss analysis on the [[DEAL_NAME]] deal (outcome: [[OUTCOME]]). INPUTS: What happened: [[DEAL_NOTES]]. Competitors involved: [[COMPETITORS]]. ANALYZE: 1. The real reason it was won/lost (separate stated from actual) 2. Where in the funnel it turned 3. What we controlled vs didn't 4. 3 repeatable lessons (process, message, or product) 5. One change to make before the next similar deal Be blunt. Flattering post-mortems are useless.

ROLE: Risk manager. TASK: Build a risk register for [[INITIATIVE]]. For each risk: description, category (technical/market/financial/operational/legal), likelihood (L/M/H), impact (L/M/H), score, owner, mitigation, and early-warning signal. Then: - Sort by score and highlight the top 3 to act on now - Distinguish risks to mitigate vs accept vs transfer - Name one "unknown unknown" worth probing CONTEXT: [[CONTEXT]]. Output as a clean table + the top-3 action summary.

ROLE: Hiring manager reducing bias. TASK: Build a scoring rubric for the "[[ROLE]]" interview. For each criterion ([[CRITERIA]]) define a 1–4 scale with a concrete behavioral anchor at each level (what a 1 looks like vs a 4). Add: - Weighting per criterion + rationale - A "must-have vs nice-to-have" split - Space for evidence (quotes), not just scores - A decision rule (e.g., no criterion below X) Goal: two interviewers should score the same candidate within one point.

ROLE: SEO analyst. TASK: Classify the keywords below by search intent and map each to a content type and funnel stage. For each keyword output: intent (informational / commercial / transactional / navigational), funnel stage (TOFU/MOFU/BOFU), recommended page type, and a priority (High/Med/Low) given we sell [[PRODUCT]]. Then summarize: where the list is weighted, and the 3 highest-leverage gaps to create content for. KEYWORDS: [[KEYWORD_LIST]]

Writing Style Analysis You are an experienced expert in text and style analysis with 20 years of experience. Your task is to analyze an existing text and create a writing pattern that helps in imitating a writing style. A writing pattern is a digital writing style fingerprint, consisting of lexical, syntactic, structural, and idiosyncratic features. It includes a description of the tone, style, and can consider the use of creativity, humor, and figurative language as well as complexity and other aspects. Analyze the following text or the specified URL regarding style, tone, expression, structure, and specific features. Once you have done that, create a comprehensive representation of the writing style as a prompt, and ask me what kind of text should be created based on it.

You are an AI assistant with web access and the ability to transform search data into applicable results. Follow this workflow: Search and Analysis Search the web for the desired information, such as rankings, current data, or product details. Analyze the search results and present a concise, structured summary (e.g., as a table or list). Creation and Export Further process the researched data and create practical results. Examples: Tables: Generate Excel or CSV files from the data. HTML files: Create an HTML file that includes the data and hotlinks to images or sources. Reports: Write compact, well-structured reports. Flexibility and Adaptation Respond to changes or additional requirements. Provide clear instructions on how the results can be used.

Mach mit deiner vorigen Antwort einen Faktencheck. Am besten nutzt du dafür ein anderes Sprachmodell, zum Beispiel Claude, Mistral oder Gemini. Am allerbesten ist für einen Faktencheck jedoch Perplexity geeignet.

Erstelle einen Beispielbericht über [dein Produkt] eines Wettbewerbers auf der Grundlage von Online-Kundenbewertungen. Bei dieser Analyse konzentriere dich auf die Benutzerfreundlichkeit des Produkts.

Erstelle eine Umfrage, um die Präferenzen und Bedürfnisse der Nutzer für eine neue [dein Produkt] für [deine Zielgruppe] zu ermitteln.

Welches sind die wichtigsten Trends in [Branche], die ich in meinen nächsten [Details zu deinem Newsletter] aufnehmen kann?

Gebe eine Liste von semantisch relevanten Themen an, die für [dein Thema] wichtig sind.

Teste mein Wissen zum Thema &#8222;[Thema]&#8220; mit 5 offenen Prüfungsfragen. Warte nach jeder Frage auf meine Antwort und bewerte sie dann mit einer kurzen Rückmeldung (inhaltlich richtig, unvollständig, falsch + Erklärung).

Erstelle 3-5 datenbasierte Argumentationsfolien zum Thema [DEIN THEMA]. Folgende Daten und Fakten stehen zur Verfügung: - [DATENPUNKT 1] - [DATENPUNKT 2] - [DATENPUNKT 3] ... Für jede Folie: 1. Formuliere eine prägnante, faktenbasierte Überschrift 2. Strukturiere die Kernaussagen in logischer Reihenfolge 3. Schlage passende Visualisierungsformen vor (Diagramm, Tabelle, Infografik) 4. Formuliere eine klare Schlussfolgerung, die das Argument unterstützt

These are our three strategic priorities for this year [list the priorities]. What KPIs should we consider for measuring success?

What are the biggest problems faced by [audience] in the [industry]?

I want to A/B test the subject lines of this email. Give me ten ideas for subject lines and ten ideas for pre-headers. Then insert the email.

Transform this unstructured AI output into a professional format: **Raw output:** [[SELECTED_TEXT]] **Desired target format:** [[FORMAT]] (Report / Table / Presentation / Email / JSON / Markdown / Notion page) **Target audience:** [[AUDIENCE]] **Use case:** [[PURPOSE]] Please: 1. Structure the content logically (most important first) 2. Apply the desired format consistently 3. Cut redundancies – keep only the essentials 4. Add meaningful headings and groupings 5. Highlight key statements, numbers, recommendations 6. Prepare a directly copy-paste ready output

Help me choose the right AI model for my use case: **Task/Use case:** [[TASK]] **Budget:** [[BUDGET]] (Free / Low / Doesn't matter) **Requirements:** [[REQUIREMENTS]] (Speed / Quality / Privacy / Context length / Multimodal) **Frequency:** [[FREQUENCY]] (once / daily / API integration) Deliver: 1. **Top 3 model recommendations** for this use case with justification 2. **Comparison table:** strengths, weaknesses, costs, context window 3. **Prompt strategy** that works for the recommended model 4. **Pitfalls** to know about for this model 5. **Cost estimate** for regular use

Create optimized prompts for AI image generation: **Image idea:** [[IMAGE_IDEA]] **Style:** [[STYLE]] (Photorealistic / Illustration / Oil painting / Digital Art / Comic / ...) **Mood/Atmosphere:** [[MOOD]] **Tool:** [[TOOL]] (Midjourney / DALL-E 3 / Stable Diffusion / Flux) Deliver: 1. **Base prompt** (clear & precise) 2. **Extended prompt** with style, lighting, composition, camera angle 3. **Negative prompts** (what should NOT be in the image) 4. **3 variations** for different interpretations 5. **Parameter recommendations** (aspect ratio, quality settings) 6. **Iteration tips:** How do I refine the output?

Design an AI prompt workflow for the following task: **Task to be automated:** [[TASK]] **Input (what I provide):** [[INPUT]] **Desired output:** [[OUTPUT]] **Tool/Platform:** [[TOOL]] (ChatGPT / Claude / API / Zapier / ...) Deliver: 1. **Workflow diagram** (steps as text flow) 2. **Prompt for each step** – fully written out 3. **Variables** that need to be customized 4. **Error handling** – what to do if a step fails? 5. **Quality control** – how do I check the output? 6. **Optimization potential** – what else could I automate?

Create a professional system prompt for an AI assistant: **Assistant name:** [[NAME]] **Purpose/Use case:** [[PURPOSE]] **Target audience using it:** [[USERS]] **Tone & personality:** [[TONE]] **Domain:** [[DOMAIN]] **Restrictions:** [[RESTRICTIONS]] (what must it never do?) System prompt structure: 1. **Role definition** – who is this assistant? 2. **Core competencies** – what can it do particularly well? 3. **Behavior rules** (dos & don'ts) 4. **Communication style** – how does it speak? 5. **Handling ambiguities** – how does it ask for clarification? 6. **Hard limits** – what does it never do under any circumstances? 7. **Example interaction** (User → Assistant) Format the final prompt for direct copy-paste.

Optimize my prompt using advanced prompt engineering techniques: **My prompt:** [[SELECTED_TEXT]] **Target output:** [[EXPECTED_RESULT]] **AI model:** [[MODEL]] (if known) Optimize according to: 1. **Role & context** – assign the AI a precise expertise role 2. **Task deconstruction** – break complex tasks into clear sub-steps 3. **Output specification** – define format, length, structure, tone precisely 4. **Examples (Few-Shot)** – insert 1-2 examples of desired output 5. **Constraints** – what should the AI explicitly NOT do? 6. **Quality check** – have the AI critically review its own output 7. **Chain-of-thought** – request step-by-step thinking where appropriate Provide the final improved prompt + explanation of each change.

Build a prompt that makes the AI self-critique and improve its output. THE TASK: [[TASK]] WHAT "GOOD" LOOKS LIKE: [[QUALITY_BAR]] Produce a prompt structure that makes the AI: 1. Produce a first draft 2. Critique it against specific criteria ([[CRITERIA]]) — honestly, finding real weaknesses 3. Revise based on its own critique 4. Confirm the final version meets the bar (or flag what still falls short) 5. Show only the final answer (or both, if I want to see the reasoning) Make the self-critique substantive, not a rubber-stamp "looks good".

Write a video generation prompt for [[TOOL]] (Sora, Runway, Veo, Kling, etc.). WHAT I WANT TO SEE: [[SCENE]] MOOD/STYLE: [[STYLE]] DURATION/FORMAT: [[FORMAT]] Produce: 1. A detailed prompt covering: subject, action, setting, camera (shot type, movement, angle), lighting, mood, and style 2. The specific cinematic terms that improve results 3. What to specify vs leave open 4. A negative/avoid note (artifacts, unwanted elements) 5. 2 variations (different camera or mood) 6. Tips for getting consistent results across clips Make it vivid and concrete, not vague.

Help me adapt a prompt from one model to another. THE PROMPT: """ [[PROMPT]] """ FROM MODEL → TO MODEL: [[FROM_TO]] WHAT'S GOING WRONG ON THE NEW MODEL: [[PROBLEM]] Deliver: 1. Why the prompt may behave differently on the new model 2. A rewritten version tuned to the target model's strengths/quirks 3. Formatting/structure adjustments that help the new model 4. What to add or remove (some models need more/less hand-holding) 5. A test input to confirm it now works Keep the original intent; optimize the delivery.

Build a prompt that makes AI a strong brainstorming partner. WHAT I'M BRAINSTORMING: [[TOPIC]] GOAL/CONSTRAINTS: [[CONSTRAINTS]] HOW WILD vs PRACTICAL: [[RANGE]] Produce a prompt that makes the AI: 1. Ask me 1–2 clarifying questions first if needed 2. Generate ideas across distinct angles (not 10 variations of one) 3. Include a few safe bets AND a few bold/unexpected ones 4. Build on my reactions rather than dumping a list 5. Pressure-test the best ideas (what would make each work/fail) 6. Help me converge on 2–3 to pursue Make it a dialogue, not a one-shot list.

Help me write a negative prompt for AI image generation. WHAT I'M GENERATING: [[SUBJECT]] TOOL: [[TOOL]] (Stable Diffusion, Flux, Midjourney…) PROBLEMS I'M SEEING: [[PROBLEMS]] (extra fingers, blurry, watermark, bad anatomy…) Deliver: 1. A negative prompt targeting the specific issues I described 2. A general-purpose negative prompt baseline for quality 3. Which terms matter most for my subject type 4. What NOT to over-negate (it can hurt results) 5. How negatives differ by tool (or if the tool ignores them) Keep it focused — bloated negatives backfire.

Help me pick and use icons consistently. PRODUCT/BRAND STYLE: [[STYLE]] WHERE ICONS APPEAR: [[USAGE]] Deliver: 1. An icon style direction (outline/filled, weight, corner style) that fits the brand 2. Sizing and grid/keyline rules for visual consistency 3. When to use icon-only vs icon+label (and accessibility implications) 4. A recommended icon set/library and how to keep additions consistent 5. Common misuse (decorative noise, ambiguous metaphors) 6. Color and state rules for icons

Write a system prompt for a customer-support AI for [[COMPANY]]. WHAT WE SELL: [[PRODUCT]] COMMON QUESTIONS: [[COMMON_TOPICS]] TONE: [[TONE]] WHEN TO ESCALATE TO A HUMAN: [[ESCALATION]] THINGS IT MUST NOT DO: [[GUARDRAILS]] Produce: 1. Identity, scope, and tone rules 2. How to handle: known issues, angry customers, out-of-scope, and unknowns 3. The escalation trigger and handoff message 4. Response format (length, links, next step) 5. Refund/policy boundaries it must respect 6. 2 example exchanges

Write the instructions for a custom AI assistant. WHAT IT'S FOR: [[PURPOSE]] WHO USES IT: [[USERS]] WHAT IT SHOULD DO: [[CAPABILITIES]] WHAT IT SHOULD NEVER DO: [[GUARDRAILS]] TONE: [[TONE]] Produce: 1. A clear role/identity statement 2. Step-by-step behavior for its main tasks 3. Scope and refusal rules 4. Output format defaults 5. A few example interactions (good responses) 6. An opening message for first-time users Keep every line behavior-changing. No filler.

Turn this one-off prompt into a reusable template. THE PROMPT: """ [[PROMPT]] """ Do this: 1. Identify the parts that change each time 2. Replace them with clear [[PLACEHOLDER]] variables (good names) 3. Add a short "fill these in" list explaining each variable 4. Tighten the instructions so it works across inputs 5. Note any variable that's optional vs required Return the clean templated prompt ready to save and reuse.

Help me write a logo brief for a designer. BRAND/BUSINESS: [[BRAND]] WHAT IT DOES: [[WHAT_IT_DOES]] PERSONALITY (3 words): [[PERSONALITY]] AUDIENCE: [[AUDIENCE]] LOGOS I LIKE / DISLIKE: [[REFERENCES]] WHERE IT'LL BE USED: [[USAGE]] Deliver a brief covering: brand essence, must-haves/must-avoids, style direction, color leanings, usage contexts (favicon to billboard), and deliverables to request. Add 5 questions a good designer would ask that I should answer up front.

Write caption options for my post so I can pick the best. PLATFORM: [[PLATFORM]] WHAT THE POST SHOWS: [[CONTENT]] GOAL: [[GOAL]] (engagement, clicks, saves, sales) VOICE: [[VOICE]] Give me 5 caption variants with different angles: - Hook/curiosity - Story/personal - Value/tip - Question to spark comments - Direct/CTA Each with a fitting first line (the hook), right length for the platform, and a CTA. Mark your top pick and why.

Help me write a [[ROLE]] toast (best man, maid of honor, parent, friend). ABOUT THE COUPLE: [[ABOUT_THEM]] HOW I KNOW THEM: [[RELATIONSHIP]] A STORY I COULD TELL: [[STORY]] TONE: [[TONE]] (funny, sweet, mix) Write a toast that: - Opens with a hook, not "for those who don't know me" - Includes one genuine story - Has a light laugh or two (nothing embarrassing) - Lands on a sincere note and a toast line - Runs about [[LENGTH]] when spoken Give me the speech + delivery tips.

Give me conversation starters for this situation. SETTING: [[SETTING]] (networking, party, date, new coworkers…) WHO'S THERE: [[PEOPLE]] MY COMFORT LEVEL: [[COMFORT]] Provide: 1. 5 easy openers that aren't "so what do you do?" 2. 3 follow-up questions to keep it flowing 3. A way to gracefully exit a conversation 4. One topic to avoid here Make them natural and low-pressure, matched to the setting.

Write a birthday message that feels personal. WHO: [[PERSON]] — our relationship: [[RELATIONSHIP]] SOMETHING SPECIFIC ABOUT THEM: [[DETAIL]] TONE: [[TONE]] (funny, heartfelt, casual) Make it: - Specific to them, not "happy birthday, hope it's great" - In my voice - The right length for [[CHANNEL]] (text, card, social) Give me 3 options with different vibes.

ROLE: System-prompt architect. TASK: Design a role/persona system prompt for an assistant that: [[ASSISTANT_PURPOSE]]. Audience: [[AUDIENCE]]. Channel: [[CHANNEL]]. DELIVER: 1. Identity & expertise (specific, not "helpful assistant") 2. Scope: what it does and explicitly does NOT do 3. Tone & style rules (with a do/don't example) 4. Behavioral rules: how to handle uncertainty, refusals, and out-of-scope asks 5. Output conventions (format, length defaults) 6. A few-shot example of an ideal exchange Keep it tight — every line should change behavior.

ROLE: Expert prompt engineer who writes prompts for others. TASK: Turn my rough request into a high-quality, reusable prompt. MY ROUGH REQUEST: [[ROUGH_REQUEST]] INTENDED MODEL: [[MODEL]]. WHO WILL USE IT: [[END_USER]]. PRODUCE: 1. A clarifying check — list any assumptions you had to make 2. The finished prompt with: clear role, context, task, step guidance, output format, and constraints 3. [[PLACEHOLDER_STYLE]]-style placeholders for the variable parts 4. A one-line usage note 5. One optional "advanced" variant for power users Optimize for clarity and reuse, not cleverness.

ROLE: Reasoning-prompt designer. TASK: Build a prompt that gets a model to reason carefully through: [[PROBLEM_TYPE]]. DELIVER: 1. A role + task framing 2. Explicit reasoning steps to follow (the scaffold) for this problem type 3. Instruction to show work, then give a clearly separated final answer 4. A self-check step before finalizing (verify against constraints) 5. Output format that separates reasoning from the answer (so it's parseable) 6. A note on when to hide vs show the reasoning to the end user Tune it so reasoning improves accuracy without rambling.

ROLE: Screenwriter with an ear for subtext. TASK: Write a dialogue scene between [[CHARACTER_A]] and [[CHARACTER_B]]. SITUATION: [[SCENE_SITUATION]]. What each secretly wants: A=[[A_WANT]], B=[[B_WANT]]. RULES: - People rarely say what they mean — use subtext and what's left unsaid - Distinct voices (vocabulary, rhythm, what each avoids) - Conflict or tension under the surface, even if polite - Action/beat lines sparingly to show, not tell - End on a shift — someone gains or loses ground TONE: [[TONE]]. Keep it to roughly one page. Format as a screenplay.

ROLE: Prompt engineer specializing in in-context learning. TASK: Design few-shot examples for the task: [[TASK_DESCRIPTION]]. Model/target: [[MODEL]]. Desired output format: [[OUTPUT_FORMAT]]. DELIVER: 1. 3–5 examples that cover the input variety (easy, typical, and a hard/edge case) 2. Each example showing input → exact desired output (consistent formatting is the lesson) 3. At least one example demonstrating how to handle ambiguity or a tricky case 4. Notes on example ordering and why 5. A short instruction preamble to pair with the examples Make the examples teach the boundaries, not just the happy path.

ROLE: Character-driven novelist. TASK: Develop a character for a [[GENRE]] story: [[CHARACTER_SEED]]. BUILD: - Surface: name, age, role, first impression - Want (conscious goal) vs Need (what they actually lack) - The wound/backstory driving them - A defining contradiction (something at odds with themselves) - Voice: how they speak, a verbal tic, what they never say - Relationships & how they change under pressure - The arc: who they are at the start vs who they could become End with a single scene idea that reveals their core in action.

ROLE: Innovation facilitator. TASK: Run SCAMPER on [[SUBJECT]] to generate new directions. For each lens, give 2–3 concrete ideas: - Substitute - Combine - Adapt - Modify/Magnify - Put to another use - Eliminate - Reverse/Rearrange Then: 1. Cluster the ideas into 3 themes 2. Pick the 2 most promising (novel × feasible) and sketch what testing them looks like 3. Flag the wildest idea worth keeping for later GOAL/CONSTRAINTS: [[GOAL]]. Push past the obvious first answers.

ROLE: Award-winning copywriter. TASK: Generate taglines for [[BRAND_OR_PRODUCT]] that [[CORE_BENEFIT]] for [[AUDIENCE]]. Produce 15 options organized by angle: - Benefit-led (what they get) - Emotional (how they'll feel) - Bold/provocative - Playful/witty - Simple/declarative Each ≤7 words. After the list, pick your top 3 and explain in one line why each works. Brand personality: [[PERSONALITY]]. Avoid clichés ("unleash", "elevate", "next level").

ROLE: Worldbuilder and lore architect. TASK: Develop a worldbuilding bible for a [[GENRE]] world centered on the theme [[THEME]]. DEVELOP: 1. Core premise & the one rule that makes this world different 2. Geography & key locations (with mood) 3. Power systems / magic / tech — and its costs and limits 4. Factions: 3–4 with goals, conflicts, and who hates whom 5. History: 3 pivotal events shaping the present 6. Everyday life & culture details that make it feel lived-in 7. The central tension a story could exploit Keep internal consistency: every rule should create both possibility and limitation.

ROLE: Typographer / brand designer. TASK: Build a typography system for [[BRAND]] with personality [[PERSONALITY]], used on [[MEDIUM]] (web/app/print). DELIVER: 1. A heading + body font pairing (with web-safe/free alternatives) and why they fit the brand 2. A modular type scale (sizes + line-heights for h1–h6, body, caption) 3. Weight and styling rules (when bold, when not) 4. Readability & accessibility notes (min sizes, contrast, line length) 5. Do/don't examples Keep it to a system a non-designer could apply consistently.

ROLE: Story structure expert. TASK: Generate plot twist options for: [[STORY_PREMISE]] (genre: [[GENRE]]). Produce [[NUMBER]] distinct twists. For each: - The twist itself - What the reader believed before (the misdirection) - The clues you'd plant earlier so it feels earned, not random - How it recontextualizes earlier events - The emotional payoff Rank them by how well they serve the theme [[THEME]]. Avoid twists that betray character logic or punish the reader.

ROLE: Brand & UI designer. TASK: Build a color palette for [[BRAND]] whose personality is [[BRAND_PERSONALITY]] and audience is [[AUDIENCE]]. DELIVER: 1. Primary, secondary, and accent colors (with hex) + the rationale/psychology 2. A neutral scale (backgrounds, text, borders) 3. Semantic colors (success/warning/error/info) 4. Light & dark mode considerations 5. Accessibility: which text/background pairs pass WCAG AA, which to avoid 6. Usage rules (do/don't) so it stays consistent Output as a tidy reference with hex codes.

A [Adjective] [Subject] in a [Location] during [Time of Day]. The image is in the style of [Artist/Style] and shows [special features or details]. The lighting is [Lighting Type], and the atmosphere is [Mood]. The image is in high resolution, with [technical details like camera settings or image quality]. Negative Prompt: [undesired elements or styles]

You are a prompt generator for AI images, and your task is to create detailed prompts. You ask me about the following points and provide examples for each point that one could choose from: subject, action, lighting, camera angle, color scheme, mood, and atmosphere.

Erzähle eine kurze Einschlafgeschichte über einen 5-jährigen Jungen mit dem Namen [Namen des Kindes] und einen Drachen, der Fahrrad fahren lernen will.

Upload: 3–4 clear photos of your pet from different angles. Create a professional character design sheet of this pet as a 3D animated character. Include: - Front view - Side profile - 3/4 view - Back view - Close-up of the face showing expression - A small walking animation pose lineup Keep the pet’s exact coloring, markings, and unique features consistent across all angles. Use a Pixar/Disney-style 3D look with clean cel-shading. Include a small color palette with hex codes for the main fur and eye colors. Use a clean white background with a subtle grid. Add the character’s name at the top. 4K resolution, suitable for a pitch deck.

Schlage kreative visuelle Designkonzepte für eine Präsentation zum Thema [DEIN THEMA] vor. Die Präsentation wird [KONTEXT/SETTING] gezeigt und soll [EMOTIONALE WIRKUNG] vermitteln. Für das Gesamtdesign: 1. Entwickle ein konsistentes Farbschema (3-4 Farben mit HEX-Codes) und begründe die Wahl 2. Schlage passende Schriftarten für Überschriften und Fließtext vor 3. Empfehle einen visuellen Stil (minimalistisch, illustrativ, fotografisch, etc.) Für konkrete Folienelemente: - Design-Ideen für Titelfolie - Vorschläge für wiederkehrende visuelle Elemente - Ideen für Diagramme und Datenvisualisierungen - Gestaltungsvorschläge für Übergänge zwischen Themen

Entwickle eine emotionale Storytelling-Sequenz von 3-4 Folien für eine Präsentation zum Thema [DEIN THEMA]. Die Geschichte soll: 1. Mit einer realen oder hypothetischen Situation beginnen, die das Problem verdeutlicht 2. Einen "Helden" einführen, der mit diesem Problem konfrontiert ist 3. Den Wendepunkt zeigen, an dem die Lösung ins Spiel kommt 4. Mit einem positiven Ergebnis und einer klaren Botschaft enden Für jede Folie: - Beschreibe kurz den Inhalt (max. 2-3 Sätze) - Schlage ein emotionales Bild oder eine Metapher vor - Formuliere eine kurze, kraftvolle Überschrift - Gib an, welche Emotion bei dieser Folie angesprochen werden soll

Erstelle eine packende Einleitung für eine Präsentation zum Thema [DEIN THEMA]. Die Präsentation richtet sich an [ZIELGRUPPE] und soll [HAUPTZIEL] erreichen. Entwickle für die ersten 3 Folien: 1. Eine überraschende Eröffnung mit einer kraftvollen Headline 2. Ein relevantes Problem oder eine Herausforderung, die das Publikum betrifft 3. Eine kurze Vorschau auf die Lösung und den Nutzen für das Publikum Ergänze jede Folie mit: - Prägnanten Stichpunkten (max. 20 Wörter pro Punkt) - Einem Vorschlag für ein passendes visuelles Element - Einer kurzen Sprechnotiz (30-50 Wörter)

List ways to market my brand on TikTok.

Create a structured onboarding plan: **Position:** [[POSITION]] **Team:** [[TEAM]] **Key systems/tools:** [[TOOLS]] **Main goals during probation:** [[GOALS]] **Days 1-5 (Orientation):** - Administrative basics - Getting to know the team - First insights into systems **Week 2-4 (Foundations):** - Understanding processes - First own tasks - Feedback meeting after 2 weeks **Month 2 (Integration):** - Independent work on tasks - Stakeholder meetings - Mid-point check-in **Month 3 (Full integration):** - Complete ownership - 90-day review: goals & expectations - Development plan for the first year

Develop a customer retention and upselling strategy: **Product/Service:** [[PRODUCT]] **Customer segment:** [[SEGMENT]] **Average customer value:** [[VALUE]]/year **Current churn rate:** [[CHURN]] % **Upselling potential:** [[UPSELL_PRODUCT]] Deliver: 1. **Customer success playbook** – when and how do I contact existing customers? 2. **Health score** – which signals indicate churn risk? 3. **Upselling moments** – when is the best time? 4. **Upselling conversation** – opening, transition, presentation, close 5. **Loyalty measures** – what keeps customers long-term? 6. **Reactivation sequence** for churned customers 7. **Referral program** – how do I get customers to recommend?

Help me make the case for a raise. MY ROLE: [[ROLE]] CURRENT PAY: [[CURRENT_PAY]] TARGET: [[TARGET]] MY WINS / ADDED VALUE: [[ACHIEVEMENTS]] MARKET CONTEXT: [[MARKET]] Deliver: 1. A tight business case (impact in numbers where possible) 2. The specific number to ask for and how to anchor it 3. An opening script for the conversation 4. How to handle "not now" / "no budget" 5. A fallback ask (non-salary) if money is off the table Confident, evidence-led, not entitled.

Help me follow up on an overdue invoice. CLIENT: [[CLIENT]] INVOICE AMOUNT: [[AMOUNT]] HOW OVERDUE: [[DAYS_OVERDUE]] PRIOR CONTACT: [[PRIOR_CONTACT]] Give me an escalating sequence: 1. Friendly reminder (assume they forgot) 2. Firmer follow-up with the due date and a clear ask 3. Final notice before late fees / pausing work 4. The line that signals consequences without threats Keep each short and professional. Tell me the right gap between each.

Help me answer the "what's your biggest weakness?" interview question. ROLE: [[ROLE]] A REAL WEAKNESS I HAVE: [[WEAKNESS]] WHAT I'M DOING ABOUT IT: [[IMPROVEMENT]] Craft an answer that: - Is honest (not "I'm a perfectionist") - Picks a real but non-disqualifying weakness for this role - Shows self-awareness and concrete steps I'm taking - Stays brief and ends on growth Give the answer + which weaknesses to AVOID mentioning for this role.

Help me build a STAR answer for a behavioral interview question. THE QUESTION: [[QUESTION]] THE EXPERIENCE I'LL USE: [[EXPERIENCE]] THE SKILL THEY'RE TESTING: [[SKILL]] Structure it as: - Situation (brief context) - Task (what I was responsible for) - Action (what I specifically did — the meat) - Result (the outcome, with a number if possible) Keep it ~90 seconds. Cut rambling. Flag if my example is weak and suggest how to strengthen it.

Act as my interviewer for a [[ROLE]] position. MY BACKGROUND: [[BACKGROUND]] INTERVIEW TYPE: [[TYPE]] (behavioral, technical, screening…) DIFFICULTY: [[LEVEL]] Do this: 1. Ask me one realistic interview question at a time 2. Wait for my answer 3. Give brief, specific feedback (what worked, what to improve) 4. Then ask the next question, getting gradually tougher Start with an opener. After ~6 questions, give an overall assessment and my top 2 things to work on.

Help me prepare for a difficult conversation. WHO WITH: [[PERSON]] WHAT IT'S ABOUT: [[TOPIC]] WHAT I WANT FROM IT: [[DESIRED_OUTCOME]] WHAT I'M WORRIED ABOUT: [[WORRY]] Give me: 1. A calm opening line that sets the tone 2. How to state my view using "I" not "you" attacks 3. Questions to understand their side 4. How to handle defensiveness or it getting heated 5. A way to land on a next step Provide a short script + the 3 things NOT to say.

Help me negotiate a lower price or bill. WHAT: [[BILL_OR_PRODUCT]] CURRENT PRICE: [[CURRENT_PRICE]] MY LEVERAGE: [[LEVERAGE]] (loyalty, competitor offer, budget, etc.) CHANNEL: [[PHONE_OR_EMAIL]] Give me: 1. A polite opening that signals I might leave/cancel 2. The specific ask (number or %), anchored reasonably 3. 2 fallback positions if they say no 4. Phrases to stay friendly but firm 5. When to walk away Make it a script I can read almost word-for-word.

Write a follow-up to someone who hasn't replied. CONTEXT: [[CONTEXT]] WHAT I'M WAITING ON: [[WHAT_I_NEED]] HOW MANY TIMES I'VE FOLLOWED UP: [[TIMES]] Make it: - Short and easy to respond to (give them an out) - Free of guilt-tripping ("just circling back", "per my last email") - Adds a small reason to reply now - One clear ask Give me 2 versions: friendly and more direct.

ROLE: Manager onboarding a new hire. TASK: Build a 30-60-90 day plan for [[NAME]] joining as [[ROLE]] on [[TEAM]]. For each phase define: focus theme, learning goals, deliverables, people to meet, and the success signal. - 30: learn & land (relationships, context, first small win) - 60: contribute (owns a real piece) - 90: operate independently (measurable outcome) Add: how I'll support each phase, and the 2 leading indicators that this hire is thriving vs struggling. Keep expectations humane.

ROLE: Manager + HR partner writing a fair PIP. TASK: Draft a PIP for [[ROLE]] addressing the gap: [[PERFORMANCE_GAP]]. INCLUDE: - Specific, observable performance concerns (facts, examples, dates — no vague labels) - Clear, measurable expectations and the standard to meet - Concrete support offered (training, coaching, resources) - Timeline + check-in dates over [[DURATION]] - What success looks like and the consequence if not met - A respectful, non-punitive tone aimed at recovery Note: this is a draft to review with HR/legal, not legal advice.

ROLE: People manager. TASK: Build a recurring 1-on-1 template for me and my report [[REPORT_NAME]] (cadence: [[CADENCE]]). INCLUDE: - Opening check-in (energy/wellbeing) - Their agenda first (what's on their mind) - Progress, blockers, and where they need air cover - Growth/career thread (revisit goal: [[GROWTH_GOAL]]) - Feedback both ways - Clear action items + owner Add 5 rotating questions to keep it from going stale, and a note on what NOT to use 1-on-1s for.

ROLE: Solutions consultant. TASK: Build a demo script for [[PRODUCT]] tailored to [[PROSPECT]] whose top pains are [[PAINS]]. STRUCTURE: - Recap of their goals (confirm before showing anything) - Demo flow: 3–4 "moments that matter" — for each, the pain → the feature → the outcome in their words - Discovery questions to weave in mid-demo - Where to pause for reactions - Handling the "can it do X?" curveball - Trial close + clear next step Avoid the feature-tour trap. Tie every click to their pain.

ROLE: Consultative sales rep. TASK: Build a discovery call question set for selling [[PRODUCT]] to [[BUYER_ROLE]]. ORGANIZE questions by: 1. Current state & process 2. Pain & cost of inaction (quantify it) 3. Desired outcome & success criteria 4. Decision process, timeline, budget, stakeholders (qualify) 5. Objection-surfacing questions For each section give 3–4 open questions phrased to invite stories, plus one "go deeper" follow-up. End with a strong close-the-call question to set next steps.

ROLE: Talent partner designing a structured interview. TASK: Build interview questions for the role "[[ROLE]]" assessing competencies: [[COMPETENCIES]]. For each competency provide: - 1 behavioral question (STAR-elicitable) - A follow-up probe - A "looks like a strong answer" vs "red flag" note for the interviewer Add 2 role-specific situational questions and 1 question that tests for [[KEY_TRAIT]]. Keep questions inclusive and free of culture-fit vagueness — assess skills and values, not sameness.

ROLE: SDR/AE who books meetings. TASK: Write a [[NUMBER]]-touch follow-up sequence to [[PROSPECT_ROLE]] after [[TRIGGER_EVENT]]. Each touch: - Has a distinct angle (value add, social proof, new insight, soft break-up) - Is ≤90 words, one clear CTA - References their context: [[CONTEXT]] - Never says "just following up" or "bumping this" Provide subject lines, body, and the recommended day-gap between touches. End the sequence with a respectful break-up email.

ROLE: Product marketing / sales enablement. TASK: Create a battlecard for [[OUR_PRODUCT]] vs [[COMPETITOR]]. INCLUDE: - One-line positioning vs them - Where we win (with the proof/demo to show) - Where they win (be honest) + how to reframe - Landmines to set early in the deal - Trap questions to ask the prospect - Objection → response for their top 3 talking points - Migration/switching story Keep it to a single skimmable card a rep can use live.

ROLE: Recruiter who treats candidates like future customers. TASK: Write a rejection email to [[CANDIDATE_NAME]] for the "[[ROLE]]" role, at stage [[STAGE]]. REQUIREMENTS: - Warm, human, and prompt — no false hope - If interviewed: 1 genuine, specific positive - Honest-but-kind framing of the decision (no "we went with someone more qualified" filler) - Optional: invite to apply to [[FUTURE_FIT]] or join talent pool - Leave them feeling respected Provide a short version (early stage) and a fuller version (final stage).

ROLE: Partnerships lead. TASK: Draft a partnership proposal from [[YOUR_COMPANY]] to [[PARTNER]]. GOAL: [[PARTNERSHIP_GOAL]]. What each side brings: us=[[YOUR_ASSETS]], them=[[THEIR_ASSETS]]. INCLUDE: - The shared opportunity (lead with their upside) - Proposed model (referral / co-marketing / integration / reseller) - What each side does and gets — make the value symmetric - Success metrics & a small first step to prove it - Clear next action TONE: collaborative, specific, low-pressure. Make it easy to say "let's pilot it".

ROLE: Pitch coach. TASK: Outline an investor pitch deck for [[COMPANY]] raising a [[ROUND]] round. For each slide give the headline takeaway + the 2–3 points to support it: 1. Problem 2. Solution 3. Why now 4. Market size (TAM/SAM/SOM) 5. Product 6. Business model 7. Traction 8. Competition / moat 9. Go-to-market 10. Team 11. Financials / projections 12. The ask & use of funds INPUTS: [[KEY_FACTS]]. Flag the single slide that will make or break this raise and why.

ROLE: Account executive closing a deal. TASK: Write an email delivering a quote for [[OFFER]] to [[CLIENT]] at [[PRICE]]. The email should: - Restate the outcome they're buying (and its value/ROI) - Present the price anchored to that value, not in isolation - Make the package/options clear (and steer to the recommended one) - Include terms, what's included, and validity date - End with a single, easy next step + a gentle deadline TONE: confident, not apologetic about price. ≤180 words.

ROLE: Manager who delegates outcomes, not tasks. TASK: Write a delegation brief for handing "[[TASK]]" to [[PERSON_OR_ROLE]]. INCLUDE: - The outcome and why it matters (the bigger goal) - Definition of done / acceptance criteria - Constraints, resources, and who to ask for help - Decision rights (what they can decide vs must check) - Deadline and check-in point - What "good" looks like (an example or anti-example) Tone: trusting, not micromanaging. Keep it under one screen.

ROLE: Digital PR / link builder. TASK: Write a backlink outreach email to [[SITE_NAME]] about linking to our resource "[[OUR_RESOURCE]]". ANGLE: [[OUTREACH_ANGLE]] (broken link / resource add / better stat / guest contribution). The email must: - Personalize line 1 with something specific about their page "[[THEIR_PAGE]]" - Give them a reason that helps THEIR readers (not us) - Be ≤120 words with one clear ask - Have a non-pushy subject line (give 3 options) Then add a short, polite follow-up version.

ROLE: Field/event marketer. TASK: Build a promotion plan for the webinar "[[WEBINAR_TITLE]]" on [[DATE]], targeting [[AUDIENCE]]. GOAL: [[REGISTRATION_GOAL]] registrations. DELIVER: - Core value proposition + 3 hook angles - Channel plan (email, social, partners, paid) with cadence from T-[[LEAD_TIME]] to live - Email sequence outline (invite, reminder, last-call, "you missed it" replay) - Social post angles (3) - Registration page bullet points - Post-event follow-up for attendees vs no-shows Include a simple timeline table.

ROLE: Customer marketing lead. TASK: Write an outreach message asking [[CUSTOMER_NAME]] for a testimonial about [[PRODUCT]]. The ask must: - Reference a specific result they got: [[KNOWN_RESULT]] - Make it low-effort (offer to draft from their answers) - Ask 3 guiding questions that produce a story (before → change → after), not adjectives - Specify where it'll be used and get permission - Respect their time; ≤120 words Then provide a 2nd version for a quick video testimonial ask.

Upload : 3–5 separate portrait photos of different people from the team. Create a single professional group photo that looks like everyone was physically together. Scene: Modern office conference room with large windows and a city view. Natural afternoon light entering from the left. Arrange all people around a conference table in a natural meeting pose: some sitting, one standing and presenting, casual but professional. Match lighting direction and intensity across all faces. Keep each person’s outfit, hairstyle, and appearance exactly as in their reference photo. Ensure shadows, reflections on the table, and perspective are consistent. The final image should look like a real corporate photo, not a collage. 4K resolution, landscape orientation.

Erstelle starke Call-to-Action Abschlussfolien für eine Präsentation zum Thema [DEIN THEMA]. Das Hauptziel der Präsentation ist [GEWÜNSCHTE HANDLUNG]. Entwickle: 1. Eine zusammenfassende Folie mit den 3-4 wichtigsten Takeaways 2. Eine motivierende CTA-Folie mit klaren nächsten Schritten 3. Eine optionale Q&A-Übergangsfolie Für die CTA-Folie: - Formuliere einen prägnanten, handlungsorientierten Titel - Beschreibe die gewünschte Handlung klar und konkret - Gib einen überzeugenden Grund, warum JETZT gehandelt werden sollte - Füge einen Zeitrahmen oder Deadline hinzu (falls zutreffend) - Schlage ein starkes visuelles Element vor, das Dringlichkeit vermittelt

I need to create a sales sequence for people attending my webinar. Please create an outline for these emails to ensure they achieve the desired success.

I need more reviews. Please help me create a campaign to ask customers for recommendations.

The majority of my business comes through referrals. Help me create messages that I can give to past clients and partners to make it easier for them to refer me and send me business. I need three versions: 1. a single sentence; 2. an email; and 3. a social media post.

My company is known for [describe value propositions]. What are four ways to properly communicate this expertise in our offers?

I am creating a re-engagement campaign. Give me six ideas for emails I can send to re-engage those who haven't opened an email in the last nine months.

Here is a transcript of me talking about my onboarding process. Please help me design a document that I can share with clients to inform them.

I am [title] in a [describe company] that sells [products or services]. We market to [target audience], whose pain points are [list pain points]. What objections might they have?

What marketing tactics should I use to reach my target audience? Make sure to describe your target audience precisely.

How can influencer marketing generate leads?

Generate the AIDA formula for [product or service].

Write a compelling email subject line to convince potential customers to switch to our service.

Create an ad campaign about [product, service, or company] targeting [audience]. Add core messages and slogans and choose the best media channels for the promotions.

Create a user journey map: **Product/Service:** [[PRODUCT]] **Persona:** [[PERSONA]] (description or name) **Scenario:** [[SCENARIO]] (What does the user want to achieve?) **Touchpoints:** [[TOUCHPOINTS]] (Which channels are involved?) For each phase of the journey: | Phase | User actions | Thoughts | Feelings | Pain points | Opportunities | Typical phases: 1. Awareness 2. Consideration 3. Decision 4. Usage/Onboarding 5. Retention Additionally: - Visualize emotion curve (description) - Identify top 3 moments of truth - Recommendations for the most critical pain points

Conduct a complete UX audit: **Product:** [[PRODUCT]] (URL or description) **Target audience:** [[AUDIENCE]] **Main user goal:** [[USER_GOAL]] **Device focus:** [[DEVICE]] (Desktop / Mobile / Both) Analyze according to Nielsen's 10 Usability Heuristics: 1. Visibility of system status 2. Match between system and real world 3. User control and freedom 4. Consistency and standards 5. Error prevention 6. Recognition rather than recall 7. Flexibility and efficiency of use 8. Aesthetic and minimalist design 9. Help users recognize/recover from errors 10. Help and documentation For each heuristic: rating (1-5), finding, concrete improvement suggestion **Priority list:** Top 5 quick wins + 3 strategic measures

Help me design a mobile app screen. SCREEN PURPOSE: [[SCREEN]] WHAT THE USER NEEDS TO DO HERE: [[USER_GOAL]] PLATFORM: [[PLATFORM]] (iOS, Android, both) KEY DATA/ACTIONS: [[CONTENT]] Deliver: 1. A layout structure (top to bottom: nav, content priority, actions) 2. The primary action and how to make it obvious 3. Platform conventions to respect (and where to follow them vs deviate) 4. Thumb-reach and one-handed-use considerations 5. Empty, loading, and error states for this screen 6. Accessibility notes Prioritize the one thing the user came here to do.

Help me set up a spacing and grid system. PRODUCT/PLATFORM: [[PLATFORM]] CURRENT INCONSISTENCY: [[PROBLEM]] Deliver: 1. A spacing scale (e.g., 4/8px base) and when to use each step 2. A layout grid (columns, gutters, margins) for key breakpoints 3. Rules for padding vs margin and component spacing 4. Vertical rhythm with the type scale 5. How to name spacing tokens 6. Do/don't examples that fix the current inconsistency Make spacing decisions automatic, not case-by-case.

Help me spec animations/transitions for my UI. WHERE: [[INTERACTION]] (page load, modal open, button press, list update…) PRODUCT FEEL: [[FEEL]] (snappy, calm, playful) Deliver: 1. What should animate (and what should NOT) 2. Duration and easing recommendations per interaction 3. Loading states: skeleton vs spinner vs progress — which and when 4. Enter/exit transitions that aid understanding (where things come from/go) 5. Performance & reduced-motion (accessibility) handling 6. The line between helpful motion and annoying motion Motion should explain or delight, never just decorate.

Help me design a reusable visual template system for social posts. PLATFORM(S): [[PLATFORMS]] BRAND VIBE: [[VIBE]] CONTENT TYPES I POST: [[CONTENT_TYPES]] (quotes, tips, announcements…) Deliver: 1. 3–4 template layouts (one per content type) described clearly 2. A consistent system: colors, fonts, spacing, logo placement 3. What stays fixed vs what changes per post 4. How to keep it recognizable while varied 5. Free tools to build these in Aim for instantly-recognizable and fast to produce.

Help me design my email newsletter layout. NEWSLETTER ABOUT: [[TOPIC]] AUDIENCE: [[AUDIENCE]] GOAL: [[GOAL]] (clicks, replies, sales, loyalty) SECTIONS I WANT: [[SECTIONS]] Deliver: 1. A scannable layout (order of sections, what's above the fold) 2. A subject-line + preview-text approach 3. Where to put the main CTA (and how many CTAs max) 4. Mobile-first formatting rules 5. A repeatable template so each issue is fast to make Optimize for skimmers.

ROLE: Product designer focused on activation. TASK: Design the onboarding flow for [[PRODUCT]] whose "aha moment" is [[AHA_MOMENT]]. NEW USER GOAL: [[USER_GOAL]]. Constraint: get to value in [[STEP_BUDGET]] steps. DELIVER: 1. The activation milestone we're optimizing for 2. Step-by-step flow (what we ask vs defer, and why) 3. Where to use progressive disclosure vs upfront setup 4. Empty-state → first-win path 5. The one step most likely to cause drop-off + how to de-risk it 6. A success metric for the flow Cut anything that doesn't move the user toward the aha moment.

ROLE: Product designer who sweats the edge states. TASK: Design the non-happy-path states for "[[FEATURE]]" in [[PRODUCT]]. For each state below, specify: what the user sees, the message/microcopy, the primary action, and the emotional goal: - Empty (first use, nothing yet) - Empty (filtered/search, no results) - Loading / skeleton - Error (recoverable) and error (blocking) - Success / completion Keep copy human and action-oriented. Turn dead ends into next steps. Brand voice: [[BRAND_VOICE]].

ROLE: UX writer. TASK: Write microcopy for "[[UI_ELEMENT]]" in a [[PRODUCT_TYPE]]. CONTEXT: The user is trying to [[USER_GOAL]] and feels [[USER_EMOTION]]. PROVIDE 3 variants each for: label/CTA, helper text, error state, success state. VOICE: [[BRAND_VOICE]]. CONSTRAINT: button labels ≤ [[MAX_CHARS]] chars. For each set, mark the recommended option and say why in ≤8 words. No jargon, no blame in error states.

Search the web for today’s top 5 cryptocurrencies by market cap: Bitcoin, Ethereum, Solana, Cardano, and XRP. Get their current prices and 24-hour percentage changes. Create a dark-themed financial dashboard inspired by professional trading terminals: - Deep blue-black background - Green accents for positive changes - Red accents for negative changes For each cryptocurrency, show: - Name and ticker - Current price (large text) - 24-hour percent change - A small 7-day sparkline chart Layout everything in a 16:9 dashboard suitable for presentation slides. Add a subtle grid in the background and a small “Last updated: [current date & time]” label at the bottom. 4K resolution.

Upload : Any author quote with author’s name. Create a premium editorial quote card (Instagram portrait format) featuring a realistic portrait on the left and the quote on the right. The text area should take about two-thirds of the image and the portrait about one-third, with a smooth gradient transition that blends the portrait edge into the background. Use a deep midnight navy background with a subtle gradient (e.g., #07162A → #0B2340). Set the quote text in soft champagne gold (e.g., #E6D3A6) — not orange, not bronze. Use the same champagne tone (or a slightly lighter off-white) for the thin divider line and the author name. Add a large, subtle opening quotation mark in a very low-opacity champagne tint (10–15%). Important: avoid brown/sepia/tan tones completely. Typography (match premium quote-card design): Use a clean, modern geometric sans-serif for the quote (Helvetica/Neue-style, Gotham-style, or similar), with medium weight for the main quote and lighter weight for the author line. Keep it extremely legible (no decorative serif fonts, no script, no heavy stylization). Use generous line spacing and consistent left alignment. Text (must be EXACT, do not change any words, punctuation, capitalization, or spacing): "Mark my words — A.I. is far more dangerous than nukes" Author line (smaller, exact): “Elon Musk” Layout: Place oversized opening quotation marks near the top-left of the text block. Place the quote beneath it, left-aligned. Near the bottom-left of the text block, add a thin horizontal line and place the author name under it. Keep ample padding around all text. No extra icons, logos, hashtags, or additional text. Output: Create a portrait image at 1080×1080 optimized for Instagram, with crisp, sharp, perfectly readable text and a polished magazine-style finish.

Upload : Product packaging photo or flat design with English text. Localize this exact packaging design into 6 language versions: 1) Japanese 2) Arabic 3) Spanish 4) German 5) Simplified Chinese (Mandarin) 6) Hindi (Devanagari script) Translate ALL visible text into the correct language for each version. Preserve the layout exactly: same logo position, colors, shapes, and imagery. For Japanese, keep vertical text where appropriate. For Arabic, use proper right-to-left layout. Make all text sharp, aligned, and professional, as if originally designed in that language. Deliver 6 separate images, each clearly showing the localized packaging, at 4K resolution suitable for print mockups.

Upload : Rough pencil sketch of a logo idea on paper. Turn this rough logo sketch into 8 professional logo variations: 1) Minimalist black line art on white. 2) Gradient blue-to-purple modern tech style. 3) Vintage badge with subtle distressed texture. 4) Neon glow logo on a dark background. 5) Watercolor artistic interpretation with soft edges. 6) Bold geometric version with simplified shapes. 7) Gold foil embossed look on dark card stock. 8) Hand-lettered organic style with natural curves. Keep the core logo concept and symbol recognizable in every variation, but explore clearly different visual directions. Present all 8 versions in a 4×2 grid, each variation clearly separated with a small label beneath it. High resolution, 4K, suitable for client presentations.

Upload : One high-quality product photo on a white background. Show this exact product in 4 lifestyle scenes: 1) On a minimalist home office desk with a MacBook and coffee. 2) Inside a gym bag with a towel and water bottle. 3) On a restaurant table with wine glasses and candlelight. 4) In an open backpack on a forest hiking trail. Keep the product IDENTICAL in every image: same angle, same materials, same reflections, same color, same logo placement. Adjust only the environment, props, and lighting style. Use natural depth of field. Output 4 separate images at 2000×2000, ready for an e-commerce carousel.

Entwickle ein Konzept für eine 15-minütige Präsentation über '[dein Thema]'. Erstelle: 1) Eine packende Einstiegsfolie, 2) Maximal 10 Hauptfolien mit Kernbotschaften, 3) Interaktive Elemente zur Einbindung des Publikums, 4) Eine überzeugende Schlussfolie. Berücksichtige dabei die Zielgruppe: [beschreibe deine Zuhörer]

Welche Mikro-Interaktionen sind bei der Entwicklung einer [dein Produkt] zu berücksichtigen?

Erstelle einen Typografie-Leitfaden für eine [deine Anwendung].

Generiere Beispiele für UI-Design-Anforderungen für eine [deine Anwendung].

Welche Arten von visuellen Darstellungen, wie Bilder oder Infografiken, wären nützlich, um den Inhalt des Artikels zum Thema [dein Thema] zu unterstützen?

Überarbeite und verbessere die folgende Präsentationsfolie: [FOLIENINHALT EINFÜGEN] Optimiere die Folie hinsichtlich: 1. Klarheit und Prägnanz der Botschaft 2. Visueller Wirkung und Layout 3. Sprachlicher Präzision und Überzeugungskraft Bitte liefere: - Eine überarbeitete Version des Folieninhalts - Vorschläge für ein verbessertes visuelles Layout - 2-3 alternative Überschriften mit mehr Impact - Tipps zur Präsentation dieser Folie

Help me write a creative brief for developing a new logo so I can give it to my designer.

Give me six ideas for headlines for a landing page about [product name] for [target audience].

Here is a script for a 30-second explainer video for our [product], which explains [what the product does] for [target audience]. Please give me a list of the different shots or animations I should include. Insert the script.

How can I convert this blog post into an infographic? Please give me an overview. Then insert the content of the blog post.

Create three ideas for call-to-action buttons based on the content of this blog post: [Insert the URL or content of the article].

Create documentation for a design system component: **Component:** [[COMPONENT]] (Button / Modal / Form / Card / Navigation / ...) **Product:** [[PRODUCT]] **Tech stack:** [[TECH]] (React / Vue / Web Components / Figma) Documentation structure: 1. **Purpose & usage** – when and why is it used? 2. **Variants** – all states and types (Primary/Secondary/Disabled/Loading) 3. **Props/Properties** – name, type, default, description, required? 4. **Do's & don'ts** – correct vs. incorrect usage with examples 5. **Accessibility** – ARIA labels, keyboard support, screen reader 6. **Code example** (complete, copy-pasteable) 7. **Responsive behavior** – how does the component change? 8. **Related components** – what belongs together?

Conduct an accessibility check: **Design/Product:** [[DESCRIPTION]] **Conformance target:** [[WCAG]] (WCAG 2.1 Level A / AA / AAA) **Target audience with disabilities:** [[AUDIENCE]] Check against WCAG criteria: **Perceivable:** - Text contrast (min. 4.5:1 for normal, 3:1 for large text) - Alt texts for all images - Captions for videos - No information conveyed by color alone **Operable:** - Full keyboard navigation - Sufficient time for interactions - No flashing content **Understandable:** - Consistent navigation - Helpful error messages **Robust:** - Compatible with screen readers For each finding: severity (Critical / Major / Minor), description, fix recommendation

Write a complete design brief: **Client:** [[COMPANY]] **Project:** [[PROJECT]] (New product / Redesign / Single feature / Campaign) **Target audience:** [[AUDIENCE]] **Business goal:** [[GOAL]] **Timeline:** [[DATE]] **Budget:** [[BUDGET]] Structure: 1. **Project background & context** 2. **Problem to be solved** 3. **Target audience** (primary & secondary users with brief personas) 4. **Design goals & success criteria** 5. **Brand guidelines & constraints** (existing systems, CI, technology) 6. **Scope** – what is IN / what is OUT of scope 7. **Deliverables** – what is expected? 8. **Feedback process & approvals** 9. **Inspirations & style references** (including what should NOT fit)

Create a detailed wireframe concept: **Product type:** [[TYPE]] (Website / App / Dashboard / Landing page) **User task to be solved:** [[TASK]] **Target audience:** [[AUDIENCE]] **Business goal:** [[GOAL]] Describe for each screen: 1. **Purpose** of this screen (1 sentence) 2. **Main element** that enables the user action 3. **Information hierarchy** (what is most/least prominent?) 4. **Navigation & flows** (where can the user go from here?) 5. **Interactive elements** (buttons, forms, links) 6. **Edge cases** (empty states, loading, errors) Screens: [[SCREEN_LIST]] (e.g. Homepage, Product page, Checkout, Confirmation) As ASCII layout or structured text description.

Suggest hashtags/keywords for my post. PLATFORM: [[PLATFORM]] POST TOPIC: [[TOPIC]] MY NICHE / AUDIENCE: [[NICHE]] Provide: 1. A mix of broad, niche, and specific tags (so I'm not lost in huge feeds) 2. Grouped by reach (high competition vs discoverable) 3. The recommended number for this platform 4. 2–3 to put in the first comment vs caption (if relevant) 5. Tags to AVOID (banned/spammy/irrelevant) Tailor it to the platform's actual best practices.

Help me write a sympathy message. I don't want to say the wrong thing. WHO I'M WRITING TO: [[RECIPIENT]] THEIR LOSS: [[LOSS]] MY RELATIONSHIP TO THEM: [[RELATIONSHIP]] A MEMORY OR DETAIL (if any): [[DETAIL]] Write something that: - Acknowledges the loss simply and sincerely - Avoids clichés and "at least…" silver linings - Offers specific support if appropriate - Is warm and brief Give a short version and a slightly fuller one. Gentle tone.

Someone sent me an angry/heated message. Help me respond so it de-escalates. THEIR MESSAGE: """ [[THEIR_MESSAGE]] """ WHAT'S ACTUALLY TRUE: [[THE_FACTS]] MY GOAL: [[GOAL]] Write a reply that: - Lowers the temperature (acknowledge feeling, don't match the heat) - Sticks to facts without being defensive or sarcastic - Fixes or clarifies what's reasonable - Sets a calm boundary if they're being unfair Give a brief version and a fuller version.

Help me say no to this without feeling guilty or being rude. THE REQUEST: [[THE_REQUEST]] WHO'S ASKING: [[WHO]] WHY I CAN'T / WON'T: [[REASON]] Write a decline that: - Is warm but unambiguous (no false "maybe") - Gives a brief honest reason without over-justifying - Offers an alternative only if I want to: [[ALTERNATIVE_OR_NONE]] - Keeps the relationship intact Keep it short. Give a direct version and a softer version.

I need to reply to this email and it's a bit difficult. Help me respond well. THEIR EMAIL: """ [[THEIR_EMAIL]] """ MY GOAL: [[WHAT_I_WANT]] MY RELATIONSHIP TO THEM: [[RELATIONSHIP]] Write a reply that: - Stays calm and professional (no defensiveness) - Acknowledges their point before making mine - Is clear about [[WHAT_I_WANT]] without over-explaining - Ends with a concrete next step Give me one concise version and one warmer version.

Shorten the text below. I want the core message in far fewer words. TEXT: """ [[TEXT]] """ OUTPUT: 1. A one-sentence TL;DR 2. A tightened version (~[[TARGET_LENGTH]]) 3. Any key detail I should NOT have cut, flagged Keep my meaning and tone. Remove repetition, hedging, and throat-clearing.

Rewrite this to feel warmer and more human, while keeping it concise. TEXT: """ [[TEXT]] """ RELATIONSHIP: [[RELATIONSHIP]] Keep the message and ask the same. Add warmth through word choice and a friendly open/close — not by adding fluff or fake enthusiasm. Give the rewrite plus a more casual variant.

Help me reschedule or cancel something. WHAT: [[EVENT_OR_MEETING]] WHY: [[REASON]] DO I WANT TO RESCHEDULE? [[RESCHEDULE_OR_CANCEL]] Write a message that: - Gives enough notice and a brief reason (no over-sharing) - Takes responsibility, doesn't make them chase me - Proposes a concrete new time if rescheduling - Stays warm and low-drama Keep it short. Tone: [[TONE]].

Help me introduce two people over email. PERSON A: [[PERSON_A]] — [[A_CONTEXT]] PERSON B: [[PERSON_B]] — [[B_CONTEXT]] WHY CONNECT THEM: [[REASON]] Write an intro that: - Says why each is worth the other's time (1 line each) - States the suggested next step clearly - Hands the thread over to them - Is short and skimmable Also give me a one-line "permission to intro?" message to send first.

Help me ask for a favor. THE FAVOR: [[FAVOR]] WHO I'M ASKING: [[WHO]] WHY THEM: [[WHY_THEM]] Write a message that: - Makes the ask specific and small (lower the effort) - Explains briefly why it matters and why them - Gives an easy way to decline - Offers something in return if relevant: [[RECIPROCITY]] Don't be over-apologetic. Confident but respectful.

Explain this investment opportunity to me clearly ⚠️: **Investment type:** [[INVESTMENT]] (ETF / Stock / Real estate / Crypto / Bonds / ...) **My prior knowledge:** [[PRIOR_KNOWLEDGE]] (None / Basic / Advanced) **My situation:** [[SITUATION]] (Age, risk tolerance, time horizon) Deliver: 1. **What is it?** – simple, honest explanation 2. **How does it work?** – mechanism in 5 steps 3. **Historical returns** & realistic expectations 4. **Risks** – what can go wrong? Worst case? 5. **Tax treatment** (general overview) 6. **Who is it suitable for?** – and who NOT? 7. **Getting started:** What would be first small steps? 8. **Common mistakes** beginners make ⚠️ Not investment advice.

Create a detailed travel plan: **Destination:** [[DESTINATION]] **Duration:** [[DAYS]] days, arrival: [[DATE]] **Travelers:** [[PEOPLE]] (Solo / Couple / Family with [[AGE]]-year-old child / Group) **Budget:** approx. [[BUDGET]] **Travel style:** [[STYLE]] (Backpacker / Comfort / Luxury / Culture / Adventure / Relaxation) **Interests:** [[INTERESTS]] Deliver: 1. **Day-by-day travel plan** – flexible with A/B options 2. **Must-see vs. hidden gems** – what do tourists skip? 3. **Accommodation recommendations** per budget category 4. **Food & drink** – local specialties & restaurants 5. **Transport tips** (between places & locally) 6. **Budget breakdown** 7. **Packing list** for this destination 8. **Important cultural rules** & safety tips

Generate the disclaimers I need for my content. WHAT I PUBLISH: [[CONTENT_TYPE]] (blog, video, finance/health tips, reviews…) DO I USE AFFILIATE LINKS / SPONSORSHIPS? [[MONETIZATION]] ANY ADVICE-LIKE CONTENT? [[ADVICE_TYPE]] Provide: 1. An affiliate/advertising disclosure (FTC-style) 2. A "not professional advice" disclaimer if relevant (financial/health/legal) 3. A results-may-vary / accuracy disclaimer 4. Where to place each 5. Short and long versions DISCLAIMER: general info, not legal advice.

Help me write a DMCA / copyright takedown notice. MY ORIGINAL WORK: [[MY_WORK]] WHERE IT'S BEEN COPIED: [[INFRINGING_URL]] PROOF I OWN IT: [[PROOF]] SEND TO: [[RECIPIENT]] (host, platform, search engine) Include the required elements: - Identification of my copyrighted work - The infringing material and its location - A good-faith statement and statement of accuracy - My contact info and signature line - A clear demand to remove it DISCLAIMER: template only, not legal advice. Don't file false claims.

Help me request my full security deposit back from a landlord. MOVE-OUT DATE: [[MOVE_OUT]] DEPOSIT AMOUNT: [[DEPOSIT]] CONDITION I LEFT IT IN: [[CONDITION]] ANY DISPUTE: [[DISPUTE]] Write a letter that: - Requests the full return by the legal/agreed deadline - References the move-out condition and any documentation (photos) - Politely cites tenant rights to a deposit return where relevant - States what I'll do if it's wrongfully withheld List what evidence to include. DISCLAIMER: general info, not legal advice — check local tenancy law.

Help me build an emergency fund plan. MONTHLY ESSENTIAL EXPENSES: [[ESSENTIAL_EXPENSES]] CURRENT SAVINGS: [[CURRENT_SAVINGS]] HOW MUCH I CAN SET ASIDE MONTHLY: [[MONTHLY_SAVINGS]] JOB STABILITY: [[STABILITY]] Deliver: 1. My target fund size (and why — months of expenses for my situation) 2. How many months it'll take at my current pace 3. Where to keep it (accessible but separate) 4. One realistic way to speed it up 5. What counts as a true emergency vs not Practical and non-judgmental.

Draft a demand letter for an unpaid invoice. WHO OWES ME: [[DEBTOR]] AMOUNT & FOR WHAT: [[AMOUNT_AND_WORK]] DUE DATE & HOW OVERDUE: [[OVERDUE]] PRIOR ATTEMPTS: [[PRIOR_CONTACT]] Include: - A clear statement of the debt and its basis - A firm demand with a specific payment deadline - The consequence of non-payment (next steps), stated factually - A professional, unemotional tone - What records to attach DISCLAIMER: A draft for review, not legal advice — consult a lawyer for serious amounts.

Help me file a warranty/refund claim. PRODUCT: [[PRODUCT]] PROBLEM: [[PROBLEM]] PURCHASE INFO: [[WHEN_WHERE]] WHAT I WANT: [[REPAIR_REPLACE_REFUND]] Write a claim message that: - States the fault and timeline clearly and unemotionally - References the warranty/return policy or consumer right if relevant - Asks for a specific outcome with a reasonable deadline - Stays polite but leaves no wiggle room List what proof to include. (General info, not legal advice.)

Help me cancel [[SERVICE]] without getting talked out of it. WHY I'M CANCELLING: [[REASON]] WILL I ACCEPT A DISCOUNT TO STAY? [[OPEN_TO_OFFER]] Give me: 1. A clear cancellation message/script 2. How to respond to "are you sure?" and retention offers 3. What to confirm in writing (effective date, no more charges) 4. A line to use if they make it hard to cancel Keep it firm and polite.

Help me dispute a charge I shouldn't have been billed. THE CHARGE: [[CHARGE_DETAILS]] WHY IT'S WRONG: [[WHY_WRONG]] WHO TO: [[MERCHANT_OR_BANK]] Write: 1. A clear, factual dispute message with the key details and dates 2. The specific resolution I'm asking for (refund/reversal) 3. A reference to relevant proof I should attach 4. A firm-but-polite escalation line if they refuse Note: general info, not legal advice. Keep records of everything.

ROLE: Fractional CFO. TASK: Build a [[MONTHS]]-month cash flow forecast for [[BUSINESS]]. INPUTS: Starting cash: [[STARTING_CASH]]. Revenue streams + timing: [[REVENUE]]. Fixed costs: [[FIXED_COSTS]]. Variable/one-off costs: [[VARIABLE_COSTS]]. DELIVER: 1. Month-by-month opening balance, inflows, outflows, closing balance 2. The month cash gets tightest (and why) 3. Runway in months at current burn 4. 3 levers to extend runway, ranked by impact vs pain 5. Assumptions list + what to watch weekly Flag any month that goes negative in bold.

ROLE: Practical personal finance coach. TASK: Build a monthly budget for someone earning [[MONTHLY_INCOME]] with goals [[GOALS]]. INPUTS: Fixed costs: [[FIXED_COSTS]]. Variable habits: [[VARIABLE_SPENDING]]. Debts: [[DEBTS]]. DELIVER: 1. A category breakdown (suggest a framework like 50/30/20 but adapt to their reality) 2. Specific monthly euro/dollar targets per category 3. Where they're likely overspending + a realistic cut 4. How much to direct to savings/debt and in what order 5. One automation to set up so it runs itself No shaming. Make it sustainable, not maximally austere.

ROLE: Money-saving auditor. TASK: Audit recurring subscriptions/costs and recommend cuts. LIST (name, cost, billing cycle, last used): [[SUBSCRIPTION_LIST]] Context: this is for [[PERSONAL_OR_BUSINESS]]. DELIVER: 1. Normalize everything to a monthly + annual cost 2. Total annual spend (the number that hurts) 3. Categorize: keep / downgrade / cancel / negotiate — with a reason each 4. Quick wins: the 3 cancellations with best savings-to-pain ratio 5. A "review again on [[REVIEW_DATE]]" reminder plan Estimate total annual savings if all recommendations are taken.

ROLE: Monetization strategist. TASK: Compare pricing models for [[PRODUCT]] sold to [[CUSTOMER]]. Evaluate the relevant options (flat, tiered, per-seat, usage-based, freemium, hybrid) against: revenue predictability, alignment to customer value, expansion potential, sales friction, and operational complexity. DELIVER: 1. A comparison table scoring each model for THIS business 2. The recommended model + the runner-up 3. A starter price structure with 2–3 tiers 4. The biggest risk of the chosen model and how to hedge it 5. One metric to watch to know if pricing is wrong CONTEXT: [[CONTEXT]].

ROLE: Contracts drafter producing a plain, balanced first draft. TASK: Draft a [[NDA_TYPE]] (mutual / one-way) NDA between [[PARTY_A]] and [[PARTY_B]] for the purpose of [[PURPOSE]]. INCLUDE standard clauses: definition of Confidential Information, exclusions, obligations, permitted disclosures, term & survival ([[TERM]]), return/destruction, no-license, remedies, governing law ([[JURISDICTION]]), and boilerplate. REQUIREMENTS: - Plain, balanced language (not one-sided) - Bracketed placeholders for anything unspecified - A short "review checklist" of the 5 clauses most worth negotiating DISCLAIMER: This is a starting draft, not legal advice — have a lawyer review before signing.

ROLE: Policy writer balancing customer trust and business protection. TASK: Write a refund/return policy for [[BUSINESS_TYPE]] selling [[PRODUCT_TYPE]]. SPECIFY: - Eligibility window and conditions ([[REFUND_WINDOW]]) - What is / isn't refundable (and why, briefly) - The exact steps to request a refund - Timeline for processing - Exchanges/store credit options - Edge cases (digital goods, sale items, subscriptions) TONE: clear, friendly, scannable. Avoid legalese where plain words work. DISCLAIMER: review against your local consumer law.

ROLE: Drafter of a firm but professional demand letter. TASK: Draft a cease & desist letter from [[SENDER]] to [[RECIPIENT]] regarding [[ISSUE]] (e.g., IP infringement, defamation, contract breach, harassment). INCLUDE: - Clear statement of the offending conduct and when it occurred - The legal basis / right being violated (in plain terms) - The specific demand (stop X, remove Y, respond by [[DEADLINE]]) - Consequence of non-compliance, stated factually (not threats) - Professional, unemotional tone DISCLAIMER: Draft for review by a qualified attorney; not legal advice.

ROLE: Financial analyst. TASK: Run a break-even analysis for [[PRODUCT]]. INPUTS: Price per unit: [[PRICE]]. Variable cost per unit: [[VARIABLE_COST]]. Fixed costs: [[FIXED_COSTS]]. DELIVER: 1. Contribution margin per unit and as a % 2. Break-even in units and in revenue (show the formula) 3. Units needed to hit a [[TARGET_PROFIT]] profit 4. Sensitivity: what break-even becomes if price ±10% or variable cost ±10% 5. The one lever that most improves the picture Explain each number in plain language for a non-finance founder.

ROLE: Contracts drafter for service work. TASK: Outline a service agreement between [[PROVIDER]] and [[CLIENT]] for [[SERVICES]]. SECTIONS to draft (with key terms): - Scope of work & deliverables - Timeline & milestones - Fees, payment schedule, late fees ([[PAYMENT_TERMS]]) - Revisions & scope-change handling - IP ownership & licensing - Confidentiality - Termination & kill fee - Liability cap & indemnity - Governing law ([[JURISDICTION]]) Flag the 3 clauses freelancers most often get burned by. DISCLAIMER: not legal advice — have it reviewed.

ROLE: Debt-payoff coach. TASK: Build a payoff plan for these debts: [[DEBT_LIST]] (balance, rate, minimum each). Monthly amount available for debt: [[MONTHLY_PAYMENT]]. DELIVER: 1. Avalanche order (highest rate first) — total interest + payoff date 2. Snowball order (smallest balance first) — total interest + payoff date + the motivation upside 3. A clear recommendation for THIS person given [[PERSONALITY_NOTE]] 4. The first 3 months' exact payment per debt 5. One way to accelerate without lifestyle pain Show the cost difference between the two methods.

ROLE: Founder writing to investors. TASK: Write the [[MONTH]] investor update for [[COMPANY]]. INPUTS: Highlights: [[HIGHLIGHTS]]. Lowlights: [[LOWLIGHTS]]. Key metrics: [[METRICS]]. Asks: [[ASKS]]. STRUCTURE: - TL;DR (3 bullets: one win, one challenge, one ask) - Metrics vs last period (with the honest story behind them) - What worked / what didn't - Specific asks (intros, hiring, advice) - Runway & plan TONE: candid and confident. Investors fund honesty + momentum, not spin. ≤500 words.

You are a local or long-term resident of [DESTINATION] who knows the real insider tips that aren't in the travel guide. Give me insider tips for: DESTINATION: [CITY/REGION] TRAVEL TIME: [WHEN?] INTERESTS: [FOOD/CULTURE/NATURE/NIGHTLIFE/SHOPPING/ART] ALREADY PLANNED: [WHICH MAINSTREAM SIGHTS?] HOW ADVENTUROUS: [VERY/MEDIUM/SAFER] Provide real insider tips: 1) FORGET THESE TOURIST TRAPS - Overrated: [What can you skip?] - Better alternative: [What instead?] - Waste of time: [What sounds good but is disappointing?] 2) LOCAL NEIGHBORHOODS - Where do young locals live? - Authentic neighborhoods - What's there? - How to get there? 3) EAT LIKE LOCALS BREAKFAST: - Where do locals have breakfast? - What to order? LUNCH: - Worker canteens - Hidden snack bars DINNER: - Local favorites (not TripAdvisor Top 10) - What is THE local specialty? STREET FOOD: - Best spots - What to try? 4) NIGHTLIFE INSIDER - Where do locals go out? - Hidden bars - Best days (not Saturday!) - Live music insider tips 5) NATURE & OUTDOOR - Unknown viewpoints - Secret beaches/parks - Hikes no one knows - Where locals picnic 6) CULTURE & ART - Alternative galleries - Street art hotspots - Local markets (not for tourists) - Hidden historical sites 7) SHOPPING INSIDER - Where do locals shop? - Flea markets and vintage - Crafts directly from artists - Souvenirs worth it (and which aren't) 8) EXPERIENCES NO ONE KNOWS - Courses and workshops - Local events and festivals - Unusual tours - Places only locals know 9) COMMUNICATION - 5 phrases that open doors - Behavior that pleases locals - Taboo topics 10) SECRET TIME WINDOWS - Best time of day for [Place] - When are attractions empty? - Weekdays vs. weekend

You are an experienced budget traveler who has traveled the world with little money and knows all the saving tricks. Give me budget travel tips for: DESTINATION: [COUNTRY/REGION] TRAVEL DURATION: [DAYS] CURRENT BUDGET: [TOTAL AMOUNT] FLEXIBLE TRAVEL TIME?: [YES/NO] MINIMUM COMFORT: [WHAT DO YOU NEED AT LEAST?] TRAVEL STYLE: [BACKPACKER/FLASHPACKER/BUDGET-CONSCIOUS] Provide comprehensive budget tips: 1) SAVE ON FLIGHTS - Best booking times - Use flexible date search - Low-cost carriers for [Destination] - Find error fares and deals - Stopover instead of direct flight - Collect miles and points - Open-jaw strategy 2) CHEAP ACCOMMODATION - Hostels: Best for [Destination] - Couchsurfing: How it works - Housesitting: Free accommodation - Airbnb hacks (long-term discounts) - Workaway/WWOOF: Work for room and board - Off-season: When are hotels cheap? - Stay outside the center 3) CHEAP FOOD - Street food: What's safe? - Find local markets - Cook yourself in hostels - Lunch menu instead of dinner - Where locals eat (not tourists) - Water: Tap water or refill stations? - Use happy hour 4) LOCAL TRANSPORT - Public vs. taxi/Uber - Know local apps - Bike rental - Walking the best option? - Night buses = save on accommodation - Shared taxis/collectivos 5) FREE ACTIVITIES - Free walking tours - Free museum days - Nature and parks - Festivals and events - Viewpoints and vistas - Beaches (which are free?) 6) BEST BUDGET TRAVEL TIME - When is off-season? - Shoulder season sweet spot - When is the most expensive time? 7) MONEY & PAYMENT - Best travel credit card (no foreign fees) - Cash: Where to withdraw cheapest? - Local currency vs. Euro - Bargaining: Where and how? 8) INSIDER SAVING TRICKS - Specific for [Destination] - Apps that help - Mistakes that cost money 9) DAILY BUDGET PLAN - Realistic budget per day - Breakdown: Sleep/food/transport/fun 10) BUDGET TRACKER - How to track expenses? - Recommend apps

You are an experienced traveler and packing expert who creates optimal packing lists for every type of trip. Create my packing list: TRAVEL TYPE: [BEACH VACATION/CITY TRIP/HIKING/BACKPACKING/BUSINESS/ROAD TRIP/CRUISE] DESTINATION: [WHERE?] DURATION: [DAYS] SEASON/WEATHER: [SUMMER/WINTER/RAINY SEASON/etc.] LUGGAGE: [CARRY-ON ONLY/SUITCASE/BACKPACK] TRAVELERS: [SOLO/WITH PARTNER/WITH CHILDREN] PLANNED ACTIVITIES: [HIKING/BEACH/GOING OUT/SPORTS/etc.] SPECIAL OCCASIONS: [BUSINESS MEETINGS/WEDDING/FESTIVAL/etc.] Provide a complete packing list: 1) DOCUMENTS & MONEY [ ] Passport (check validity!) [ ] ID card [ ] Visa (if needed) [ ] Flight tickets/bookings [ ] Travel health insurance [ ] Credit cards (at least 2) [ ] Cash in local currency [ ] Driver's license (international?) [ ] Copies of all documents (digital + paper) 2) CLOTHING Tops: [ ] T-shirts: X pieces [ ] Long sleeves: X pieces [ ] [Others depending on travel type] Bottoms: [ ] Pants: X pieces [ ] Shorts: X pieces [ ] [Others] Shoes: [ ] Everyday shoes [ ] [Hiking shoes/sandals/etc.] Miscellaneous: [ ] Underwear: X pieces [ ] Socks: X pairs [ ] Sleepwear [ ] Swimwear [ ] Jacket/raincoat 3) TOILETRIES [ ] Toothbrush & toothpaste [ ] Shampoo & shower gel (travel size!) [ ] Deodorant [ ] Sunscreen [ ] [Others as needed] [ ] Medications (bring prescriptions!) [ ] First aid kit 4) TECH [ ] Phone + charger [ ] Power bank [ ] Adapter (for [COUNTRY]) [ ] Camera [ ] Headphones [ ] E-reader 5) TRAVEL COMFORT [ ] Neck pillow [ ] Earplugs [ ] Sleep mask [ ] Travel pharmacy 6) ACTIVITY-SPECIFIC [Add according to travel type] 7) CARRY-ON ESSENTIALS - What MUST be in the carry-on? - Observe liquid rules 8) PACKING TIPS - Roll instead of fold - Use packing cubes - Plan outfit combinations - 1 emergency outfit in carry-on 9) CHECKLIST BEFORE DEPARTURE [ ] Secure home [ ] Arrange care for plants/pets [ ] Forward mail [ ] Inform bank

You are an experienced travel planner. Plan my trip to: [DESTINATION] Duration: [DAYS] Create for me: 1. A day-by-day itinerary 2. The main highlights I shouldn't miss 3. Practical tips on transport and accommodation 4. Insider tips off the beaten path Ask about my interests if helpful.

Erstelle mir einen Mietvertrag für eine möblierte Wohnung in [Stadt, Land], inklusive Kaution und Nebenkosten.

Help me with retirement planning ⚠️ (not investment advice): **Age:** [[AGE]] years **Planned retirement:** [[RETIREMENT_AGE]] **Current pension entitlements:** [[PENSION]]/month (if known) **Possible monthly savings rate:** [[SAVINGS_RATE]] **Risk tolerance:** [[RISK]] (Low / Medium / High) Deliver: 1. **Retirement gap calculation** – how much is missing monthly? 2. **The 3 pillars** of retirement provision explained (statutory, occupational, private) 3. **Overview of retirement instruments** (pros/cons) 4. **Compound interest calculation** – what does [[SAVINGS_RATE]]/month grow to by retirement? 5. **Account for inflation** 6. **Next steps** – what should I do NOW? ⚠️ Not investment advice.

Create a business financial plan ⚠️: **Business type:** [[TYPE]] (Startup / Freelance / SME / E-Commerce / ...) **Phase:** [[PHASE]] (Founding / Growth / Scaling) **Monthly revenue:** [[REVENUE]] **Monthly costs:** [[COSTS]] **Capital requirement:** [[NEED]] for [[PURPOSE]] Deliver: 1. **P&L overview** (profit and loss statement) 2. **Liquidity planning** – when does it get tight? 3. **Break-even analysis** 4. **Financing options** (loan / grants / investor / bootstrapping) 5. **KPIs** to track monthly 6. **Cash runway** – how long does the money last? 7. **Growth scenario calculation** (conservative / realistic / optimistic) ⚠️ Not tax or legal advice.

Explain tax-saving opportunities to me ⚠️ (not tax advice – overview only): **Situation:** [[SITUATION]] (Employed / Self-employed / Landlord / Investor) **Annual income:** [[INCOME]] gross **Special circumstances:** [[CIRCUMSTANCES]] (Home office / Business travel / Children / Real estate / ...) Deliver overview of: 1. **Work-related expenses** – what can I deduct? 2. **Special expenses** – insurance, retirement provision, donations 3. **Extraordinary burdens** – what falls under this? 4. **Tax bracket** – am I in the optimal one? 5. **For self-employed:** commonly forgotten business expenses 6. **Deadlines** – when must what be submitted? 7. **Is a tax advisor worthwhile?** – when and why? ⚠️ For specific tax questions always consult a tax advisor.

Help me understand and compare a loan ⚠️: **Loan amount:** [[AMOUNT]] **Term:** [[TERM]] months **Purpose:** [[PURPOSE]] **Offers (interest rates):** [[RATES]] Deliver: 1. **Total cost calculation** for each offer (interest + fees) 2. **Effective annual interest rate** explained 3. **Monthly payment** per offer 4. **Comparison:** Which offer is cheapest and why? 5. **Hidden costs** to watch out for (processing fees, residual debt insurance) 6. **Early repayment** – how much can I save by paying off early? 7. **Checklist** before I sign ⚠️ Not financial advice.

Create a structured financial plan ⚠️ (not financial advice): **Net income:** [[INCOME]]/month **Fixed expenses:** [[FIXED_COSTS]] **Variable expenses:** [[VARIABLE]] **Current savings:** [[SAVINGS]] **Debts:** [[DEBTS]] (interest rate: [[INTEREST_RATE]] %) **Financial goal:** [[GOAL]] by [[DATE]] Deliver: 1. **Budget analysis** – where does the money go? 2. **50/30/20 rule** applied to my numbers 3. **Savings potential** – concrete categories where I can cut 4. **Debt repayment strategy** (Avalanche vs. Snowball) 5. **Emergency fund** – how much and where? 6. **Savings plan** with concrete monthly amounts 7. **Goal achievement calculation** with timeframe ⚠️ Not investment advice – consult a financial advisor for investment decisions.

Analyze this freelancer/service contract ⚠️ (not legal advice): [[SELECTED_TEXT]] Focus on points critical for freelancers: 1. **Work contract vs. service contract** – distinction for bogus self-employment 2. **Fee & payment terms** – fair or one-sided? 3. **Copyright & IP** – who owns the created work? 4. **Confidentiality (NDA)** – scope and duration 5. **Non-compete clause** – how far does it reach? 6. **Liability clauses** – what happens with delays or defects? 7. **Termination** – under what conditions? 8. **Tax implications** – VAT, tax number ⚠️ For important contracts always consult a lawyer or freelancer association.

Write an effective complaint/complaint letter: **Problem:** [[PROBLEM]] (Defective product / Poor service / Incorrect billing / ...) **Company:** [[COMPANY]] **Date & reference number:** [[REFERENCES]] **Already undertaken:** [[PREVIOUS_STEPS]] **Desired resolution:** [[GOAL]] (Refund / Replacement / Rectification / Compensation) Structure: 1. Facts: What exactly happened? (facts, no emotions) 2. Legal basis: briefly mention (warranty, consumer protection) 3. Concrete demand with deadline 4. Announcement of next steps (consumer advice center, ombudsman, legal action) Tone: firm, factual, polite but clear

Formulate a professional demand letter: **Situation:** [[SITUATION]] (Unpaid invoice / Service not rendered / Contract breach) **Debtor:** [[DEBTOR]] **Amount/Service:** [[AMOUNT_OR_SERVICE]] **Due date:** [[DUE_DATE]] **Previous measures:** [[PREVIOUS_NOTICE]] (First / Second / Final notice) Structure: 1. Subject: clear and unambiguous 2. Facts: briefly state the claim with evidence 3. Deadline: clear deadline (typically 14 days) 4. Announcement of further steps: factual, not threatening 5. Contact option for amicable settlement Tone: factual, firm, professional (not aggressive) ⚠️ Not legal advice – consult a lawyer for larger amounts.

Explain this privacy policy to me in plain language ⚠️: [[SELECTED_TEXT]] Please answer: 1. **What data is collected?** (personal, technical, behavioral data) 2. **For what purpose?** (analytics, advertising, contract fulfillment, ...) 3. **Who is data shared with?** (third parties, partners, international transfers) 4. **How long is data stored?** 5. **What rights do I have?** (access, deletion, objection, data portability) 6. **Particularly critical points** I should know 7. **Comparison: Is this normal or unusual?** ⚠️ Not legal advice – contact a data protection officer or lawyer if uncertain.

Analyze this contract in plain language ⚠️ (not legal advice – for orientation only): [[SELECTED_TEXT]] Deliver: 1. **What is it about?** – contract type and essential content in 3 sentences 2. **My rights** – what may/can I do? 3. **My obligations** – what am I committing to? 4. **⚠️ Critical clauses** – unusual or one-sided formulations 5. **Term & termination** – how and when can I cancel? 6. **Penalties/Liability** – what does a violation cost me? 7. **What I could negotiate** – which clauses are typically negotiable? 8. **Recommendation:** Should I consult a lawyer? ⚠️ This is not legal advice. Always consult a lawyer for important contracts.

Help me optimize my sleep: **Current problem:** [[PROBLEM]] (Falling asleep / Staying asleep / Waking too early / Not feeling rested) **Sleep duration:** [[SLEEP_HOURS]] hours **Wake time:** [[WAKE_TIME]] **Known causes:** [[CAUSES]] (Stress / Screens / Caffeine / Irregularity / ...) Deliver: 1. **Sleep hygiene checklist** (evidence-based) 2. **Evening routine** (60-minute plan before sleep) 3. **Morning routine** that stabilizes the sleep-wake cycle 4. **Nutrition tips** for better sleep 5. **Environment optimization** (temperature, darkness, noise) 6. **Techniques for faster sleep onset** (4-7-8 breathing, body scan, etc.) 7. **When is a doctor visit advisable?**

Help me establish a new habit permanently: **Desired habit:** [[HABIT]] **Why it matters to me:** [[MOTIVATION]] **Context (when/where):** [[CONTEXT]] **Previous failed attempts:** [[FAILED_ATTEMPTS]] **Current disruptive habit:** [[BAD_HABIT]] (if relevant) Based on "Atomic Habits" (James Clear): 1. **Cue** – which trigger do I design? 2. **Craving** – how do I make the habit attractive? 3. **Response** – how do I make it easy? (2-minute rule) 4. **Reward** – immediate reward 5. **Habit stacking** – which existing habit do I attach it to? 6. **Environment design** – how do I shape my environment? 7. **Tracking method** & accountability 8. **If-then plan** for the 3 most common obstacles

Create a 7-day deceleration plan: **Main stressor:** [[STRESSOR]] (Work / Social media / Sensory overload / Burnout prevention) **Available time daily:** [[MINUTES]] minutes **What I must keep:** [[MUST_KEEP]] Plan for each day: - Morning routine (15-20 min.) - 1 mindfulness exercise - 1 digital detox measure - Evening ritual (10-15 min.) Additionally: - Social media fasting plan - 5 immediate measures for acute stress - Long-term habits that build resilience - When professional help is advisable

Create a progressive training plan: **Goal:** [[GOAL]] (Lose weight / Build muscle / Endurance / General fitness / Sport-specific) **Fitness level:** [[LEVEL]] (Beginner / Intermediate / Advanced) **Available time:** [[DAYS]] training days/week, [[MINUTES]] minutes each **Equipment:** [[EQUIPMENT]] (None / Dumbbells / Home complete / Gym) **Injuries/Restrictions:** [[RESTRICTIONS]] **Duration:** [[WEEKS]] weeks Deliver: - Training plan per week (days, muscle groups, exercises, sets/reps) - Progression principle (how do I improve week by week?) - Warm-up & cool-down routine - Recovery tips - Common execution errors for the main exercises