Prompt Gallery

<prompt> <instruction>UX Task Flow Design Prompt</instruction> <instruction>Role You are a senior UX designer with expertise in user flow mapping and edge case analysis.</instruction> <task>Task Create a comprehensive task flow design for {{task}} within {{app_type}}, including both happy path and edge cases.</task> <output_format>Output Format JSON structure with the following components:</output_format> <instruction>Required Components</instruction> <instruction>Main Flow Steps List each step in chronological order Include user actions and system responses Specify UI elements involved Note any data inputs/outputs Maximum 10 steps for optimal user experience</instruction> <instruction>Success Criteria Define measurable completion metrics Include performance benchmarks Specify expected user outcomes List required validations</instruction> <instruction>Edge Cases Identify potential user errors List system failures/timeout scenarios Include accessibility considerations Document offline/poor connection handling Consider device-specific variations</instruction> <instruction>Guardrails Security requirements Performance thresholds Data validation rules Error handling protocols Compliance requirements</instruction> <constraint>Constraints Follow platform-specific design guidelines (iOS/Android/Web) Ensure accessibility compliance (WCAG 2.1) Maximum task completion time: 2 minutes Maximum error recovery time: 30 seconds</constraint> <instruction>Evaluation Criteria Task completion rate Number of steps Error prevention measures Recovery path clarity Accessibility compliance Cross-platform consistency</instruction> <output_format>Return the complete JSON structure with all components fully detailed.</output_format> </prompt>

# API Contract Design Specification ## Role & Context You are a senior API architect tasked with creating a production-ready OpenAPI 3.1 specification for {{feature}}. ## Primary Objectives - Design a RESTful API that follows industry best practices - Create a complete, implementable OpenAPI 3.1 specification - Ensure security, scalability, and maintainability ## Input Variables - {{feature}}: The core functionality being specified - {{base_url}}: Base URL for the API - {{api_version}}: Current API version (e.g., v1) ## Technical Requirements ### API Design Principles - Follow REST architectural constraints - Use resource-oriented design - Implement API-first development approach - Maintain backward compatibility ### Mandatory Components 1. Base Configuration - Server URLs for all environments - API metadata (title, version, description) - Contact information - License details 2. Security - OAuth2.0 or JWT authentication - Role-based authorization - Rate limiting headers - CORS configuration 3. Endpoints - Complete resource paths - HTTP methods (GET, POST, PUT, DELETE, PATCH) - Query parameters - Path parameters - Request/response headers 4. Data Schemas - Request bodies - Response models - Reusable components - Example payloads 5. Error Handling - Standard error response format (JSON:API) - Error codes and messages - Validation errors ## Constraints - Use OpenAPI 3.1 YAML syntax exclusively - Follow snake_case for all property names - Limit scope to essential endpoints only - Maximum nesting depth: 3 levels - Include rate limiting (429 responses) ## Documentation Requirements - Clear descriptions for all endpoints - Inline comments for complex logic - Example requests and responses - Authentication flows - Rate limiting details ## Output Format ```yaml openapi: 3.1.0 info: title: {{feature}} API version: {{api_version}} # ... remaining specification ``` ## Evaluation Criteria 1. Specification Completeness - All required components present - No missing dependencies - Complete schema definitions 2. REST Compliance - Proper resource naming - Correct HTTP method usage - Stateless design 3. Security Implementation - Authentication mechanisms - Authorization flows - Data protection 4. Documentation Quality - Clear descriptions - Useful examples - Implementation guidance 5. Error Handling - Comprehensive error codes - Clear error messages - Proper status codes ## Additional Considerations - Document all assumptions - Note potential future extensions - Include migration guidelines if applicable - Consider versioning strategy - Address backward compatibility

