workflowworkflowco-star
0

MCP Server Integration Planner for Custom Tools

#ROLE Expert workflow strategist with deep knowledge of AI-assisted workflows #CONTEXT Design how to expose your internal APIs as MCP servers for AI agent consumption #OBJECTIVE Create a ready-to-use prompt that solves a specific workflow problem #STYLE Clear, actionable, professional #TONE Confident, helpful, no hype #AUDIENCE Professionals seeking to automate workflow tasks with AI #RESPONSE A structured prompt using the CO-STAR framework that includes: - Clear role definition - Specific context with placeholders {variable} - Measurable objective - Style and tone guidance - Target audience specification - Exact response format with constraints

P
PromptAura Team
workflowworkflowape
0

Agentic Workflow Debugger and Optimizer

#ACTION Given a workflow description, identify bottlenecks, suggest parallelization, and estimate cost/latency #PURPOSE Save time and improve quality in workflow work #EXPECTATION Output that requires minimal editing, follows best practices, and solves the stated problem

P
PromptAura Team
researchresearchtrace
0

Decision-Oriented Data Analyst Agent

#TASK Turn raw datasets into actionable business recommendations with clear risk/benefit analysis #REQUEST Create a prompt that teaches the AI to perform this research task consistently #ACTION Provide clear instructions, examples, and validation criteria #CONTEXT User will provide specific inputs via variables; task occurs in professional research setting #EXAMPLE Input: {example_input} Expected: {example_output}

P
PromptAura Team
researchresearchspecs
0

Context-Aware Literature Review Synthesizer

#SITUATION Upload multiple papers and get a synthesized review highlighting contradictions, gaps, and consensus #PURPOSE Produce accurate, useful research output that saves time #EXPECTED OUTPUT Specific format with: [list key components], constrained to [length/format], includes [required elements] #CONTEXT Assumes user has basic research knowledge and access to necessary data/files #STYLE Direct, professional, no marketing fluff

P
PromptAura Team
marketingmarketingcraft
0

AI-Powered Brand Voice Auditor for Social Media

#CONTEXT Analyze social media posts for brand voice consistency and suggest improvements #ROLE Professional marketing copywriter #ACTION Generate compelling, on-brand content that drives engagement #FORMAT Markdown with clear sections, variables marked, length constraints if applicable #TARGET marketing professionals targeting specific audience segments

P
PromptAura Team
marketingmarketingrtf
0

Agentic Marketing Campaign Orchestrator

#ROLE marketing specialist #TASK Plan and execute multi-channel marketing campaigns with AI agents handling content creation, scheduling, and performance analysis #FORMAT Variables in {double braces}, sections with clear headers, no filler text, output ready for copy-paste

P
PromptAura Team
videovideorisen
0

Educational Video Lesson Planner with Interactive Elements

#ROLE Video process engineer #INSTRUCTIONS 1. Identify the core video task to automate 2. Break it into sequential steps an AI can follow 3. Add validation checkpoints 4. Specify required inputs and expected outputs 5. Include error handling and fallback instructions #STEPS [Step 1: Define inputs and constraints] [Step 2: Process data/context] [Step 3: Generate primary output] [Step 4: Validate against requirements] [Step 5: Format and deliver final result] #END GOAL A repeatable, reliable video workflow that produces consistent quality #NARROWING Focus on: Design educational videos with quizzes, branching scenarios, and knowledge checks Constraints: Must work with current AI models, require minimal editing, include safety checks

P
PromptAura Team
videovideoco-star
0

Multimodal Video Script Generator for Product Demos

#ROLE Expert video strategist with deep knowledge of AI-assisted workflows #CONTEXT Create engaging product demo videos combining screen capture, voiceover, and annotations using AI #OBJECTIVE Create a ready-to-use prompt that solves a specific video problem #STYLE Clear, actionable, professional #TONE Confident, helpful, no hype #AUDIENCE Professionals seeking to automate video tasks with AI #RESPONSE A structured prompt using the CO-STAR framework that includes: - Clear role definition - Specific context with placeholders {variable} - Measurable objective - Style and tone guidance - Target audience specification - Exact response format with constraints

P
PromptAura Team
workflowworkflowmulti-agent
0

Agent Handoff Protocol Designer

#SITUATION You are designing a multi-agent workflow where specialized agents need to pass tasks, context, and intermediate results to each other reliably. #PURPOSE Define a handoff protocol that specifies what information is transferred when an agent completes its subtask, ensuring the receiving agent has everything needed to continue without loss of context or redundancy. #EXPECTED OUTPUT A protocol document that includes: - Trigger conditions for handoff (task completion, time limit, error) - Data payload schema (what fields are included, types, examples) - Context preservation rules (what short-term and long-term memory to transfer) - Acknowledgment mechanism (how the receiver confirms receipt) - Error handling (what happens if handoff fails) - Versioning and backward compatibility guidance #CONTEXT Assume agents are built using a common framework (e.g., LangGraph, AutoGen) and communicate via message passing. Each agent has access to a shared scratchpad and private memory. #STYLE Technical, precise, uses bullet lists and code snippets for schema examples.

P
PromptAura Team
videovideoeducational
0

Educational Video Script Builder

#CONTEXT You need to create a short educational video (5-10 minutes) that explains a concept clearly and keeps viewers engaged. #ROLE Educational video scriptwriter who structures content for retention and engagement using storytelling principles. #ACTION 1. Start with a hook: surprising fact, question, or brief anecdote related to the concept. 2. State the learning objective clearly. 3. Break the concept into 3-5 digestible chunks using analogies and visual metaphors. 4. For each chunk, provide: narration script, suggested visuals/animations, and on-screen text. 5. Include a brief example or case study to illustrate application. 6. End with a summary and a call-to-action (e.g., "try this exercise", "learn more"). 7. Add speaker notes for pacing and emphasis. #FORMAT Output as a two-column script: left column for audio/narration, right column for visuals and timing. Alternatively, provide a detailed outline with timestamps. #TARGET Educators, content creators, or trainers who want to produce effective instructional videos without starting from scratch.

P
PromptAura Team
imageimageproduct-photography
0

Product Photo Scene Describer

#ROLE Product photography director who creates detailed scene descriptions for AI image generation or human photographers. #TASK Generate a vivid, detailed prompt that describes the product, setting, lighting, composition, and mood for a product photograph that highlights key features and appeals to the target audience. #FORMAT Output as a single paragraph suitable for feeding into an image generation model (Midjourney, DALL·E, Stable Diffusion) or as a brief for a photoshoot. Include: - Product description (material, color, key details) - Setting/context (where the product is placed) - Lighting (type, direction, quality) - Composition (angle, framing, depth of field) - Mood/style (e.g., luxurious, rugged, playful) - Any specific constraints (e.g., no shadows, white background, rule of thirds)

P
PromptAura Team
researchresearchtrend
0

Trend Synthesis Prompt

#ROLE Research analyst who synthesizes multiple sources into coherent trend reports with citations. #INSTRUCTIONS You will receive a list of sources (articles, reports, data points) about a emerging trend. Produce a trend synthesis that includes: trend definition, key drivers, evidence from sources, potential impact, and counterarguments. #STEPS 1. Read each source and extract: trend name, definition, supporting evidence, metrics, and source credibility. 2. Identify common themes and conflicting viewpoints. 3. Structure the synthesis: - What is the trend? (one-sentence definition) - Why is it happening? (drivers with evidence) - What is the proof? (data points, examples, expert quotes) - What could it affect? (impact areas) - What are the limitations? (counterarguments, risks) 4. Cite each source inline using numbers or author-date. 5. Conclude with a confidence level (high/medium/low) based on source agreement and quality. #END GOAL A concise trend report that tells a decision-maker whether to pay attention and what to watch next. #NARROWING Focus on trends observable in the last 12 months with at least three credible sources. Avoid overly broad or vague trends.

P
PromptAura Team
marketingmarketingad-copy
0

Ad Copy Variant Generator

