Generates a fully structured, SEO-friendly article on any topic.
Act as an expert SEO copywriter. Write a comprehensive, 1500-word blog post about [TOPIC]. Include naturally placed keywords: [KEYWORDS]. Structure with an engaging intro, H2 and H3 headings, bullet points for readability, and a strong conclusion with a call to action. Tone should be [TONE]. Include an FAQ section at the end with 3-5 common questions and answers.
Writes conversion-focused product descriptions for any e-commerce item.
Write a compelling e-commerce product description for [PRODUCT NAME]. Key features: [LIST FEATURES]. Target buyer: [BUYER PERSONA]. Price point: [PRICE]. Tone: [TONE — professional/playful/luxurious]. Include: a punchy headline, a 2-3 sentence intro that sells the transformation, 5-7 benefit-focused bullet points, and a short paragraph for SEO with naturally included keywords: [KEYWORDS]. Keep the total under 300 words.
Writes a complete, engaging newsletter issue from topic to CTA in one shot.
Write a [TONE — conversational/professional/witty] email newsletter issue for [NEWSLETTER NAME], sent to [AUDIENCE DESCRIPTION]. This week's main topic: [TOPIC]. Include: (1) a subject line (provide 3 options — curiosity, benefit, and question formats), (2) a personal opening paragraph of 2–3 sentences that references something timely or relatable, (3) the main body with 2–3 sections using subheadings, each with a key insight and a practical takeaway, (4) one curated link recommendation with a 1-sentence reason why it's worth reading, (5) a CTA closing paragraph. Total length: 350–500 words.
Produces structured technical documentation any reader can follow and act on.
Write clear technical documentation for [FEATURE/FUNCTION/API NAME]. Audience: [AUDIENCE — developers/end users/business users]. Format: [README / API reference / user guide / onboarding doc]. Include: (1) a one-paragraph overview of what it does and why it exists, (2) prerequisites and requirements, (3) step-by-step setup or usage instructions (numbered), (4) code examples or screenshots where relevant [describe them in brackets if you can't include them], (5) common errors and how to fix them, (6) a FAQ section with 3–5 common questions. Write in plain, direct language. Avoid jargon unless it's standard in [FIELD].
Generates a complete, structured chapter outline with story beats and transitions.
Create a detailed chapter outline for a book titled [BOOK TITLE] targeting [AUDIENCE]. Genre/category: [GENRE — self-help/business/memoir/fiction]. This is for Chapter [NUMBER]: [CHAPTER TITLE]. The chapter should advance the reader from [STARTING STATE — what they know/believe/feel at the start] to [ENDING STATE — what they should know/believe/feel by the end]. Provide: (1) chapter goal in one sentence, (2) opening hook concept (the first scene or idea that draws the reader in), (3) 5–8 sections with headings and 2–3 bullet sub-points each, (4) a key story, example, or exercise to include per section, (5) closing summary and bridge to the next chapter. Aim for approximately [WORD COUNT] words total.
Produces a publication-ready press release following AP style and journalistic best practices.
Write a professional press release for [COMPANY NAME] announcing [NEWS — product launch/funding/partnership/event/award]. Key facts: (1) What is the announcement? [DETAILS], (2) Why does it matter? [SIGNIFICANCE], (3) Who is affected? [AUDIENCE/MARKET], (4) When does it take effect? [DATE]. Include: a headline (newsworthy, under 10 words), a dateline (City, Date), a lead paragraph that answers who/what/when/where/why in 50 words, two body paragraphs with supporting details and context, one quote from a spokesperson: [NAME, TITLE], a boilerplate 'About [Company]' paragraph, and press contact information placeholders. Follow AP style.
Writes a complete, timed speech with hooks, story beats, and a memorable close.
Write a [LENGTH — 5/10/15/20]-minute speech script for [SPEAKER NAME] speaking at [EVENT TYPE — conference/webinar/company all-hands/commencement]. Topic: [TOPIC]. Audience: [AUDIENCE DESCRIPTION]. Desired emotional outcome: [OUTCOME — inspired/educated/motivated/entertained]. Include: (1) an opening hook (a story, surprising stat, or provocative question — not 'Hello, I'm excited to be here'), (2) a clear thesis stated within the first 90 seconds, (3) 3 main points, each with a supporting story or example and a memorable one-liner, (4) smooth transitions between sections, (5) a powerful closing call-to-action or moment of reflection. Mark [PAUSE] where the speaker should pause. Aim for approximately 130 words per minute.
Instantly scaffold complex React components with styling and types.
Create a modern, accessible React component for [COMPONENT NAME] using Tailwind CSS and TypeScript. Include necessary props with proper typing, sensible default values, and use Lucide React icons where appropriate. Follow best practices for responsive design. Add aria attributes for accessibility. Export the component and its prop types.
Thorough code review across bugs, security, performance, and style.
Review the following [LANGUAGE] code for: (1) bugs and logical errors, (2) security vulnerabilities, (3) performance issues, (4) readability and maintainability, (5) adherence to best practices. For each issue found, explain what the problem is, why it matters, and provide a corrected code snippet. Rate the overall code quality out of 10 and summarize your top 3 recommended improvements.
Code to review:
[PASTE CODE HERE]
Writes and explains SQL queries for any database type.
Generate a SQL query to [DESCRIBE WHAT YOU WANT TO RETRIEVE OR DO]. The database uses [DATABASE TYPE — PostgreSQL/MySQL/SQLite]. Relevant tables and their key columns: [LIST TABLES AND COLUMNS]. Requirements: [ANY SPECIFIC REQUIREMENTS — filtering, ordering, joining, aggregating]. After writing the query, explain each clause in plain English so a non-developer could understand what it does. Then suggest one optimization if applicable.
Scaffolds a complete, validated, well-documented REST API endpoint in any stack.
Design and implement a REST API endpoint for [ENDPOINT PURPOSE — e.g. 'user authentication', 'product search', 'order creation']. Stack: [LANGUAGE/FRAMEWORK — Node.js/Express, Python/FastAPI, etc.]. Include: (1) the route definition with HTTP method and path, (2) request validation (required fields, types, constraints), (3) business logic with inline comments, (4) success response with example JSON (200/201), (5) error responses for: 400 bad request, 401 unauthorized, 404 not found, 500 server error, (6) one middleware function for authentication/logging if relevant. Follow RESTful conventions. Add JSDoc or docstring comments.
Produces a complete, normalized database schema with SQL and relationship explanations.
Design a relational database schema for [APPLICATION TYPE — e.g. e-commerce platform, SaaS app, social network]. Core features: [LIST 3–5 MAIN FEATURES]. Database: [PostgreSQL/MySQL/SQLite]. For each table, provide: (1) table name and purpose, (2) all columns with data type, constraints (PRIMARY KEY, NOT NULL, UNIQUE, DEFAULT), and a brief description, (3) foreign key relationships and the relationship type (one-to-one, one-to-many, many-to-many). After the schema, provide: the CREATE TABLE SQL statements in order of dependency, 2–3 example indexes to add for query performance, and one data integrity challenge to watch out for in this design.
Generates a thorough, well-organized test suite covering happy paths, edge cases, and errors.
Write a comprehensive unit test suite for the following [LANGUAGE] function/class using [TEST FRAMEWORK — Jest/Pytest/JUnit/etc.].
Code:
[PASTE CODE HERE]
Include tests for: (1) the happy path (expected inputs producing expected outputs), (2) edge cases (empty strings, null/undefined, zero, negative numbers, maximum values), (3) error cases (invalid inputs that should throw or return errors), (4) any async behavior if applicable. Use descriptive test names in the format 'should [expected behavior] when [condition]'. Add a brief comment explaining what each test group is validating. Aim for at least 90% branch coverage.
Provides a clear, opinionated system architecture recommendation with tradeoffs and a phased roadmap.
I'm building [SYSTEM DESCRIPTION — e.g. 'a real-time chat application', 'a multi-tenant SaaS platform']. My expected scale: [SCALE — e.g. '10,000 DAU', '100 requests/second']. Current tech stack: [STACK]. Explain the recommended architecture for this system, covering: (1) a high-level architecture diagram described in text (components, how they connect, data flow), (2) the right database choice(s) and why (SQL vs NoSQL, caching layer), (3) key architectural patterns to apply (microservices vs monolith, event-driven, CQRS, etc.) and the tradeoff for each, (4) the 3 biggest scalability risks in this design and how to mitigate them, (5) a phased build plan: what to build in Phase 1 (MVP), Phase 2 (growth), and Phase 3 (scale). Be opinionated and practical.
Diagnoses errors, explains root causes in plain English, and provides corrected code with prevention tips.
Help me debug the following issue in my [LANGUAGE/FRAMEWORK] application.
Error message:
[PASTE ERROR HERE]
Relevant code:
[PASTE CODE HERE]
Context: [DESCRIBE WHAT YOU WERE TRYING TO DO AND WHEN THE ERROR OCCURS]
Please: (1) identify the most likely root cause, (2) explain why this error is occurring in plain English, (3) provide a corrected version of the relevant code with changes highlighted, (4) explain what the fix does, (5) suggest how to prevent this class of error in future (code patterns, linting rules, or tests to add). If you need more context to be certain, list the specific information that would help you confirm the diagnosis.
Writes short, personalized cold emails that get replies.
Write a compelling cold email from [YOUR NAME] at [YOUR COMPANY] to [RECIPIENT NAME], who is a [RECIPIENT ROLE] at [RECIPIENT COMPANY]. The purpose is to [GOAL — e.g. request a meeting, pitch a partnership, introduce a product]. Reference this specific detail about them: [PERSONALIZATION DETAIL]. Keep the email under 150 words. Use a subject line that creates curiosity without being clickbait. End with a single, low-friction CTA.
Generates 15 data-driven, audience-specific YouTube video ideas.
I run a YouTube channel about [NICHE]. My target audience is [AUDIENCE DESCRIPTION]. Generate 15 video ideas that: (1) have strong search potential, (2) are not oversaturated, (3) match my audience's current pain points, and (4) would perform well as both long-form videos and YouTube Shorts. For each idea, include a suggested title, a one-sentence hook for the first 15 seconds, and 3 key points to cover.
Creates complete landing page copy from hero to CTA.
Write high-converting landing page copy for [PRODUCT/SERVICE NAME]. Target audience: [AUDIENCE]. Main benefit: [BENEFIT]. Key differentiator: [WHAT MAKES IT UNIQUE]. Include: a headline and subheadline (test 3 variations), a hero paragraph (2-3 sentences), a features section with 4-6 benefit-focused bullets, social proof placeholder, and a CTA section. Write in a [TONE] voice. Focus on benefits, not features.
A complete month of strategic, mixed-format social content.
Create a 30-day social media content calendar for [BRAND/CREATOR NAME] in the [NICHE] space. Target platform: [PLATFORM — Instagram/LinkedIn/X/TikTok]. Audience: [AUDIENCE]. Content mix: 40% educational, 30% entertaining, 20% promotional, 10% community/engagement. For each of the 30 days, provide: post type, topic, 1-sentence content description, and suggested posting time. Vary the formats (carousel, single image, reel, text post).
Creates a complete, practical brand voice guide with examples and a tone matrix.
Develop a comprehensive brand voice guide for [BRAND NAME], a [INDUSTRY] company. Target audience: [AUDIENCE]. Core value proposition: [VALUE PROP]. Brand personality we're going for (choose 3): [TRAITS — e.g. bold, empathetic, witty, authoritative, playful, premium]. Deliver: (1) a brand voice archetype with a one-paragraph description, (2) 4 core voice characteristics, each with a 'We are X / We are not Y' definition, (3) a tone matrix showing how the voice shifts across contexts (social media vs. support email vs. sales page vs. error messages), (4) 10 'Before and After' copy examples that show the brand voice in practice, (5) 5 words we never use and 5 words we always use, (6) a one-paragraph 'elevator test' summary the whole team can memorize.
Produces a structured, actionable competitive analysis with strategic positioning recommendations.
Conduct a structured competitor analysis for [YOUR COMPANY/PRODUCT] in the [INDUSTRY/NICHE] space. My product: [BRIEF DESCRIPTION]. Key competitors to analyze: [LIST 3–5 COMPETITORS]. For each competitor, provide: (1) positioning statement — how they describe themselves, (2) pricing model and tier structure, (3) key features/differentiators, (4) apparent target audience, (5) estimated strengths (what they do better than us), (6) apparent weaknesses (where they fall short). Then deliver: a competitive positioning map (describe it in text: X-axis = [ATTRIBUTE 1], Y-axis = [ATTRIBUTE 2] — where does each company sit?), our biggest vulnerability to address, and our strongest differentiator to double down on. End with 3 strategic recommendations.
Generates 20 subject lines across 5 psychological categories, with a top-3 recommendation.
Generate 20 email subject lines for [EMAIL PURPOSE — newsletter issue / product launch / re-engagement / cold outreach]. Email content summary: [1–2 SENTENCE SUMMARY]. Audience: [AUDIENCE]. Goal metric: [OPEN RATE / REPLY RATE / CLICK RATE]. Deliver 4 subject lines in each of these 5 categories: (1) Curiosity gap ('You're making this mistake every day'), (2) Direct benefit ('Double your open rates in 7 days'), (3) Question format ('Are you leaving 40% of your revenue on the table?'), (4) Social proof ('How [NAME/BRAND] achieved [RESULT]'), (5) Urgency or scarcity. For each subject line, add a 'Why it works' annotation of one sentence. Flag your top 3 picks and explain why.
Creates 3 research-quality customer personas with day-in-the-life narratives and messaging guidance.
Build 3 detailed customer personas for [PRODUCT/SERVICE NAME] in the [INDUSTRY] space. Base the personas on this customer data or assumptions: [DESCRIBE WHAT YOU KNOW — demographics, behaviors, use cases, pain points]. For each persona, provide: (1) Name, age, job title, and location, (2) a day-in-the-life narrative paragraph (80–100 words), (3) primary goals (what success looks like for them), (4) top 3 pain points related to [YOUR PRODUCT CATEGORY], (5) how they currently solve the problem (status quo), (6) their decision-making triggers (what makes them buy), (7) their objections to buying [YOUR PRODUCT], (8) the message that would resonate most with them, (9) where to reach them (channels, communities, media). End with one sentence per persona summarizing how [YOUR PRODUCT] maps to their core need.
Generates a comprehensive ad creative brief with 3 distinct concepts ready to hand to a creative team.
Write a detailed creative brief for an ad campaign for [PRODUCT/SERVICE]. Campaign objective: [OBJECTIVE — awareness/conversions/retargeting]. Platform(s): [GOOGLE/META/LINKEDIN/TIKTOK]. Budget range: [BUDGET]. Audience: [TARGET AUDIENCE]. Provide: (1) campaign theme/big idea in one sentence, (2) key message hierarchy: primary message (the one thing the ad must communicate), secondary messages (supporting points), and proof points, (3) creative direction: visual style, color palette guidance, talent/imagery recommendations, (4) copy direction: tone, must-include phrases, words to avoid, CTA options, (5) 3 specific ad concept ideas — each with a headline, body copy (under 100 chars for social), and a visual description, (6) key performance indicators and how to define success.
Writes investor-ready business plan sections on demand.
Write a professional [SECTION NAME — e.g. Executive Summary, Market Analysis, Competitive Landscape] for a business plan for [BUSINESS CONCEPT]. The company targets [TARGET MARKET] in the [INDUSTRY] space. Key value proposition: [VALUE PROP]. Format it for a seed-stage investor pitch deck. Be specific and data-driven where possible, noting where real data should be inserted. Keep it under 400 words.
Transforms messy meeting notes into clear decisions and action items.
Convert the following meeting notes or transcript into a structured summary. Output: (1) Meeting overview in 2-3 sentences, (2) Key decisions made, (3) Action items as a table with columns: Task, Owner, Deadline, Priority (High/Medium/Low), (4) Open questions that need follow-up, (5) A suggested subject line and 3-sentence follow-up email draft. Be concise and use clear, direct language.
Meeting notes:
[PASTE NOTES OR TRANSCRIPT]
Writes balanced, specific, and professional performance reviews that motivate rather than deflate.
Write a [TONE — constructive/positive/direct] performance review for [EMPLOYEE NAME], a [JOB TITLE] who has been in this role for [DURATION]. Review period: [PERIOD]. Their key responsibilities: [LIST 3–5 RESPONSIBILITIES]. Accomplishments this period: [LIST ACHIEVEMENTS]. Areas for improvement: [LIST 1–3 AREAS]. Overall rating: [RATING — Exceeds/Meets/Below Expectations]. Include: (1) an opening paragraph summarizing overall performance in 2–3 sentences, (2) accomplishments section with specific, measurable impact for each achievement, (3) areas for growth section — written as development opportunities, not criticism — with 1 concrete suggestion for each, (4) a forward-looking paragraph on goals and development plan for the next period, (5) a closing sentence that reflects the overall tone. Avoid generic filler phrases like 'team player' or 'hard worker' without specifics.
Generates tailored interview questions, model answers, and strategic preparation for any role.
Act as a senior recruiter helping me prepare for an interview for [JOB TITLE] at [COMPANY NAME]. My background: [YOUR EXPERIENCE AND SKILLS IN 3–4 SENTENCES]. The role is focused on: [KEY RESPONSIBILITIES FROM JOB DESCRIPTION]. Generate: (1) 10 likely interview questions for this specific role and company (mix of behavioral, situational, and technical), (2) for each question: a model answer framework (not a script — a structure I can adapt), highlighting which of my experiences to draw from, (3) 5 questions I should ask the interviewer that demonstrate strategic thinking and genuine interest, (4) 3 potential red flags in my background that might come up and how to address them proactively, (5) a one-paragraph 'Tell me about yourself' answer tailored to this specific role. For behavioral questions, structure answers using the STAR method (Situation, Task, Action, Result).
Provides psychologically grounded, natural-sounding responses to your most common sales objections.
I sell [PRODUCT/SERVICE] to [TARGET CUSTOMER]. Price: [PRICE POINT]. My top value propositions: [LIST 3]. The most common objections I hear are: [LIST 3–5 OBJECTIONS — e.g. 'It's too expensive', 'We already use a competitor', 'Now isn't the right time', 'I need to think about it']. For each objection, provide: (1) the underlying concern the prospect is really expressing (the psychological driver), (2) an 'Acknowledge and Reframe' response that validates their concern without being defensive, (3) a clarifying question to ask that opens the conversation further, (4) the strongest piece of evidence or social proof to use in response, (5) a trial close — a low-pressure next step to propose after addressing the objection. Write all responses in natural, conversational language — not salesy or scripted.
Produces a structured risk matrix with mitigation strategies for any business decision.
Conduct a structured risk assessment for [PROJECT/INITIATIVE/BUSINESS DECISION]. Context: [DESCRIBE WHAT YOU'RE PLANNING TO DO AND WHY]. Timeframe: [TIMELINE]. Key stakeholders: [LIST STAKEHOLDERS]. Identify and analyze: (1) Strategic risks — threats to the achievement of objectives, (2) Operational risks — execution, process, and resource risks, (3) Financial risks — cost overruns, revenue shortfalls, market risks, (4) Reputational risks — public, media, or stakeholder perception risks, (5) Legal and compliance risks. For each risk identified, provide: risk description, likelihood (High/Medium/Low), potential impact (High/Medium/Low), a risk score (likelihood × impact), and 2 mitigation strategies. Conclude with a risk priority matrix: list the top 5 risks to address first and one recommended contingency plan for the highest-priority risk.
Creates a complete quarterly OKR framework with key results, leading indicators, and risk flags.
Create a quarterly OKR (Objectives and Key Results) framework for [TEAM/COMPANY NAME] in [QUARTER AND YEAR]. Current focus: [DESCRIBE YOUR MAIN STRATEGIC PRIORITY THIS QUARTER]. Recent context: [ANY KEY EVENTS — e.g. new product launch, restructuring, market shift]. For each of 3 Objectives: (1) write the Objective as an inspiring, qualitative statement of direction (not a metric), (2) write 3–4 Key Results per Objective — each must be: specific, measurable with a number or percentage, achievable in one quarter, and results-focused (not task-focused), (3) identify one leading indicator metric to track weekly as an early signal that you're on track, (4) flag one key risk that could prevent hitting this OKR. Also provide: a team-level OKR alignment table showing how each team's OKRs connect to the company OKRs, and 3 anti-patterns to avoid when running OKR review meetings.
Turns dense research papers into clear, actionable summaries.
Summarize the following research paper or article for a non-expert audience. Include: (1) the core research question or thesis, (2) key methodology in plain language, (3) top 3-5 findings, (4) practical implications for [TARGET AUDIENCE], (5) limitations or caveats, (6) your verdict on how credible and important this research is. Avoid jargon. Use bullet points for findings.
[PASTE PAPER OR ABSTRACT HERE]
Synthesizes multiple sources into a thematic, publication-ready literature review with gap analysis.
Synthesize a literature review on [RESEARCH TOPIC] based on the following sources (paste abstracts or key points from each): [PASTE SOURCES HERE — at least 3]. My research question: [YOUR QUESTION]. My audience: [ACADEMIC JOURNAL / THESIS / POLICY BRIEF / BUSINESS REPORT]. Deliver: (1) a thematic synthesis — group the findings across sources by theme, not by source, (2) areas of consensus (what the literature agrees on), (3) areas of debate or contradiction (where sources disagree and why), (4) gaps in the existing literature — what has not been studied yet, (5) how the existing literature informs my research question, (6) a suggested organizational structure for presenting this review in my paper. Cite each source using [CITATION STYLE — APA/MLA/Chicago] with placeholder numbers I can replace.
Generates a bias-aware, mixed-method survey with question-type rationale and bias flags.
Design a survey for [RESEARCH PURPOSE — customer satisfaction / product feedback / employee engagement / market research / academic study]. Target respondents: [AUDIENCE]. Key insights needed: [LIST 3–5 THINGS YOU WANT TO LEARN]. Survey length: [SHORT (5–8 Qs) / MEDIUM (10–15 Qs) / LONG (20+ Qs)]. Include: (1) a brief, non-leading survey introduction (2 sentences), (2) questions organized by section with headings, (3) a mix of question types — Likert scale (1–5 or 1–7), multiple choice, ranking, and at least 2 open-ended questions, (4) a Net Promoter Score question if applicable, (5) demographic questions at the end (not the start). For each question: flag whether it measures attitude, behavior, or knowledge. Highlight any questions that may introduce bias and suggest how to rephrase them.
Evaluates claim credibility with source analysis, red flag detection, and a verification verdict.
Evaluate the credibility of the following claim and its source.
Claim: [STATE THE CLAIM CLEARLY]
Source: [NAME THE SOURCE — article title, publication, author, date, URL if available]
Context: [WHERE YOU ENCOUNTERED THIS CLAIM]
Analyze: (1) Is this claim verifiable? What type of evidence would confirm or disprove it? (2) Source credibility — evaluate: author expertise, publication reputation, potential conflicts of interest, date (is the data current?), and methodology if it's a study, (3) Red flags — list any signs of bias, cherry-picking, misleading framing, or missing context, (4) Corroboration — what other credible sources would need to confirm this claim? List 2–3 specific sources or source types to check, (5) Verdict: Likely Accurate / Needs Verification / Likely Misleading / False — with your reasoning. Always recommend primary sources over secondary reporting.
Produces a structured STEEP trend analysis with three scenarios and strategic decision guidance.
Conduct a trend analysis for [INDUSTRY/TOPIC] over the [TIMEFRAME — next 1 / 3 / 5 years]. Context: [YOUR ROLE OR ORGANIZATION AND WHY THIS MATTERS TO YOU]. Analyze using the STEEP framework — Social, Technological, Economic, Environmental, and Political trends: (1) For each STEEP category, identify 2–3 key trends and describe their direction, speed, and certainty level (High/Medium/Low), (2) Identify the 3 'megatrends' — the most powerful forces that will shape everything else, (3) Build 3 future scenarios: Optimistic (things go well), Pessimistic (key risks materialize), and Wild Card (a low-probability, high-impact event that changes everything), (4) Strategic implications: what decisions should [YOUR ORGANIZATION] make now, hedge against, or monitor? (5) 5 early warning indicators to track that signal which scenario is unfolding. Ground the analysis in real evidence and name specific signals you're already seeing.
Creates a structured expert interview guide with warm-up, core, challenge, and closing questions.
Generate a set of expert interview questions for a research interview with [EXPERT'S ROLE/TITLE] in the [FIELD] industry. My research topic: [TOPIC]. My research goal: [WHAT YOU'RE TRYING TO UNDERSTAND OR PROVE]. The interview will last [DURATION — 30/45/60 minutes]. Provide: (1) 5 warm-up questions to build rapport and establish context (easy, biographical, or experience-based), (2) 10 core research questions that probe the expert's knowledge, experiences, and opinions on your topic — organized by sub-theme, (3) 5 challenge questions that push back gently or explore tension ('Some argue the opposite — what's your view?'), (4) 3 forward-looking questions ('What do you think happens next?'), (5) a closing question that invites reflection and any insights you haven't covered. Mark which questions are [ESSENTIAL] vs. [IF TIME ALLOWS]. Include a note on how to handle answers that go off-topic.
A publication-ready B2B case study that turns customer wins into persuasive sales assets.
Write a compelling customer case study for [COMPANY_NAME] about how they used [PRODUCT_OR_SERVICE] to solve [CORE_PROBLEM]. Structure the case study with four clearly labeled sections: Challenge, Solution, Implementation, and Results. Open with a one-sentence hook that leads with the most impressive outcome. Use a confident, third-person narrative voice and include direct quotes from [CUSTOMER_CONTACT_NAME], [CUSTOMER_JOB_TITLE] at [CUSTOMER_COMPANY]. Quantify results wherever possible using the following metrics: [METRIC_1], [METRIC_2], [METRIC_3]. Close with a forward-looking statement about what [CUSTOMER_COMPANY] plans to do next. The finished case study should be approximately [TARGET_WORD_COUNT] words and suitable for a B2B sales enablement page.
case studyB2Bcustomer successstorytellingsales enablement
A structured, authoritative whitepaper introduction that earns reader trust and sets up the full argument.
Write the introduction section for a whitepaper titled "[WHITEPAPER_TITLE]" aimed at [TARGET_AUDIENCE] in the [INDUSTRY] industry. The introduction should be approximately 400–600 words and accomplish four things: (1) open with a striking industry statistic or provocative question to establish urgency, (2) clearly state the problem or knowledge gap the whitepaper addresses, (3) preview the key arguments or findings covered in the full document, and (4) end with a clear transition sentence that leads the reader into the body. Use an authoritative, research-backed tone — no hype, no fluff. The whitepaper argues that [CORE_THESIS]. Primary source references should be noted as [SOURCE_PLACEHOLDER] so the author can insert citations later.
A numbered, hook-driven tweet thread engineered for shares and profile follows.
Write a high-engagement Twitter/X thread on the topic: [TOPIC]. The thread should be exactly [NUMBER_OF_TWEETS] tweets long. Tweet 1 must be a standalone hook — a bold claim, contrarian take, or surprising fact — that makes someone stop scrolling and click "read more." Each subsequent tweet should deliver one clear, specific insight and end with a micro-cliffhanger or transition to the next. The final tweet should include a call to action: [CTA — e.g., follow for more, link to article, reply with X]. Write in a [TONE — e.g., educational, punchy, conversational] voice for an audience of [TARGET_AUDIENCE]. Keep every tweet under 280 characters. Number each tweet (1/, 2/, etc.) and do not use generic filler phrases like "let's dive in" or "a thread."
SEO-ready podcast show notes with chapters, takeaways, and resource links ready to publish.
Write complete show notes for a podcast episode titled "[EPISODE_TITLE]" (Episode [EPISODE_NUMBER]) of the "[PODCAST_NAME]" podcast. The guest is [GUEST_NAME], [GUEST_TITLE] at [GUEST_COMPANY]. The episode covers: [BRIEF_EPISODE_SUMMARY]. Structure the show notes as follows: (1) a 2–3 sentence episode summary optimized for search and written in second person ("You'll learn…"), (2) 5–7 bullet-point key takeaways, (3) a timestamped chapter list using the following times and topics: [TIMESTAMPS_AND_TOPICS], (4) links and resources mentioned: [RESOURCES_LIST], (5) a one-sentence guest bio with a link to [GUEST_WEBSITE_OR_LINKEDIN]. Write in a warm, direct tone that matches the show's voice: [SHOW_VOICE — e.g., analytical and data-driven]. Keep the summary under 160 characters for SEO meta use.
A polished, user-friendly changelog entry that communicates product value without technical noise.
Write a customer-facing product changelog entry for version [VERSION_NUMBER] of [PRODUCT_NAME], released on [RELEASE_DATE]. Use the following raw engineering notes as your source material: [RAW_ENGINEERING_NOTES]. Translate technical jargon into plain language benefits — focus on what the user can now do, not how it was built. Organize the entry into three labeled sections: New Features, Improvements, and Bug Fixes. Lead each bullet with a strong action verb (e.g., "Added," "Improved," "Fixed"). For any breaking changes, add a clearly marked WARNING block. Write for a [TARGET_USER — e.g., non-technical end user / developer] audience. Keep the total entry under 300 words and maintain a [TONE — e.g., friendly, professional] tone consistent with the product's brand voice.
changelogrelease notesproduct writingSaaSuser communication
Cleaner, more maintainable code with a documented change log explaining every refactoring decision.
Refactor the following [LANGUAGE] code to improve readability, maintainability, and performance without changing its external behavior. Code to refactor: [CODE_BLOCK]. Apply these specific improvements: (1) eliminate duplicate logic using appropriate abstractions, (2) replace magic numbers and strings with named constants, (3) break functions longer than [MAX_FUNCTION_LINES] lines into smaller, single-responsibility functions, (4) rename variables and functions to clearly express intent, (5) add inline comments only where the "why" is non-obvious. Output the refactored code first, then provide a bulleted summary of every change made and the reason for each change. If you identify any bugs or edge cases in the original code, flag them separately under a "Potential Issues" heading but do not fix them unless instructed.
Complete, structured API reference documentation generated directly from source code with examples and error docs.
Generate complete API reference documentation for the following [LANGUAGE] code: [CODE_BLOCK]. For each public function, method, or endpoint, produce a documentation block containing: (1) a one-sentence description of what it does, (2) Parameters table with columns: Name, Type, Required, Default, Description, (3) Return value — type and description, (4) a practical usage example with realistic sample data, (5) possible errors or exceptions thrown and when they occur. Format the output in [FORMAT — e.g., Markdown, JSDoc, OpenAPI YAML]. Follow the [DOCUMENTATION_STANDARD — e.g., Google Style Guide, Microsoft Docs style] conventions. If any function behavior is ambiguous from the code alone, note it with a [CLARIFICATION NEEDED] flag rather than guessing.
A production-ready relational database schema with SQL CREATE statements, indexes, and a clear ER summary.
Design a relational database schema for [PROJECT_DESCRIPTION]. The system must support the following core use cases: [USE_CASE_LIST]. Use [DATABASE_TYPE — e.g., PostgreSQL, MySQL] conventions. For each table, specify: table name, all columns with data types and constraints (PRIMARY KEY, NOT NULL, UNIQUE, FOREIGN KEY), and a brief comment explaining the table's purpose. Define all foreign key relationships and indicate whether each is one-to-one, one-to-many, or many-to-many. Include appropriate indexes for columns that will be frequently filtered or joined. Identify any junction tables needed for many-to-many relationships. Output the schema as valid SQL CREATE TABLE statements followed by a plain-English Entity-Relationship summary. Flag any design decisions that involve trade-offs and explain your rationale.
A ready-to-commit CI/CD pipeline config with lint, test, build, and deploy stages tailored to your stack.
Generate a CI/CD pipeline configuration for a [PROJECT_TYPE — e.g., Node.js API, Python Django app, React frontend] project hosted on [REPOSITORY_PLATFORM — e.g., GitHub, GitLab, Bitbucket] using [CI_PLATFORM — e.g., GitHub Actions, GitLab CI, CircleCI]. The pipeline must include these stages: (1) Install dependencies, (2) Run linting with [LINTER], (3) Run unit tests with [TEST_FRAMEWORK] and enforce a minimum [COVERAGE_THRESHOLD]% code coverage, (4) Build the production artifact, (5) Deploy to [DEPLOYMENT_TARGET] when pushing to the [DEPLOY_BRANCH] branch. Add environment variable placeholders for secrets (do not hardcode values). Include caching for dependencies to minimize build time. Output the complete configuration file with inline comments explaining each stage. Note any additional secrets or environment variables the team must configure in the CI platform UI.
A one-page, research-backed B2B customer persona that aligns sales and marketing on exactly who they're targeting.
Build a detailed B2B customer persona for [COMPANY_NAME]'s [PRODUCT_OR_SERVICE]. Use the following research inputs: customer interview themes: [INTERVIEW_THEMES], top customer job titles: [JOB_TITLES], and common objections heard during sales: [OBJECTIONS_LIST]. Structure the persona with these sections: (1) Persona name and role snapshot (title, company size, industry), (2) Day-in-the-life narrative (3–4 sentences describing a typical workday), (3) Primary goals and KPIs they are measured on, (4) Top 3 pain points with specific language they use to describe each, (5) Triggers that cause them to seek a solution like [PRODUCT_OR_SERVICE], (6) Buying process — who else is involved, typical evaluation timeline, decision criteria, (7) Preferred content formats and channels. Write in second person ("Your persona is…") and keep the total under 600 words so it fits on one page.
Complete pricing page copy with tier names, feature bullets, FAQs, and a headline that converts browsers into buyers.
Write the full copy for a SaaS pricing page for [PRODUCT_NAME]. The product has [NUMBER_OF_TIERS] pricing tiers: [TIER_NAMES_AND_PRICES]. For each tier, write: (1) a memorable tier name tagline (not just "Starter/Pro/Enterprise"), (2) a one-sentence value statement describing who this tier is for, (3) a bulleted feature list of [FEATURES_PER_TIER] — lead with the most compelling differentiator, (4) a CTA button label. Also write: the page headline (outcome-focused, not feature-focused), a two-sentence subheadline, an FAQ section with answers to these questions: [FAQ_QUESTIONS], and a trust bar line featuring [SOCIAL_PROOF — e.g., "Trusted by 4,000+ teams"]. Use [TONE — e.g., confident and direct / friendly and approachable] copy. Avoid the words "affordable," "cheap," and "simple."
A personalized, low-friction testimonial request email that gets responses by making the ask feel effortless.
Write a short, warm email from [SENDER_NAME] at [COMPANY_NAME] to [CUSTOMER_NAME] at [CUSTOMER_COMPANY] requesting a testimonial or review for [PRODUCT_OR_SERVICE]. The customer achieved [SPECIFIC_RESULT] using [PRODUCT_OR_SERVICE] approximately [TIME_SINCE_RESULT] ago. The email should: open by referencing their specific result (not a generic "hope you're well"), make the ask clear and low-friction (suggest they answer 2–3 guiding questions rather than write from scratch), include those 2–3 guiding questions focused on: the problem before, the result achieved, and who they'd recommend this to, offer a specific format option ([FORMAT — e.g., a 2–3 sentence written quote / a 60-second video]), and give a clear deadline of [DEADLINE]. Keep the email under 200 words, use a conversational tone, and avoid making the customer feel like they're doing a favor for marketing — frame it as sharing their story.
An inclusive, outcome-focused job description that attracts qualified candidates and accurately represents the role.
Write a compelling job description for a [JOB_TITLE] role at [COMPANY_NAME], a [COMPANY_DESCRIPTION — e.g., Series B fintech startup / enterprise healthcare SaaS]. The role reports to [REPORTING_MANAGER_TITLE] and is [WORK_ARRANGEMENT — e.g., fully remote / hybrid in New York]. Structure the job description with these sections: (1) Role in one sentence — what this person will own, not a generic summary, (2) What you'll do — 5–7 bullet points of specific, outcome-focused responsibilities (avoid "assist with" and "support"), (3) What you'll bring — separate "Must Have" (3–5 items) from "Nice to Have" (2–3 items) qualifications, (4) What we offer — compensation range [SALARY_RANGE], benefits highlights [BENEFITS], and 2–3 culture differentiators that are actually true, not clichés. Use inclusive language, avoid jargon, and keep the total under 500 words. The tone should reflect the company's voice: [COMPANY_VOICE].
A balanced, evidence-based performance review that gives employees clear feedback and actionable growth goals.
Write a structured performance review for [EMPLOYEE_NAME], [EMPLOYEE_TITLE], covering the review period [START_DATE] to [END_DATE]. Use the following inputs: their stated goals for the period: [GOALS_LIST], notable accomplishments: [ACCOMPLISHMENTS], areas where they fell short: [GAPS], and peer feedback themes: [PEER_FEEDBACK]. Structure the review as: (1) Overall performance summary (3–4 sentences, lead with strengths), (2) Goal-by-goal assessment — for each goal state whether it was Met, Exceeded, or Missed and provide one specific example, (3) Strengths — 2–3 specific, evidence-backed strengths (no vague praise), (4) Development areas — 2 areas for growth framed constructively with a suggested action for each, (5) Goals for next review period — 3 SMART goals. Use direct, professional language. Avoid filler phrases like "rockstar" or "goes above and beyond." Keep the total under 600 words.
A professional partnership proposal that clearly articulates mutual value and moves both parties toward a decision.
Write a partnership proposal from [YOUR_COMPANY_NAME] to [PARTNER_COMPANY_NAME] proposing a [PARTNERSHIP_TYPE — e.g., co-marketing, technology integration, reseller, joint venture] partnership. Your company: [YOUR_COMPANY_DESCRIPTION]. Their company: [PARTNER_COMPANY_DESCRIPTION]. The proposal should cover: (1) Executive summary — the partnership in two sentences and the mutual benefit, (2) Why this partnership makes sense now — market context and timing, (3) What each party brings to the table — your assets and their assets, (4) Proposed partnership structure — specific activities, responsibilities, and resource commitments from each side, (5) Success metrics — 3 KPIs that will be used to evaluate the partnership at [REVIEW_TIMEFRAME], (6) Proposed next steps with a decision deadline. Write in a confident, peer-to-peer tone — this is a proposal between equals, not a pitch. Total length: 500–700 words. Avoid buzzwords like "synergy" and "win-win."
A structured QBR document that gives executives a clear, honest view of the quarter and a confident path forward.
Create a Quarterly Business Review (QBR) document for [COMPANY_OR_TEAM_NAME] covering [QUARTER] [YEAR]. Use the following data inputs: revenue or key metrics: [METRICS_DATA], top initiatives completed: [INITIATIVES], missed targets: [MISSED_TARGETS], and strategic priorities for next quarter: [NEXT_QUARTER_PRIORITIES]. Structure the QBR with these sections: (1) Executive snapshot — a 4-bullet dashboard of the quarter's most critical numbers, (2) Wins — 3–4 accomplishments with specific results and business impact, (3) Misses — 2–3 targets not hit, root cause for each, and corrective actions already taken or planned, (4) Key learnings — 2 insights the business is taking forward, (5) Q[NEXT_QUARTER] priorities — 3–5 strategic priorities each with an owner and success metric, (6) Asks — any resources, decisions, or support needed from leadership. Write for an executive audience: direct, data-first, no fluff. Total: 500–800 words.
A prioritized risk register with mitigation strategies and an executive summary ready for stakeholder review.
Write a risk assessment document for [PROJECT_OR_INITIATIVE_NAME] at [COMPANY_NAME]. The initiative involves: [INITIATIVE_DESCRIPTION]. Identify and document risks across these categories: operational, financial, legal/compliance, reputational, and technical. For each risk: (1) give it a descriptive name, (2) write a 1–2 sentence description of the risk scenario, (3) assign a Likelihood score (Low/Medium/High), (4) assign an Impact score (Low/Medium/High), (5) calculate an overall Risk Level (using a standard likelihood × impact matrix), (6) describe the mitigation strategy, (7) name a Risk Owner. Present the risks in a table format sorted by Risk Level (highest first). After the table, write a 3–4 sentence executive summary that communicates the overall risk posture and the top two risks requiring immediate attention. Use this additional context to identify risks: [ADDITIONAL_CONTEXT].
A specific, evidence-based SWOT analysis with a strategic synthesis that turns findings into actionable priorities.
Conduct a comprehensive SWOT analysis for [COMPANY_OR_PRODUCT_NAME] in the [INDUSTRY] industry. Use the following context: company description: [COMPANY_DESCRIPTION], target market: [TARGET_MARKET], key competitors: [COMPETITORS], and recent developments: [RECENT_DEVELOPMENTS]. For each of the four quadrants, provide exactly [ITEMS_PER_QUADRANT — e.g., 4–5] specific, evidence-based points — avoid generic statements that could apply to any company. Strengths and Weaknesses should be internal factors; Opportunities and Threats should be external. After the four quadrants, write a 150-word "So What" synthesis section that identifies the two highest-priority strategic implications: the most critical strength to leverage against the most relevant opportunity, and the most urgent weakness that must be addressed to neutralize the top threat. Format the output with the four quadrants as labeled sections followed by the synthesis.
A structured synthesis report that transforms raw interview notes into clear themes, quotes, and actionable next steps.
Synthesize the following user interview transcripts or notes into a structured research report. Raw interview data: [INTERVIEW_DATA — paste notes or transcripts]. Number of interviews conducted: [NUMBER_OF_INTERVIEWS]. Research objective: [RESEARCH_OBJECTIVE]. Structure the synthesis as: (1) Methodology snapshot — participants, interview format, and dates, (2) Top themes — identify [NUMBER_OF_THEMES — e.g., 4–6] recurring themes, give each a clear name, and support each with 2–3 direct quotes from participants (anonymized as P1, P2, etc.), (3) Key tensions or contradictions — points where participants disagreed or expressed conflicting needs, (4) Unmet needs — specific needs that no current solution addresses well, (5) Surprising findings — 2–3 things that contradicted assumptions, (6) Recommended next steps — 3 specific research or design actions. Use neutral, objective language. Do not interpret beyond what the data supports.
user researchUX researchqualitative researchinterviewssynthesis
A structured patent search brief that gives your IP attorney a clear starting point and saves hours of preliminary research.
Prepare a patent search brief for the invention described as: [INVENTION_DESCRIPTION]. The invention operates in the field of: [TECHNICAL_FIELD]. The key inventive concept to protect is: [CORE_INVENTIVE_CONCEPT]. The brief should include: (1) Invention summary in 3–4 plain-language sentences, (2) Proposed search strategy — list 8–12 specific keywords and keyword combinations to use in patent databases (USPTO, Espacenet, Google Patents), (3) Recommended International Patent Classification (IPC) codes relevant to this invention (list at least 3 with explanations), (4) Key prior art to investigate — names or descriptions of [KNOWN_PRIOR_ART] that should be compared against the invention, (5) Questions for the patent attorney — 4–5 open questions about claim scope, prior art concerns, or patentability hurdles that the attorney should address. Note: this brief is for research purposes and does not constitute legal advice.
A scenario-based trend analysis report that moves executives from awareness to concrete action in one document.
Write a trend analysis report on [TREND_TOPIC] for the [INDUSTRY] industry, targeting [AUDIENCE — e.g., C-suite executives, product managers]. Cover the period [TIME_PERIOD — e.g., 2023–2026]. Structure the report as: (1) Trend overview — define the trend and explain why it matters now (2–3 sentences), (2) Driving forces — 3–4 macro forces (technological, regulatory, behavioral, economic) accelerating this trend with supporting data points from: [DATA_SOURCES], (3) Current adoption landscape — which segments are early adopters, which are laggards, and why, (4) Impact scenarios — describe three scenarios: Base Case, Accelerated Adoption, and Disruption Case — with a 2–3 sentence description of each and its probability, (5) Implications for [COMPANY_TYPE — e.g., mid-market SaaS vendors], (6) Recommended actions — 3 specific actions a leader in this space should take in the next [TIMEFRAME — e.g., 6 months]. Use confident, analytical language. Cite [DATA_SOURCES] throughout.
A systematic citation search brief with Boolean queries, journal lists, and inclusion criteria that make literature reviews faster and more thorough.
Create a structured research brief to guide a systematic search for academic citations on the topic: [RESEARCH_TOPIC]. The citation search is for: [PURPOSE — e.g., a literature review / a white paper / a grant application]. Required citation types: [CITATION_TYPES — e.g., peer-reviewed journals, meta-analyses, systematic reviews]. Date range: [DATE_RANGE — e.g., 2015–present]. Include: (1) 10–15 specific search queries optimized for Google Scholar, PubMed, or JSTOR using Boolean operators (AND, OR, NOT) and field tags, (2) A list of the top 5–8 most relevant academic journals in this field to search directly, (3) Key authors or research groups known to publish in this area: [KNOWN_AUTHORS], (4) Inclusion criteria — 4 specific criteria a study must meet to be included, (5) Exclusion criteria — 3 criteria that disqualify a study, (6) A suggested citation management workflow using [CITATION_TOOL — e.g., Zotero, Mendeley, EndNote]. Format all Boolean search strings in code blocks for easy copy-paste.
A crisp, decision-ready executive summary that gives busy leaders everything they need to act without reading the full report.
Write an executive summary of the following [DOCUMENT_TYPE — e.g., research report, business plan, technical proposal]: [FULL_DOCUMENT_OR_KEY_POINTS]. The executive summary is for [AUDIENCE — e.g., the board of directors, a potential investor, a government agency] and will be read in approximately 2 minutes. Structure the executive summary as follows: (1) Opening statement — one sentence that captures the core finding or recommendation, (2) Context — 2 sentences on why this matters now, (3) Key findings or proposed solution — 3–4 bullet points, each starting with a bold label and containing the most critical information from the full document, (4) Recommendation or call to action — what you are asking the reader to decide, approve, or do, (5) Next steps — 2–3 specific actions with owners and deadlines: [NEXT_STEPS]. Target length: [TARGET_LENGTH — e.g., 250–300 words]. Use active voice, avoid jargon, and assume the reader has not read the full document.
A complete brand identity brief that gives designers and agencies a clear creative direction without micromanaging the execution.
Create a comprehensive brand identity brief for [BRAND_NAME], a [COMPANY_DESCRIPTION]. The brief will guide a designer or agency building the brand's visual identity from scratch. Include the following sections: (1) Brand positioning — core value proposition in one sentence and the brand's position relative to competitors: [COMPETITORS], (2) Brand personality — 4–5 personality traits written as "We are [X] but not [Y]" to define the character with nuance, (3) Target audience — primary persona summary: [PERSONA_DESCRIPTION], (4) Visual direction — describe the desired aesthetic using 3 reference brand examples and explain what to borrow from each (not copy), (5) Logo direction — describe the mark type (wordmark, lettermark, icon + wordmark), mood, and any must-avoid directions, (6) Color direction — 2–3 adjectives that describe the color mood and any colors that must be avoided, (7) Typography direction — heading personality and body copy readability needs, (8) Deliverables required — list all assets needed: [DELIVERABLES_LIST]. Keep the total brief under 800 words.
A prioritized UI/UX audit report with severity ratings and specific recommendations your team can act on immediately.
Conduct a structured UI/UX audit of [PRODUCT_NAME], focusing on [AUDIT_SCOPE — e.g., the onboarding flow / the checkout funnel / the mobile app]. Evaluate the product against these dimensions and provide specific, actionable findings for each: (1) Usability — can users accomplish [KEY_TASK] without confusion? Identify friction points, (2) Visual hierarchy — does the layout guide the eye to the right actions in the right order? (3) Consistency — are UI patterns, terminology, and interactions consistent throughout the flow? List any inconsistencies found, (4) Accessibility — flag any issues against WCAG 2.1 AA standards (color contrast, touch target size, screen reader labels), (5) Mobile responsiveness — list any breakpoints or elements that fail on [DEVICE_TYPES], (6) Copy and microcopy — are error messages, labels, and CTAs clear and action-oriented? For each finding, assign a severity (Critical / High / Medium / Low) and provide a specific recommendation. Conclude with a prioritized remediation list of the top 5 issues to fix first.
A complete, WCAG-checked color palette with hex codes, usage rules, and semantic colors ready for your design system.
Generate a complete design-system-ready color palette for [BRAND_NAME] based on the following inputs: brand personality: [BRAND_PERSONALITY — e.g., bold and innovative / calm and trustworthy], industry: [INDUSTRY], primary brand color (if any): [PRIMARY_COLOR_OR_NONE], and competitors' color territories to avoid: [COMPETITOR_COLORS]. Produce the following: (1) Primary palette — 1 primary brand color with hex code and rationale, (2) Secondary palette — 2–3 complementary colors with hex codes that work harmoniously with the primary, (3) Neutral palette — 5 neutral tones (near-white to near-black) optimized for UI backgrounds, surfaces, and text, (4) Semantic colors — hex codes for Success (green), Warning (amber), Error (red), and Info (blue), all harmonized with the brand palette, (5) For every color, provide: hex code, RGB values, usage guidance (where to use it), and WCAG contrast ratio against white (#FFFFFF) and dark (#1A1A1A) backgrounds. Flag any colors that fail AA contrast for text use.
color palettedesign systembrandingUI designaccessibility
Complete design system component documentation with anatomy, variants, usage rules, and code snippets for designers and engineers.
Write the documentation for the [COMPONENT_NAME] component in the [DESIGN_SYSTEM_NAME] design system. The component is used for: [COMPONENT_PURPOSE]. Structure the documentation page as: (1) Overview — 2–3 sentences describing what the component is and when to use it, (2) Anatomy — list and describe each sub-element of the component (e.g., label, icon, container) in a bulleted list, (3) Variants — document each variant: [VARIANTS_LIST] with a description of when each is appropriate, (4) States — document each interactive state: [STATES — e.g., default, hover, active, disabled, loading, error] with a one-sentence description, (5) Usage guidelines — 3–4 "Do" and 3–4 "Don't" rules with specific examples, (6) Accessibility notes — keyboard behavior, ARIA roles/attributes required, and screen reader behavior, (7) Code snippet — a sample implementation in [FRAMEWORK — e.g., React, Vue] with props table showing: Prop Name, Type, Default, Required, Description. Write for an audience of product designers and frontend engineers.
A thorough wireframe spec that gives designers everything they need to start building without a single back-and-forth question.
Write a detailed wireframe specification for the [SCREEN_OR_FEATURE_NAME] screen of [PRODUCT_NAME]. This spec will be handed to a designer to create low-fidelity wireframes. Include: (1) Screen purpose — one sentence on what the user accomplishes on this screen, (2) Entry points — how does a user arrive at this screen? List all navigation paths, (3) Layout grid — specify columns, gutters, and breakpoints for [BREAKPOINTS — e.g., mobile 375px, tablet 768px, desktop 1440px], (4) Content hierarchy — list every content element on the screen in priority order (1 = most important), describe its type (heading, body text, image, CTA, form field, etc.) and rough position, (5) Interactive elements — for each button, link, or form element, specify: label, action on click/tap, and destination or outcome, (6) Edge cases and empty states — describe what the screen shows when: data is loading, there is no data, and an error occurs, (7) Annotations — flag any elements requiring specific UX rationale. User goal for this screen: [USER_GOAL].
A complete icon design brief that ensures every icon in the set looks like it came from the same hand.
Write a design brief for a custom icon set for [PRODUCT_OR_BRAND_NAME]. The icon set will be used in: [USE_CONTEXTS — e.g., web app navigation, mobile UI, marketing materials]. The brief must cover: (1) Icon style definition — line weight (specify in px at 24x24px), corner radius, fill vs. outline approach, and visual metaphor approach (literal vs. abstract), (2) Grid and sizing — master grid size, safe zone/padding, and export sizes required: [EXPORT_SIZES], (3) Brand alignment — describe how the icon style should reflect the brand personality: [BRAND_PERSONALITY], and reference 2–3 icon sets whose style is close to the target aesthetic (and what to borrow from each), (4) Icons required — list all [NUMBER_OF_ICONS] icons needed organized by category: [ICON_LIST_BY_CATEGORY], (5) Consistency rules — 4 non-negotiable rules the designer must follow for every icon (e.g., stroke caps, minimum line weight, pixel-snapping), (6) Deliverables — file formats (SVG, PNG, icon font), naming convention, and Figma/Illustrator organization structure.
A complete typography pairing system with scale, usage rules, and licensing notes for consistent brand typography.
Recommend and document a typography pairing system for [BRAND_NAME], a [BRAND_DESCRIPTION]. The system will be used across [USE_CONTEXTS — e.g., web, mobile, print collateral]. Based on the brand personality ([BRAND_PERSONALITY]) and the target audience ([TARGET_AUDIENCE]), recommend: (1) Display/Headline typeface — name the font, classify it (serif, sans-serif, slab, etc.), explain why it fits the brand, and specify weights to use, (2) Body typeface — name the font, explain its readability rationale at small sizes, and specify weights to use, (3) Pairing rationale — explain in 3–4 sentences why these two typefaces work together (contrast, tension, hierarchy), (4) Type scale — define a modular scale with specific px/rem values and line heights for: H1, H2, H3, Body Large, Body Default, Caption, Label, (5) Usage rules — 4 specific rules (e.g., "Never use Display typeface below 24px," "Body copy is always left-aligned"), (6) Fallback stack — provide web-safe fallback stacks for both typefaces, (7) Licensing note — confirm whether each font is Google Fonts (free), Adobe Fonts, or requires purchase.
A structured, goal-focused design critique that gives designers specific, actionable feedback tied to user outcomes.
Facilitate a structured design critique for the following design: [DESIGN_DESCRIPTION_OR_SHARE_LINK]. The design is for [PRODUCT_OR_FEATURE_NAME] and is intended to help [USER_TYPE] accomplish [USER_GOAL]. The design is currently at [DESIGN_STAGE — e.g., concept / wireframe / high-fidelity]. Provide critique in the following structured format: (1) First impression — describe what the eye goes to first and whether that matches the intended hierarchy, (2) Goal alignment — evaluate whether the design successfully helps the user accomplish [USER_GOAL]; cite specific elements that help or hinder, (3) What's working — 3–4 specific design decisions that are effective and why, (4) Opportunities — 3–4 specific, actionable improvements framed as questions or suggestions (not orders), each with a rationale, (5) Open questions — 2–3 questions the designer should answer before the next iteration, (6) Priority recommendation — one most important change to make before the next review. Keep feedback specific and tied to user goals, not personal taste.
design critiquedesign reviewfeedbackUXdesign process
A WCAG 2.1 AA accessibility audit with severity ratings, WCAG criterion references, and a prioritized remediation roadmap.
Perform a structured accessibility audit of [PRODUCT_NAME] against WCAG 2.1 Level AA standards. Audit scope: [AUDIT_SCOPE — e.g., homepage, checkout flow, account settings]. For each of the following categories, identify specific issues, their WCAG criterion reference (e.g., 1.4.3 Contrast), severity (Critical / Serious / Moderate / Minor), affected element, and a specific remediation recommendation: (1) Perceivable — color contrast, text alternatives for images, captions for media, (2) Operable — keyboard navigability, focus indicators, skip navigation, touch target sizes (minimum 44x44px), (3) Understandable — form labels, error identification, consistent navigation, (4) Robust — valid HTML semantics, ARIA roles and attributes, screen reader compatibility. After the findings, provide: (a) a prioritized remediation roadmap grouped by severity, (b) a quick wins list — 3–5 issues fixable in under 1 hour each, (c) tools used for testing: [TESTING_TOOLS — e.g., axe, NVDA, Lighthouse, manual keyboard test].
A complete motion design spec with timing tokens, easing curves, and reduced-motion fallbacks that keeps animations consistent and accessible.
Write a motion design specification for [PRODUCT_NAME] that will guide developers and motion designers implementing animations. The spec covers: [ANIMATION_SCOPE — e.g., micro-interactions across the web app / the onboarding screen transitions]. Include the following sections: (1) Motion principles — 3 brand-aligned principles that govern all animation decisions (e.g., "Motion is purposeful: every animation communicates a state change"), (2) Timing tokens — define the standard duration values (e.g., Instant: 100ms, Fast: 200ms, Medium: 350ms, Slow: 500ms) and when to use each, (3) Easing tokens — define at least 3 easing curves (e.g., ease-in-out, spring, linear) with their cubic-bezier values and appropriate use cases, (4) Animation inventory — for each of the following UI interactions: [INTERACTIONS_LIST], specify: trigger, animation type, duration token, easing token, and any delay, (5) Reduced motion — describe the reduced-motion fallback for every animation, as required by the prefers-reduced-motion media query, (6) Implementation notes — provide CSS or [ANIMATION_LIBRARY — e.g., Framer Motion, GSAP] code snippets for the 3 most complex animations.
A personalized weekly plan with daily themes, priority ranking, and conflict flags that gets you focused before Monday even starts.
Help me plan my work week of [WEEK_START_DATE]. Here is my context: open projects and deadlines: [PROJECTS_AND_DEADLINES], meetings already scheduled: [SCHEDULED_MEETINGS], energy pattern (when I do my best deep work): [ENERGY_PATTERN — e.g., mornings are best for deep work, afternoons for meetings], and top priority this week: [TOP_PRIORITY]. Using this information: (1) identify the 3 most important outcomes I must achieve by Friday to call this week a success, (2) suggest a daily theme or focus for each day (Mon–Fri) that batches similar work together, (3) flag any deadline or capacity conflicts I should resolve before the week starts, (4) identify 1–2 tasks I should delegate or defer to protect time for my top priority, (5) recommend one "defensive scheduling" action to protect focus time. Present the output as a scannable weekly plan I can review in under 2 minutes each Monday morning.
A weighted decision matrix with scores, rankings, and a plain-English interpretation that makes complex choices defensible.
Build a weighted decision matrix to help evaluate these options: [OPTIONS_LIST]. The decision criteria are: [CRITERIA_LIST]. For each criterion, I'll provide a weight (1–5) reflecting its importance: [CRITERIA_WEIGHTS]. Instructions: (1) Create a matrix with options as rows and criteria as columns, (2) Score each option on each criterion from 1–10 based on the following context: [OPTION_CONTEXT], (3) Multiply each score by its criterion weight to get a weighted score, (4) Sum the weighted scores for each option to produce a Total Score, (5) Rank options by Total Score. After the matrix, write a 3–4 sentence interpretation that: identifies the top-ranked option, notes if the result is close (within 10% of each other — suggesting the scores are inconclusive), and flags any criterion where the top-scoring option is significantly weaker than alternatives (a potential hidden risk). Present the matrix as a formatted table. Decision context: [DECISION_CONTEXT].
A crisp meeting summary with decisions, action items, and owners that prevents anything from falling through the cracks.
Write a concise, action-oriented meeting summary from the following notes or transcript: [MEETING_NOTES_OR_TRANSCRIPT]. Meeting details: title: [MEETING_TITLE], date: [MEETING_DATE], attendees: [ATTENDEES_LIST]. Structure the summary as: (1) Meeting purpose — one sentence on why this meeting was held, (2) Key decisions made — bulleted list of decisions, each starting with "Decided:" and including the rationale if relevant (3–5 decisions max), (3) Action items — a table with columns: Action, Owner, Due Date — list every commitment made, no matter how small, (4) Open questions — items that were raised but not resolved, with a note on who is responsible for resolving each, (5) Next meeting — date, purpose, and who should attend. Keep the entire summary under 400 words. Use past tense for decisions, present tense for action items. Do not include discussion tangents — only decisions and commitments.
A complete delegation brief that gives your delegate context, authority, and resources to execute without micromanagement.
Write a delegation brief for the following task being handed off to [DELEGATE_NAME], [DELEGATE_ROLE]. Task: [TASK_DESCRIPTION]. The brief must give the delegate everything they need to execute independently without coming back to ask basic questions. Include: (1) Task context — why this task matters and how it connects to [BROADER_GOAL] (2–3 sentences), (2) Desired outcome — describe what "done" looks like in concrete, measurable terms, (3) Scope and boundaries — explicit list of what is in scope and what is out of scope or should not be changed, (4) Resources and access — tools, files, contacts, and credentials they will need: [RESOURCES_LIST], (5) Constraints — non-negotiables: deadline ([DEADLINE]), budget ([BUDGET_IF_APPLICABLE]), stakeholders to keep informed, (6) Decision authority — what decisions can the delegate make independently vs. what requires your sign-off, (7) Check-in points — scheduled touch points: [CHECKIN_SCHEDULE]. Keep the brief under 400 words and write in second person ("You will…").
Step-by-step process documentation clear enough for a first-timer to follow without asking a single question.
Write clear, step-by-step process documentation for: [PROCESS_NAME]. This process is performed by [ROLE — e.g., the account manager / the DevOps team] and occurs [FREQUENCY — e.g., weekly / whenever a new client is onboarded]. Process overview provided by the subject matter expert: [PROCESS_DESCRIPTION_OR_BRAIN_DUMP]. Structure the documentation as: (1) Process overview — purpose, who runs it, frequency, and estimated time to complete, (2) Prerequisites — tools, access, and information the person must have before starting, (3) Step-by-step instructions — numbered steps, each with: the action (imperative verb), the specific tool or location, the expected result/output, and a screenshot placeholder [SCREENSHOT: description] where visuals would help, (4) Decision points — if/then branches in the process with clear criteria for each path, (5) Common errors and fixes — top 3 mistakes made and how to recover, (6) Completion criteria — how does the person know they're done? Write for someone doing this process for the first time.
process documentationSOPsknowledge managementoperationstraining
A complete, personalized habit system with stacked routines, minimum viable versions, and a failure recovery protocol.
Design a personalized habit tracking system for [YOUR_NAME_OR_ROLE] based on the following goals: [GOALS_LIST]. Habits I want to build: [DESIRED_HABITS]. Habits I want to break: [HABITS_TO_BREAK]. Available time for habit work each day: [DAILY_TIME_AVAILABLE]. Tool I'll use to track: [TRACKING_TOOL — e.g., Notion, paper journal, Streaks app, Habitica]. Design the system with: (1) A curated habit list — select the 5–7 highest-leverage habits from my list, explain why each was chosen and why others were deferred (too many habits = failure), (2) Habit stacking plan — group habits into morning, midday, and evening routines using "After I [ANCHOR], I will [HABIT]" format, (3) Minimum viable versions — for each habit, define the 2-minute "minimum" version for hard days, (4) Tracking setup — exact fields, columns, or structure to use in [TRACKING_TOOL], (5) Review cadence — weekly and monthly review questions to assess progress, (6) Failure protocol — a specific plan for what to do after missing a day (to prevent the "what's the point" spiral).
A personalized inbox zero system with filters, a processing workflow, and templates that cut daily email time in half.
Design a personalized inbox zero system for [NAME] based on the following context: email volume: [DAILY_EMAIL_VOLUME — e.g., 80–120 emails/day], email client: [EMAIL_CLIENT — e.g., Gmail, Outlook, Apple Mail], biggest current pain points: [PAIN_POINTS — e.g., nothing gets filed, I miss important emails, I use inbox as a to-do list], and time willing to spend on email per day: [TIME_BUDGET — e.g., 45 minutes total]. Design the system with: (1) Folder/label structure — the exact folder or label hierarchy to set up (keep to under 10 folders), (2) Filter rules — 5–8 specific filter rules to auto-label, archive, or route common senders/subjects, (3) Processing workflow — a 4-step decision tree for every email: Do it / Delegate it / Defer it / Delete/Archive it — with time thresholds, (4) Processing schedule — when to check email (times and maximum session length), (5) Template library — 3 reusable reply templates for the most common email types: [COMMON_EMAIL_TYPES], (6) Weekly maintenance — a 10-minute Friday cleanup routine. The goal is to reach inbox zero by [TARGET_DATE].
A complete, Grade-8-level knowledge base article with prerequisites, numbered steps, and troubleshooting that deflects support tickets.
Write a help center / knowledge base article on the topic: [ARTICLE_TOPIC]. This article is for [AUDIENCE — e.g., end users of a SaaS product / internal employees]. The article should help the reader accomplish: [USER_GOAL]. Subject matter expert input: [SME_NOTES_OR_BRAIN_DUMP]. Structure the article as: (1) Title — written as a task ("How to [action]") or a question ("How do I [action]?"), (2) Overview — 1–2 sentences explaining what the reader will be able to do after reading this, (3) Before you begin — any prerequisites, permissions, or context the reader needs, (4) Step-by-step instructions — numbered steps with imperative verbs; every step produces one clear action. Add [NOTE: text] for important caveats and [TIP: text] for shortcuts, (5) Troubleshooting — 3 common problems and their solutions in a "Problem → Solution" format, (6) Related articles — suggest 2–3 logical next articles the reader might need: [RELATED_TOPICS]. Write in plain language, second person ("you"), active voice. Target reading level: Grade 8.
A phased onboarding checklist with clear ownership and 30/60/90-day success criteria that gets new hires productive faster.
Build a comprehensive onboarding checklist for a new [ROLE — e.g., software engineer / account executive / product manager] joining [COMPANY_NAME]. Onboarding period: [ONBOARDING_DURATION — e.g., first 30/60/90 days]. Company context: [COMPANY_CONTEXT — size, stage, team structure]. Organize the checklist by timeline with these phases: (1) Before Day 1 — actions for HR/manager to complete (equipment, access, welcome message), (2) Day 1 — orientation priorities that help the new hire feel welcomed and oriented (meetings, accounts, tour), (3) Week 1 — foundational knowledge and relationships to establish, (4) Days 8–30 — deeper product/process learning and first contributions, (5) Days 31–60 — increasing ownership and delivering first solo work (if [ONBOARDING_DURATION] is 60+ days), (6) Days 61–90 — operating independently and setting 90-day goals (if applicable). For each item, include: the task, who owns it (new hire vs. manager vs. HR vs. buddy), and a checkbox format. Add a "Success at 30/60/90 days looks like..." section defining measurable outcomes.
A timed, step-by-step retrospective facilitation guide that turns team reflections into committed action items.
Create a complete retrospective facilitation guide for a [TEAM_TYPE — e.g., product engineering team / sales team] sprint/project retrospective. The retro covers: [SPRINT_OR_PROJECT_DESCRIPTION]. Team size: [TEAM_SIZE]. Duration of retro: [RETRO_DURATION — e.g., 60 minutes]. Format: [FORMAT — e.g., in-person / remote via Miro]. The guide should include: (1) Pre-retro prep (5 min before) — what the facilitator sets up and any pre-work sent to participants, (2) Icebreaker (5 min) — one specific, low-stakes prompt that loosens the group without wasting time, (3) Retrospective format — use [RETRO_FORMAT — e.g., Start / Stop / Continue / 4Ls: Liked, Learned, Lacked, Longed For / Mad, Sad, Glad] with exact facilitator prompts for each section, (4) Affinity grouping (10 min) — how to cluster similar themes and vote on priorities, (5) Action items (15 min) — process for converting top themes into 2–3 specific action items with owners and a due date, (6) Closing (5 min) — how to end the retro on a positive note and commit to follow-through. Include timing for each section.
A complete dashboard requirements doc that gives data engineers and analysts everything needed to build without a back-and-forth.
Write a dashboard requirements document for a [DASHBOARD_NAME] dashboard to be built for [PRIMARY_AUDIENCE — e.g., the executive team / the growth marketing team]. The dashboard's purpose: [DASHBOARD_PURPOSE]. Include the following sections: (1) Business objective — the specific decision this dashboard enables (not just "visibility"), (2) Primary users and their questions — for each user type: [USER_TYPES], list the top 3 questions they need this dashboard to answer, (3) Metrics and KPIs — for each metric: name, definition (exact calculation formula), data source, refresh frequency, and desired visualization type, (4) Filters and dimensions — list all filter controls users need (date range, region, segment, etc.) with default values, (5) Layout sketch — describe the grid layout in words (e.g., "KPI scorecard row at top, two charts side by side below, full-width table at bottom"), (6) Data sources — list all tables or APIs needed: [DATA_SOURCES], (7) Access control — who can view, who can edit, (8) Success criteria — how will you know the dashboard is actually being used and useful?
A structured KPI framework with formulas, owners, targets, and data sources that makes every metric unambiguous and accountable.
Define a complete KPI framework for [TEAM_OR_FUNCTION — e.g., the customer success team / the product organization] at [COMPANY_NAME]. Business objective this framework serves: [BUSINESS_OBJECTIVE]. For each of the following proposed KPIs: [KPI_LIST], provide a structured definition containing: (1) KPI name and plain-English definition (what does it actually measure?), (2) Calculation formula — exact formula using available data fields, (3) Data source — which system or table this comes from, (4) Measurement frequency — how often it should be calculated (daily, weekly, monthly), (5) Target — current baseline: [CURRENT_BASELINE], target value: [TARGET], and timeframe, (6) Owner — who is accountable for moving this number, (7) Leading vs. lagging — classify each KPI and explain why, (8) Relationship to other KPIs — does this metric drive or correlate with another? After defining all KPIs, add a "KPI hierarchy" section showing how the individual KPIs roll up to the top-level business objective. Flag any KPIs where data is not currently available or reliable.
A complete cohort analysis plan with query skeleton, cohort definitions, and an interpretation guide ready for a data analyst to execute.
Design a cohort analysis plan to answer this business question: [BUSINESS_QUESTION — e.g., "Are users who sign up via our referral program more retained at 90 days than organic signups?"]. Product or service being analyzed: [PRODUCT_NAME]. Available data: [AVAILABLE_DATA_DESCRIPTION]. The plan should specify: (1) Cohort definition — how will cohorts be grouped? (by acquisition date, acquisition channel, first product action, plan tier, etc.) and the exact cohort window (e.g., weekly cohorts from [START_DATE] to [END_DATE]), (2) Cohort size minimum — the minimum cohort size required for statistical reliability and how to handle small cohorts, (3) Key metrics per cohort — retention rate at Days [DAY_INTERVALS], and any secondary metrics: [SECONDARY_METRICS], (4) Analysis dimensions — which dimensions to slice by: [DIMENSIONS — e.g., acquisition channel, geography, plan type], (5) Expected output format — table structure and visualization type (heatmap vs. line chart), (6) SQL query skeleton — provide a skeleton query structure using [DATA_WAREHOUSE — e.g., BigQuery, Snowflake] syntax that a data analyst can populate, (7) Interpretation guide — how to read the results and what patterns indicate problems vs. health.
A statistically rigorous A/B test design with sample size math, guardrail metrics, and clear decision criteria.
Design a rigorous A/B test for the following change: [CHANGE_DESCRIPTION] on [PRODUCT_OR_PAGE]. The test document must include: (1) Hypothesis — written in the format: "We believe that [CHANGE] will cause [METRIC] to [INCREASE/DECREASE] because [RATIONALE]," (2) Primary metric — the single metric that will determine the winner, and why it was chosen over alternatives, (3) Secondary and guardrail metrics — metrics to monitor for unintended effects, (4) Sample size calculation — using a baseline conversion rate of [BASELINE_RATE]%, minimum detectable effect of [MDE]%, confidence level of [CONFIDENCE — e.g., 95%], and power of [POWER — e.g., 80%]: calculate the required sample size per variant, (5) Test duration — based on current traffic of [DAILY_TRAFFIC] sessions/day, calculate the minimum test runtime and explain why stopping early is dangerous, (6) Segmentation — which user segments to include/exclude and why, (7) Rollout plan — traffic split ([CONTROL]% control vs. [VARIANT]% variant) and how it will be implemented, (8) Decision criteria — exact rules for calling a winner, a loser, or extending the test.
A dataset-specific cleaning checklist that catches structural errors, missing data, and outliers before they corrupt your analysis.
Generate a comprehensive data cleaning checklist for the dataset described as: [DATASET_DESCRIPTION]. The dataset contains [NUMBER_OF_ROWS] rows and [NUMBER_OF_COLUMNS] columns. It will be used for: [INTENDED_ANALYSIS]. Known data quality issues: [KNOWN_ISSUES]. The checklist should cover: (1) Structural checks — column names (standardized, no spaces, consistent case), data types (verify each column's type matches its content), duplicate rows (detection and removal criteria), (2) Missing data — for each column, specify: what % missing is acceptable, and the imputation or removal strategy, (3) Outlier detection — which columns to check for outliers, the method to use (IQR, Z-score, domain-specific rules), and the threshold for flagging vs. removing, (4) Consistency checks — cross-column validation rules (e.g., "end_date must be after start_date"), (5) Domain-specific checks — [DOMAIN_SPECIFIC_RULES — e.g., email format, phone number format, valid country codes], (6) Documentation — what to log for each cleaning action (original value, new value, reason), (7) Final validation — 3 sanity checks to run after cleaning to confirm the dataset is ready. Format as a step-by-step checklist with checkboxes.
data cleaningdata qualityETLanalyticsdata engineering
A clean, commented SQL report query with CTEs, performance notes, and a plain-English walkthrough of the logic.
Write a SQL query (or set of queries) to produce the following report: [REPORT_DESCRIPTION]. Database: [DATABASE_TYPE — e.g., PostgreSQL, BigQuery, Snowflake, MySQL]. Available tables and their relevant columns: [TABLE_SCHEMA_DESCRIPTION]. Report requirements: (1) Metrics to calculate: [METRICS_LIST], (2) Dimensions to group by: [DIMENSIONS], (3) Filters to apply: [FILTERS — e.g., date range, active users only, specific regions], (4) Sort order: [SORT_ORDER], (5) Output format: [OUTPUT_FORMAT — e.g., one row per day per segment / one summary row per user]. Write the query with: (a) clear CTE (Common Table Expression) structure for readability — break complex logic into named steps, (b) inline comments on any non-obvious logic, (c) a note on expected query performance and any indexes that should exist for efficiency. After the query, provide a plain-English explanation of what each CTE or major section does. If any requirement is ambiguous or the schema appears to be missing data, flag it with a [QUESTION: ...] comment in the code.
A detailed visualization spec with chart types, data mappings, accessible colors, and annotation guidance that a developer can build directly.
Write a data visualization specification for displaying the following data: [DATA_DESCRIPTION]. The visualization is for: [AUDIENCE — e.g., executive dashboard / customer-facing report / internal analyst]. The key insight the visualization must communicate: [KEY_INSIGHT]. For each visualization recommended: (1) Chart type and rationale — name the chart type and explain in one sentence why it's the right choice for this data and message, (2) Data mapping — specify exactly which data field maps to X axis, Y axis, color, size, and tooltip, (3) Title and labels — provide the exact chart title (state the insight, not the topic), axis labels, and legend labels, (4) Formatting — number formatting, date formatting, color palette (use [BRAND_COLORS] or suggest neutral accessible colors), (5) Annotations — any reference lines, callout labels, or highlighted regions and what they show, (6) Interactivity — if applicable, what hover states, filters, or drill-downs are needed, (7) Accessibility — alt text for the chart and any colorblind-safe considerations. Recommend [NUMBER_OF_VIZZES — e.g., 2–3] visualizations that work together to tell the complete story.
A complete anomaly detection brief with method recommendations, alert thresholds, and a triage runbook for on-call engineers.
Write an anomaly detection brief for monitoring [METRIC_OR_SYSTEM — e.g., daily revenue / API error rate / user sign-ups] at [COMPANY_NAME]. The goal is to automatically flag when something is wrong so the team can investigate before customers are impacted. The brief must cover: (1) Metric definition — exact calculation of the metric being monitored and its data source, (2) Baseline behavior — describe the expected patterns: typical range [EXPECTED_RANGE], known seasonality (day-of-week, monthly cycles, holidays), and trend direction, (3) Anomaly types to detect — for each of the following anomaly types: spike, drop, gradual drift, and missing data — define what constitutes an anomaly (e.g., "a drop of more than 20% versus the same day last week"), (4) Detection method — recommend a specific statistical method (e.g., Z-score, IQR, EWMA, Prophet) appropriate for this metric's characteristics and explain why, (5) Alerting logic — alert threshold, cooldown period to prevent alert fatigue, and who gets notified via [NOTIFICATION_CHANNEL], (6) Triage runbook — a 5-step investigation checklist for the on-call engineer when an anomaly fires. Context: [ADDITIONAL_CONTEXT].
A data-backed customer segmentation plan with defined segments, validation criteria, and activation recommendations.
Design a customer segmentation plan for [COMPANY_NAME]'s [CUSTOMER_BASE — e.g., B2B SaaS customer base / e-commerce buyers]. Business objective of the segmentation: [OBJECTIVE — e.g., personalize onboarding emails / prioritize CSM coverage / identify expansion targets]. Available data for segmentation: [AVAILABLE_DATA — e.g., firmographic data, product usage events, CRM fields, purchase history]. The plan must include: (1) Segmentation hypothesis — propose 3–4 candidate segmentation approaches (e.g., by company size, by usage depth, by use case, by lifecycle stage) and recommend the best one with a rationale, (2) Segment definitions — for the recommended approach, define each segment with: name, description, qualifying criteria (using specific fields and thresholds), estimated % of customer base, and strategic value, (3) Data requirements — list every data field needed and its source system, (4) Analysis method — specify the technique (rule-based, k-means clustering, RFM scoring, etc.) and the tool/environment ([TOOL — e.g., SQL + Python, Tableau, dbt]), (5) Validation — how will you confirm the segments are meaningful and stable? (6) Activation plan — for each segment, the recommended action.
A complete funnel analysis plan with stage definitions, drop-off diagnostics, query skeletons, and experiment hypotheses.
Create a funnel analysis plan for [FUNNEL_NAME — e.g., the free-to-paid conversion funnel / the e-commerce checkout funnel] at [COMPANY_NAME]. The funnel covers the journey from [FUNNEL_START] to [FUNNEL_END]. Define the analysis as follows: (1) Funnel stages — list each stage in order with: stage name, the specific user action that defines entry into the stage, and the data event or field that captures it in [ANALYTICS_PLATFORM — e.g., Mixpanel, Amplitude, GA4, SQL], (2) Conversion rate baseline — current conversion rate at each step: [CURRENT_RATES] and the industry benchmark if known, (3) Drop-off analysis — for the 2 highest drop-off stages, specify: what data to pull to diagnose why users drop off (session recordings, heatmaps, exit surveys, error logs), (4) Segmentation cuts — which dimensions to slice the funnel by: [DIMENSIONS — e.g., acquisition channel, device type, plan type, geography], (5) SQL or analytics query skeleton — provide a query skeleton for calculating stage-by-stage conversion in [DATA_WAREHOUSE], (6) Experiment hypotheses — for each major drop-off point, propose 1 specific experiment to improve conversion with a hypothesis statement, (7) Reporting cadence — how often this funnel should be reviewed and by whom.