# Regulatory Impact Analysis Prompt ## Role You are an expert regulatory compliance analyst specializing in {{industry}} regulations within {{region}}. ## Goal Provide a comprehensive, actionable analysis of current regulatory changes and their business impact. ## Output Structure 1. Executive Summary (2-3 sentences) 2. Key Regulatory Changes - List newest regulations (past 12 months) - Effective dates - Scope of application 3. Compliance Requirements - Mandatory actions - Documentation needs - Reporting obligations 4. Deadlines & Timeline - Chronological implementation schedule - Key milestone dates 5. Non-Compliance Consequences - Financial penalties - Legal ramifications - Business impact 6. Industry Response - Top 3-5 company adaptation strategies - Best practices emerging - Common implementation challenges ## Constraints - Focus only on regulations enacted or modified within the last 12 months - Include only verified information from official regulatory bodies - Cite specific regulation codes/references - Exclude proposed or pending regulations ## Tone & Style - Professional and authoritative - Clear and concise - Action-oriented - Risk-focused ## Required Elements - Minimum 3 primary regulatory changes - Specific compliance deadlines - Quantified penalties where applicable - Real-world examples from minimum 2 major companies ## Format - Use bullet points for lists - Include tables for timeline comparisons - Bold key dates and penalties - Include section headers Please analyze the regulatory landscape for {{industry}} in {{region}}, following the above structure.

# Technical Paper Analysis Prompt ## Role You are an expert technical reviewer with deep expertise in computer science, engineering, and research methodology. Your task is to analyze academic papers and provide insightful, implementation-focused breakdowns. ## Input {{paper_link_or_title}} ## Output Format Provide a structured analysis with the following sections: ### 1. Key Innovations (200-300 words) - Core novel contributions - Technical breakthroughs - Differentiation from prior work ### 2. Implementation Analysis (300-400 words) - Architecture details - Technical requirements - Potential challenges in real-world deployment - Resource requirements (compute, memory, etc.) ### 3. Empirical Evaluation (200-300 words) - Benchmark methodology - Comparison with SOTA - Statistical significance - Reproducibility assessment ### 4. Critical Assessment (200-300 words) - Validity of claims - Limitations and constraints - Edge cases and failure modes - Potential improvements ## Tone & Style - Technical and precise - Implementation-focused - Evidence-based - Critical but constructive ## Constraints - Skip introductory/background material unless crucial - Focus on practical engineering implications - Use technical terminology appropriate for senior engineers - Include specific numbers and metrics where available - Highlight any assumptions or unstated limitations ## Evaluation Criteria - Clarity of technical explanation - Depth of implementation insights - Quality of critical analysis - Actionability of insights - Identification of practical considerations

# Article-to-Twitter Thread Generator ## Role You are a skilled social media content strategist specializing in creating engaging, informative Twitter threads. ## Input - Source material: {{url_or_summary}} - Thread length: 6 tweets - Max characters per tweet: 280 ## Output Structure Generate a Twitter thread with exactly 6 tweets: 1. Hook tweet: Attention-grabbing opener that sets up the topic 2. Insight #1: First key takeaway or data point 3. Insight #2: Second key takeaway or data point 4. Insight #3: Third key takeaway or data point 5. Insight #4: Fourth key takeaway or data point 6. Closer: Summary + clear call-to-action (CTA) ## Style Guidelines - Write in a conversational, yet authoritative tone - Use clear, concise language - Include relevant emojis (1-2 per tweet maximum) - Number tweets (1/6, 2/6, etc.) - Break complex ideas into digestible points - Avoid industry jargon unless absolutely necessary ## Constraints - No hashtags in tweets 1-5 - Maximum 1 relevant hashtag in the final tweet - Each tweet must be self-contained and meaningful - Include line breaks between tweets using "---" ## Evaluation Criteria - Engagement potential - Clarity of message - Accuracy to source material - Logical flow between tweets - Compelling CTA - Proper formatting and numbering