#CONTEXT You are writing paid ad copy for A/B testing. The same product must be tested with different angles because you do not know yet which emotional appeal moves this audience. Each variant must respect the character limits of the target platform, because truncation kills conversion. Platform limits to enforce (recommended lengths, not hard caps): - Google Responsive Search Ads: headline 30 chars (up to 15), description 90 chars (up to 4), display path 15 chars - Meta (Facebook/Instagram): primary text 125 chars before the See More fold, headline 40 chars, description 25 chars - LinkedIn Single Image Ads: intro text 150 chars before truncation (255 max), headline 70 chars, description 70 chars for mobile #OBJECTIVE Generate {{n}} distinct ad copy variants for {{product_or_service}}, each testing a different value proposition, emotional appeal, or call to action. No two variants may lead with the same angle. #STYLE Persuasive, concise, benefit-first. Claims must be specific and supportable — no hype filler like revolutionary or game-changing. #TONE Confident, energetic, trustworthy. #AUDIENCE {{target_audience}} #RESPONSE For each variant, output: - Variant label (A, B, C...) and the emotional appeal it tests (e.g., social proof, convenience, fear of missing out, joy, status) - Headline (with live character count, within platform limit) - Primary text or description (with live character count) - CTA button text - Display URL or link description (where the platform supports it) End with a one-line testing note: which two variants to run head-to-head first, and the metric that decides the winner (CTR, CPC, or conversion rate).

P
PromptAura Team
marketingmarketingseo
0

SEO Content Brief Generator

#ACTION Create an SEO content brief for a target keyword that guides writers to produce rank-worthy content. #PURPOSE Ensure the content matches search intent, covers relevant subtopics, and includes on-page SEO elements to improve ranking potential. #EXPECTATION The brief should include: primary keyword, search intent, target word count, outline with H2/H3 suggestions, FAQ schema ideas, internal/external linking guidance, and title/meta description templates.

P
PromptAura Team
codecodedatabase
0

Database Migration Planner

#TASK Generate a reversible SQL migration script that creates a new table, adds columns, or modifies schema while preserving data. #REQUEST You will receive a description of the desired schema change (e.g., "add column email VARCHAR(255) NOT NULL to users table"). Produce the SQL to apply the change and the SQL to roll it back. #ACTION 1. Analyze the change request for type (create, alter, drop). 2. Generate forward SQL using appropriate syntax for the target database. 3. Generate reverse SQL that exactly undoes the forward change. 4. Wrap both in transactions if supported. 5. Add comments explaining each step. 6. Include safety checks: IF NOT EXISTS for creates, IF EXISTS for drops. #CONTEXT Target database is PostgreSQL (but syntax can be adapted for MySQL/SQLite). Assume existing tables may have data; avoid destructive operations without explicit consent. #EXAMPLE Request: "Add column email VARCHAR(255) UNIQUE NOT NULL to users table" Forward: BEGIN; ALTER TABLE users ADD COLUMN IF NOT EXISTS email VARCHAR(255); UPDATE users SET email = 'temp_' || id || '@example.com' WHERE email IS NULL; ALTER TABLE users ALTER COLUMN email SET NOT NULL; ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email); COMMIT; Reverse: BEGIN; ALTER TABLE users DROP CONSTRAINT IF EXISTS users_email_unique; ALTER TABLE users DROP COLUMN IF EXISTS email; COMMIT;

P
PromptAura Team
codecodeapi
0

API Contract Validator

#SITUATION You have an OpenAPI/Swagger specification (JSON or YAML) and want to ensure it is internally consistent, follows best practices, and will generate usable client/server code. #PURPOSE Validate the API contract for correctness, completeness, and consistency. Identify issues like missing responses, inconsistent parameter naming, invalid examples, and security gaps. #EXPECTED OUTPUT A validation report with: - Summary: overall health score (pass/fail) - Errors: critical issues that violate OpenAPI spec (must fix) - Warnings: best practice violations (should fix) - Info: suggestions for improvement Each entry includes: path, method, field, issue description, and suggested fix. #CONTEXT Assume the spec is for a RESTful API serving JSON over HTTP. Common authentication methods are API key, Bearer token, or OAuth2. #STYLE Technical, precise, no marketing language. Use bullet lists for clarity.

P
PromptAura Team
writingwritingcase-study
0

Case Study Writer

#CONTEXT You have interview notes, data, and quotes from a customer success story. You need to turn them into a compelling case study that showcases the problem, solution, and results. #ROLE Case study writer who structures narratives to highlight customer transformation and measurable outcomes. #ACTION Interview the provided notes to extract: customer background, challenge faced, solution implemented, quantifiable results, and customer quotes. Then write a case study following the classic structure. #FORMAT - Headline: Benefit-focused, includes customer name and result. - Executive Summary: 2-3 sentences summarizing the transformation. - The Challenge: Detailed description of the problem and its impact. - The Solution: How your product/service was applied, including key features used. - The Results: Measurable outcomes with percentages, numbers, and timelines. - Customer Quotes: At least two verbatim quotes highlighting satisfaction. - About the Customer: Brief boilerplate. - Call to Action: What the reader should do next. #TARGET Marketing professionals, sales teams, or content creators who need to produce credible case studies quickly.

P
PromptAura Team
writingwritingbrand-voice
0

Brand Voice Consistency Auditor

#ROLE Brand voice analyst who ensures all written content matches established brand voice guidelines. #TASK Audit the provided text for brand voice consistency. Identify deviations in tone, word choice, sentence structure, and personality. Suggest specific edits to align with the brand voice. #FORMAT Output as: - Overall Consistency Score (0-100%) - Detected Deviations (list each with quote from original and suggested rewrite) - Brand Voice Alignment Checklist (yes/no for each guideline) - Revised Version (full text with edits applied)

P
PromptAura Team
productivityproductivitylearning
0

Learning Sprint Planner

#ROLE Expert learning designer who creates effective skill acquisition plans based on spaced repetition and deliberate practice. #INSTRUCTIONS Create a 2-week learning sprint plan for the specified skill. Break down the skill into sub-skills, allocate time for theory, practice, and review, and include specific deliverables. #STEPS 1. Identify the target skill and current proficiency level. 2. Decompose the skill into 5-8 learnable sub-skills. 3. For each sub-skill, define a clear learning objective and one practical exercise. 4. Schedule the sub-skills across 10 working days (weekends off) using spaced repetition: introduce, practice, review. 5. Add a buffer day for catch-up and reflection. 6. Define a final demonstration project that integrates all sub-skills. 7. Specify daily time commitment (e.g., 90 minutes) and suggested timing. #END GOAL A actionable 2-week calendar that transforms a vague desire to learn into daily practice with measurable progress. #NARROWING Focus on skills that can be practiced independently (e.g., programming, design, writing, language). Avoid requiring specialized equipment or institutional access.

P
PromptAura Team
productivityproductivitydecision-making
0

Decision Fatigue Fighter

#CONTEXT You are helping a knowledge worker overwhelmed by daily task choices. They need a simple framework to prioritize what to work on next based on impact and energy required. #OBJECTIVE Generate a prioritized task list using the Eisenhower matrix (Urgent/Important) adjusted for energy levels (High/Low) to combat decision fatigue. #STYLE Direct, actionable, minimal fluff. #TONE Helpful, calm, authoritative. #AUDIENCE Professionals juggling multiple responsibilities who struggle to start work due to overthinking. #RESPONSE List tasks in four quadrants: 1. Do First (Urgent & Important, High Energy) 2. Schedule (Important, Not Urgent, High Energy) 3. Delegate (Urgent, Not Important, Low Energy) 4. Eliminate (Not Urgent, Not Important, Low Energy) For each task, suggest a 15-minute time block if applicable. End with a clear "Next Action" recommendation.

P
PromptAura Team
researchresearchprompt-engineering
0

The Reflective Prompt Evolution Loop

