Prompt Library
High-signal templates to get better outputs from LLMs instantly.
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.
SEOBloggingCopywriting
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.
E-commerceCopywritingMarketing
Writing
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.
NewsletterEmailWriting
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].
Technical WritingDocumentationDevelopers
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.
BooksOutliningLong-form Writing
Writing
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.
PRCommunicationsBusiness
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.
Public SpeakingPresentationsScripts
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.
ReactTypeScriptTailwind
Coding
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]
CodingCode ReviewDebugging
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.
SQLCodingDatabase
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.
APIBackendRESTCoding
Coding
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.
DatabaseSQLArchitectureCoding
Coding
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.
TestingTDDQuality AssuranceCoding
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.
ArchitectureSystem DesignScalability
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.
DebuggingError HandlingCoding
Marketing
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.
SalesEmailOutreach
Marketing
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.
YouTubeContent CreationVideo
Marketing
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.
CopywritingMarketingConversion
Marketing
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).
Social MediaMarketingPlanning
Marketing
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.
BrandingCopywritingMarketing
Marketing
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.
StrategyCompetitive AnalysisMarketing
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.
Email MarketingCopywritingTesting
Marketing
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.
PersonasResearchMarketing Strategy
Marketing
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.
AdvertisingCreativeCampaigns
Business
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.
BusinessStartupsPlanning
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]
ProductivityBusinessMeetings
Business
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.
HRManagementFeedback
Business
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).
CareerInterviewsJob Search
Business
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.
SalesObjection HandlingBusiness Development
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.
Risk ManagementStrategyBusiness Planning
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.
OKRsGoal SettingStrategyLeadership
Research
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]
ResearchSummarizationAcademic
Research
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.
AcademicResearchLiterature Review
Research
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.
Survey DesignResearch MethodsData Collection
Research
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.
Fact-CheckingMedia LiteracyResearch
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.
StrategyForesightTrend Analysis
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.
Qualitative ResearchInterviewsJournalism
Writing
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.
whitepaperthought leadershipB2B contentlong-formintroduction
Writing
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."
twitterXthreadsocial mediaviral content
Writing
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.
podcastshow notesSEOcontent repurposingaudio
Writing
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.
refactoringclean codecode qualitymaintenancebest practices
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.
APIdocumentationdeveloper docscodereference
Coding
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.
databaseschemaSQLPostgreSQLdata modelingbackend
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.
CI/CDDevOpsGitHub Actionspipelineautomationdeployment
Marketing
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.
personaICPB2Bcustomer researchmarketing strategy
Marketing
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."
pricingSaaSconversionlanding pagecopywriting
Marketing
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.
testimonialsocial proofemailcustomer successreview request
Business
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].
hiringjob descriptionrecruitingHRtalent acquisition
Business
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.
performance reviewHRmanagementemployee feedbackpeople ops
Business
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."
partnershipB2Bbusiness developmentproposalalliances
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.
QBRquarterly reviewexecutive reportingbusiness reviewstrategy
Business
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].
risk assessmentrisk managementproject managementcompliancegovernance
Research
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.
SWOTstrategic analysiscompetitive intelligencebusiness strategyresearch
Research
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
Research
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.
patentIPintellectual propertylegalinnovationresearch
Research
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.
trend analysisindustry researchmarket intelligenceforecastingstrategy
Research
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.
academic researchcitationsliterature reviewscholarlybibliography
Research
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.
executive summarybusiness writingreportscommunicationleadership
Design
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.
brandingbrand identitydesign brieflogovisual identity
Design
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.
UX auditUI reviewusabilityproduct designaccessibility
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.
design systemcomponent librarydocumentationUIfrontend
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].
wireframeUX specproduct designinformation architectureprototyping
Design
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.
iconsicon designdesign briefUIvisual design
Design
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.
typographytype pairingdesign systemfontsbrand design
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].
accessibilityWCAGa11yinclusive designaudit
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.
motion designanimationmicro-interactionsdesign systemUI
Productivity
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.
planningweekly reviewtime managementproductivityfocus
Productivity
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].
decision makingprioritizationframeworksanalysisstrategy
Productivity
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.
meeting notesaction itemsproductivitycommunicationfollow-up
Productivity
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…").
delegationmanagementleadershipproductivityteam
Productivity
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
Productivity
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).
habitsproductivity systembehavior changetrackingroutine
Productivity
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].
inbox zeroemailproductivitytime managementorganization
Productivity
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.
knowledge basehelp centerdocumentationsupportself-service
Productivity
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.
onboardingHRemployee experiencechecklistpeople ops
Productivity
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.
retrospectiveagileteam managementfacilitationcontinuous improvement
Data Analysis
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?
dashboarddata visualizationrequirementsanalyticsBI
Data Analysis
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.
KPIsmetricsanalyticsperformance measurementOKRs
Data Analysis
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.
cohort analysisretentionanalyticsSQLproduct analytics
Data Analysis
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/B testingexperimentationCROstatisticsproduct analytics
Data Analysis
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
Data Analysis
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.
SQLreportingdata analysisbusiness intelligencequeries
Data Analysis
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.
data visualizationchartsBIdashboardanalytics
Data Analysis
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].
anomaly detectionmonitoringalertingdata engineeringobservability
Data Analysis
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.
segmentationcustomer analyticsCRMpersonalizationdata strategy
Data Analysis
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.
funnel analysisconversionproduct analyticsCROSQL
Marketing
A scroll-stopping LinkedIn post with a bold hook, concrete argument, and reply-driving CTA, formatted for the feed.
Write a LinkedIn post on the following topic: [TOPIC]. My audience is [AUDIENCE, e.g., SaaS founders, marketing managers]. My goal for this post is [GOAL, e.g., build credibility, generate leads, start a conversation]. My tone is [TONE, e.g., direct and slightly contrarian, warm and practical]. The post should: (1) open with a single bold sentence or question that stops the scroll, no "I'm excited to share" or preamble, (2) make one clear argument or tell one specific story with a concrete detail (number, name, or outcome), (3) break the text into short paragraphs, max 2 sentences each, (4) end with one direct call-to-action or question that invites a reply, (5) stay under 1,300 characters total. Do not use hashtag spam. Limit to 3 targeted hashtags maximum. No em dashes in the opening line.
linkedinsocial-mediacopywritingthought-leadership
Writing
A complete, camera-ready YouTube script with hook, structured content, B-roll cues, and a CTA, formatted for natural delivery.
Write a complete YouTube video script on the topic: [VIDEO TOPIC]. Target audience: [AUDIENCE]. Video length target: [LENGTH, e.g., 8–12 minutes]. My channel style is [STYLE, e.g., fast-paced and data-driven, conversational and story-based]. Structure the script as follows: (1) Hook (first 30 seconds), open with a bold claim, surprising fact, or direct promise that tells the viewer exactly what they will get and why they should care now, (2) Intro (30–60 sec), briefly establish credibility and preview the 3–5 main points, (3) Main content, structured sections with a clear heading for each point, concrete examples or case studies, and natural transition lines between sections, (4) CTA section, one clear ask (subscribe, click link, comment), (5) Outro (30 sec). Include [B-ROLL] and [ON-SCREEN TEXT] cues in brackets. Use conversational language. Write as if speaking, short sentences, active voice, no jargon.
youtubevideoscriptwritingcontent-creation
Marketing
A 5-email onboarding sequence that gets new customers to their activation moment, with subject lines, CTAs, and a reactivation nudge.
Write a [NUMBER, e.g., 5-email] onboarding email sequence for [PRODUCT/SERVICE]. The customer just signed up for [PLAN/TIER]. Their primary goal is [CUSTOMER GOAL]. The most important action they need to take in the first 7 days is [KEY ACTIVATION ACTION]. Write each email with: subject line, preview text, opening line (no "Welcome!" preamble), body (under 150 words), and one CTA. Email 1 (Day 0, immediately after signup): confirm signup and get them to complete [FIRST ACTION] right now. Email 2 (Day 1): show them the fastest path to [KEY VALUE MOMENT]. Email 3 (Day 3): share one customer story or data point that proves [KEY BENEFIT]. Email 4 (Day 5): address the most common reason customers don't complete setup, [COMMON OBJECTION]. Email 5 (Day 7): if they haven't [KEY ACTIVATION ACTION] yet, send a direct re-engagement prompt with a personal offer or low-friction alternative. Keep every email scannable, outcome-focused, and in a [BRAND TONE, e.g., warm and direct, professional and concise] voice.
emailonboardingcustomer-successsequences
A complete PRD with problem statement, user stories, success metrics, and acceptance criteria, ready for engineering review.
Write a Product Requirements Document for the following feature or product: [FEATURE/PRODUCT NAME]. Context: [2-3 sentence description of what this is and why we're building it]. Write the PRD with these sections: (1) Problem Statement, what specific user problem does this solve, and what is the cost of not solving it, (2) Target Users, primary persona(s) with their context and current workaround, (3) Goals and Success Metrics, 2–3 measurable outcomes we will track to know this worked (include specific KPI targets), (4) Scope, what is in scope for v1 and what is explicitly out of scope, (5) User Stories, write the 5 most critical user stories in the format "As a [user], I want to [action] so that [outcome]" with acceptance criteria for each, (6) Edge Cases and Constraints, list 3–5 edge cases the engineering team must consider, (7) Dependencies, what does this feature depend on or block, (8) Open Questions, list unresolved decisions that need stakeholder input. Keep the tone precise and implementation-agnostic.
product-managementPRDuser-storiesrequirements
Complete user stories with Given/When/Then acceptance criteria, story points, and edge case coverage, ready for sprint planning.
I need you to write agile user stories for the following feature: [FEATURE DESCRIPTION]. Our tech stack is [STACK, e.g., React frontend, Node.js API, PostgreSQL]. Our users are [USER TYPES, e.g., admin users and end customers]. For each user story: (1) write the story in the format "As a [role], I want to [capability] so that [benefit]", (2) write 3–5 acceptance criteria in Given/When/Then format, (3) flag any technical dependencies, API calls, or database changes required, (4) estimate a story point value (1, 2, 3, 5, or 8) with a one-line justification. Generate stories for these scenarios: happy path (the main use case working as expected), error states (what happens when the feature fails or receives bad input), and edge cases (boundary conditions, empty states, concurrent users). Format the output as a numbered list of stories, each complete enough for a developer to start implementation without needing a follow-up meeting.
agileuser-storiesscrumproduct-managementdevelopment
Business
A spoken pitch deck script for each slide, investor-ready narrative that builds urgency, proves traction, and closes with a clear ask.
Write the narrative script for a [LENGTH, e.g., 10-slide] investor pitch deck for [COMPANY NAME]. Company context: [2-3 sentences describing what the company does, for whom, and what stage you are at]. Here are the key facts to weave in: problem we solve: [PROBLEM], our solution: [SOLUTION], market size: [TAM/SAM/SOM], traction: [KEY METRICS OR MILESTONES], business model: [HOW WE MAKE MONEY], team: [FOUNDER BACKGROUNDS], and ask: [FUNDING AMOUNT AND USE]. Write the spoken script for each slide, not bullet points, but the actual words the founder says while the slide is on screen. Each slide script should be 60–90 seconds when spoken. Make the opening memorable. Make the problem feel urgent. Make the traction slide concrete with specific numbers. Make the team slide personal and relevant to the problem. End the ask slide with a clear statement of what changes when they invest. Tone: confident, specific, and human, not corporate.
fundraisingpitch-deckstartupsinvestor-relations
Three optimized, copy-paste-ready image generation prompts in different visual styles, with subject, lighting, camera, and negative prompts.
I want to generate an image using [TOOL, e.g., Midjourney, DALL-E 3, Flux, Ideogram]. Here is what I am trying to create: [ROUGH DESCRIPTION OF THE IMAGE]. My intended use is [USE CASE, e.g., website hero banner, social post, product mockup, illustration for an article]. Please write me 3 optimized prompts for this image, one for realism, one for a stylized/illustrated look, and one for a dark/cinematic aesthetic. For each prompt: (1) describe the subject with specific visual details (expression, position, clothing, action), (2) specify the environment and lighting (time of day, light source, mood), (3) specify camera style (lens type, distance, angle) where relevant, (4) add 3–5 style or quality modifiers appropriate for [TOOL], (5) add a negative prompt list of things to exclude. Format each prompt as a single, comma-separated string ready to paste directly into the tool.
image-generationmidjourneydall-eprompt-engineeringdesign
Marketing
A one-page competitive battle card with win/lose scenarios, pre-loaded objection responses, and landmine questions, ready for the sales floor.
Create a sales battle card for competing against [COMPETITOR NAME] when selling [YOUR PRODUCT/SERVICE]. Include: (1) Competitor overview, what they offer, their typical customer, and their core selling message in 2 sentences, (2) Where we win, 3–4 specific scenarios where our product is the better choice, stated as situation-specific claims ("When a customer needs X, we win because Y"), (3) Where they win, be honest: 2 situations where the competitor has a genuine advantage so reps aren't caught off guard, (4) Common objections and responses, list 5 objections a prospect raises when comparing us to [COMPETITOR] and write a concise, non-defensive rebuttal for each, (5) Landmines to plant, 3 questions our reps can ask that reveal weaknesses in [COMPETITOR's] offering before the prospect raises it themselves, (6) Proof points, 2 customer quotes, case studies, or stats that directly counter [COMPETITOR's] key claims (use [PLACEHOLDER] format for any we need to source). Format as a one-page reference card a rep can scan in 60 seconds mid-call.
salescompetitive-intelligenceobjection-handlingbattle-card
Writing
A natural, spoken-word voiceover script with delivery cues, emotional beats, and word count, ready for human recording or AI text-to-speech.
Write a voiceover script for [CONTENT TYPE, e.g., product demo video, explainer video, ad, documentary segment]. Length: [TARGET DURATION, e.g., 60 seconds, 2 minutes]. Subject: [WHAT THE VOICEOVER IS ABOUT]. Tone: [TONE, e.g., confident and direct, warm and reassuring, energetic and youthful]. The voiceover will be read by [VOICE TYPE, e.g., a professional AI voice, a human presenter, a character narrator]. Write the script so that: (1) sentences are short and spoken-word natural, no sentence should be hard to say in one breath, (2) contractions are used throughout ("you're", "it's", "we've") to sound human, (3) emotional beats are marked in [BRACKETS] for the voice talent or TTS tool, e.g., [pause], [emphasize], [warm], (4) the script reads at approximately [WPM, e.g., 140 words per minute] which is [DURATION] when spoken, (5) the opening 10 seconds hooks the listener without announcing what you're about to tell them. Include a word count at the end.
voiceoverscriptwritingvideoaudiocontent
Marketing
A complete 30-day content calendar with daily topics, weekly themes, platform breakdowns, and an evergreen backup bank.
Build a 30-day content strategy for [BRAND/CREATOR NAME] across these platforms: [PLATFORMS, e.g., LinkedIn, Instagram, YouTube]. My audience is [AUDIENCE DESCRIPTION]. My business goal for the next 30 days is [GOAL, e.g., generate 50 qualified leads, grow LinkedIn following by 500, launch a new product]. My content pillars are (or help me define 3): [PILLARS or "help me define these"]. For each of the 30 days, specify: the platform, content format (e.g., carousel, short-form video, text post, newsletter, long video), topic or angle, and a one-line creative hook or title. Group the days by week and include: a weekly theme that ties the content together, one hero piece of content per week that takes more production effort but has the highest reach potential, and a content repurposing map showing how each hero piece gets sliced into 3–4 derivative posts for other platforms. At the end, include a list of the 10 evergreen topics I should have ready as backup content when I miss a day.
content-strategycontent-calendarsocial-mediamarketing
Writing
Turns a handful of writing samples into a documented brand voice guide anyone on the team can follow.
You are a brand voice analyst. I'm going to give you 3-5 samples of writing that represent how I want my brand to sound. Analyze them and produce a structured Brand Voice Guide with the following sections:
1. Voice Summary: 2-3 sentences describing the overall personality
2. Tone Attributes: list 4-6 adjectives that define the tone, each with a one-sentence explanation and a "this, not that" contrast (e.g., "Confident, not arrogant")
3. Vocabulary Rules: words and phrases to always use, words to never use, and jargon policy
4. Sentence Patterns: average sentence length, use of questions, preferred structures (active vs. passive, lists vs. paragraphs)
5. Punctuation & Formatting: em dash usage, exclamation points, capitalization style, emoji policy
6. Channel Adaptation Notes: how the voice should flex for email vs. social vs. long-form
Here are my writing samples:
[PASTE 3-5 SAMPLES HERE]
WritingBrandingStyle Guide
Writing
Scores any draft against your stated brand rules and flags exactly what needs fixing before it goes out.
You are a content compliance auditor. I'm going to give you two things:
1. My rules: a set of brand voice, style, or compliance rules that all content must follow.
2. A draft: a piece of content to audit against those rules.
Analyze the draft and produce a Compliance Report with:
- Overall Score: Pass / Conditional Pass / Fail
- Violations Table: each violation listed with: the exact offending text, which rule it breaks, severity (Critical / Warning / Nit), and a suggested fix
- Clean Sections: note which parts of the draft fully comply (so the writer knows what's working)
- Summary: 2-3 sentence overall assessment
Be thorough but fair. Flag real violations, not stylistic preferences that aren't covered by the stated rules.
My Rules:
[PASTE YOUR RULES HERE]
Draft to Audit:
[PASTE DRAFT HERE]
WritingEditingQuality Control
Converts a rambling voice memo or bullet list into a polished, publish-ready thought-leadership post in the founder's own voice.
You are a ghostwriter for a solo founder or executive. I'm going to give you raw material: either a voice-memo transcript, a bullet list of ideas, or rough notes. Turn it into a polished first-person thought-leadership piece.
Rules:
- Maintain the speaker's authentic voice, don't make it sound like a different person
- First person throughout
- Structure: hook, core insight, supporting evidence or story, takeaway the reader can act on
- Length: 600-1,200 words (LinkedIn article length) unless I specify otherwise
- No cliches: no "in today's fast-paced world," no "at the end of the day," no "game-changer"
- Concrete over abstract, if the raw material has a specific example, lead with it
- End with a perspective or question, never a generic CTA like "What do you think?"
Target platform: [LinkedIn / Blog / Newsletter, specify one]
Raw material:
[PASTE TRANSCRIPT, BULLETS, OR NOTES HERE]
WritingContent CreationThought Leadership
Writing
Adapts a piece of content for a new market's culture and conventions instead of just translating the words.
You are a content localization specialist. I have a piece of content written for one market, and I need it adapted for a different target market. This is NOT just translation, I need cultural adaptation.
Adapt the following content for [TARGET MARKET] by:
1. Idioms & expressions: replace culture-specific idioms with local equivalents (don't just translate literally)
2. Cultural references: swap out references that won't resonate (sports analogies, holidays, pop culture, business norms)
3. Numbers & units: convert currency, measurements, date formats, and number formatting to local conventions
4. CTAs & tone: adjust the directness, formality, and call-to-action style for what works in this market
5. Legal/compliance: flag any claims, testimonials, or data-use statements that may need local legal review
6. Sensitivity check: flag anything that could be culturally insensitive or inappropriate in the target market
Output the adapted content, then a Localization Notes section listing every change you made and why.
Source market: [e.g., US English]
Target market: [e.g., Germany / DACH region]
Content type: [e.g., landing page, email, social post]
Original content:
[PASTE HERE]
WritingLocalizationInternational
Produces a severity-ranked code review with a clear merge verdict, matching how a senior engineer reviews a pull request.
You are a senior staff engineer conducting a code review. I'm going to paste a code diff (or a code snippet being proposed for merge). Review it and produce structured feedback.
For each comment:
- Line/section: reference the specific code
- Severity: one of: BLOCKING (must fix before merge), SECURITY (potential vulnerability), WARNING (should fix, not a blocker), NIT (style/preference, optional)
- Issue: what's wrong
- Suggestion: how to fix it, with code if applicable
After all line comments, provide:
- Summary verdict: Approve / Request Changes / Needs Discussion
- Architecture note: any structural concern that isn't visible in the diff alone
- Test coverage: note any untested paths or missing edge cases
Be opinionated but fair. Distinguish real problems from style preferences.
Diff:
[PASTE DIFF OR CODE HERE]
CodingCode ReviewQuality Control
Turns a raw dependency audit dump into a prioritized, actionable patch plan ranked by real-world exploitability.
You are a security engineer triaging vulnerabilities from a dependency audit. I'm going to paste the output of a security scan (npm audit, pip audit, Snyk report, or similar). Produce a prioritized remediation plan.
For each vulnerability:
- Priority: P0 (patch today), P1 (patch this week), P2 (patch this sprint), P3 (track/accept risk)
- CVE/Advisory: the identifier
- Package: affected dependency
- Exploitability: how easy it is to exploit in YOUR context, is the vulnerable code path actually reachable in your app?
- Business impact: what's the worst-case outcome if exploited
- Fix: exact version to upgrade to, or workaround if no patch exists
- Breaking risk: likelihood the upgrade introduces breaking changes
End with:
- Recommended order of operations: which patches to bundle, which to test carefully
- Accepted risks: any P3s you'd recommend formally accepting, with justification
Audit output:
[PASTE AUDIT REPORT HERE]
CodingSecurityDevOps
Generates complete, developer-ready API documentation directly from your actual function code.
You are a technical writer generating API documentation. I'm going to paste a function, class, or module. Produce clean, enterprise-standard API docs with:
1. Overview: one-paragraph description of what this does and when to use it
2. Signature: the function/method signature with types
3. Parameters: table with: name, type, required/optional, default, description
4. Returns: type and description of the return value, including shape for objects/arrays
5. Errors/Exceptions: what it throws/returns on failure, with conditions
6. Usage Examples: 2-3 realistic code examples (basic usage, with options, error handling)
7. Notes: edge cases, performance considerations, or gotchas
Use clean markdown formatting. Write for a developer who has never seen this codebase.
Code:
[PASTE FUNCTION OR MODULE HERE]
CodingDocumentationDeveloper Tools
Converts messy, multi-person incident notes into a structured, blameless postmortem ready to share with the team.
You are an SRE writing a blameless postmortem. I'm going to give you raw incident timeline notes, messy, incomplete, possibly from multiple people. Produce a structured postmortem document following Google SRE / enterprise standards.
Sections:
1. Incident Summary: 2-3 sentences: what happened, impact, duration
2. Timeline: chronological, in UTC, from first signal to full resolution. Format: HH:MM: [DETECT/ESCALATE/MITIGATE/RESOLVE] Description
3. Impact: users affected, revenue impact, SLA implications, data loss
4. Root Cause: technical root cause, clear and specific
5. Contributing Factors: organizational or process factors that let the root cause slip through
6. What Went Well: things that worked during the response
7. What Went Wrong: things that slowed detection or resolution
8. Action Items: table with: action, owner, priority (P0/P1/P2), due date, status
9. Lessons Learned: 2-3 takeaways for the broader team
Rules:
- Blameless: never name individuals as the cause. Use roles or systems.
- Specific: include exact times, error messages, and metrics where the raw notes provide them
- Honest: if something went wrong in the response, say so plainly
Raw incident notes:
[PASTE HERE]
CodingDevOpsDocumentation
Turns a plain-language brand description into a complete, developer-ready design system spec.
You are a design systems architect. I'm going to describe my brand's visual identity, colors, fonts, logo, general aesthetic. Produce a structured Design System Specification I can hand to any designer or developer to build consistent assets.
Output sections:
1. Color System: primary, secondary, accent, semantic (success/warning/error/info), neutrals. For each: hex, RGB, usage rules, accessible contrast pairings
2. Typography Scale: font families (display, body, mono), size scale (in rem), weight usage rules, line-height ratios
3. Spacing Scale: base unit and scale (4px or 8px base), named sizes (xs through 3xl), usage guidelines
4. Component Rules: buttons, cards, inputs, badges, with border-radius, shadow, and padding specs
5. Layout Grid: max-width, column structure, breakpoints, gutter sizes
6. Iconography: style (outline/filled/duotone), size scale, stroke width
7. Motion & Animation: timing function, duration scale, when to animate vs. not
8. Do/Don't Examples: 3-4 visual rules stated as do/don't pairs
My brand:
[DESCRIBE YOUR BRAND VISUALS HERE, colors, fonts, logo, mood, existing examples]
DesignBrandingDesign Systems
Runs any screen or flow through a Nielsen heuristic evaluation and returns ranked, fixable UX issues.
You are a senior UX designer conducting a heuristic evaluation. I'm going to describe a screen, page, or user flow (or paste a screenshot if using a vision model). Evaluate it against Nielsen's 10 Usability Heuristics and produce a structured review.
For each heuristic, rate it: PASS / MINOR ISSUE / MAJOR ISSUE / NOT APPLICABLE
For any issue found:
- Heuristic violated: which of the 10
- Where: the specific element or interaction
- Severity: 0 (not a problem) to 4 (usability catastrophe)
- Issue: what's wrong
- Recommendation: how to fix it
End with:
- Top 3 priorities: the three changes that would most improve the experience
- What's working well: 2-3 things the design does right
Screen/flow to evaluate:
[DESCRIBE OR PASTE SCREENSHOT HERE]
DesignUXQuality Control
Turns a rough creative brief into three ready-to-run, on-brand image generation prompts with settings.
You are an AI art director. I'm going to give you two things:
1. My brand style: colors, aesthetic, mood, things to avoid
2. A rough creative brief: what I need the image to show
Turn this into 3 optimized image-generation prompts (for Midjourney, DALL-E, or Ideogram) that will produce on-brand results.
For each prompt:
- The prompt: full text, structured for the target model
- Negative prompt (if applicable): what to exclude
- Recommended settings: aspect ratio, style parameter, model version
- Why this approach: one sentence on the creative choice
Rules:
- Incorporate brand colors and aesthetic into the prompt as style modifiers
- Avoid generic stock-photo aesthetics
- Each of the 3 prompts should take a different creative angle on the same brief
My brand style:
[DESCRIBE YOUR BRAND AESTHETIC]
Creative brief:
[WHAT DO YOU NEED THIS IMAGE FOR / WHAT SHOULD IT SHOW]
DesignAI ArtBranding
Design
Flags WCAG 2.1 AA accessibility violations in any screen description and gives specific fixes for each.
You are an accessibility specialist. I'm going to describe a screen, page, or component design. Audit it against WCAG 2.1 AA standards and produce a structured report.
For each issue found:
- WCAG criterion: the specific guideline (e.g., 1.4.3 Contrast)
- Level: A, AA, or AAA
- Element: what's affected
- Issue: what fails
- Impact: who is affected and how
- Fix: specific remediation
End with:
- Compliance summary: estimated % of WCAG 2.1 AA criteria met
- Top 3 quick wins: easiest high-impact fixes
- Positive notes: anything already done well for accessibility
Design to audit:
[DESCRIBE THE SCREEN, layout, colors with hex values, interactive elements, text content, images]
DesignAccessibilityQuality Control
Marketing
Builds a personalized account research brief on a target company for account-based outreach.
You are a B2B sales researcher. I'm targeting a specific company for outreach. Research them and produce a structured Account Brief I can use to personalize my outreach.
Output sections:
1. Company Snapshot: name, industry, size, HQ, key products/services, founding year
2. Leadership: 2-3 key decision-makers with titles and LinkedIn presence
3. Recent Activity: last 3-6 months: press releases, funding, hires, product launches, awards, or notable social posts from leadership
4. Likely Pain Points: 3-5 pain points based on their size, industry, and recent activity (be specific, not generic)
5. Buying Signals: indicators they might be in-market for a solution like mine: tech stack clues, job postings, recent vendor changes, growth trajectory
6. Personalization Angles: 3 specific hooks I could use in outreach
7. Recommended Approach: which channel, what tone, and what NOT to say
My company/product (for context): [BRIEF DESCRIPTION OF WHAT YOU SELL]
Target company: [NAME OR DOMAIN]
MarketingSalesABMResearch
Marketing
Generates 10 emotionally distinct ad copy variants for the same offer so you can test which angle converts.
You are a performance copywriter. I need to test different emotional/psychological angles for an ad. Generate exactly 10 ad copy variants for the same offer, each using a DIFFERENT psychological angle.
The 10 angles to cover:
1. Fear of missing out (FOMO)
2. Social proof
3. Pain agitation
4. Aspiration/identity
5. Curiosity gap
6. Logic/ROI
7. Urgency/scarcity
8. Contrarian/myth-busting
9. Empathy/validation
10. Authority/credibility
For each variant:
- Angle: which of the 10
- Headline (max 40 chars)
- Body copy (max 125 chars)
- CTA (max 25 chars)
- Why it works: one sentence
Platform: [Facebook / Google / LinkedIn / Instagram, specify one]
The offer: [DESCRIBE YOUR PRODUCT/SERVICE AND THE SPECIFIC OFFER]
Target audience: [WHO ARE YOU TARGETING]
MarketingAdvertisingCopywriting
Designs a complete, staged email nurture sequence mapped to a specific point in the customer journey.
You are an email marketing strategist. I need a nurture email sequence for a specific stage of my customer journey. Design the full sequence.
For each email in the sequence:
- Email # and send timing (e.g., Day 0, Day 3, Day 7)
- Subject line (under 50 chars, no clickbait)
- Purpose: what this email accomplishes in the sequence
- Body outline: opening hook, key message, proof/evidence, CTA
- CTA: specific action you want them to take
- Tone note: how the tone should shift from the prior email
End with:
- Sequence logic: what triggers entry, what exits them, what happens after the sequence ends
- Metrics to watch: which email to optimize first, target benchmarks
Funnel stage: [e.g., cold prospect, post-demo no-reply, free trial onboarding, win-back]
Product/service: [WHAT YOU SELL]
Audience: [WHO RECEIVES THESE EMAILS]
MarketingEmailAutomation
Marketing
Analyzes a competitor's actual messaging and returns counter-positioning angles you can use without naming them.
You are a positioning strategist. I'm going to paste a competitor's messaging (from their website, ads, or pitch deck). Analyze it and produce a Competitive Positioning Brief I can use to differentiate against them.
Output sections:
1. Competitor Positioning Summary: what they're claiming, who they're targeting, what their core value prop is
2. Strengths: what they do well in their messaging (be honest)
3. Weaknesses & Gaps: where their positioning is vulnerable: vague claims, missing proof, audience gaps, pricing blind spots
4. Head-to-Head Comparison: table comparing their positioning vs. yours on 5-6 key dimensions
5. Counter-Positioning Angles: 3-4 specific angles you can use to position against them without naming them
6. Messaging Ammunition: 2-3 ready-to-use lines that exploit their weak spots
Rules:
- Never recommend naming the competitor in your own copy
- Be honest about where they're stronger
Competitor messaging:
[PASTE THEIR WEBSITE COPY, AD COPY, OR PITCH DECK TEXT]
My positioning (for context):
[BRIEF DESCRIPTION OF YOUR POSITIONING]
MarketingStrategyCompetitive Analysis
Productivity
Extracts owners, deadlines, and priorities from raw meeting notes so nothing discussed gets lost.
You are an executive assistant processing meeting notes. I'm going to paste raw meeting notes or a transcript. Extract and structure all action items.
For each action item:
- Action: clear, specific, starts with a verb
- Owner: who's responsible (use the name mentioned, or "[UNASSIGNED]" if unclear)
- Deadline: stated deadline, or "[NO DEADLINE, SUGGEST ONE]" with your recommendation
- Context: one sentence on why this matters
- Dependencies: any blockers or things that need to happen first
- Priority: High / Medium / Low
Also produce:
- Decisions Made: list of explicit decisions reached during the meeting
- Open Questions: things discussed but NOT resolved
- Next Meeting Agenda Suggestions: 2-3 items to cover next time
Meeting notes:
[PASTE HERE]
ProductivityMeetingsOrganization
Productivity
Turns your raw calendar and task list into a prioritized weekly briefing telling you exactly where to focus.
You are my chief of staff. I'm going to paste my calendar for the week and my current task list. Produce a Weekly Briefing that tells me exactly where to focus.
Sections:
1. Week at a Glance: total meetings, deep-work blocks available, busiest day, lightest day
2. Top 3 Priorities This Week: the 3 things that will matter most in 30 days if I do them now
3. Calendar Conflicts & Warnings: back-to-back meetings with no breaks, double-bookings, meetings that could be emails
4. Tasks: Do / Delegate / Defer / Drop: categorize every task on my list
5. Prep Required: anything I need to prepare before a meeting or deadline this week, with prep time estimate
6. Energy Map: which days should be deep work vs. meetings vs. admin
7. One Thing to Say No To: the single lowest-ROI commitment on my calendar this week
My calendar:
[PASTE CALENDAR EVENTS WITH TIMES]
My task list:
[PASTE CURRENT TASKS]
ProductivityPlanningTime Management
Productivity
Converts a vague goal into a properly formatted OKR with measurable, outcome-based key results.
You are an OKR coach. I'm going to describe a goal or strategic priority. Help me turn it into a properly formatted OKR with 3-5 measurable key results.
Rules for good OKRs:
- The Objective is qualitative, ambitious, and inspiring
- Key Results are quantitative, specific, and time-bound
- Key Results measure OUTCOMES, not activities
- Each Key Result should be achievable but stretchy (70% confidence of hitting it)
- Include the measurement method for each KR
Output:
- Objective: the refined objective statement
- Key Results: 3-5 measurable KRs, each with: the metric, target number, current baseline, measurement method
- Grading guidance: what 0.3, 0.7, and 1.0 looks like for each KR
- Risk flags: anything about these KRs that might make them gameable or misleading
My goal:
[DESCRIBE YOUR GOAL HERE]
ProductivityPlanningGoal Setting
Productivity
Turns messy raw notes and Slack threads into a clean, searchable knowledge base article with flagged gaps.
You are a technical writer turning raw notes into a clean, searchable knowledge base article. I'm going to paste messy notes, meeting notes, Slack messages, bullet points, or stream-of-consciousness text. Turn them into a structured wiki article.
Output format:
1. Title: clear, searchable
2. TL;DR: 2-3 sentence summary at the top
3. Body: organized under logical headings with short paragraphs, bullet lists, bold key terms on first use, code blocks for technical content
4. Related Topics: 2-3 links to related articles (suggest titles even if they don't exist yet)
5. Last Updated: today's date
6. Owner: "[ASSIGN]" placeholder
Rules:
- Fill in obvious gaps with "[NEEDS INFO: what's missing]" flags rather than guessing
- If the notes contradict themselves, flag both versions and mark "[RESOLVE: which is correct?]"
- Write for someone who has zero context
Raw notes:
[PASTE HERE]
ProductivityDocumentationKnowledge Management
Produces a full market sizing and competitive landscape brief for any named market or topic.
You are a market intelligence analyst. I'm going to name a market, industry, or topic. Produce a structured Market Intelligence Brief.
Sections:
1. Market Overview: what this market is, who the buyers are, what problem it solves
2. Market Size & Growth: TAM/SAM/SOM estimates with sources, growth rate, key drivers
3. Key Players: 5-8 notable companies with: name, positioning, estimated revenue/funding, and what makes them notable
4. Trends: 3-5 trends shaping this market in the next 12-24 months
5. Risks & Headwinds: 3-4 threats: regulatory, competitive, technological, macroeconomic
6. Opportunities & White Space: where the gaps are for a new entrant or differentiator
7. Data Sources: where you'd go for ongoing monitoring of this market
Rules:
- Cite sources or note when an estimate is inferred
- Distinguish between facts, consensus estimates, and your analysis
- Flag data that may be outdated with "[VERIFY: may be outdated]"
Market/topic:
[NAME THE MARKET]
ResearchMarket IntelligenceStrategy
Research
Fact-checks a specific claim or statistic against supporting and contradicting sources ranked by credibility.
You are a research analyst fact-checking a claim. I'm going to give you a specific claim or statistic. Verify it by finding supporting and contradicting evidence.
Output:
1. The Claim: restate it precisely
2. Verdict: Confirmed / Partially True / Unverified / Likely False / False
3. Supporting Evidence: sources that support the claim, each with: source name, date, what it says, credibility rating (High/Medium/Low)
4. Contradicting Evidence: sources that challenge or contradict the claim, same format
5. Nuance & Context: important caveats
6. Recommended Citation: if usable, the strongest source to cite; if not, a corrected version with a proper source
Credibility ratings:
- High: peer-reviewed research, government data, established industry reports
- Medium: reputable journalism, company-published data, industry association reports
- Low: blog posts, social media, self-reported surveys with unclear methodology
The claim:
[PASTE THE SPECIFIC CLAIM OR STATISTIC HERE]
ResearchFact-CheckingAnalysis
Research
Synthesizes multiple paper summaries into a themed literature review with identified research gaps.
You are a research synthesizer. I'm going to paste summaries, abstracts, or key findings from multiple papers/articles on the same topic. Produce a thematic literature review synthesis.
Output:
1. Topic Statement: one sentence defining the research question or domain
2. Thematic Synthesis: organize findings by THEME, not by paper. Group related findings across papers under 3-5 thematic headings, noting where sources agree and disagree
3. Consensus View: what the literature collectively suggests
4. Research Gaps: 3-5 questions the existing literature does NOT answer
5. Methodological Notes: any concerns about methodology across the papers
6. Recommended Next Reads: 2-3 research directions worth pursuing
Papers/sources:
[PASTE SUMMARIES, ABSTRACTS, OR KEY FINDINGS, label each with Author/Title/Year]
ResearchAcademicAnalysis
Research
Turns scattered competitor news into a ranked digest with strategic implications and concrete actions.
You are a competitive intelligence analyst. I'm going to paste recent news, announcements, or observations about one or more competitors. Turn them into a structured Competitive Intelligence Digest with strategic implications for my business.
Output:
1. Digest Summary: 2-3 sentence overview of what happened this period
2. Signal Analysis: for each piece of intel: what happened, signal type (Product/Pricing/Hiring/Funding/Partnership/Market Entry/Messaging Change), strength of signal (Strong/Moderate/Weak), strategic implication, recommended response
3. Pattern Watch: any emerging patterns across signals
4. Updated Threat Assessment: which competitor became more/less threatening and why
5. Actions for This Week: 1-3 concrete actions based on this intel
My business context: [BRIEF DESCRIPTION OF YOUR POSITIONING]
Competitor intel:
[PASTE NEWS, ANNOUNCEMENTS, OR OBSERVATIONS]
ResearchCompetitive IntelligenceStrategy
Converts raw monthly metrics and notes into a polished, one-page board-ready update.
You are a chief of staff drafting a board update. I'm going to paste raw metrics, notes, and highlights from the past month/quarter. Turn them into a polished board-ready update.
Format:
1. Executive Summary: 3-4 sentences: where the business is, what changed, what's next
2. Key Metrics Dashboard: table of 5-8 KPIs with: metric, current value, prior period, change, target, status
3. Wins: 2-4 highlights with brief context
4. Challenges: 2-3 issues with: what's happening, impact, and mitigation plan
5. Strategic Updates: progress against stated priorities or OKRs
6. Financial Summary: revenue, burn, runway, notable line items
7. Ask / Discussion Items: 1-2 items where you need board input or a decision
8. Next Period Priorities: top 3 focus areas for the coming month/quarter
Rules:
- Lead with the headline, not the buildup
- Bad news is stated plainly with a mitigation plan, never buried or softened
- Numbers are compared against TARGETS, not just prior period
- Keep it to one page if printed (under 800 words)
Raw data/notes:
[PASTE HERE]
BusinessReportingCommunication
Business
Flags risky or one-sided contract clauses and suggests specific redline language before you sign.
You are a contract analyst (not a lawyer, this is not legal advice). I'm going to paste a contract or agreement. Review it and flag risky, unusual, or one-sided clauses.
For each flagged clause:
- Section/clause: where in the document
- Risk level: High / Medium / Low
- Issue: what's problematic and why
- Market standard: what this clause typically looks like in fair contracts
- Suggested redline: specific language to propose as a counter
Also include:
- Missing protections: standard clauses that SHOULD be in this contract but aren't
- Favorable Terms: anything unusually good for you
- Overall Risk Assessment: summary: sign as-is / negotiate specific terms / walk away / get a lawyer
Important: This is analytical support, not legal advice. Always recommend the user consult a qualified attorney for significant contracts.
Contract text:
[PASTE HERE]
BusinessLegalRisk Management
Business
Builds best, base, and worst-case 12-month financial projections from your stated business assumptions.
You are a financial planning analyst. I'm going to describe my business model and key assumptions. Build three financial scenarios, Best Case, Base Case, and Worst Case, with monthly projections for the next 12 months.
For each scenario:
- Assumptions: what changes from base case
- Monthly P&L: revenue, COGS, gross margin, operating expenses, net income (table format, months 1-12)
- Key Milestones: when do you hit breakeven, $10K MRR, $25K MRR (or note if you don't)
- Cash Position: starting cash + monthly net = running cash balance
- Breaking Point: when does cash run out in worst case
End with:
- Sensitivity Analysis: which single variable has the biggest impact on outcomes
- Decision Triggers: "If X happens by month Y, do Z" for each scenario
My business model:
[DESCRIBE: pricing, current revenue, monthly costs, expected growth rate, churn assumptions, starting cash]
BusinessFinanceStrategy
Builds a negotiation brief with specific pressure points and counter-offer language for any vendor proposal.
You are a procurement negotiation specialist. I'm going to paste a vendor's proposal or pricing page. Produce a Negotiation Brief that prepares me to get better terms.
Output:
1. Proposal Summary: what they're offering, at what price, with what terms
2. Market Comparison: how this pricing compares to alternatives (name 2-3 competitors and their pricing)
3. Negotiation Angles: 3-5 specific angles: what's inflated or negotiable, where they have incentive to discount, what you can offer in exchange
4. Red Lines: terms you should not accept and why
5. Counter-Offer Template: a specific counter-proposal with language you can send
6. Walk-Away Alternative: what you do if they won't negotiate (your BATNA)
The vendor proposal:
[PASTE HERE]
My context: [YOUR BUDGET, TIMELINE, AND HOW MUCH YOU NEED THIS VENDOR VS. ALTERNATIVES]
BusinessProcurementNegotiation
Data Analysis
Turns a raw metrics dump into a 60-second executive narrative with clear recommended actions.
You are a business analyst writing an executive narrative for a dashboard or metrics report. I'm going to paste raw numbers. Turn them into a narrative that answers three questions: What changed? Why does it matter? What should we do?
Rules:
- Lead with the most important change, not the first metric in the list
- Compare to targets AND prior period
- Call out anomalies, anything that moved more than 15% in either direction
- End with 2-3 specific recommended actions
- Write for a busy executive who will spend 60 seconds reading this
- Under 300 words
Raw metrics:
[PASTE YOUR NUMBERS, include current values, prior period, and targets if available]
Data AnalysisReportingCommunication
Data Analysis
Reads raw A/B test numbers and returns a statistical significance verdict with a clear ship or kill call.
You are a data analyst interpreting A/B test results. I'm going to paste the raw results. Tell me whether the results are statistically significant and what to do next.
Output:
1. Test Summary: what was tested, control vs. variant
2. Results Table: side-by-side metrics for control and variant
3. Statistical Significance: is the difference statistically significant at 95% confidence? Include confidence level, p-value estimate, sample size assessment
4. Practical Significance: even if statistically significant, is the effect size large enough to matter?
5. Verdict: SHIP IT / KILL IT / KEEP RUNNING / ITERATE
6. Caveats: anything that could invalidate these results
7. Next Test Suggestion: what to test next based on what you learned
Test results:
[PASTE RESULTS, include: sample sizes, conversion rates, confidence intervals if available, test duration]
Data AnalysisTestingDecision Making
Data Analysis
Analyzes cohort retention data and returns the drop-off point plus concrete actions to fix it.
You are a growth analyst running a cohort retention analysis. I'm going to describe or paste customer/user data. Produce a cohort analysis with actionable retention insights.
Output:
1. Cohort Definition: how you're grouping users
2. Retention Table: cohort vs. time period matrix showing retention rates (or describe the pattern if you can't build the full table)
3. Key Findings: drop-off cliff, stabilization point, best cohort, worst cohort
4. Behavioral Correlations: what separates users who retain from those who churn
5. Recommended Actions: 1-2 to reduce early drop-off, 1-2 to improve long-term retention, 1 segment to double down on
6. Metrics to Track Going Forward
Data:
[DESCRIBE OR PASTE YOUR USER/CUSTOMER DATA]
Data AnalysisCustomer ResearchRetention
Data Analysis
Generates a ranked list of likely root causes for a sudden metric spike or drop, with a step-by-step investigation plan.
You are a data analyst investigating a metric anomaly. I'm going to describe a sudden spike or drop in a business metric. Help me identify the most likely root causes.
Output:
1. Anomaly Summary: what changed, by how much, and the time window
2. Hypothesis List: rank 5-7 possible root causes from most to least likely, each with: hypothesis, likelihood (High/Medium/Low), evidence needed, how to check
3. Investigation Playbook: step-by-step order to investigate, fastest/cheapest hypotheses first
4. Quick Fixes: if any hypothesis is confirmed, the immediate mitigation
5. Prevention: what monitoring/alerting would catch this faster next time
The anomaly:
[DESCRIBE: what metric, normal range, what happened, when, any known context like deploys/campaigns/external events]
Data AnalysisTroubleshootingOperations