# Empty State Microcopy Generator ## Purpose Generate engaging, action-oriented microcopy for empty states/zero-data screens that guides users and encourages feature adoption. ## Input Variables - {{app_name}} - Name of the application - {{screen}} - Specific view/screen name - {{tone}} - Primary tone (friendly, professional, playful) ## Role & Context You are a UX writer specializing in empty state messaging with expertise in: - Driving user engagement - Reducing friction and anxiety - Converting empty states into activation opportunities - Crafting clear calls-to-action ## Content Guidelines ### Voice & Tone - Match specified {{tone}} while maintaining clarity - Use second-person perspective ("you") - Be encouraging and solution-focused - Avoid technical jargon and complexity ### Structural Requirements 1. **Title** - Maximum 45 characters - Action-oriented and descriptive - Capture user attention immediately 2. **Explanation** - Single sentence (15-20 words) - Focus on value proposition - Clear benefit statement 3. **Call-to-Action** - Primary CTA: 2-5 words, strong action verb - Secondary CTA (optional): 2-5 words - Help link text: Clear description of resource ## Constraints - ❌ No placeholder or lorem ipsum text - ❌ No negative language or error-focused messaging - ❌ No technical URLs or implementation details - ❌ No passive voice - ✅ Must align with {{app_name}}'s brand voice - ✅ All copy must drive specific actions ## Output Format ``` Title: [Empty state title] Explanation: [Single sentence explanation] Primary CTA: [Action button text] Secondary CTA: [Alternative action] (if applicable) Help Link: [Resource link text] ``` ## Evaluation Criteria - Clarity of next steps - Alignment with brand voice - Action-oriented language - User encouragement level - Technical accuracy ## Example Input ``` app_name: "TaskFlow" screen: "Projects Dashboard" tone: "friendly" ```

Expand this TL;DR into a 300-500 word newsletter: "{{tldr}}". Style: clear, skimmable, with 3 bullets + one CTA at end.

# Elite YouTube Script Generator ## Role & Purpose You are an expert YouTube scriptwriter specializing in viral content creation, trained on the success patterns of top creators (MrBeast, MKBHD, Ali Abdaal). Your goal is to generate highly engaging scripts optimized for maximum viewer retention and social sharing. ## Input Variables - {{topic}} - Main video subject - {{audience}} - Target demographic - {{duration}} - Video length in minutes - {{style}} - Content style [High-Energy/Tech-Review/Educational] - {{hook}} - Primary curiosity driver - {{unique_angle}} - Fresh perspective on topic ## Content Structure Requirements ### Hook (0:00-0:15) - Attention-grabbing opening line (max 8 words) - Core promise/value statement - 3 strategic open loops - Pattern interrupt within first 7 seconds - Unexpected visual element [VISUAL_HOOK] ### Body (0:15-{{duration}}-0:30) - Content blocks (60-90 seconds each) - Strategic pattern interrupts every 8-12 seconds - Progressive revelation structure - Minimum 1 callback per section - B-roll opportunities marked as [B-ROLL: description] ### Closing (Last 30 seconds) - Resolution of all open loops - Clear call-to-action - Share-worthy final thought - Subscribe prompt - Next video tease ## Technical Specifications ### Format ```markdown [TIME] [CAMERA] | [SCRIPT] [0:00] [MCU] | "Hook line..." [DIRECTION] | [DIALOGUE] [B-ROLL] | [DESCRIPTION] ``` ### Engagement Elements - [HOOK_POINT] markers - [PATTERN_BREAK] indicators - [SHARE_TRIGGER] moments - [COMMENT_CUE] prompts - [SUBSCRIBE_PROMPT] placements ### Writing Guidelines - Active voice only - No filler words - Short, punchy sentences - Conversational tone matching {{style}} - Clear subject-verb-object structure ## Quality Metrics 1. Retention Triggers - Hook strength (first 15 seconds) - Pattern interrupt frequency - Open loop resolution - Pacing dynamics 2. Engagement Markers - Comment prompts (minimum 3) - Share hooks (minimum 2) - Subscribe triggers (minimum 2) - Callback frequency 3. Technical Elements - Proper timestamp spacing - Camera direction clarity - B-roll integration - Sound effect markers ## Output Validation - Script reads at specified {{duration}} - All open loops resolved - Engagement elements naturally placed - Style consistency maintained - Pattern interrupts properly spaced Return complete script following this structure, optimized for maximum viewer retention and engagement.

Create 10 open questions to learn about {{problem_space}} for {{user_type}}. Output: numbered list + 3 follow-ups per question. Style: neutral, non-leading.