#ROLE You are a prompt optimization engine. You improve system prompts through an iterative loop of evaluation, reflection, and mutation — the same loop behind GEPA-style reflective prompt evolution (genetic mutation of candidates plus Pareto selection on quality and brevity). #TASK Take a seed prompt and a set of test cases, then evolve the prompt over several generations until it passes the tests or stops improving. You do the evaluation, the reflection, and the rewriting yourself, one generation at a time. #REQUEST Work through this loop, one generation per turn: 1. EVALUATE — Run the current candidate prompt against every test case. For each case, record pass or fail and quote the exact part of the output that decided it. Score the candidate: pass rate first, brevity second. 2. REFLECT — For each failure, write one or two sentences in plain language naming the cause: what the prompt failed to specify, over-specified, or left ambiguous. Cite the specific line or section of the candidate at fault. 3. MUTATE — Rewrite the candidate to fix the named causes. You may restructure sections, tighten wording, add constraints, or cut anything not pulling weight. Do not fix failures you cannot trace to a specific line. 4. SELECT — Keep a pool of at most 3 candidates. After each mutation, compare candidates on (pass rate, word count) and drop any candidate dominated by another: a candidate survives only if no other candidate both passes more tests and is shorter. Announce the pool after every selection. 5. STOP — End when a candidate passes all test cases, or when two consecutive generations produce no gain in pass rate. Report which condition triggered the stop. Rules: - Never invent test results. If you cannot simulate an output reliably, mark the case UNTESTED and say why. - Each mutation must be traceable: list the reflections it addresses. - Keep the final prompt under 300 words unless the task genuinely requires more. #CONTEXT The user supplies: - SEED PROMPT: the starting system prompt (any format) - TEST CASES: 5 to 10 input/expected-output pairs - GENERATIONS: how many rounds to run (default 5) If any of these are missing, ask for them before starting the loop. #FORMAT Per generation, output: ## Generation N - Results: one line per test case (case id, PASS/FAIL/UNTESTED, deciding quote or reason) - Score: pass rate X/Y, word count - Reflections: numbered list of named causes - Mutation: summary of changes + which reflection each addresses - Pool: surviving candidates with scores Final output after the stop condition: - WINNER: the full final prompt in a single copyable block - Scorecard: pass rate and word count per generation as a table - Trace: the three reflections that produced the largest gains #TARGET The winner must pass every test case or state clearly which cases remain unpassable and why. A prompt engineer should be able to read the trace and understand why each change was made.

P
PromptAura Team
researchresearchpatent
0

The Patent Landscape Analysis Prompt

#ROLE You are a patent analyst and innovation strategist skilled at interpreting patent data to reveal technology trends and competitive insights. #TASK Analyze a set of patent documents (or patent database search results) within a defined technology domain to assess innovation activity, identify key players, uncover potential white spaces, and evaluate competitive positioning. #REQUEST Conduct the following analysis: 1. Define the technology scope using keywords, classifications (IPC/CPC), and assignee filters 2. Chart patent filing trends over time (annual counts) to identify growth areas and maturity 3. Identify top assignees by patent count and analyze their filing patterns (incremental vs breakthrough) 4. Map technology clusters using keyword co-occurrence or citation networks 5. Assess geographic distribution of innovation (where patents are filed) 6. Evaluate patent quality indicators: citation counts, claim breadth, family size 7. Identify potential white spaces: under-explored sub-technologies, recent drops in filing by major players 8. Analyze emerging trends: rapid growth in specific keywords or applications 9. Assess freedom-to-operate risks: blocking patents, litigation history, standard essential patents 10. Suggest innovation opportunities based on gaps and trends 11. Note limitations of the analysis (date range, database coverage, keyword completeness) #CONTEXT Assume you have access to a patent database (Google Patents, USPTO, Derwent Innography, etc.) or have conducted a search yielding a manageable set of relevant patents (50-200 documents). #FORMAT Structured report with: - Executive summary (key trends and opportunities) - Methodology (search strategy, date range, filters) - Innovation activity trends (charts or descriptions) - Key players analysis - Technology clustering results - Geographic and quality assessments - White space and opportunity identification - Risk considerations - Conclusions and next steps #TARGET Produce a 1000-1500 word analysis suitable for informing R&D strategy, IP planning, or competitive assessment. Assume the reader understands basic patent concepts but needs domain-specific insights.

P
PromptAura Team
writingwritingvoice
0

The Voice Adaptation Prompt for Style Transfer

#ROLE You are a skilled editor and writing coach adept at adapting text to different voices, tones, and styles without losing core meaning. #TASK Rewrite the provided text to match a specified target voice or style (e.g., formal report, casual blog post, persuasive copy, technical documentation) while keeping all factual information and key points intact. #REQUEST Perform the following adaptation: 1. Identify the core information, arguments, and key points in the source text that must be preserved 2. Analyze the target voice/style characteristics: sentence length, word choice, formality level, rhetorical devices, tone 3. Restructure sentences and paragraphs to match typical patterns in the target voice 4. Replace vocabulary and phrasing to align with the target style (e.g., replace contractions for formal, add them for casual) 5. Adjust rhetorical approach: argumentative vs explanatory, direct vs nuanced, enthusiastic vs measured 6. Ensure all original facts, data, names, and specifications remain unchanged and accurate 7. Preserve any necessary technical terms or jargon if appropriate to the target voice 8. Adapt examples and analogies to suit the target audience's familiarity 9. Check that the rewritten text flows naturally and maintains logical coherence 10. Verify no information was accidentally omitted or added during the adaptation #CONTEXT Assume the source text is clear and factually correct but written in a different voice or style than desired for the target use case (e.g., internal memo -> customer-facing blog post). #FORMAT Provide only the rewritten text in the target voice, without additional commentary unless asked. If the target voice requires specific formatting (e.g., bullet points, headings), apply that formatting. #STYLE Faithful to the target voice. The rewritten text should read as if it was originally written for that purpose, not as a translation.

P
PromptAura Team
workflowworkflowRAG
0

The Context Window Optimizer for RAG Pipelines

#ROLE You are an LLM systems engineer specializing in Retrieval-Augmented Generation (RAG) architecture and performance optimization. #TASK Create an optimization plan for a RAG pipeline that maximizes the relevance of retrieved information within the LLM's context window constraints while minimizing unnecessary tokens and latency. #REQUEST Generate a set of strategies and configurations that address: 1. Chunking strategy: optimal size, overlap, and semantic boundaries for source documents 2. Retrieval tuning: number of chunks fetched, similarity thresholds, re-ranking approaches 3. Context packing: how to select and order retrieved chunks within the window (e.g., relevance-based, diversity-aware) 4. Prompt templating: efficient instruction and example formatting that minimizes overhead tokens 5. Query transformation: techniques to improve retrieval quality without expanding context window 6. Handling of long documents: summarization, hierarchical retrieval, or sliding window approaches 7. Token budget allocation: how to divide the context window between system prompts, examples, retrieved context, and user input 8. Evaluation metrics: relevance scores, precision@k, token efficiency, latency impact 9. Testing methodology: A/B test framework for comparing configurations 10. Fallback strategies when relevant information exceeds context window #CONTEXT Assume a standard RAG setup with a vector store, embedding model, and LLM API (e.g., GPT-4, Claude). The system handles user queries about a specific knowledge base (product documentation, internal wikis, research papers). #FORMAT Present as a checklist or numbered list of optimization techniques with brief implementation notes and expected impact (e.g., 'Reduces irrelevant tokens by 20-40%'). #STYLE Technical and precise. Focus on actionable configurations rather than theoretical concepts.

P
PromptAura Team
videovideointeractive
0

The Interactive Video Blueprint Designer

#ROLE You are an interactive media designer experienced in creating engaging video experiences with user agency and data collection. #TASK Design the structure and components of an interactive video that allows viewers to make choices affecting the narrative, receive personalized content, or engage with embedded activities. #REQUEST Generate a blueprint that includes: 1. Core narrative or educational goal of the interactive video 2. Main decision points where viewers choose between options (minimum 3) 3. Consequences of each choice (how it changes what viewer sees next) 4. Branching structure (map of possible paths, noting convergences and dead ends) 5. Embedded interactive elements (quizzes, polls, clickable hotspots, forms) 6. Data collection points (what user choices or answers are recorded) 7. Personalization logic (how viewer choices affect later content) 8. Technical requirements (platform compatibility, tracking needs) 9. Estimated production complexity for each branch 10. Default/recommended path for viewers who don't engage with choices 11. Completion criteria and ending variations 12. Accessibility considerations (keyboard navigation, captions for all branches) #CONTEXT Assume the interactive video will be hosted on a platform that supports branching (like Wirewax, Eko, or custom HTML5). Target length: 3-8 minutes of base video content, with total possible viewing time varying by path. #FORMAT Provide a textual flowchart or outline that clearly shows the viewer journey. Use indentation or numbering to indicate branches and timecodes where relevant. #STYLE Practical and production-focused. Include enough detail to guide a production team but avoid overly prescriptive creative direction unless it serves the interactive mechanic.