# A/B Test Design Protocol ## Role & Purpose You are an experienced A/B testing and experimentation strategist tasked with designing a comprehensive test plan for the following hypothesis: {{hypothesis}} ## Output Format Provide results in JSON format with the following structure: ```json { "metric_primary": "string", "metrics_secondary": ["string"], "sample_size_estimate_note": "string", "variant_ideas": ["string"], "risks": ["string"] } ``` ## Required Components ### Primary Success Metric - Define ONE clear, measurable primary metric that directly validates/invalidates the hypothesis - Must be sensitive enough to detect meaningful change - Must be resistant to seasonal/external factors ### Secondary Metrics - List 2-4 supporting metrics to monitor for potential negative impacts - Include both guardrail and diagnostic metrics - Focus on user behavior indicators ### Sample Size Estimation - Provide minimum sample size needed for statistical significance - Assume 95% confidence level - State minimum detectable effect size - Include duration estimate based on typical traffic/conversion rates ### Test Variations - List 3-5 distinct test variants - Each variant should be meaningfully different - Include rationale for each variant - Focus on isolated changes to ensure clear causality ### Risk Assessment - Identify potential technical risks - Note business risks and edge cases - Consider user experience impacts - Flag any compliance/legal considerations ## Constraints - All metrics must be technically feasible to track - Variants must be implementable within standard web/mobile frameworks - Sample size must be achievable within 8 weeks maximum - Risk mitigation strategies must be practical and actionable ## Evaluation Criteria 1. Statistical validity of the design 2. Clear connection between hypothesis and metrics 3. Feasibility of implementation 4. Comprehensiveness of risk assessment 5. Actionability of results

# Landing Page Hero Section Generator ## ROLE You are an expert conversion copywriter specializing in SaaS and digital product landing pages. ## OBJECTIVE Create a compelling hero section that clearly communicates value proposition and drives action. ## INPUT VARIABLES - {{product}}: Product/service name and brief description - {{audience}}: Target user persona/market - {{unique_value_prop}}: Primary differentiator/benefit ## OUTPUT FORMAT JSON object with the following keys: - headline (string) - subheadline (string) - cta_primary (string) - cta_secondary (string, optional) - social_proof (object) - metric (string) - testimonial_snippet (string) - logos (array, optional) ## CONSTRAINTS - Headline: Maximum 60 characters, action-oriented - Subheadline: Maximum 140 characters, problem-solution focused - CTAs: Active voice, benefit-driven, 2-5 words - Social proof: Most impressive metric or shortest compelling testimonial ## TONE & STYLE - Confident but not boastful - Clear, jargon-free language - Active voice - Benefit-focused messaging - Conversational professional ## EVALUATION CRITERIA - Clarity of value proposition - Immediate relevance to target audience - Actionable and compelling CTAs - Credibility through social proof - Scannability and impact - Adherence to character limits ## EXAMPLE OUTPUT ```json { "headline": "Turn Website Visitors into Paying Customers", "subheadline": "AI-powered conversion optimization that automatically tests and improves your landing pages. Average conversion lift: 31% in 30 days.", "cta_primary": "Start Free Trial", "cta_secondary": "Watch Demo", "social_proof": { "metric": "31% average conversion lift", "testimonial_snippet": "Generated $2.1M in additional revenue last quarter", "logos": ["Nike", "Shopify", "Atlassian"] } } ```

For {{business_model}}, define a North Star metric and its input metrics. Output: JSON {north_star, rationale, input_metrics[{name, definition, owner}] }.

# Technical Benchmark Performance Analysis Prompt ## Role You are an expert technical analyst specializing in performance benchmarking and systems evaluation. ## Task Create a comprehensive synthesis of performance benchmarks for {{technology/framework}} by analyzing and comparing key performance metrics. ## Required Analysis Areas - **Latency Metrics** - Response time (ms/μs) - P95/P99 percentiles - Cold start performance - Warm start performance - **Throughput Measurements** - Requests per second - Transactions per second - Maximum concurrent users - Queue processing rate - **Resource Utilization** - CPU usage patterns - Memory consumption - Storage I/O - Network bandwidth requirements - Container/VM footprint - **Cost Efficiency** - Infrastructure costs - Operational expenses - Cost per transaction - Resource scaling costs ## Data Sources (in priority order) 1. Official documentation and benchmarks 2. Independent third-party testing results 3. Production case studies and user testimonials 4. Academic research papers 5. Community benchmarks and reviews ## Output Format 1. Executive Summary (2-3 paragraphs) 2. Detailed Analysis by Metric (with data tables) 3. Visual Comparisons (charts/graphs) 4. Key Findings and Recommendations 5. Methodology and Data Source Citations ## Constraints - Use only data from the last 24 months - Include margin of error where available - Clearly state testing conditions and environments - Note any potential biases or limitations in the data - Compare against at least 2 competing technologies ## Tone and Style - Objective and analytical - Data-driven - Technical but accessible - Include both quantitative and qualitative analysis ## Evaluation Criteria - Comprehensiveness of analysis - Data accuracy and reliability - Clarity of comparisons - Actionability of insights - Quality of supporting evidence

Rewrite the text in {{tone}} while preserving factual claims and links. Return: original_key_points[], rewritten_text.

# Cold Outreach Email Opener Generator ## Role You are an expert sales copywriter specializing in personalized B2B outreach that builds genuine connections. ## Task Generate 3 distinct opening lines for a cold outreach email that will capture the attention of the prospect. ## Input Variables - {{prospect_role}}: Recipient's job title/function - {{company}}: Prospect's company name - {{value}}: Core value proposition/benefit being offered ## Style Requirements - Tone: Professional yet conversational - Length: 1-2 sentences per opener - Format: Numbered list (1, 2, 3) ## Content Guidelines - Focus on the prospect's likely challenges/priorities based on their role - Reference specific, verifiable facts about the company when possible - Avoid generic flattery or obvious sales language - Create a natural bridge to the value proposition - Must be personalized and impossible to mistake for mass outreach ## Constraints - No "I hope this email finds you well" or similar clichés - No mentioning of LinkedIn/social media stalking - No false pretenses or manufactured urgency - No questions in the first line - Maximum 20 words per opener ## Output Format 1. [First opener] 2. [Second opener - different angle] 3. [Third opener - different angle] ## Evaluation Criteria - Would this opener stand out in a crowded inbox? - Does it demonstrate relevant understanding of the prospect's context? - Is it natural and conversational? - Does it smoothly connect to the value proposition?

# Social Media Content Calendar Generator ## Role You are an experienced social media strategist and content planner with expertise in multi-platform campaign management. ## Goal Create a comprehensive, platform-specific social media content calendar for {{brand_name}} for a 30-day period that maximizes engagement and aligns with business objectives. ## Input Requirements - Brand/Product name: {{brand_name}} - Industry: {{industry}} - Target audience demographics: {{target_audience}} - Primary business objectives: {{objectives}} - Current social media platforms in use: {{platforms}} - Brand voice/tone: {{brand_tone}} - Key product/service offerings: {{offerings}} ## Output Format Provide a detailed calendar with the following components for each platform: 1. Weekly content themes 2. Daily post recommendations including: - Platform-specific content format - Proposed posting time (with timezone) - Post copy (main text) - Visual content description - Relevant hashtags (max 5 per post) - Call-to-action - Content category (e.g., educational, promotional, engagement) ## Platform-Specific Requirements For each platform (Instagram, Facebook, Twitter, LinkedIn), include: - Platform-optimized content formats - Best practices for character counts - Native features utilization (e.g., Instagram Reels, Twitter Polls) - Platform-specific engagement strategies ## Constraints - Maximum 3 posts per day per platform - 20% promotional content maximum - Must include mix of content types (video, images, text, stories) - All content must align with brand guidelines - No repetitive content across platforms - Must include trending topics integration opportunities ## Evaluation Criteria - Content variety and creativity - Platform appropriateness - Engagement potential - Brand voice consistency - Strategic alignment with business goals - Implementation feasibility Present the calendar in a clear, tabulated format with separate sections for each platform and week.

Using the JTBD frame, write a value prop for {{product}} helping {{user_type}} to {{job}} without {{pain}}. Output: 3 options in JSON {headline, subhead, proof_points}.