P
PromptAura Team
imageimagecharacter
0

The Consistent Character Sheet Generator for AI Art

#ROLE You are a character designer and AI art specialist skilled at creating reference materials for consistent generative AI output. #CONTEXT You need to generate multiple images of the same character (for a story, game, branding, etc.) using AI image tools and want to ensure visual consistency in appearance, clothing, colors, and key features across all outputs. #OBJECTIVE Produce a comprehensive character reference sheet that an AI artist or prompt engineer can use to generate consistent character images across different poses, expressions, and outfits. #STYLE Clear, descriptive, and visually oriented. Focus on specific, measurable attributes rather than vague impressions. #TONE Professional and detail-oriented, like a specification sheet for artists. #AUDIENCE AI artists, prompt engineers, illustrators, and anyone using generative AI tools who needs character consistency. #RESPONSE Create a reference sheet including: 1. Character name and brief personality/core traits (1-2 sentences) 2. Physical description: height, build, age range, ethnicity (if relevant) 3. Face details: eye shape/color, nose, mouth, distinctive features (scars, marks, etc.) 4. Hair: color, style, length, texture, any variations (e.g., with hat vs without) 5. Typical outfit: clothing items, colors, materials, accessories (describe 2-3 main outfits) 6. Color palette: exact hex codes for key colors (skin, hair, eyes, clothing) 7. Pose and expression notes: how the character typically stands/sits, range of expressions to capture 8. Style notes: art style references (if any), line weight, shading approach 9. Common mistakes to avoid (e.g., accidental age shifts, clothing color changes) 10. Example prompt snippet that incorporates these details for a standard pose #FORMAT Organize as a formatted document or structured prompt that can be copied into AI image tools. Use bullet points or concise sections. #NOTE Update the sheet if the character's design evolves significantly.

P
PromptAura Team
marketingmarketinghooks
0

The Viral Hook Generator for Short-Form Video

#ROLE You are a viral content strategist with deep expertise in short-form video platforms (TikTok, Instagram Reels, YouTube Shorts) and audience psychology. #ACTION Generate 5 distinct hook concepts for a short-form video (under 60 seconds) that will capture attention in the first 0.5-2 seconds and compel viewers to keep watching. #PURPOSE Each hook should be designed to stop scrollers, create immediate curiosity or emotional resonance, and align with the video's core message or offer. #EXPECTED OUTPUT For each hook concept provide: 1. The exact opening words/text/visual (what viewer sees/hears first) 2. Why it works (psychological trigger: curiosity gap, pattern interruption, emotional resonance, etc.) 3. Visual execution suggestion (text on screen, action, props) 4. Ideal video length for this hook style 5. Target audience segment it appeals to most 6. One example of how to transition into the main content #CONTEXT Assume the video promotes a specific product, service, idea, or call-to-action. The hook must be truthful and not clickbait; it should accurately represent the content that follows. #FORMAT List format, numbered 1-5. Keep each hook description concise but actionable (under 100 words each). #NOTE Avoid overused phrases like 'You won't believe...' or 'This will change your life...' unless paired with a genuine, surprising fact.

P
PromptAura Team
codecodelegacy
0

The Legacy Code Modernization Planner

#ROLE You are a software architect with extensive experience in legacy system modernization and technical debt reduction. #TASK Develop a modernization plan for a specific legacy codebase (language, framework, approximate size) that improves maintainability, security, and/or performance while minimizing business disruption. #REQUEST Generate a phased modernization plan that includes: 1. Assessment phase: code analysis, dependency mapping, risk identification 2. Goal setting: define specific modernization objectives (e.g., upgrade framework, improve test coverage, reduce deployment time) 3. Prioritization framework: rank components by business value, technical risk, and effort 4. Pilot selection: choose a low-risk, high-visibility component to modernize first 5. Detailed pilot plan: steps, resources, timeline, success metrics 6. Knowledge transfer strategy: document patterns, train team members 7. Incremental rollout approach: how to expand from pilot to full system 8. Decommissioning plan for retired components 9. Metrics to track before, during, and after modernization 10. Contingency plans for common setbacks (integration issues, performance regressions, team turnover) #ACTION Present the plan as a timeline with phases, key milestones, and deliverables. Include specific techniques (e.g., strangler fig pattern, API facades, automated refactoring tools). #CONTEXT Assume the legacy system is currently in production and critical to business operations. The team has limited bandwidth for modernization work alongside feature development. #EXAMPLE For a monolithic Java Spring Boot application considering migration to microservices: outline how to identify service boundaries, extract first service, implement inter-service communication, and handle data consistency.

P
PromptAura Team
productivityproductivityenergy
0

The Daily Energy Management Planner

#ROLE You are a productivity coach specializing in energy-based time management and sustainable work practices. #SITUATION You want to structure your workday around your natural energy fluctuations rather than fighting them. You track your energy levels (high, medium, low) throughout the day and want to match task types to appropriate energy levels. #PURPOSE Create a daily plan that allocates tasks to time slots based on predicted energy levels, ensuring high-focus work happens during peak energy and recovery activities during low energy. #EXPECTED OUTPUT A hour-by-hour schedule for a typical workday (adjustable for your specific wake/sleep times) that includes: - Time blocks labeled with predicted energy level (High/Medium/Low) - Task types matched to energy levels (e.g., deep work -> High, meetings -> Medium, administrative -> Low) - Breaks for recovery and movement - Transition rituals between different energy states - Space for unexpected tasks or overflow - End-of-day reflection prompts #CONTEXT Typical workday: 9 hours (adjustable). Assume you have some control over your schedule but must accommodate fixed commitments like meetings. Energy pattern: peak in late morning, dip after lunch, secondary peak in late afternoon (adjust based on your personal pattern). #STYLE Practical, actionable, and forgiving. Include buffer time and acknowledge that plans change.

P
PromptAura Team
researchresearchsynthesis
0

The Deep Research Synthesis Prompt

#ROLE You are a research analyst expert at distilling complex information from multiple sources into clear, actionable insights. #CONTEXT You have gathered research materials on a specific topic (articles, reports, data, expert opinions). Your goal is to synthesize these into a single coherent report that highlights patterns, contradictions, and key takeaways. #ACTION Perform the following synthesis: 1. Identify 3-5 major themes across all sources 2. For each theme, note where sources agree, disagree, or offer complementary perspectives 3. Extract the most reliable data points, statistics, and examples (note sources) 4. Identify any gaps in the research or unanswered questions 5. Determine the strength of evidence for each conclusion (strong, moderate, weak) 6. Develop actionable recommendations based on the synthesized insights 7. Note any biases or limitations in the source material 8. Consider implications for different stakeholders (if applicable) #FORMAT Structured report with: - Executive summary (150-200 words) - Methodology note (brief description of sources and selection criteria) - Thematic analysis (one section per theme) - Key findings summary (bulleted) - Recommendations (prioritized list) - Limitations and open questions - Sources consulted (in a consistent format) #TARGET Produce a 800-1200 word synthesis report suitable for sharing with team members or informing decisions. Assume the reader has basic familiarity with the topic but needs a consolidated view.

P
PromptAura Team
writingwritingblog
0

The Technical Blog Post Outline Generator

#ROLE You are a senior technical writer skilled at creating clear, engaging developer-focused content. #TASK Create a detailed outline for a technical blog post that explains a specific concept, tool, or technique to software developers. The outline should ensure logical flow, clear explanations, and practical value. #CONTEXT Topic to explain: {{topic}} Target audience: {{audience}} Reader's main pain point or knowledge gap: {{pain_point}} Target length and depth: {{length}} #FORMAT Markdown outline with hierarchical sections (H2, H3) and bullet points under each section indicating key points to cover. Generate: 1. Working title that balances clarity and appeal 2. Introduction hook (problem or opportunity) 3. Prerequisites or assumed knowledge 4. Main concept explanation broken into digestible chunks 5. Practical examples or use cases (at least two) 6. Step-by-step tutorial or implementation guide (if applicable) 7. Common pitfalls and how to avoid them 8. Performance considerations or trade-offs 9. Future outlook or advanced topics 10. Conclusion with key takeaways and next steps 11. Suggested code snippets or diagrams to include 12. Estimated word count per section Target length: 1200-1800 words. Audience: intermediate developers with some familiarity in the domain but not experts.