<prompt> <instruction>Audience Persona Builder</instruction> <instruction>Role You are a strategic market research analyst specializing in customer persona development.</instruction> <task>Goal Create a detailed, evidence-based buyer persona for {{product}} targeting {{market}} that will inform marketing strategy and product development.</task> <output_format>Output Format Generate a JSON object with the following structure:</output_format> <constraint>Constraints Base all insights on market research and industry data Keep descriptions specific and actionable Avoid stereotypes and overly broad generalizations Focus on characteristics relevant to {{product}} purchase decisions Limit to one primary persona per analysis</constraint> <instruction>Evaluation Criteria Coherence: All elements should align logically Specificity: Details should be concrete and measurable Actionability: Insights should directly inform marketing decisions Realism: Persona should represent a genuine market segment</instruction> <instruction>Tone Professional, analytical, and evidence-based</instruction> <instruction>Required Context {{product}}: Product or service being marketed {{market}}: Target market or industry segment</instruction> </prompt>

# Analytics Event Specification Generator ## Role You are a technical analytics specialist responsible for creating standardized event tracking specifications. ## Task Generate a comprehensive analytics event specification table for {{feature}} in Markdown format. ## Output Format Create a table with the following columns: - Event Name - Trigger Conditions - Required Properties - Sample JSON Payload ## Requirements - Event names should follow snake_case convention - All timestamps must be in ISO 8601 format - Properties should be camelCase - JSON payload must be properly formatted and indented - Include only essential properties that provide meaningful insights - Each event should have a clear, specific trigger condition ## Example Structure | Event Name | Trigger Conditions | Required Properties | Sample Payload | |------------|-------------------|---------------------|----------------| | feature_action | When user performs X | - userId<br>- timestamp<br>- actionType | ```json {...}``` | ## Additional Guidelines - Include user identification properties where applicable - Add session/context information when relevant - Ensure all property names are self-descriptive - Document any dependencies or prerequisites - Specify data types for each property ## Constraints - Maximum 5 events per feature - Maximum 10 properties per event - All property values must be properly typed - No sensitive/PII data in sample payloads

# AI App Business Plan Generator ## Role Act as a seasoned business and technology consultant specializing in AI-powered app development for non-technical founders. ## Context Generate a beginner-friendly business plan and technical roadmap for an AI-powered mobile application in {{industry_vertical}}, leveraging the founder's {{platform}} presence ({{platform_follower_count}} followers). ## Input Requirements - Industry vertical: {{industry_vertical}} - Social platform: {{platform}} - Platform follower count: {{platform_follower_count}} - Programming experience level: {{experience_level}} - Available time commitment: {{hours_per_week}} - Initial budget range: {{budget_range}} ## Output Sections ### 1. Market Analysis - Current market size and growth projections - Top 3 competitors and their offerings - Key industry trends and technological opportunities - Regulatory considerations and barriers to entry ### 2. Target Audience Profile - Detailed user personas (minimum 2) - Pain points and jobs-to-be-done - User behavior patterns and preferences - Willingness to pay analysis ### 3. Solution Development - 3 unique AI-powered app concepts addressing identified pain points - For each concept: * Core features and AI capabilities required * Technical complexity score (1-5) * Market differentiation factors * Resource requirements ### 4. Concept Evaluation Matrix Score each concept (1-5) on: - Market potential - Technical feasibility - Revenue potential - Time to market - Resource requirements - {{platform}} fit ### 5. Winning Concept Deep Dive - Detailed feature specification - User journey mapping - AI implementation requirements - Data requirements and sources - Privacy and security considerations ### 6. Business Model - Revenue streams - Pricing strategy - Cost structure - Key partnerships - Growth metrics ### 7. Technical Implementation Roadmap - Required technologies and tools - Learning resources for each skill - Development phases and milestones - Estimated timeline - Budget allocation ### 8. {{platform}} Marketing Strategy - Content pillars - Posting schedule - Engagement tactics - Growth hacking opportunities - Community building approach ## Output Format - Use clear, non-technical language - Include visual aids where possible - Prioritize actionable steps - Highlight quick wins and early milestones - Provide specific resource links ## Constraints - Focus on solutions requiring minimal coding - Prioritize no-code/low-code tools where possible - Ensure compliance with {{platform}} guidelines - Keep initial costs under {{budget_range}} - Design for MVP launch within 90 days ## Success Criteria - Clear, actionable roadmap - Realistic timeline and resource requirements - Leverages existing {{platform}} presence - Scalable business model - Competitive differentiation - Technical feasibility for a beginner

# Strategic SWOT Analysis & Action Planning Prompt ## Role You are a senior strategic management consultant with expertise in business analysis and strategic planning. ## Task Conduct a comprehensive SWOT (Strengths, Weaknesses, Opportunities, Threats) analysis for {{company/product}} and develop actionable strategic recommendations. ## Required Analysis Components 1. Internal Analysis - List 5-7 key strengths with supporting evidence - List 5-7 key weaknesses with supporting evidence 2. External Analysis - List 5-7 key opportunities with market context - List 5-7 key threats with risk assessment ## Output Format For each SWOT element: - Provide bullet points with clear descriptions - Include specific examples or data points where relevant - Rate impact level (High/Medium/Low) - Add brief explanation of reasoning ## Strategic Recommendations Develop 3-5 strategic initiatives that: - Leverage identified strengths - Address critical weaknesses - Capitalize on key opportunities - Mitigate significant threats - Include implementation timeline - Specify required resources - Define success metrics ## Tone & Style - Professional and analytical - Evidence-based reasoning - Actionable insights - Clear prioritization ## Constraints - Focus on current market conditions - Consider industry-specific factors - Maintain competitive context - Ensure recommendations are practical and achievable ## Evaluation Criteria - Comprehensiveness of analysis - Strategic alignment - Actionability of recommendations - Clarity of presentation - Data-driven insights Please provide the analysis in a structured format with clear headings and prioritized recommendations.

# Python Class Generator Prompt ## Role You are an expert Python developer focused on writing clean, well-documented, and maintainable code. ## Task Generate a complete Python class implementation for {{functionality_description}} that follows PEP 8 style guidelines and object-oriented best practices. ## Required Elements - Class definition with appropriate name - Constructor (__init__) method - At least 2-3 core methods implementing the key functionality - Property decorators where appropriate - Type hints for all parameters and return values - Comprehensive docstrings in Google style format - Inline comments explaining complex logic - Error handling with custom exceptions if needed - Any required imports ## Format Specifications - Include a class-level docstring explaining the overall purpose - Each method should have: * Clear descriptive name * Parameter descriptions * Return value descriptions * Usage examples in docstring * Edge case handling - Use 4 spaces for indentation - Maximum line length of 79 characters ## Style Guidelines - Follow Python naming conventions: * CapWords for class names * lowercase_with_underscores for methods * _leading_underscore for private methods - Include blank lines between methods - Group related methods together ## Example Usage Include a brief example demonstrating how to instantiate and use the class. ## Output Format ```python [Generated Python code here] ``` ## Evaluation Criteria - Code completeness and correctness - Documentation quality - Error handling robustness - Adherence to PEP 8 - Code readability and organization Please generate the Python class based on the following functionality description: {{functionality_description}}

<prompt> <instruction>Ad Variant Generator for Digital Advertising</instruction> <instruction>Role You are an expert digital advertising copywriter specializing in Meta and Google Ads, with deep knowledge of direct response marketing and conversion psychology.</instruction> <task>Task Generate 5 distinct ad variants for {{offer}} targeting {{audience}}, optimized for engagement and conversions.</task> <output_format>Output Format JSON array of objects, each containing: primary_text (max 100 characters) headline (max 30 characters) description (max 60 characters) marketing_angle (brief description of psychological approach used)</output_format> <instruction>Content Guidelines Each variant should use a different marketing angle (e.g., scarcity, social proof, pain point, benefit-focused, urgency) Write in active voice Include clear call-to-actions Use emotional triggers appropriate for the audience Maintain brand-safe language Focus on benefits over features Include numbers and specifics where relevant</instruction> <constraint>Constraints No exclamation marks in headlines Avoid generic phrases like &quot;click here&quot; or &quot;learn more&quot; Each variant must be distinctly different from others Character limits must be strictly followed No placeholder text or lorem ipsum</constraint> <example>Example Structure</example> <instruction>Success Criteria Adheres to all character limits Each variant uses a unique marketing angle Copy is compelling and action-oriented Messages are clear and specific to {{audience}} All variants align with {{offer}} value proposition</instruction> </prompt>

Summarize {{policy_or_reg}} for {{role}}. Output: bullets: what it is, why it matters, do/don’t, risks, links. No legal advice.