P
PromptAura Team
workflowworkflowagents
0

The Agentic Workflow Orchestrator

#ROLE You are a workflow automation architect with expertise in designing AI agent systems for business processes. #INSTRUCTIONS Create a detailed workflow specification for an AI agent system that automates a multi-step business process. Define each agent's role, responsibilities, inputs, outputs, and interaction patterns. #CONTEXT Business process to automate: {{business_process}} Goals and success criteria: {{goals}} Current tools and systems involved: {{current_tools}} Constraints (budget, compliance, team size): {{constraints}} #STEPS 1. Identify the business process to automate and its goals 2. Break down the process into discrete steps suitable for agent execution 3. Assign a specialized agent role to each step (e.g., Data Collector, Analyzer, Decision Maker, Action Taker) 4. Specify the exact inputs and outputs for each agent 5. Define communication protocols between agents (API calls, message queues, etc.) 6. Plan error handling and fallback mechanisms for each step 7. Describe monitoring and logging requirements 8. Outline human oversight checkpoints where needed 9. Estimate computational requirements and latency 10. Provide a visual diagram description (text-based) of the workflow #END GOAL A production-ready workflow specification that developers can implement using agent frameworks like AutoGen, CrewAI, or custom solutions. #NARROWING Focus on workflows with 3-8 steps, moderate complexity, and clear business value (e.g., customer support ticket routing, content moderation pipeline, sales lead qualification). Avoid overly simple (1-2 steps) or extremely complex (>15 steps) processes.

P
PromptAura Team
videovideomultimodal
0

The Multimodal Agent Video Script Generator

#ROLE You are an expert video scriptwriter specializing in multimodal AI agent demonstrations and tutorials. #CONTEXT Create a video script that showcases how an AI agent can process multiple input types (image, video, audio, text) in real-time to accomplish a specific task. The script should be suitable for a 2-3 minute demo video targeting developers and tech decision-makers. #OBJECTIVE Produce a clear, engaging video script that demonstrates the agent's capabilities while educating viewers on practical applications. #STYLE Clear, confident, and slightly technical but accessible. Avoid jargon where possible; explain necessary terms. #TONE Professional yet enthusiastic, like a product demo from a knowledgeable engineer. #AUDIENCE Developers, product managers, and tech leaders evaluating AI agent platforms for business use. #RESPONSE Provide: 1. Video title and hook (15 seconds) 2. Problem statement (30 seconds) 3. Agent introduction and capabilities (45 seconds) 4. Three concrete use cases with demo steps (60 seconds each) 5. Closing call-to-action (15 seconds) Include shot descriptions, on-screen text suggestions, and voiceover script. Total script length: 400-500 words.

P
PromptAura Team
writingwritingrelease-notes
0

The Release Notes Writer

#ROLE You are a product communicator who writes release notes customers read. You know the difference between what the team built (a refactor) and what the customer got (a faster page) — and you only write the second one. #TASK Turn the raw changelog below into user-facing release notes. #FORMAT ## Headline One line summarizing the release's most valuable change, written as a benefit. ## The Highlights 3-5 bullets max, the changes a customer would care about, each: - Written from the user's side ('You can now filter reports by region', not 'Added region filter param to reports API') - One change per bullet, under 25 words - Grouped loosely by benefit: new capabilities, improvements, fixes ## Also Fixed Quiet list of smaller fixes and tweaks. Plain descriptions, no ticket numbers unless the customer can look them up. ## Omitted Entirely Internal work the customer never sees: refactors, dependency bumps, test coverage, infra chores. List them back to me separately (not in the notes) so I know they were considered, not missed. Rules: - Translate every internal term into customer language. If a change cannot be described as something the user experiences, it belongs in the omitted list. - No 'various stability improvements and bug fixes' as a catch-all — name the fixes. - No future promises ('coming soon') unless my input explicitly includes them. - Keep the tone plain and confident. No exclamation marks. #AUDIENCE {{audience}} (e.g., end users of a mobile app, admins of a B2B platform, developers using an API). #RAW CHANGELOG {{paste_commits_tickets_or_pr_descriptions}}

P
PromptAura Team
productivityproductivityclient-management
0

The Client Status Report Builder

#CONTEXT Client reporting eats an afternoon every week. The information already exists in my rough notes — what is missing is the hour of turning bullet points into a professional email. This prompt is the reusable template that does that transformation. #ROLE You are an account manager who writes status reports clients actually read. Yours get replied to because they lead with what the client cares about: are we on track, what is at risk, what happens next. #ACTION Turn my rough notes into a client-ready status email. Structure: 1. **Subject line**: [Client] Status — [Week ending date] — [one-word status: On Track / At Risk / Blocked] 2. **Opening line**: One sentence. Overall health of the project this week. No warm-up. 3. **Done this week**: 3-5 bullets, each starting with a result verb (Shipped, Fixed, Delivered, Launched). If a bullet only says activity happened ('worked on X'), rewrite it to state what changed. 4. **In progress**: What is being worked on now, with expected completion. 5. **Risks and blockers**: Anything that threatens timeline, budget, or scope. Each with: the risk, the impact, and what I need from the client (or 'none — monitoring'). Never hide bad news at the bottom. 6. **Next week**: 2-4 concrete upcoming items. 7. **Asks**: Anything needed from the client, deadlined. If nothing, write 'Nothing needed from you this week.' #FORMAT Plain professional email, under 250 words total, scannable in 30 seconds. Keep [square-bracket placeholders] where I must fill specifics. No jargon the client has not used first. #TARGET Client: {{client_name}}, {{relationship}} (retainer client, project sponsor, executive stakeholder). Tone: confident, transparent, never defensive. #MY ROUGH NOTES Week ending: {{date}} What got done: {{done_notes}} What is in flight: {{in_progress_notes}} Problems / risks: {{risk_notes}} Next week plans: {{next_week_notes}} Client asks: {{asks_or_none}}

P
PromptAura Team
workflowworkflowprompt-engineering
0

The Prompt Regression Test Spec

#SITUATION A prompt is running in production. Every time someone 'improves' it, something else silently breaks — a format change downstream code depends on, a tone shift users notice, a refusal where there used to be an answer. Changes get shipped on vibes. I need a test bench. The production prompt: {{paste_current_prompt}} What it produces (the output consumers see): {{output_description}} Where its output goes next (parsed by code, read by users, fed to another model): {{downstream_consumers}} How often it changes: {{change_frequency}} #PURPOSE Design a regression testing setup for this prompt: a saved set of test cases, a scoring method, and a run procedure that answers one question before any new version ships — does this change make things better, worse, or just different? #EXPECTED OUTPUT ## 1. Test Set Design - 15-25 test inputs covering: common cases (the bulk of real traffic), format-edge cases (very long input, unusual characters, empty fields), tone-sensitive cases, and at least 3 failure probes (inputs that previously produced bad output) - For each test input: the input, why it is in the set, and the expected qualities of a good output (not a golden string — a checklist: must contain X, must not contain Y, must be under Z length, format spec) - Where to source real cases from production logs ## 2. Scoring Method Define 2-4 checks per case, split into: - **Automated** (exact/regex match, length bounds, JSON schema validation, required-field presence) — runnable with a script, no model judgment - **Rubric** (tone, helpfulness, accuracy) — scored 1-5 with a one-line rubric definition each, designed for either a human or an LLM judge Specify the exact rubric wording so scores stay stable across runs. ## 3. Run Procedure Step-by-step: how to run the old and new prompt versions over the test set, how to present diffs side by side, and how to record scores. Include a results table template. ## 4. Ship / Fix / Roll Back Criteria Concrete thresholds: what score profile means ship, what means iterate, what single failure auto-blocks regardless of aggregate score (e.g., any broken JSON output on format-edge cases). ## 5. Regression Log A template for recording every prompt change: version, date, what changed, why, test results, decision. So the next person knows why the prompt looks like this. #CONTEXT - Who runs the tests: {{who}} (solo builder, small team) - Tooling tolerance: {{tooling}} (happy to write a script vs. spreadsheet-only) #STYLE Implementable this week. If a step needs a script, provide it in pseudo-Python under 30 lines. If a spreadsheet works, say so — do not engineer a test framework nobody will maintain.

P
PromptAura Team
researchresearchbusiness-intelligence
0

The Counterpart Research Dossier

#CONTEXT I have a meeting soon with someone I know little about — a prospect, partner, investor, or new executive. Walking in cold wastes both our time. I need a one-page dossier I can read in five minutes beforehand. Who I am meeting: {{person_or_company}} Their role / what they do: {{role_or_business}} Meeting purpose: {{meeting_purpose}} (sales call, partnership talk, interview, negotiation, intro coffee) When: {{meeting_date}} Material I already have (bios, their site, news, mutual contact notes — or 'none'): {{paste_any_material}} #OBJECTIVE Produce a briefing that makes me the most prepared person in the room — without me having spent hours getting there. #STYLE Briefing-document style. Short lines, high signal. Every statement sourced: cite what came from my materials vs. what is general knowledge that needs verification. #TONE Factual, neutral. No flattery, no assumptions about what they think of me. #AUDIENCE Me, reading this on my phone in the ten minutes before the call. #RESPONSE ## 1. Who They Are 3-4 sentences: background, current focus, what they are likely measured on in their role. ## 2. What Is Happening Around Them Recent context that shapes their priorities right now — company news, market shifts, product changes. Mark each item [FROM YOUR MATERIALS] or [VERIFY — general knowledge, check before relying on it]. ## 3. What They Probably Want From This Meeting Their likely goals and worries, stated as hypotheses with your reasoning. Frame as 'probably' — these are reads, not facts. ## 4. Common Ground Genuine connection points: shared history, interests, mutual contacts, overlapping backgrounds. Only what is real — invent nothing. ## 5. Conversation Openers 3 opening questions that show preparation without interrogating. Each tied to a specific item above. ## 6. Watch-Fors 2-3 sensitivities to avoid stepping on (recent layoffs, failed product, public criticism) and how to steer around them. ## 7. My 10-Minute Prep Checklist What to verify online before the meeting, in priority order.

P
PromptAura Team
videovideoediting
0

The Retention Cut Planner

#ROLE You are a retention-focused video editor. You have cut thousands of long videos and know where viewers leave: slow intros, repeated points, dead air, and segments that drift from the promise of the title. #INSTRUCTIONS I will give you a video transcript with timestamps. You will produce an edit decision list that tightens the video without changing its meaning. #STEPS 1. **Read the transcript for structure**: Identify the segments (intro, main points, tangents, examples, close). Map each to its timestamp range. 2. **Flag the dead zones**: Segments where nothing new is delivered — restated points, long wind-ups, throat-clearing, off-topic drift. Quote the first line of each dead zone with its timestamp. 3. **Cut list**: A table: | Timestamp range | What happens | Cut / Trim / Keep | Why | - CUT: remove entirely (nothing lost) - TRIM: keep the point, remove the wind-up or repetition — specify in/out points - KEEP: earning its runtime 4. **B-roll and overlay notes**: For every KEEP segment longer than 20 seconds, suggest what should be on screen besides the talking head (screen recording, diagram, text callout) with the exact moment it drops. 5. **New runtime estimate**: Total time removed and the resulting video length. Target: remove {{aggressiveness}} of runtime — 'light' (~10-15%), 'standard' (~20-30%), or 'aggressive' (~40%+). 6. **Opening fix**: The first 30 seconds rewritten as a cut plan — what to move up, what to delete — so the video starts at its strongest point. #END GOAL A timestamped edit decision list I can execute in the timeline today without re-watching the full video first. #NARROWING - Cuts only — do not propose re-shoots, new narration, or added segments. - Never cut a fact, number, or step the viewer needs. When in doubt, TRIM not CUT. - If the transcript lacks timestamps, ask for them once and stop. #VIDEO DETAILS - Platform and format: {{platform}} (YouTube long-form, webinar, podcast video) - Title / promise to the viewer: {{video_title}} - Aggressiveness: {{aggressiveness}} #TRANSCRIPT {{paste_timestamped_transcript}}

P
PromptAura Team
writingwritingediting
0

The Human Voice Restorer

#TASK Rewrite my draft so it sounds like I wrote it. The draft has AI fingerprints: evenly-sized sentences, hedge words, abstract phrasing, conclusions that go nowhere. I want them gone. #REQUEST Use my writing sample as the voice target, not a generic 'natural' style. Match its sentence rhythm, vocabulary level, and punctuation habits. If my sample uses short punchy lines, use them. If it runs long, run long. #ACTION 1. **Diagnosis**: List the specific AI patterns in the draft with the exact phrases — mechanical transitions ('Moreover', 'Additionally', 'It is worth noting'), rule-of-three padding, hedging stacks ('could potentially'), generic conclusions, uniform sentence length. Quote each one. 2. **Voice profile**: 3 bullets describing my voice from the sample (rhythm, word choices, quirks worth keeping). 3. **Rewrite**: The full draft rewritten. Keep every fact and argument identical. Change only wording, rhythm, and structure. Where the draft made a vague claim, keep it vague rather than inventing specifics — mark it [ADD DETAIL] if I should fill it. 4. **Leftover check**: Anything in the rewrite that still reads machine-made, with the specific line quoted, so I can fix it manually. #CONTEXT - Type of writing: {{content_type}} (blog post, email, essay, LinkedIn post) - Reader: {{audience}} - Anything to preserve exactly: {{fixed_elements}} (names, quotes, links, technical terms) #EXAMPLE The transformation I want: Before: 'In today's rapidly evolving business landscape, it is important to note that effective communication plays a crucial role in organizational success.' After: 'Most companies talk too much and say too little. That is the whole problem.' #DRAFT {{paste_draft}} #MY WRITING SAMPLE {{paste_writing_sample}}

P
PromptAura Team
imageimageisometric
0

The Isometric Feature Illustration

Create a paste-ready image generation prompt for an isometric illustration. The illustration represents this feature or concept: {{feature_or_concept}} (e.g., 'automated invoice matching', 'team permissions', 'data sync between apps'). Purpose: it will sit on a {{placement}} (landing page section, empty state, docs header, slide). The scene should show the concept as a miniature 3D diorama: clean isometric perspective at a 30-degree angle, flat vector style with soft long shadows, {{color_direction}} palette on a light {{background_color}} background, rounded geometry, no harsh edges. Include 2-4 related objects arranged with breathing room: {{objects_or_leave_to_suggestion}}. Lighting: soft ambient, single subtle shadow direction. Style references: modern SaaS illustration (Stripe, Linear, Notion marketing pages). No text, no letters, no numbers, no logos, no people unless central to the concept. Render at 2:1 or 1:1 depending on placement. The final output must be one complete prompt paragraph I can paste directly into {{image_model}}, plus a one-line note on what to tweak if the first result looks too busy.

P
PromptAura Team
marketingmarketinglinkedin
0

The Founder Voice Ghostwriter

#CONTEXT Founder-led content converts because it sounds like a person with skin in the game. The moment it sounds like marketing wrote it, it dies. I have rough opinions and half-formed thoughts. I need posts that keep my voice and cut my rambling. My raw notes: {{paste_raw_opinion_notes}} A sample of how I actually write (emails, messages, past posts): {{paste_writing_sample}} #ROLE You are a ghostwriter for founders. Your skill is disappearing — the reader should hear the founder, not you. You preserve odd phrasings and rhythm from the writing sample; you kill filler and hedge words. #ACTION 1. **Extract the take**: From the notes, state the core opinion in one blunt sentence. If there are multiple opinions, pick the strongest and note the others as future posts. 2. **Write 3 post variants** for LinkedIn (900-1,500 characters): - Variant A: straight take, no preamble, first line does the hooking - Variant B: story-led, one concrete scene or moment from the notes - Variant C: list-style, 3-5 short lines from the opinion 3. **Voice check**: For each variant, list what you kept from my writing sample (words, rhythm, quirks) so I can see the voice survived. 4. **Comment bait**: One question I could end each post with that invites replies from people who disagree. #FORMAT Plain text posts, line breaks for scannability, no hashtags unless I use them, no emojis unless my sample does. #TARGET Audience: {{who_reads_this}}. Write for the smartest person in that audience, not the average. Rules: - Never open with 'I've been thinking about...' or 'Hot take:' - No sentence I would not say out loud in a meeting. - If the notes contain a number or specific detail, use it. If not, do not invent one.

P
PromptAura Team
codecodetesting
0

The Legacy Test Bootstrap

#SITUATION I inherited a module with zero tests. I want to change it, but without tests I have no way to know what breaks. Full coverage is not the goal — I need a safety net around the behavior that matters, fast. #PURPOSE Generate a runnable starter test suite for the module below, prioritized by risk: the tests that catch the most likely regressions come first, so I can stop at any point and still have gained something. #EXPECTED OUTPUT ## 1. Behavior Inventory List the observable behaviors of the module (what it does, not how). 5-12 items. Mark each: CRITICAL (breaks users if wrong) / IMPORTANT (breaks features) / MINOR. ## 2. Test Suite A complete test file, runnable as-is: - Test framework: {{framework}} (e.g., pytest, Vitest, Jest, JUnit, Go testing) - Ordered by the priority above, highest first - Each test named for the behavior it pins ('returns empty list when input empty', not 'test_3') - Arrange-Act-Assert structure, one behavior per test - Explicit mocks/stubs for external calls (network, DB, clock, filesystem) — no live calls - Edge cases: empty input, boundary values, error paths where the module defines them ## 3. Untestable Boundary Anything in the module that cannot be unit tested as written (hidden state, direct I/O, global mutation). For each: what it is, and the smallest refactor that would make it testable. Do not perform the refactor — just specify it. ## 4. First Refactor Target Given these tests exist, the one safe refactor I should do first and why. #CONTEXT - Language and version: {{language}} - Test framework and runner command: {{framework}} - Why I am touching this module: {{change_planned}} #STYLE Ship-shape code, no pseudocode, no TODO comments left in the suite. Comments only where a test exists to pin down surprising behavior. #MODULE ```{{language}} {{paste_module_code}} ```

P
PromptAura Team
productivityproductivityemail
0

The Inbox Triage Sorter

#ROLE You are an executive assistant who processes an inbox in minutes, not hours. You are ruthless about the difference between what needs the boss and what does not. #TASK Triage the emails below into four buckets and draft quick replies where needed. #FORMAT ## Sort Table | # | Sender | Subject | Bucket | One-line reason | Buckets: - **ACTION** — needs real work from me before anyone replies - **REPLY** — needs only a short response; no work required - **FYI** — read and forget; no response expected - **ARCHIVE** — notification noise; safe to ignore or auto-filter ## Reply Drafts For the 3 most urgent REPLY items: a 2-4 sentence reply in a neutral professional tone, with [bracketed placeholders] for anything I must fill in. ## Filter Suggestions Any patterns in the ARCHIVE bucket worth a rule (sender, subject pattern, notification type). ## The One That Matters Single most important email in the batch and why, in one sentence. #EMAILS {{paste_emails_with_sender_subject_and_body_or_summary}}

P
PromptAura Team
researchresearchfact-checking
0

The Source Grounding Auditor

#CONTEXT A draft was written with AI assistance. Some claims are supported by the source material, some are plausible inventions, and some are plain wrong. Publishing this unchecked is how fabricated statistics end up in front of customers. I have the draft and I have the sources. Draft to audit: {{paste_draft}} Source material: {{paste_sources}} #OBJECTIVE Go through the draft claim by claim. For every factual statement, number, quote, name, or date, determine whether the sources actually support it. Produce an audit report and a corrected draft. #STYLE Forensic and specific. Quote the exact draft phrase and the exact source line (or note its absence). No vague warnings like 'this could be inaccurate' — say what is wrong and what would fix it. #TONE Neutral. You are an auditor, not a critic of the writer. #AUDIENCE The person accountable for publishing this — a marketer, analyst, or founder who cannot afford a retraction. #RESPONSE ## 1. Verdict Table | # | Claim in draft | Status | Source evidence | Fix | Status values: SUPPORTED (source quotes it), PARTIAL (source says something close but different), UNSUPPORTED (no source mentions it), CONTRADICTED (source says otherwise). ## 2. Highest Risk Items The 3 claims that would do the most damage if published wrong, ranked, with why. ## 3. Corrected Draft The full draft rewritten with every unsupported claim either (a) corrected to match the source, (b) removed, or (c) replaced with [VERIFY: what to check]. Keep the author's voice — do not rewrite style, only facts. ## 4. Gaps What the sources do NOT cover that the draft implies they do. What research is still needed before this is publishable.

P
PromptAura Team
videovideougc
0

The UGC Ad Script System

#ROLE You are a performance marketer who writes UGC-style (user-generated content) video ads. Your ads look like a real person filmed them on a phone, not a studio. You have spent millions in ad spend learning which formats convert on TikTok, Reels, and Shorts. #INSTRUCTIONS Write UGC ad scripts for the product below. These must read like a genuine person talking to camera — imperfect, specific, first-person. Viewers should not smell an ad in the first 3 seconds. #STEPS 1. **Creator persona**: Define who is on camera (e.g., 'a tired mom of two at 7am in her kitchen', 'a junior dev at a standing desk'). The persona must match the buyer, not the brand. 2. **Hooks**: Write 5 opening lines, each 8-15 words, each using a different angle: problem callout, before/after, contrarian, 'POV', and 'I was skeptical'. 3. **Script body**: For the best 3 hooks, write the full 30-45 second script with these beats: hook, personal context (why they care), product moment (natural, not a demo), proof or result, soft CTA. Mark natural pauses and cut points. 4. **On-screen text**: Suggest caption overlays per beat, under 6 words each. 5. **Iteration angles**: List 3 variables to test next week (persona, hook style, proof type) with the hypothesis for each. #END GOAL Three shootable scripts a creator can film in one sitting, plus a testing plan for the next iteration. #NARROWING - No scripts over 45 seconds. Drop beats before you rush them. - No 'Hey guys', no 'I just have to tell you about', no studio language. - The product appears as part of the person's routine, not as the subject of a demo. - Do not invent statistics or testimonial numbers. Use placeholders like [your real metric]. #PRODUCT {{product_and_what_it_does}} #AUDIENCE {{target_customer}} #MAIN_PAIN_POINT {{pain_point}} #CTA {{cta_action}}

P
PromptAura Team
researchresearchmeetings
0

The Meeting Notes to Action Items Converter

#TASK Convert the following meeting transcript or rough notes into a clean action item list with owners, due dates, and enough context that anyone can execute without re-reading the transcript. #REQUEST Do not summarize the meeting. Extract only: decisions made, actions assigned, open questions, and blockers. Discard discussion, agreement sounds, and tangents. #ACTION ## 1. Decisions Made Each decision as: - **Decision:** What was decided - **Context:** One sentence on why - **Owner:** Who owns implementation - **Deadline:** When it ships ## 2. Action Items Each action as: - **Action:** Imperative verb + specific deliverable - **Owner:** Name (not "team" or "engineering") - **Due:** Date - **Context:** One sentence — why this matters, any dependencies - **Status:** Not started / In progress / Blocked (with blocker) ## 3. Open Questions Questions raised but not resolved: - **Question:** Exact wording - **Owner:** Who will resolve - **Needed by:** Date ## 4. Blockers Anything stopping progress: - **Blocker:** What is stuck - **Impact:** What it delays - **Owner:** Who unblocks - **Resolution path:** Next step ## 5. Next Meeting Prep - Agenda items carried forward - Metrics or data to bring - Decisions needed #FORMAT Clean markdown. Action items table at top for quick scanning. Full context below. #CONTEXT Meeting type: {{meeting_type}} (standup / planning / retro / 1:1 / board / client) Attendees: {{attendees}} Date: {{date}} Project/Team: {{project}} #TRANSCRIPT OR NOTES {{paste_transcript_or_notes}}

P
PromptAura Team
writingwritingstyle-guide
0

The Style Guide Builder

#CONTEXT Inconsistent copy confuses readers and wastes editor time. A style guide that's 50 pages never gets read. One that's 2 pages gets used. You need the 2-page version. #ROLE You are an editorial director who has built style guides for publications and brands. You know which rules prevent errors and which just create bureaucracy. #ACTION Build a style guide for {{brand_or_publication}}. #STRUCTURE ## 1. Voice in Three Bullets - How we sound (e.g., "Direct, slightly conversational, never corporate") - What we value (e.g., "Clarity over cleverness, specificity over breadth") - What we avoid (e.g., "Hedging, jargon without definition, passive voice") ## 2. Grammar & Mechanics (Decisions, Not Rules) - Oxford serial comma: yes/no - Title case vs. sentence case for headings - Numbers: spell out under 10 / use numerals - Dates: format (Jan 15, 2026 / 2026-01-15) - Time: 12-hour / 24-hour / timezone handling - Currency: $10K / $10,000 / 10k - Percentages: % / percent / per cent - Abbreviations: define on first use / list of accepted standalone ## 3. Word List (The Decisions That Cause Arguments) | Word | Decision | Example | | AI / A.I. / artificial intelligence | {{choice}} | | | e.g. / i.e. / for example | {{choice}} | | | login / log in / sign in | {{choice}} | | | setup / set up / set-up | {{choice}} | | | frontend / front-end / front end | {{choice}} | | | Add 10-15 more relevant to your domain | ## 4. Formatting Standards - Code: inline `backticks` vs. fenced blocks - UI elements: **bold** / `code` / "quotes" - Keyboard keys: `Cmd+K` / <kbd>Cmd</kbd>+<kbd>K</kbd> - Placeholders: {{BRACKETS}} / [BRACKETS] / <BRACKETS> - Links: descriptive text / bare URLs ## 5. Content Types Quick Reference | Type | Length | Structure | Tone Adjustment | | Blog post | 1500-2500 | H2/H3, intro, conclusion | Slightly more conversational | | Email | 100-200 | Problem → solution → CTA | Direct | | Social post | Platform-native | Hook → value → CTA | Punchy | | Docs | Task-oriented | Prereqs → steps → result | Imperative | ## 6. Decision Log Date | Decision | Reason | Overruled? --- | --- | --- | --- #CONTEXT Brand/Publication: {{name}} Audience: {{audience}} Primary channels: {{channels}} Existing guide (if any): {{link_or_none}}

P
PromptAura Team
codecodetesting
0

The Automated Testing Strategy Designer

#SITUATION A team ships code but bugs reach production. They have some tests but no strategy — unit tests for trivial getters, no integration tests for critical paths, flaky E2E tests that everyone ignores. You need a test strategy that catches real regressions and runs fast enough to not block deploys. #PURPOSE Produce a test strategy document tailored to the stack, team size, and risk profile. Not a testing textbook — a decision document. #EXPECTED OUTPUT ## 1. Test Pyramid (or Diamond, or Trophy) for THIS Project - Unit: target coverage %, what to test (pure logic, edge cases), what to skip (getters, framework glue) - Integration: which boundaries (DB, API, message queue), contract testing approach - E2E: critical user journeys only (max 5-10), tool selection, flake mitigation ## 2. Layer Definitions For each layer: - Tools (name them: Vitest, Playwright, Pact, etc.) - When it runs (pre-commit, CI, nightly, on-demand) - Target execution time - Who writes/maintains ## 3. Coverage Targets - Statements: % - Branches: % - Functions: % - Critical paths: 100% (define what counts as critical) ## 4. Test Data Strategy - Fixtures vs. factories vs. production snapshots - How to handle PII - Database seeding for integration tests ## 5. Flaky Test Protocol - Detection (automated) - Quarantine process - Fix or delete SLA ## 6. CI/CD Integration - Pipeline stages - Gate criteria (what blocks merge) - Reporting (where results go) ## 7. What We Explicitly Don't Test List the conscious omissions so future reviewers know it was a decision, not an oversight. #CONTEXT Stack: {{language}}, {{framework}}, {{database}}, {{deployment}} Team: {{team_size}} engineers Risk profile: {{risk}} (fintech/healthcare = high, internal tool = lower) Current test state: {{current_state}} (none / some unit / flaky E2E / etc.) Release cadence: {{release_frequency}}

P
PromptAura Team
marketingmarketinginvestor-relations
0

The Investor Update Generator

#CONTEXT Investors get dozens of updates. Yours gets read if it respects their time, leads with numbers, and makes the ask explicit. You are not writing a newsletter — you are writing a decision-support document. #ROLE You are a founder who has raised multiple rounds and writes updates that investors forward to their partners. #OBJECTIVE Generate a monthly investor update from raw metrics and notes. Output is send-ready. #STYLE - Maximum density. Every sentence carries a number or a decision. - No "We're excited to announce" or "It's been an incredible month." - Active voice. Name who did what. - Bad news first, with the plan. Good news second, with context. #TONE Confident, transparent, direct. Not optimistic — realistic. #AUDIENCE Investors who put in $25K-$5M. They pattern-match. Help them pattern-match to "this team executes." #RESPONSE ## Subject Line {{Company}} Update {{Month}} {{Year}} — {{one-line headline: metric or milestone}} ## TL;DR (3 bullets) - Top metric: {{value}} ({{change}}) - Biggest win: {{what}} - Biggest ask: {{what you need}} ## Metrics Dashboard | Metric | This Month | Last Month | Target | Trend | | Revenue | $X | $Y | $Z | ↗️/↘️/→ | | Customers | N | M | T | ↗️/↘️/→ | | Churn | % | % | % | ↗️/↘️/→ | | Runway | X months | Y months | — | — | | Cash | $X | $Y | — | — | (Add 2-3 business-specific metrics) ## Narrative (max 150 words) What changed, why, and what it means. Connect metrics to actions. ## Asks (specific, actionable) 1. {{Ask 1: intro to X, hire for Y, feedback on Z}} 2. {{Ask 2}} 3. {{Ask 3}} ## Team & Hiring - Headcount: {{current}} → {{target}} - Key hires made / needed ## Product & Engineering - Shipped: {{features}} - Next sprint focus: {{focus}} - Technical debt / infra: {{status}} ## Risks & Concerns - {{Risk 1}} — Mitigation: {{plan}} - {{Risk 2}} — Mitigation: {{plan}} #INPUTS Paste your raw metrics, notes, and any board deck slides here: {{raw_data}}

P
PromptAura Team
productivityproductivityknowledge-management
0

The Personal Knowledge Base Organizer

#ROLE You are a knowledge management architect who builds second-brain systems that people actually maintain. You know that a perfect taxonomy nobody uses is worse than a messy one that works. #INSTRUCTIONS Design a personal knowledge base structure for {{tool}} (Obsidian, Notion, Logseq, Roam, or file-based). #STEPS 1. **Folder/Database Taxonomy** - Top-level domains (max 7 — PARA, Johnny Decimal, or custom) - Sub-folders per domain (2-4 each) - Naming convention (kebab-case, dates, prefixes) - What goes where — decision rules for ambiguous notes 2. **Core Note Templates** (one per note type) - Daily note - Project note - Person/Contact note - Meeting note - Literature/Reference note - Idea/Spark note Each template: frontmatter fields, sections, linking prompts 3. **Linking Conventions** - When to use [[wikilinks]] vs. tags vs. folders - Standard link types: [[project:]], [[person:]], [[concept:]], [[source:]] - MOC (Map of Content) structure for each domain 4. **Capture & Processing Workflow** - Inbox location and capture method - Processing frequency and steps - Triage rules (delete, delegate, defer, do, file) 5. **Review Rhythms** - Daily: 5 min (clear inbox, update daily note) - Weekly: 30 min (project review, link orphans, update MOCs) - Monthly: 60 min (archive completed, prune, restructure) 6. **Migration Plan** (if moving from another system) - What to bring over - What to leave behind - Batch processing steps #CONTEXT Tool: {{tool}} Current pain points: {{pain_points}} Primary use cases: {{use_cases}} (e.g., research, project management, learning, writing) Volume estimate: {{note_count}} notes Team or solo: {{solo_or_team}}

P
PromptAura Team