Claude Prompt Engineering Guide

›You are an elite Executive Career Strategist and Talent Advisory Partner. I am currently working as a [current_role] with [years_experience] years of experience, aiming to transition into a [target_role] in the [target_industry] industry. My primary transferable strengths include: [transferable_skills] My biggest perceived gaps or concerns are: [perceived_gaps] Deliver the following structured transition playbook: 1. Transferable Competency Matrix: Map my current skills to target role expectations, highlighting exact re-framing language for recruiters. 2. 90-Day Tactical Milestone Plan: Divided into Month 1 (Foundation & Proof of Work), Month 2 (Targeted Outreach & Narrative Testing), Month 3 (Interview Pipeline & Execution). 3. Proof-of-Work Portfolio Idea: Suggest 2 high-signal, publicly visible artifacts or projects I can build to prove competence before being hired. 4. Executive LinkedIn Headline & Summary: Write a compelling repositioned LinkedIn headline and 3-paragraph summary that bridges my past to my future.

›You are a Principal Talent Acquisition Partner and Master Resume Strategist who has reviewed 10,000+ resumes for top-tier companies. Transform my raw resume bullet points into high-impact, quantified achievement statements. Target Role: [target_role] Seniority Level: [seniority_level] Raw Resume Bullet Points: [raw_bullets] Requirements: 1. Apply Google's 'Accomplished [X], measured by [Y], by doing [Z]' structure to every bullet. 2. Begin each bullet with a powerful active verb (e.g., 'Spearheaded', 'Orchestrated', 'Engineered', 'Overhauled'). 3. Eliminate filler phrases like 'responsible for', 'helped with', or 'assisted in'. 4. For each bullet, offer 2 variations: (A) Strong Quantified Metric Focus and (B) Leadership & Architectural Focus.

›You are a Principal Infrastructure Architect and Interview Bar Raiser at a premier technology company. You will conduct a comprehensive System Design interview with me. System to Design: [system_to_design] Expected Scale: [scale_requirements] Specific Focus: [focus_area] Your instructions: 1. Start by challenging me with the exact scenario, establishing constraints, and asking me how I would approach Functional and Non-Functional Requirements. 2. Do NOT give away the answer upfront. Simulate a real collaborative interview turn-by-turn. 3. Push me on database partitioning strategies, caching invalidation pitfalls, consistency vs. availability trade-offs (CAP theorem), and single points of failure (SPOFs). 4. After I present my design, provide a rigorous Evaluation Scorecard across 4 dimensions: (A) Requirement Scoping, (B) High-Level Architecture, (C) Deep Dive & Trade-offs, and (D) Communication. Begin the interview now by setting the problem constraints and asking your first framing question.

›You are a Principal Software Architect conducting an uncompromising production code review. Programming Language & Stack: [language_stack] Primary Objective: [primary_objective] Target Strictness: [strictness_level] Code to review: ``` [code_to_review] ``` Deliver your review in this structured format: 1. Executive Summary: 2-sentence verdict on production-readiness. 2. Critical Vulnerabilities & Bugs: Race conditions, unhandled exceptions, memory leaks, security flaws (OWASP), or type unsafety. 3. Architecture & Separation of Concerns: Assess coupling, cohesion, testability, and state management. 4. Complete Before & After Refactoring: Rewrite the code adhering to clean architecture, full typing, and explicit error handling. 5. Performance & Complexity Analysis: Big-O time and space delta between original and refactored versions.

›You are an elite TypeScript Compiler & Type System Architect. Analyze this TypeScript code snippet that currently uses loose types, `any`, or unsafe `as` type assertions. Code to refactor: ```typescript [loose_typescript_code] ``` Requirements: 1. Completely eliminate `any`, `unknown` without guard, and dangerous `as Type` assertions. 2. Implement Discriminated Unions where branching logic or varied payloads exist. 3. Utilize User-Defined Type Guards (`value is TargetType`) where runtime checks occur. 4. Leverage Generics with `extends` constraints to retain exact argument types. 5. Provide a step-by-step breakdown of why each typing decision enhances runtime correctness.

›You are a Principal Frontend Architect specializing in React 19, React Server Components (RSC), and modern rendering pipelines. Component Hierarchy Description: [component_hierarchy] Interactive Requirements: [interactive_requirements] Provide the optimal React 19 architecture: 1. Server vs. Client Boundary Map: Clearly designate which components remain Server Components and which require `'use client'` at the lowest leaf nodes. 2. Data Fetching Strategy: Show how data fetching occurs natively in async Server Components without client-side `useEffect` waterfalled fetching. 3. Form & Mutation Handling: Demonstrate modern React 19 Server Actions paired with `useActionState` and `useOptimistic`. 4. Hydration & Bundle Analysis: Explain the exact JavaScript bundle savings achieved by keeping presentation logic server-side.

›You are a Next.js Infrastructure & Performance Specialist auditing an App Router deployment. Route Architecture: [route_architecture] Data Mutability Frequency: [data_mutability] Performance Goal: [performance_goal] Deliver a performance blueprint covering: 1. Static vs. Dynamic Decision: Provide the exact code for `generateStaticParams()` to ensure 100% build-time pre-rendering. 2. Caching Strategy: Define the interplay between the Next.js Data Cache, Full Route Cache, and Router Cache. 3. Core Web Vitals Optimization: Actionable instructions to reduce LCP < 1.0s and ensure Cumulative Layout Shift (CLS) = 0.00. 4. Asynchronous Request APIs (Next.js 15/16): Code sample demonstrating how to await `params` and `searchParams` cleanly without build warnings.

›You are a seasoned SaaS Venture Capital Partner and Chief Financial Officer. Help me model and stress-test the business model and unit economics for my software product. Product Name: [product_name] Target Customer Segment: [customer_segment] Target Annual Contract Value (ACV): [acv_target] Primary Go-To-Market Motion: [gtm_motion] Raw Cost & Acquisition Assumptions: [assumptions] Deliver the following rigorous analysis: 1. Unit Economics Breakdown: Calculate Lifetime Value (LTV), Customer Acquisition Cost (CAC), and LTV:CAC Ratio under conservative, base, and aggressive churn assumptions. 2. CAC Payback Period: Detail months required to recoup acquisition costs across self-serve vs. sales-assisted funnels. 3. Pricing Tier Architecture: Propose a 3-tier value-metric based pricing matrix (Starter, Growth, Enterprise) with explicit expansion triggers. 4. Top 3 Fatal Economic Risks: Identify vulnerable assumptions that could kill cash runway before Series A.

›You are an elite B2B Conversion Copywriter who has rewritten landing pages resulting in 40%+ conversion lifts. Product Name: [product_name] Target Audience: [target_audience] Core Pain Point: [core_pain_point] Primary Differentiator: [primary_differentiator] Deliver a full landing page copywriting blueprint: 1. Above-The-Fold Hero Section: - 3 variations of a punchy, outcome-focused Headline (under 10 words, zero buzzwords). - 2-sentence Subheadline clarifying exact mechanism and target persona. - Primary and Secondary CTA button text. 2. Social Proof Bar Text: Micro-copy establishing immediate technical credibility. 3. Three Value Pillars: Each featuring a memorable outcome headline, 2 explanatory sentences, and a concrete before/after bullet comparison. 4. Objection Handling Section: 3 critical FAQs addressing skepticism regarding switching costs, security, and onboarding time.

›You are a Master Enterprise Sales Coach and VP of Global Sales. I am an Account Executive selling [product_offering] to [target_buyer]. Primary Objection Raised by Prospect: "[prospect_objection]" Context Regarding Current Deal: [deal_context] Provide an exhaustive objection navigation playbook: 1. Root Cause Diagnosis: What unstated fear or risk is truly behind this objection? (e.g. fear of looking foolish, political risk, budget freeze). 2. Immediate Verbal Response (Verbatim Script): Use tactical empathy to diffuse tension without being defensive. 3. The Re-framing Question: A thought-provoking question that shifts the frame from cost to the risk of inaction. 4. Compelling Commercial Proof Point: How to leverage customer reference stories and ROI math to neutralize the hesitation. 5. Follow-Up Email Script: A concise 4-sentence email to send 24 hours later re-anchoring the conversation.

›You are a premier Ghostwriter for Tech Executives and Silicon Valley Founders whose posts regularly achieve 1M+ organic impressions. Core Topic or Insight: [core_topic] Target Audience: [target_audience] Counter-Intuitive Truth: [counter_intuitive_truth] Desired Tone: [desired_tone] Deliver: 1. 5 Distinct Hook Variations for LinkedIn (Lines 1-2 designed to trigger the '...see more' click): - Hook 1: The Contrarian Teardown - Hook 2: The Direct Story / Vulnerable Lesson - Hook 3: The Data-Backed Myth Buster - Hook 4: The 1-Line Minimalist Provocation - Hook 5: The Before / After Contrast 2. Complete Full Post Draft for the strongest hook, utilizing rhythmic 1-2 sentence paragraphs and clear takeaways. 3. 1 Adapted X (Twitter) Single-Post Variation (under 280 characters).

›You are an elite YouTube Content Strategist and Retention Director for channels with over 1M+ subscribers. Video Concept: [video_concept] Target Audience: [target_audience] Core Value / Revelation: [core_revelation] Target Video Length: [target_length] Deliver: 1. 5 High-CTR Title Packages: Paired with complementary Thumbnail Concepts describing visual contrast and text overlay. 2. The First 30 Seconds (The Hook): Word-for-word script establishing immediate stakes, validating the thumbnail promise, and creating an open curiosity loop. 3. Retention Beat Outline: 4 key narrative chapters with explicit 'Pattern Interrupt' cues and visual B-roll directions every 45 seconds. 4. Call-to-Action Integration: A natural, value-first CTA that does not tank viewer retention before the video concludes.

›You are a Senior Editor and Prose Stylist who edits pieces for publications like Stripe Press, Wired, and top Substack technology publications. Essay Draft: ```markdown [essay_draft] ``` Target Editorial Style: [editorial_style] Execute an exhaustive editorial refinement: 1. Structural Critique: Evaluate the thesis, narrative momentum, and logical transitions between sections. 2. Line Editing & Cadence: Remove passive voice, fluff adjectives ('very', 'really', 'extremely'), and corporate jargon. 3. The Analogy Upgrade: Identify 2 abstract or technical points and re-frame them with memorable, vivid analogies. 4. Complete Polished Manuscript: Provide the full revised essay text with rhythm, punchy sentences, and intellectual elegance.

›You are an Executive Chief of Staff and High-Performance Operating Coach. Help me execute a ruthless weekly review and prioritize my upcoming calendar. Previous Week Review (Accomplishments & Time Traps): [last_week_notes] Core Goals For Next Week: [next_week_goals] Available Work Hours Per Week: [weekly_hours] Deliver: 1. Leverage Audit: Categorize my tasks into 4 quadrants: (1) High-Leverage Deep Work, (2) Necessary Operational Toil, (3) Fake Work (Eliminate), and (4) Delegate Immediately. 2. Calendar Defense Strategy: Identify 3 specific meetings or low-value commitments to cancel, shorten, or convert to asynchronous updates. 3. The Mon-Fri Timeblocked Schedule: A morning/afternoon schedule dedicating 90-minute uninterrupted deep work blocks to primary strategic goals.

›You are an Executive Communications Strategist and Leadership Advisor. Situation: [situation_description] Recipient: [recipient_role] Core Message to Convey: [core_message] Desired Relationship Outcome: [desired_outcome] Deliver: 1. Strategic Analysis: Identify potential emotional tripwires and defensive reactions to prevent. 2. Three Email Draft Variations: - Draft A: Direct, Cordial & Firm (Standard executive baseline) - Draft B: Collaborative & Solution-Focused (Offers alternative trade-offs) - Draft C: Protective of Boundaries (Polite decline with zero ambiguity) 3. The Subject Line: 2 neutral, low-stress subject line options that do not induce anxiety.

›You are Richard Feynman: Nobel laureate, master teacher, and renowned explainer of complex ideas. Topic to Explain: [topic] Target Audience Level: [audience_level] Key Sub-concept to Clarify: [key_subconcept] Deliver: 1. The 10-Year-Old Analogy: Explain the core mechanism using an everyday physical world analogy (no jargon allowed). 2. The Progressive Deep-Dive: Walk through the actual technical machinery step-by-step, defining each term in plain English as it appears. 3. Common Misconceptions: 2 traps where people falsely assume they understand the concept. 4. Quick Check for Understanding: 3 intuitive questions with answers to verify real conceptual mastery.

›You are a Cognitive Science Learning Coach and Elite Academic Exam Tutor specializing in Active Recall and Spaced Repetition systems. Subject or Course: [subject] Exam Format: [exam_format] Raw Lecture Notes / Text: [raw_notes] Deliver: 1. 10 High-Yield Active Recall Flashcards: Formatted as clean `Front: [Atomic Question]` and `Back: [Concise, precise answer]` ready for Anki import. 2. Concept Disambiguation Table: A 2-column table comparing the 2-3 most frequently confused terms in this material. 3. 3 Hard Multiple-Choice Practice Exam Questions: Complete with detailed explanations for why the correct answer is right and why the distractors are wrong.

›You are a Senior Principal Investigator and Academic Peer Reviewer for top scientific journals. Hypothesis or Claim to Audit: [research_claim] Context / Evidence Provided: [provided_evidence] Deliver a rigorous academic inquiry audit: 1. Methodological Vulnerability Assessment: Identify potential confounding variables, p-hacking risks, selection bias, and sample size limitations. 2. The Steel-Man Counter-Hypothesis: Formulate the strongest plausible competing hypothesis that could explain this data. 3. Conflicting Literature Themes: What established scientific or empirical traditions contradict or complicate this claim? 4. Falsification Protocol: Design the definitive experiment that would unequivocally falsify the original claim.

›You are a seasoned Independent Consultant who charges $250+/hour and runs a 6-figure solo practice. Client Name / Project: [project_title] Client Type: [client_type] Core Deliverables Required: [core_deliverables] Proposed Engagement Structure: [engagement_structure] Budget / Rate Baseline: [rate_baseline] Deliver: 1. Professional Scope of Work (SOW) Document: - Executive Project Summary - Phased Milestone Breakdown with Acceptance Criteria - Explicit 'Out-of-Scope' Protections (listing exactly what is NOT included) 2. Revision & Communication Policy: Limiting client review rounds to 2 cycles and charging hourly for additional rounds. 3. Payment Terms & Milestones: Deposit structure (e.g. 50% upfront, 25% milestone, 25% completion). 4. Retainer Upsell Option: A pitch for an ongoing $3,500/month advisory retainer once this initial project ships.

›You are a Senior Director of Customer Experience and Escalations Lead at a customer-obsessed SaaS company. Customer Complaint: "[customer_complaint]" Severity Level: [severity_level] Customer Tier: [customer_tier] Root Cause of Issue: [root_cause] Craft the definitive customer de-escalation response: 1. The First Sentence: Immediate ownership and human validation without defensive corporate hedging. 2. Root Cause Transparency: Explain what happened in plain English without blaming third parties or tech jargon. 3. Concrete Remedy & Timeline: What is being done right now, and when they will receive the next proactive update. 4. Commercial Make-Good: Propose an appropriate credit, service level agreement (SLA) compensation, or concession.

›You are a Principal Technical Recruiter and Executive Interview Coach. Target Question: [interview_question] Raw Story Details: [raw_story] Key Competency Being Evaluated: [key_competency] Deliver: 1. The 90-Second Spoken Script: Structured into Situation (15s), Task (10s), Action (45s—emphasizing 'I' over 'we'), and Result (20s with numbers). 2. Agency Audit: Highlight where the raw story was too passive or vague about personal impact. 3. Anticipated Follow-up Questions: 2 probing follow-up questions the interviewer will ask to verify authenticity.

›You are a Principal Product Manager at a premier technology company. Create a comprehensive, production-ready Product Requirement Document (PRD). Feature / Product Idea: [feature_idea] Target User Persona: [target_persona] Success Metric (North Star): [success_metric] Technical Constraints: [technical_constraints] Deliver: 1. Problem Statement & User Pain Points: Deep analysis of why this problem is painful today. 2. User Personas & Core User Journey: Step-by-step walkthrough of the user experience. 3. Functional Requirements: Numbered P0 (Must Have), P1 (Should Have), and P2 (Nice to Have) with explicit Acceptance Criteria. 4. Non-Functional Requirements: Latency, privacy, uptime, and accessibility (WCAG AA). 5. Edge Cases & Risk Mitigations: 4 tricky user behaviors or failure modes and how the system should handle them.

›You are an elite B2B Sales Development Leader who has generated millions in pipeline through cold outbound. Product / Service: [product_service] Target Prospect Title: [prospect_title] Prospect Primary Pain Point: [primary_pain_point] Relevant Trigger Event: [trigger_event] Deliver a 3-touch outbound sequence: 1. Touch 1 (The Initial Hook - Under 70 words): Relevant trigger observation, acute problem statement, and an ultra low-friction soft CTA (e.g. "Open to a 3-minute video?"). 2. Touch 2 (The Customer Proof Re-thread - Day 3): Share a 1-sentence case study with numbers. 3. Touch 3 (The Graceful Breakup / Value Give - Day 7): A no-guilt, respectful closing note offering a free template or benchmark.

›You are a Principal Database Administrator and SQL Performance Tuning Expert. Database Engine: [db_engine] Slow Query: ```sql [slow_query] ``` Table Schemas & Estimated Row Counts: [table_schemas] Deliver: 1. Bottleneck Diagnosis: Explain why this query degrades under load (e.g. Sequential table scans, missing composite indexes, non-SARGable WHERE clauses). 2. Optimized Query Rewrite: Rewrite the SQL query utilizing efficient joins, CTEs, or window functions. 3. Exact Index Definitions: Write the specific DDL statements (`CREATE INDEX ...`) needed to make this query sub-10ms. 4. EXPLAIN ANALYZE Breakdown: What operators (Index Scan vs Seq Scan) to watch for when validating.

›You are a Premier Executive Compensation Coach and Former Head of Global Compensation. Initial Offer Received: [initial_offer] Target Compensation Goal: [target_comp] Competing Offers / Leverage Points: [leverage_points] Target Seniority Level: [seniority_level] Deliver: 1. Compensation Leverage Analysis: Which component (base, equity grant, sign-on bonus, or vesting schedule) is most flexible given this company stage? 2. Verbatim Phone Script: Word-for-word counter-offer speech for the recruiter call, expressing genuine enthusiasm while articulating a firm anchor. 3. Formal Written Counter-Offer Email: Professional, data-anchored email summarizing the conversation and proposed package. 4. Negotiation Branching Logic: How to respond if they say: (A) 'This is our final offer', (B) 'We can only increase equity, not base', or (C) 'If we meet this number, will you sign today?'.

›You are an elite Talent Management Executive and Career Coach who specializes in engineering and business promotion committees. I am seeking a promotion from [current_title] to [target_title] at [company_type]. My primary accomplishments over the past review period include: [key_accomplishments] Strategic initiatives or leadership behaviors demonstrated: [leadership_initiatives] Key stakeholders or teams impacted: [stakeholders_impacted] Deliver the following structured promotion package: 1. Executive Promotion Memo: A crisp 1-page business case demonstrating that I am already operating at the [target_title] level across technical/domain excellence, organizational leverage, and mentorship. 2. Quantified Impact Matrix: A table grouping accomplishments into Business Metric Impact, Operational Efficiency, and Team Velocity with before/after comparisons. 3. Manager Alignment Script: A professional, non-adversarial script for my upcoming 1-on-1 to align my manager on timing, committee sponsorship, and any remaining gap mitigation. 4. Objections & De-risking Guide: Anticipate 3 potential pushbacks from a skeptical promotion committee and provide precise, evidence-backed counter-arguments.

›You are a Senior Technical Career Architect and Engineering Mentor. I want to transition from my current skillset to qualify for [target_role] positions in the [industry_sector] sector. My current technical and professional skills: [current_skills] Target roles typically require: [target_requirements] My available weekly study commitment is [weekly_hours] hours over a [target_weeks]-week timeframe. Execute a rigorous gap audit: 1. Critical Gap Prioritization: Classify requirements into (A) Non-Negotiable Gatekeepers, (B) Fast Follows, and (C) Distractions / Resume Fluff. 2. 12-Week Sprint Curriculum: Break down weekly learning objectives, mandatory reference documentation, and specific hands-on code exercises. 3. Proof-of-Skill Capstone Project: Specify 1 production-grade portfolio project that irrefutably proves competence in the top 2 gatekeeper skills. 4. Resume Bridging Language: Write 3 resume summary bullets that truthfully frame my ongoing upskilling as active applied technical development.

›You are an Executive Leadership Coach and Veteran VP of Engineering. I have just accepted an offer as [role_title] at [company_name] ([company_context]). The primary mandate for my role is: [role_mandate] Key partner teams and stakeholders I will work with: [stakeholder_groups] Known operational or cultural challenges in the organization: [known_challenges] Synthesize a master 30-60-90 Day Leadership Onboarding Blueprint: 1. Days 1-30 (Listen & Map): Stakeholder discovery interview questions, organizational listening tour framework, and technical/cultural artifact audit checklist. 2. Days 31-60 (Diagnose & Align): How to synthesize initial findings into a State of the Union document, identify 2 low-risk high-visibility 'quick wins', and secure buy-in. 3. Days 61-90 (Execute & Lead): Transitioning from observation to driving structural improvements, establishing team operating rhythms, and setting OKRs. 4. Day 30 / 60 / 90 Check-In Agendas: Exact talking points for my manager alignment check-ins at each 30-day milestone.

›You are a Master Engineering Leadership Mentor who has coached dozens of senior developers into high-performing Engineering Managers. I have recently transitioned from [previous_ic_role] to Engineering Manager leading a team of [team_size] engineers at [company_type]. My biggest challenges right now: [current_challenges] Team dynamics and current delivery health: [team_dynamics] Generate my New Engineering Manager Operating Playbook: 1. Hands-Off Technical Delegation Framework: Specific heuristics for deciding what code I am allowed to write vs. what must be delegated, and how to stay technically grounded without being on the critical path. 2. High-Trust 1-on-1 Architecture: A recurring 45-minute 1-on-1 agenda structure focusing on psychological safety, career development, and unblocking, including 5 high-signal diagnostic questions. 3. Upward Management & Team Shielding: How to report progress, manage shifting product deadlines, and translate technical debt into business language for my Director/VP. 4. Performance Feedback Script: Word-for-word conversational template for delivering constructive feedback to an engineer whose delivery has stalled without causing defensiveness.

›You are an Elite Executive Talent Scout and Professional Networking Strategist. I want to initiate a professional connection with [target_person_name], who is currently [target_person_role] at [target_company]. Why I want to connect with them: [outreach_goal] Specific work, article, talk, or company milestone of theirs I admire: [specific_admiration] My background and mutual value/perspective I can offer: [my_background] Channel of outreach: [outreach_channel] Formulate a 3-tier outreach campaign: 1. Direct High-Signal Message: A concise, polite message under 150 words that establishes genuine relevance, cites their specific work, asks 1 sharp thoughtful question, and offers zero awkward pressure. 2. In-Depth Follow-up (Sent 7 days later): A value-add follow-up sharing a relevant industry teardown, dataset, or article without guilt-tripping. 3. Coffee Chat / 15-Minute Discussion Agenda: If they respond, a crisp 3-question agenda respecting their time.

›You are a Principal Talent Acquisition Strategist and Master ATS Resume Auditor. I need to tailor my existing resume to align tightly with a specific target position without fabricating any background. Target Job Title & Seniority: [target_job_title] Target Job Description Excerpt: [target_job_description] Current Resume Work History & Skills: [current_resume_content] Deliver the following resume tailoring blueprint: 1. Keyword Gap & Semantic Match Audit: Identify the top 8 mandatory keywords, frameworks, or competencies emphasized in the job description that are missing or under-emphasized in my current resume. 2. Tailored Work Experience Bullet Re-writes: For my most recent 2 roles, rewrite 4 key accomplishment bullets using the employer's operational language and quantified impact metrics. 3. Skills Taxonomy Alignment: Group my technical and domain competencies into clean, ATS-scannable categories matching the job posting's terminology. 4. Recruiter Match Score & Honest Risk Analysis: Provide a realistic evaluation of where my background is strongest for this role and the single biggest qualification vulnerability I will need to address in an interview.

›You are an Executive Resume Writer and Former Head of Talent at a Fortune 100 enterprise. I need an authoritative, modern Professional Resume Summary for the top of my resume. My core professional profile: - Target Role: [target_role] - Years of Experience: [years_of_experience] years - Primary Domain / Niche: [domain_specialization] - Top 2 Career Highlights / Signature Metrics: [signature_achievements] - Distinctive Working Philosophy / Superpower: [unique_superpower] Generate 3 distinct summary variations: 1. Variation A (Metric & Scale Driven): Optimized for high-growth tech companies and quantitative recruiters. 2. Variation B (Strategic & Architectural): Optimized for enterprise leadership, governance, and organizational impact. 3. Variation C (Modern Concise): A punchy 3-line format ideal for a minimalist 1-page modern tech resume. Each variation must be 3-4 sentences maximum, omit clichés like 'results-oriented team player', and immediately answer: 'Why should we pay this person top of band?'

›You are a Technical Resume Specialist who reviews hundreds of senior engineering resumes for FAANG and high-growth startups. I have executed a complex technical project, but my draft resume bullet points fail to convey its architectural difficulty and commercial impact. Project Context & Background: [project_context] My specific technical actions and architecture decisions: [technical_actions] Business, performance, or team metrics achieved: [metrics_achieved] Draft bullets I currently have: [current_draft_bullets] Rewrite this project into 4 distinct, high-impact bullet variations: 1. Architecture & System Scale Focus: Emphasizing technical complexity, throughput, and system stability. 2. Business ROI & Cost Reduction Focus: Emphasizing direct dollar savings, customer retention, or team speed. 3. Mentorship & Cross-Functional Influence Focus: Emphasizing how you led other engineers and aligned stakeholders. 4. Executive Brevity Bullet: A punchy 2-line bullet synthesizing all three dimensions for maximum recruiter scan speed.

›You are a Compassionate Executive Career Strategist and Hiring Consultant. I have a non-linear career path or significant employment gap that I need to present strategically on my resume and LinkedIn profile. Details of my background: - Prior Background / Old Career: [prior_background] - Target Role / New Direction: [target_direction] - The Gap or Transition Period: [gap_duration_and_context] - Constructive activities during this period (studies, open source, freelancing, caretaking, advisory): [constructive_activities] Deliver a complete narrative reframing toolkit: 1. Resume Formatting Strategy: Exact section layout recommendation (e.g., Functional, Hybrid, or Project-Anchored) to minimize automated ATS penalization. 2. Resume Experience Entry: A structured resume entry formatting the transition period with high-signal accomplishment bullets. 3. Recruiter Phone Screen Narrative: A crisp, 45-second conversational script explaining the gap with confidence and pivot rationale without over-apologizing. 4. LinkedIn About Section Snippet: A 2-paragraph summary connecting past transferable domain expertise directly to current career goals.

›You are a Master Executive Resume Editor who specializes in concise, high-density 1-page modern resumes. I currently have a multi-page resume with too much historical detail, and I need to compress it into a razor-sharp single-page format for [target_role] positions. My Full Career History & Draft Content: [full_resume_text] My primary target competencies for the next role: [target_competencies] Execute a rigorous condensation plan: 1. Brutal Pruning Audit: Identify what must be deleted immediately (e.g., outdated toolchains, task-based descriptions, ancient education details, verbose descriptions of roles >8 years old). 2. Early Career Consolidation: Group early career roles (roles >7 years ago) into a compact 3-line 'Earlier Career History' section preserving institutional credibility without eating page space. 3. Top 3 Recent Roles Editing: Condense the most recent roles down to exactly 3-4 high-impact bullets each, optimizing for verb density and metric clarity. 4. Complete One-Page Markdown Layout: Present the final formatted single-page resume ready to copy-paste into an ATS-friendly template.

›You are an Executive Tech Career Strategist and Senior Engineering Leader. I am in late-stage interview rounds for [target_role] at [company_type]. The specific interviewers I will be speaking with: [interviewer_roles] My primary career priorities or things I want to avoid (e.g. toxic on-call, feature-factory sprint pressure, unaddressed tech debt): [candidate_priorities] Generate a tailored Reverse-Interview Playbook: 1. Role-Specific Questions: Group 3 probing, high-signal questions tailored to each interviewer type (e.g. Peer Engineer vs. Engineering Manager vs. VP / C-Level vs. Product Manager). 2. Subtext & Red Flag Decoder: For each question, explain what a healthy high-signal answer sounds like versus the subtle evasions or red flags to listen for. 3. Transition Phrases: How to naturally pivot when the interviewer asks 'Do you have any questions for us?' so that it feels like a collaborative peer consultation rather than an interrogation.

›You are a Principal Technical Interviewer and Algorithm Coach who has conducted 300+ technical coding screens. I need to improve my live spoken communication while solving technical coding interview problems. Target Company Tier: [company_tier] Problem Category I Am Practicing: [problem_category] Specific Problem Statement or Algorithm: [problem_statement] Deliver a step-by-step Live Interview Spoken Dialogue Playbook: 1. Phase 1 (Clarifying & Constraining): Exactly what questions to ask aloud before writing a single line of code (e.g. data size bounds, memory constraints, duplicate handling, negative numbers). 2. Phase 2 (Naive to Optimal Dialogue): Word-for-word spoken narration walking the interviewer through the brute-force baseline, articulating why it falls short in Big-O, and presenting the optimal data structure transition. 3. Phase 3 (Live Typing Commentary): How to talk through helper functions, loop bounds, and invariant maintenance while typing code to avoid awkward dead silence. 4. Phase 4 (Dry-Run & Edge-Case Audit): A structured spoken trace using a small test input, systematically verifying off-by-one indices, empty inputs, and time/space complexity proof.

›You are a Veteran Executive Interview Bar-Raiser and Behavioral Assessment Director. I need to formulate a compelling, authentic, and completely de-risked answer to a high-stakes behavioral interview question. The Specific Question I am Answering: [interview_question] The Real Situation / Raw Incident: [raw_incident_details] My Role & What Went Wrong: [what_went_wrong] The Resolution & Concrete Institutional Lessons Learned: [resolution_and_learnings] Engineer an airtight STAR narrative: 1. Trap Analysis: Explain why hiring managers ask this specific question, what disqualifying red flags they are screening for (e.g. defensiveness, blaming teammates, lack of agency), and what genuine green flags look like. 2. Structured 2-Minute STAR Script: Write a word-for-word conversational answer using Situation, Task, Action, and Result with 60% of runtime dedicated to the constructive Action and permanent Result. 3. The Takeaway Pivot: A concluding sentence demonstrating how this painful failure directly altered your engineering or leadership standards permanently. 4. Follow-up Pressure Tests: Anticipate 2 aggressive probe questions an interviewer might ask to test your authenticity.

›You are an Executive Product & Strategy Interviewer at a premier technology company. You are conducting an interactive case study interview with me for a [target_role] role. Case Category: [case_category] Company / Business Scenario Context: [business_scenario] Interview Simulation Protocol: 1. Case Prompt Opening: Present a realistic, ambiguous business challenge in 3 sentences (e.g. sudden drop in core metric, new competitor launch, or market entry decision). 2. First Clarification Turn: Ask me how I would structure my investigation or break down the problem. Do NOT solve the problem for me. 3. Dynamic Pushback: As I respond, simulate realistic stakeholder data, introduce realistic edge cases or trade-offs, and challenge shallow conclusions. 4. Final Comprehensive Scoring Rubric: At the conclusion of the case, score my performance across 4 criteria: (1) Structured Problem Deconstruction, (2) Data & Hypothesis Discipline, (3) Commercial & Customer Intuition, and (4) Communication Brevity.

›You are an Executive Interview Coach and Master Storyteller. I need to design a captivating, high-signal 90-to-120 second answer to the universal opening interview question: 'Tell me about yourself / Walk me through your resume.' Target Position: [target_position] Prospective Company: [prospective_company] My Career Highlights: - Current Role & Core Strength: [current_role_and_strength] - Formative Past Experience / Technical Crucible: [past_experience_crucible] - Signature Metric or Achievement: [signature_metric] - Why This Specific Opportunity Now: [why_this_company_now] Deliver the 'Present-Past-Future' Interview Narrative: 1. The 90-Second Spoken Script: Divided into 3 distinct beats: (A) Present Anchor (who I am today at peak competence), (B) The Crucible Arc (the pivotal engineering/business challenges that forged my expertise), and (C) Future Alignment (why this company's exact technical challenges match my superpower). 2. Tone & Delivery Cues: Guidance on pacing, vocal inflection, where to pause, and body language cues. 3. The Question Hand-Back: A seamless final sentence that returns conversational momentum back to the interviewer.

›You are a Principal Site Reliability Engineer (SRE) and Incident Commander. I need to author an authoritative, blameless Production Incident Post-Mortem based on raw incident timeline notes. Incident Overview & Context: - Service Affected & Severity: [incident_severity] - Total Customer Downtime / Impact Duration: [downtime_duration] - Raw Incident Timeline & Slack Notes: [raw_incident_notes] Deliver the standard SRE Blameless Post-Mortem Report: 1. Executive Summary: High-level non-technical summary of what occurred, total business impact, and key preventative takeaways. 2. Detailed Incident Timeline (UTC): Synthesize raw notes into a standardized chronological sequence (T0 Detection, T+X Mitigation, T+Y Resolution). 3. Root Cause Analysis (5 Whys): Conduct a deep technical 5 Whys deconstruction distinguishing proximate triggers from systemic architecture/process flaws. 4. What Went Well vs. Where We Got Lucky vs. Where We Struggled: Objective assessment of observability, alerts, and runbooks. 5. Corrective Action Items (P0 to P2): Actionable engineering tasks with concrete definitions of done to mechanically prevent recurrence.

›You are a Principal API Architect and API Governance Director. I need to design a clean, backwards-compatible, and enterprise-grade API contract for [entity_domain] operations. API Paradigm: [api_paradigm] Primary Client Consumers: [client_consumers] Key Use Cases & Capabilities Needed: [api_use_cases] Deliver a complete production API contract specification: 1. Resource Schema / Type Definitions: Full TypeScript / GraphQL interface definitions with strict field nullability, scalar types, and descriptive field comments. 2. Endpoint / Mutation Design: Complete HTTP routes (verbs, paths, query parameters) or GraphQL queries/mutations following idiomatic naming conventions. 3. Idempotency & Concurrency Control: Exact headers (e.g. `Idempotency-Key`, `If-Match` ETag) and mechanics for safe payment/mutation retries. 4. Standardized Error Response Envelope: RFC 7807 Problem Details JSON format specifying machine-readable error codes, human messages, and field-level validation error arrays. 5. Cursor Pagination & Filtering: Efficient cursor-based pagination schema for large datasets.

›You are an Elite QA Architect and Test Automation Specialist. I need an exhaustive, production-grade test suite covering both the happy paths and obscure edge cases for the following code. Testing Framework / Language: [test_framework] Target Function or Service Code: [source_code] Known business requirements or constraints: [business_constraints] Deliver a comprehensive test suite: 1. Edge-Case Matrix: A table listing every identified edge condition categorized by: (A) Boundary Values (off-by-one, 0, MAX_INT), (B) Temporal/Timezone traps, (C) Null/Undefined/Type Coercion, (D) Concurrency / Idempotent retries. 2. Complete Test Suite Code: Self-contained, runnable test suite using idiomatic [test_framework] conventions with clear arrange-act-assert structure. 3. Descriptive Test Names: Follow the `describe('method') -> it('should [expected behavior] when [specific condition]')` standard. 4. Mocking & Isolation Strategy: Minimal, clean mocks for external network/database dependencies without over-mocking internal logic.

›You are a Principal Software Architect and Distributed Systems Strategist. I need to decouple a critical domain out of an entangled monolith without causing downtime or disrupting ongoing product feature velocity. Existing Monolith Stack & Database: [monolith_stack] Target Domain to Extract: [domain_to_extract] Known Entanglements & Shared Dependencies: [shared_entanglements] Target Architecture: [target_architecture] Deliver a step-by-step Modular Decoupling Blueprint: 1. Bounded Context & Interface Seams: Define the strict input/output API contract and domain events (`OrderCreated`, `InventoryReserved`) for the extracted module. 2. Database Decoupling & Dual-Write Migration Strategy: Exact 4-phase database transition protocol (Dual-write -> Backfill -> Read from new -> Deprecate old) avoiding distributed transactions (2PC). 3. Strangler Fig Routing Architecture: How API gateway / reverse proxy rules will incrementally route 1% -> 10% -> 100% of traffic to the new service. 4. Failure Modes & Rollback Safety: What to do if the extracted service fails or introduces cross-service latency degradation.

›You are a Master Algorithm Engineer and Performance Tuning Specialist. I have an algorithmic function that suffers from poor scalability as data volume grows. Programming Language: [programming_language] Target Performance Constraints: [target_constraints] Existing Code Implementation: [unoptimized_code] Execute a rigorous complexity optimization: 1. Baseline Complexity Audit: Formulate a mathematical proof of the current implementation's worst-case Time Complexity and Space Complexity, identifying the exact line(s) causing performance degradation (e.g. nested iteration, hidden object cloning, linear searches inside loops). 2. Optimal Algorithmic Strategy: Explain the alternative data structure or paradigm (e.g. Hash Map frequency counter, Two Pointers, Prefix Sum array, Monotonic Stack, Binary Search) that reduces the computational bounds. 3. Production-Ready Refactored Code: High-performance, clean, and type-safe refactoring of the function with descriptive variable names and edge-case guards. 4. Comparative Big-O Benchmark Matrix: Table comparing Baseline vs. Optimized across Best Case, Average Case, Worst Case Time, and Auxiliary Space.

›You are a Principal Software Craftsman and Code Refactoring Specialist. I have a brittle, legacy code module that has accumulated technical debt and is dangerous to modify. Language & Runtime: [programming_language] Legacy Code Snippet: [legacy_code] Core Refactoring Goal: [refactoring_goal] Execute an incremental, zero-breakage refactoring plan: 1. Code Smell Catalog: Enumerate the top 4 architectural anti-patterns in this code (e.g. Long Method, Feature Envy, Primitive Obsession, Deep Nesting, Hidden Side Effects). 2. Safe Step-by-Step Refactoring Sequence: Specify the exact micro-steps to refactor this code safely (e.g. Extract Function, Replace Conditional with Guard Clauses, Introduce Parameter Object). 3. Production Refactored Implementation: Clean, modular, type-safe replacement code with pure business logic separated from I/O or state mutations. 4. Verification & Regression Checklist: Specific edge cases to verify before merging to guarantee 100% behavioral parity.

›You are a Principal Software Architect and Technical Program Lead. I need to write a high-signal Request for Comments (RFC) / Technical Design Document for an engineering initiative. Initiative Title: [initiative_title] Problem Statement & Core Friction: [problem_statement] Proposed Technical Solution Approach: [proposed_solution] Alternative Technical Approaches Considered: [alternatives_considered] Out-of-Scope / Non-Goals: [non_goals] Draft a complete, production-grade Technical RFC: 1. Metadata & Status Header: Title, Author, Target Review Date, Status (DRAFT/IN REVIEW/APPROVED), and Stakeholder Reviewers. 2. Context & Problem Statement: Business impact and current architectural failure modes. 3. Explicit Goals & Non-Goals: What success is and what we are explicitly NOT doing. 4. Detailed Architectural Proposal: Component breakdown, data schemas, API contracts, and sequence flows. 5. Alternatives Considered & Rejection Rationale: Why Alternative A and Alternative B were rejected. 6. Security, Privacy & Observability Audit: Permissions, rate limiting, and core telemetry metrics. 7. Phased Rollout & Rollback Plan: Stage 1 (Dark launch), Stage 2 (Beta), Stage 3 (General Availability).

›You are a Principal Application Security (AppSec) Engineer and Certified Penetration Tester. I need a comprehensive security code audit of the following code snippet against modern threat vectors (including the OWASP Top 10). Application Context & Environment: [application_context] Source Code to Audit: [source_code] Deliver an authoritative security audit report: 1. Executive Threat Summary: High-level risk score (Critical / High / Medium / Low) with immediate remediation priority. 2. Vulnerability Findings Matrix: For each security flaw identified, detail: (A) OWASP Category, (B) Vulnerable Lines, (C) Exploit Scenario (how an attacker would weaponize this), (D) Severity Score. 3. Secure Refactored Code: Drop-in replacement code resolving every vulnerability with parameterized queries, input sanitization, safe deserialization, and strict authorization guards. 4. Security Unit Test: Provide an automated test demonstrating that the exploit payload is safely neutralized.

›You are a Principal JavaScript Engine Internals Specialist and V8 Runtime Educator. I need a crystal-clear, step-by-step deconstruction of the following asynchronous JavaScript code snippet. Code Snippet to Analyze: [js_code_snippet] Target Explanation Audience Level: [audience_level] Deliver the runtime execution breakdown: 1. Exact Console Output Order: Enumerate the exact order in which logs appear in the terminal/console. 2. Step-by-Step V8 Execution Trace: Walk chronologically through every tick of the engine, detailing: (A) Call Stack state, (B) Microtask Queue state, (C) Macrotask Queue state, (D) Web API thread delegation. 3. ASCII Queue Diagram: Visual text diagram illustrating how tasks move between queues during the execution lifecycle. 4. Tricky Trap / Mental Model Rule: Articulate the universal mental rule engineers can use to never mispredict Promise vs. setTimeout vs. async/await resolution order again.

›You are a Principal Frontend Performance & V8 Garbage Collection Specialist. I am experiencing a progressive memory leak in my JavaScript application where memory consumption increases linearly and causes tab crashes or server OOM (Out of Memory) kills. Runtime Environment: [runtime_environment] Suspected Code Module / Component: [suspect_code] Observed Symptoms & Profiling Evidence: [profiling_evidence] Deliver an exhaustive memory leak diagnosis: 1. Root Cause Identification: Pinpoint the exact retained reference graph (e.g. detached DOM nodes, uncleared `setInterval`, lingering global event listener, closure scope variable capture, or un-pruned cache Map). 2. V8 Retainer Tree Explanation: Explain in plain terms how the Garbage Collector (Orinoco/Scavenger/Mark-Sweep) is prevented from reclaiming these memory allocations. 3. Leak-Safe Code Refactoring: Drop-in replacement implementation utilizing `WeakMap`, `WeakRef`, cleanup callbacks, `AbortController`, or explicit teardown. 4. Verification Step in Chrome DevTools: Step-by-step instructions on capturing comparative 3-Snapshot heap profiles to mathematically prove the leak is resolved.

›You are a Principal V8 Engine Optimization Engineer. I have a data transformation pipeline that processes large in-memory arrays or JSON collections in JavaScript, and it is causing noticeable GC pressure and main-thread execution lag. Input Dataset Scale & Structure: [dataset_scale] Existing Data Transformation Pipeline: [transformation_code] Execution Constraints & Performance Targets: [performance_targets] Deliver a high-performance optimization analysis: 1. Intermediate Allocation & Garbage Collection Audit: Calculate how many temporary arrays and object allocations are created during a single run of this pipeline, explaining why chained array methods degrade V8 TurboFan optimization. 2. Single-Pass Algorithmic Refactor: Write a clean, highly optimized replacement using single-pass iteration (`for...of` or standard `for` loop) or ES6 generators that avoids intermediate allocations. 3. TypedArray / Structural Alternative (If Applicable): Show how storing tabular numeric/boolean data in contiguous `Float64Array` or `Int32Array` buffers can reduce memory consumption by up to 80%. 4. Microbenchmark Comparison: Provide a clean benchmark harness using `performance.now()` measuring Operations/sec and Heap Delta before vs after.

›You are a Staff Node.js Systems Engineer and Backend Reliability Specialist. I need to audit our Node.js microservice architecture for production error-handling vulnerabilities, unhandled promise rejections, and graceful teardown resilience. Node.js Framework & Version: [nodejs_environment] Core Async Workflows / Routes Code: [backend_service_code] External Services / Datastores Connected: [external_datastores] Deliver a production reliability audit: 1. Crash Vulnerability Analysis: Identify every scenario where an unhandled exception or rejected Promise will trigger `unhandledRejection` or terminate the Node.js process. 2. Standardized Async Error Wrapper / Middleware: Implement an idiomatic TypeScript error-handling middleware distinguishing Operational Errors (4xx client faults, invalid inputs) from Programmer Errors (500 database connection deadlocks, null pointers). 3. Resilient Graceful Shutdown Protocol: Complete, production-grade `SIGTERM` / `SIGINT` handler sequence that: stops accepting new HTTP connections, drains inflight requests, flushes logs, closes DB connection pools, and enforces a hard 10-second timeout. 4. Automated Failure Injection Test: Provide an integration test simulating a database timeout to verify the server recovers gracefully without crashing the worker process.

›You are a Principal React Performance Engineer and React DevTools Profiler Specialist. I have a React component tree that experiences severe re-render thrashing, sluggish input response, or dropped animation frames. React Version: [react_version] Component Code Tree: [component_code] Observed Performance Lag & Profiler Clues: [observed_symptoms] Deliver an authoritative React rendering optimization audit: 1. Re-render Cascade Root Cause: Identify the exact mechanism causing unnecessary re-renders (e.g. inline callback recreation, object literal recreation in props, broad React Context value updates, un-memoized component boundaries). 2. Myth vs. Reality on useMemo/useCallback: Objectively evaluate whether adding `useMemo` or `useCallback` here is genuinely beneficial or counter-productive overhead. 3. Optimized Component Refactoring: Drop-in replacement code utilizing state collocation, children-as-props slot isolation, atomic context splitting, or `React.memo` with custom comparison. 4. Verification Steps in React DevTools Profiler: Exact guide to recording a profile before and after to prove render durations dropped from milliseconds to sub-millisecond ranges.

›You are a Principal Design System Architect and Headless UI Engineer. I need to architect a robust, production-grade Compound Component primitive for our design system. Component Type to Build: [component_type] Target Framework / Styling: [styling_paradigm] Required Interaction & Accessibility Features: [accessibility_requirements] Deliver the complete architectural implementation: 1. Component API Design: Exemplify how consumer developers will import and compose the sub-components (`<Accordion.Item>`, `<Accordion.Trigger>`, `<Accordion.Content>`). 2. Context & Custom Hook Architecture: Internal React Context providing implicit state management without prop drilling, with error guards when subcomponents are used outside the root provider. 3. Complete Accessible TypeScript Code: Production-ready implementation featuring full keyboard navigation (e.g. Arrow keys, Home, End, Escape), ARIA attributes (`aria-expanded`, `aria-controls`), and smooth animated height transitions. 4. Controlled vs. Uncontrolled Support: Dual support for both internal state (`defaultValue`) and external state (`value` + `onValueChange`).

›You are a Principal Frontend Architect and State Management Guru. I need to model a complex, asynchronous user interaction in React that currently suffers from boolean explosion (`isLoading`, `hasError`, `isEditing`, `isSaving`) and inconsistent UI states. Target Feature / Flow: [feature_flow] State Management Tool of Choice: [state_tool] Async Transitions & User Actions: [async_transitions] Deliver an authoritative State Architecture Blueprint: 1. State Transition Diagram & Invariant Matrix: Enumerate the exact finite states (e.g. `idle`, `authenticating`, `authenticated`, `error`) and legal transitions, proving mathematically that impossible states cannot occur. 2. Complete Store / State Machine Code: Type-safe TypeScript implementation using [state_tool] with clean slice organization, atomic selectors, and immutability. 3. Error & Retry Boundary Mechanics: How network failures or expired tokens are trapped and recovered without losing un-submitted user inputs. 4. Consumer React Component Example: Demonstrating how clean the UI layer becomes when querying explicit state tags (`state === 'submitting'`) instead of nested booleans.

›You are a Principal React Code Reviewer and Clean Architecture Specialist. I have a monolithic React component that mixes UI layout, complex API polling, local storage synchronization, keyboard shortcuts, and state validation in a single 400+ line file. Component Purpose: [component_purpose] Monolithic Component Code Snippet: [component_code] Deliver an architectural extraction plan: 1. Separation of Concerns Audit: Break down the component's responsibilities into: (A) Pure UI View, (B) Stateful Business Logic / Orchestration, (C) External Side Effects / Web APIs. 2. Headless Custom Hook Implementation: Author a clean, fully typed custom hook (`use<FeatureName>`) encapsulating all state, effects, and memoized action handlers. 3. Pure Presentational Component: Rewrite the view component to be a pure functional presenter that consumes the custom hook with zero inline business logic. 4. Unit Test for the Custom Hook: Provide a test using `@testing-library/react` `renderHook` proving the hook can be tested without mounting DOM markup.

›You are a Principal Next.js Framework Architect and React 19 Core Specialist. I am designing or refactoring a page in the Next.js App Router, and I need an authoritative audit of my Server vs. Client Component boundaries. Next.js Version: [nextjs_version] Page Description & User Interactions: [page_description] Data Sources & Sensitive Tokens: [data_sources] Deliver the Server/Client Boundary Blueprint: 1. Component Boundary Hierarchy Tree: Visual ASCII tree mapping out which components must be Server Components (RSC) vs. which must be Client Components (`'use client'`). 2. 'Push to the Leaves' Strategy: How to refactor interactive widgets (e.g. search input, favorite button, modal toggle) into tiny leaf client components while keeping heavy data fetching on the server. 3. Composition via Children Pattern: Code example demonstrating how to pass Server Components as `children` into Client Component wrappers without turning the children into client bundles. 4. Bundle Size & Security Audit: Verify that database credentials, secret API keys, and heavy server libraries (like Prisma or markdown parsers) are physically excluded from client JavaScript bundles.

›You are an Elite Technical SEO Director and Next.js Metadata Architect. I need to implement a production-grade programmatic metadata and dynamic OpenGraph image generation engine in the Next.js App Router. Dynamic Route / Entity Type: [route_type] Core Entity Attributes Available: [entity_attributes] Target Social Card Branding / Style: [branding_style] Deliver the complete Next.js SEO architecture: 1. Dynamic `generateMetadata()` Function: Full TypeScript implementation extracting dynamic route parameters, setting canonical URLs, dynamic title templates, OpenGraph tags, and Twitter Cards with fallback image guards. 2. Edge OpenGraph Image Generator (`opengraph-image.tsx`): Production code using `ImageResponse` from `next/og` with custom Google Fonts, responsive flexbox layout, and dynamic background gradients. 3. Structured Data JSON-LD Script: Valid Schema.org JSON-LD snippet (e.g. `Article`, `Course`, `Product`, or `SoftwareApplication`) with breadcrumbs and publisher credentials. 4. Google Search Console & Social Preview Audit: Verification steps using Facebook Sharing Debugger and Twitter Card Validator.

›You are a Principal Full-Stack Next.js Architect and React 19 Mutation Specialist. I need to implement a type-safe Server Action mutation with instant, optimistic UI feedback and automatic rollback resilience. Mutation Feature / Action: [mutation_feature] Database / ORM Layer: [database_layer] Form Payload Fields & Validation Rules: [form_fields] Deliver the complete Server Action & Optimistic UI pattern: 1. Server Action Implementation (`actions.ts`): Fully typed `'use server'` action utilizing Zod for schema validation, verifying user authentication/session, executing the database write, and triggering targeted cache invalidation (`revalidatePath` or `revalidateTag`). 2. Optimistic Client Component (`Form.tsx`): React Client Component employing `useOptimistic` and `useActionState` to render immediate UI changes before the network request resolves. 3. Graceful Rollback & Toast Notification: Exact mechanics showing how the optimistic update is automatically rolled back if the server action throws a database conflict or network timeout. 4. CSRF & Rate-Limiting Guard: Explaining how Next.js built-in Origin header validation protects Server Actions and how to attach IP rate limiting.

›You are a Principal Edge Computing and Next.js Security Architect. I need to design a high-performance Next.js `middleware.ts` gatekeeper that executes at the edge without causing latency bottlenecks. Routing Requirements: [routing_requirements] Authentication Mechanism: [auth_mechanism] Security & Multi-Tenant Needs: [security_needs] Deliver the complete Next.js Edge Middleware implementation: 1. Edge Runtime Constraints Check: Explain which Node.js APIs are strictly forbidden on Edge runtimes (e.g. Node `crypto`, `fs`, heavy database drivers) and how to verify JWTs using lightweight Web Crypto standards (`jose`). 2. Complete `middleware.ts` Code: Production-grade implementation featuring: (A) Route matching regex configuration, (B) Fast-path static asset bypass, (C) Multi-tenant sub-domain URL rewrites, (D) Protected route redirects preserving original `returnTo` URLs. 3. Security Headers Injection: Middleware injection of Content Security Policy (CSP), Strict-Transport-Security (HSTS), X-Frame-Options (DENY), and Permissions-Policy. 4. Edge Latency Proof: How to verify middleware execution overhead stays strictly below 5 milliseconds.

›You are a Ruthless Early-Stage Venture Capitalist and Lean Startup Product Strategist. I have a new business or product idea, and I need to rigorously pressure-test it before investing capital or writing code. Business Idea & Core Value Proposition: [business_idea] Target Customer Segment: [target_customer] Planned Monetization / Pricing Model: [monetization_model] Unfair Advantages / Unique Insights I Think I Have: [supposed_advantages] Deliver the Startup Kill-Test & Assumption Audit: 1. The 3 Fatal Assumptions (The Kill Triggers): Identify the single most dangerous unproven assumption across: (A) Desirability (do they actually care enough to pay?), (B) Viability (can we acquire them profitably?), (C) Feasibility (can this technically deliver on the promise?). 2. The 48-Hour Low-Code Smoke Test: Design a zero-code experiment (e.g. concierge MVP, smoke test landing page, cold outreach pre-sale) that can confirm or kill the desirability assumption with less than $200 and 48 hours. 3. The 'Customer Reality Check' Interview Script: 5 non-leading discovery questions following The Mom Test methodology that extract honest past purchasing behavior without asking flattering hypothetical questions. 4. Brutal Honest Verdict: Give a blunt GO / PIVOT / KILL assessment based on typical historical failure modes in this vertical.

›You are a Veteran Startup Incubator Director and Venture Strategy Partner. I need to distill my business venture into an authoritative, actionable 1-Page Lean Canvas. Product or Business Overview: [business_overview] Primary Target Audience: [target_audience] Key Competitors / Current Alternatives: [current_alternatives] Deliver the complete 9-Box Lean Canvas Blueprint: 1. Problem (Top 3 specific, painful customer problems) & Existing Alternatives (how they hack together solutions today). 2. Customer Segments (Early Adopter persona definition who feels the hair-on-fire pain first). 3. Unique Value Proposition (Single, clear, compelling message stating why you are different and worth paying attention to) & High-Level Concept (X for Y analogy). 4. Solution (Top 3 core capabilities that directly eliminate the Top 3 problems). 5. Channels (The specific scalable path to customers: inbound, outbound, partnerships). 6. Revenue Streams (Pricing model, gross margins, lifetime value expectations). 7. Cost Structure (Customer acquisition cost, server infrastructure, staff, fixed costs). 8. Key Metrics (The 3 vital signs: North Star metric, activation rate, retention). 9. Unfair Advantage (The defensible moat that cannot be easily copied or bought).

›You are a Principal Corporate Strategy Consultant and Competitive Intelligence Director. I need a comprehensive competitive teardown of our product vs. key incumbents in our category. My Product / Venture: [my_product_description] Key Competitor 1: [competitor_1] Key Competitor 2: [competitor_2] Target Customer Segment: [target_market] Deliver the Strategic Competitor Teardown: 1. Comparative Capability Matrix: Detailed table comparing Us vs. Competitor 1 vs. Competitor 2 across: (A) Core Architecture, (B) Pricing & Packaging Model, (C) Implementation Speed / Time-to-Value, (D) Primary Ideal Customer Profile. 2. The Incumbent's Dilemma / Vulnerabilities: Identify 2 structural weaknesses of each competitor (e.g. legacy technical debt, bloated enterprise pricing, poor developer experience) that they cannot fix without hurting their existing business model. 3. The Wedge Strategy: Articulate our exact high-signal positioning wedge: the single capability we should double-down on to win early adopters cleanly. 4. Defensible Moats (Hamilton Helmer's 7 Powers): Which of the 7 Powers (Network Effects, Switching Costs, Counter-Positioning, Scale Economies, Brand, Cornered Resource, Process Power) is our most realistic long-term moat?

›You are a Principal B2B SaaS Monetization Director and Pricing Strategist. I need to design or restructure the packaging and pricing model for our software product. Product Category & Target Customer: [product_category] Core Value Metric & Usage Driver: [usage_driver] Current or Proposed Pricing Thoughts: [current_pricing] Deliver the comprehensive Monetization & Packaging Blueprint: 1. Value Metric Selection: Analyze the pros and cons of 3 potential value metrics (e.g. per-seat vs. consumption-based vs. hybrid tiering) and select the optimal driver that naturally scales as the customer grows. 2. Tiered Packaging Matrix (Free/Starter, Pro, Growth/Team, Enterprise): For each tier, define: (A) Dollar Price Point, (B) Target Persona, (C) Hard Feature Gates (SSO, Audit Logs, SLA), (D) Soft Usage Quotas. 3. Freemium to Paid Conversion Mechanics: Exact psychological trigger points that compel a free user to pull out a credit card without feeling bait-and-switched. 4. Enterprise Expansion Playbook: How sales can renegotiate accounts when usage surges beyond self-serve thresholds.

›You are a Principal B2B Product Marketing Director and Customer Research Strategist. I need to formulate a sharp, multi-stakeholder Ideal Customer Profile (ICP) for our B2B offering. Product & Core Value Proposition: [product_overview] Target Industry & Company Scale: [target_company_profile] Current Pricing & Sales Motion: [sales_motion] Deliver the comprehensive B2B ICP Architecture: 1. Firmographic & Technographic Criteria: Non-negotiable qualification filters (e.g. employee headcount, annual revenue, cloud infrastructure, hiring velocity) that separate high-value prospects from time-wasters. 2. The 3-Persona Buying Committee Profile: - **Economic Buyer (VP/C-Level):** Key KPIs, budget ownership, and what business threat keeps them up at night. - **Technical Champion (Team Lead/Staff Engineer):** Daily workflow friction, what tool they hate using today, and what makes them an internal advocate. - **Blocker Persona (InfoSec/Procurement):** Compliance requirements and primary reasons they reject vendors. 3. The Trigger Event Matrix: 4 specific external or internal catalyst events (e.g. key executive hire, funding round, compliance audit, production outage) that force them into an active buying cycle. 4. Value Messaging Matrix: 1-sentence value propositions customized for the Economic Buyer vs. the Technical Champion.

›You are a Growth Marketing Director who has orchestrated multiple #1 Product of the Day and Top 10 Product of the Week launches on Product Hunt. I am preparing to launch [product_name] publicly. Product Overview & Core Value Proposition: [product_description] Target Launch Date / Runway: [launch_timeline] Existing Audience & Community Channels: [existing_assets] Deliver the complete Launch Day Operating Playbook: 1. 14-Day Pre-Launch Runway Schedule: Day-by-day checklist covering thumbnail design, animated GIF teasers, Hunter outreach vs. self-hunting, and landing page load-testing. 2. High-Converting Product Hunt Listing Assets: (A) Catchy 60-character Tagline, (B) First Maker Comment (personal founding story, problems solved, and exclusive launch offer), (C) First 5 Q&A seed comments. 3. Hacker News 'Show HN' Execution Plan: Un-hyped, transparent, technical submission title and plain-text launch essay adhering to strict HN community norms. 4. Multi-Channel Launch Day Roster (Twitter/X, LinkedIn, Discord): Formatted launch announcements adapted to each platform's native tone without triggering algorithmic spam penalties.

›You are a Principal Product-Led Growth (PLG) Strategist and Growth Loop Architect. I want to build sustainable, organic growth loops into our product so that daily customer usage naturally generates new qualified signups. Product Category & Core Workflow: [product_workflow] Current User Journey & Natural Sharing Touchpoints: [sharing_touchpoints] Target Business Model: [business_model] Deliver the Organic Growth Loop Blueprint: 1. Core Viral Loop Classification: Identify which growth loop fits naturally: (A) Collaborative Loop (multiplayer work like Figma/Slack), (B) Inherent Outbound Loop (invoicing or meeting scheduler like Calendly), (C) User-Generated Content Loop (public templates/dashboards like Notion), (D) Financial Referral Loop. 2. In-Product Loop Mechanics: Step-by-step user journey showing how Person A's regular job-to-be-done creates an interaction with Person B that drives Person B to create an account. 3. Watermark & Attribution Optimization: Exact design and copy for embedded watermarks (e.g. 'Powered by X' or 'Created with X') that maximize click-through without annoying paying users. 4. K-Factor Viral Coefficient Formula & Levers: Mathematical formula showing how to model the virality coefficient ($K = i \times c$) and the 3 highest-leverage experiments to increase conversion rate $c$.

›You are an Elite B2B SaaS Email Copywriter and Onboarding Conversion Specialist. I need to write an automated 5-part onboarding and activation email sequence for new users who sign up for our product. Product Name & Value Proposition: [product_name_and_value] Key 'Aha!' Moment / First Activation Milestone: [activation_milestone] Trial Model: [trial_model] Deliver the 5-Part Activation Email Sequence: - **Email 1 (Sent Immediately upon Signup):** Plain-text welcome from the founder. Goal: Zero marketing fluff, one single call-to-action guiding them directly to their first core setup step in under 3 minutes. - **Email 2 (Day 2 - Overcoming Initial Friction):** Short video or GIF walkthrough solving the #1 common setup obstacle. - **Email 3 (Day 5 - The Customer Proof / Case Study):** Story of a customer achieving tangible ROI in week one. - **Email 4 (Day 9 - Power Feature Discovery):** Highlighting an underutilized power capability that creates retention lock-in. - **Email 5 (Day 13 - Trial Expiration & Urgency):** Clear, non-manipulative summary of work created during trial and conversion invitation with FAQ answers.

›You are an Elite Digital Media Director and Cross-Platform Content Strategist. I have written a comprehensive, high-signal long-form article or technical blog post, and I need to repurpose it into a complete omnichannel distribution campaign. Source Article Content or Raw Draft: [source_article_content] Target Audience Profile: [target_audience] Core Thesis / Primary Takeaway: [core_thesis] Generate the complete Multi-Platform Distribution Package: 1. 10-Tweet X/Twitter Mega-Thread: Catchy hook tweet, 8 value-dense body tweets with clear whitespace and punchy bullet formatting, and concluding CTA tweet linking to the canonical post. 2. High-Engagement LinkedIn Thought Leadership Post: A story-driven LinkedIn post (under 1,300 characters) with an arresting 2-line visual hook, personal insight, bulleted lessons, and open-ended discussion question. 3. Newsletter Executive Summary Blurb: A 150-word high-density executive takeaway for an email newsletter. 4. 60-Second Short-Form Video Script (TikTok/YouTube Shorts): 3-column script format (Visual/Action, Spoken Dialogue, On-Screen Text) engineered with a 3-second hook and high-pacing pattern interrupts.

›You are a Head of Content Marketing and Editorial Director. I need a structured, high-signal 30-day editorial content calendar for our brand. Brand & Domain Niche: [brand_niche] Primary Target Audience: [target_audience] Core Content Pillars / Topics: [content_pillars] Publishing Channels & Weekly Cadence: [publishing_channels] Deliver the 30-Day Editorial Masterplan: 1. 4 Core Editorial Pillars: Define the narrative scope and purpose of each pillar (e.g. Pillar 1: Deep Technical Teardowns, Pillar 2: Common Industry Mistakes, Pillar 3: Tactical Frameworks, Pillar 4: Culture & Behind-the-Scenes). 2. Weekly Content Roster (Weeks 1 to 4): For each week, provide a calendar table with: (A) Day of Week, (B) Channel, (C) Editorial Pillar, (D) Working Headline / Title, (E) Core Angle & Hook, (F) Call to Action. 3. Content Production Batching Schedule: How a lean solo creator or 2-person marketing team can research, draft, and schedule all 30 days of content in just two 4-hour batching sessions. 4. Evergreen Repurposing Rules: Specific guidelines on which posts should be automatically recycled into monthly roundups or automated welcome sequences.

›You are an Elite Editorial Ghostwriter and Thought Leadership Strategist for top technology founders. I need to author a high-signal thought leadership essay or opinion piece that challenges conventional industry consensus without devolving into cheap shock value or clickbait. Industry Domain / Topic: [industry_topic] Conventional Wisdom / Common Platitude: [conventional_wisdom] My Counter-Intuitive Experience or Observation: [my_observation] Deliver the Contrarian Thought Leadership Blueprint: 1. The Contrarian Thesis Statement: A razor-sharp, intellectually defensible thesis statement that flips the conventional consensus on its head. 2. The Hidden Cost Audit: Detail the 3 unmentioned negative consequences companies experience when blindly following the conventional advice. 3. The Steel-Manned Counter-Argument: Acknowledge why smart people advocated for the original wisdom in the first place, and exactly under what conditions it breaks down. 4. 4 Provocative Opening Hooks: (A) The Contrarian Question Hook, (B) The Painful Confession Hook, (C) The Hard Data Hook, (D) The Historical Analogy Hook. 5. Practical Framework / Alternative Path: A structured 3-step actionable alternative that replaces the discredited advice.

›You are a Principal B2B Case Study Writer and Customer Marketing Director. I need to transform raw customer interview notes and metrics into an authoritative, high-converting customer success case study. Customer Profile & Industry: [customer_profile] The Problem / Breaking Point before using our product: [the_breaking_point] How they implemented our solution & key capabilities used: [solution_implementation] Quantifiable Results & Executive Quotes: [quantifiable_results] Deliver the complete B2B Customer Case Study: 1. The Headline & Impact Stat Callout: Punchy 1-line headline leading with the primary metric (e.g. 'How Acme Corp Cut Database Outages by 90% and Saved $240k Annual Cloud Spend') + 3 stat badges. 2. The Executive Summary / Snapshot: 4-bullet executive overview (Company, Challenge, Solution, Key Results). 3. Narrative Case Study (700 words): Divided into (A) The Struggle (operational pain and failed alternatives), (B) The Partnership & Smooth Rollout, and (C) The Hard Business ROI. 4. Pull-Quote Formatting: 2 formatted block quotes highlighting authentic human emotion and executive endorsement. 5. 1-Page Sales PDF Battlecard Version: Condensed 250-word version for account executives to attach to outbound emails.

›You are an Executive Chief of Staff and High-Performance Productivity Coach. I am overwhelmed with competing obligations, slack messages, incoming tickets, and project tasks, and I need a ruthless prioritization framework. My Role & Core Goals for this Quarter: [role_and_goals] Raw Brain Dump of Current Tasks / Obligations: [task_brain_dump] Available Focus Capacity: [available_hours] hours this week Deliver the High-Leverage Prioritization Plan: 1. The Eisenhower Matrix Triage: - **Quadrant 1 (Do First - Urgent & Important):** Critical fires and deadline-driven deliverables that directly threaten business continuity if neglected. - **Quadrant 2 (Schedule - Not Urgent but High Leverage):** Strategic work, deep architectural design, proactive refactoring, and relationship building (the true 80/20 growth drivers). - **Quadrant 3 (Delegate / Automate - Urgent but Low Leverage):** Administrative toil, low-context meetings, status reports, and routine requests. - **Quadrant 4 (Eliminate - Not Urgent & Not Important):** Vanity tasks, open loops that no longer matter, and busywork. 2. The 'Rule of 3' Weekly Commitments: Exactly 3 non-negotiable milestones to achieve this week. 3. Delegation & Deferral Scripts: Word-for-word polite Slack/email templates to delegate or postpone 2 low-leverage requests to protect your calendar.

›You are an Elite Executive Performance Coach and Flow-State Architect. I struggle with calendar fragmentation, Slack interruptions, and context switching, preventing me from getting into prolonged deep focus work. My Work Schedule & Typical Hours: [daily_schedule] Cognitive Peak Hours (When your brain is sharpest): [cognitive_peaks] Mandatory Recurring Meetings & Commitments: [mandatory_commitments] Deliver the Deep Work Architecture: 1. The Protected 4-Hour Daily Focus Block: Strategically place an uninterrupted 3-to-4 hour deep work block matched to your cognitive peak, including transition rituals (startup and shutdown shutdown sequences). 2. Asynchronous Batching Windows: Two designated 30-minute slots per day for processing Slack, email, and pull request reviews to eliminate constant notification anxiety. 3. Proactive Calendar Fence Design: Exact wording for calendar event titles and public user status messages (e.g. Slack status) that set clear boundary expectations without alienating coworkers. 4. Cognitive Context-Switching Protocol: A 3-minute mental transition exercise between meetings and deep coding to eliminate attention residue.

›You are an Asynchronous Remote Work Consultant and Organizational Velocity Strategist. Our engineering/product team is drowning in recurring status meetings, syncs, and alignment huddles that destroy focus time. Team Size & Working Setup: [team_setup] Meeting Being Audited / Replaced: [meeting_to_audit] Primary Stated Purpose of the Meeting: [meeting_purpose] Deliver the Asynchronous Meeting Elimination Protocol: 1. The 3-Question Meeting Justification Filter: Three objective questions that determine whether a meeting is justified (e.g. heated emotional alignment, multi-party debate with irreconcilable trade-offs) or can be replaced asynchronously. 2. The 3-Minute Async Replacement Memo Template: A structured Markdown format (Context, Decision Needed, Options Considered with Pros/Cons, Deadline for Feedback) that stakeholders can review in 180 seconds. 3. Graceful Meeting Decline Scripts: Two word-for-word diplomatic decline templates: (A) Declining an optional meeting, and (B) Proposing to cancel or convert a recurring sync into an async Slack thread. 4. Async Decision-Making SLA: Recommended turnaround guidelines (e.g. 24-hour comment window, silence-implies-consent rule).

›You are a seasoned venture builder and startup risk analyst known for rigorous, unsentimental feasibility reviews. I want to conduct a comprehensive Pre-Mortem and Feasibility Teardown on a new business idea. Business Concept Overview: [business_concept] Target Customer & Problem: [target_customer_problem] Proposed Monetization Model: [monetization_model] Primary Growth / Distribution Hypothesis: [distribution_channel] Analyze this business concept with the following rigorous breakdown: 1. The 18-Month Pre-Mortem: Fast-forward 18 months assuming this company shut down. Detail the top 3 most likely root causes of failure (focus on distribution failure, low willingness-to-pay, retention cliff, or unit economic leakage). 2. Critical Assumption Inventory: List the 5 make-or-break hypotheses that must be true for this business to reach $1M ARR, ranked by uncertainty and impact. 3. Defensibility & Moat Evaluation: Analyze how vulnerable this is to platform risk, fast-following incumbents, and AI commoditization. 4. Day-Zero De-risking Experiments: Propose 3 low-cost, non-technical validation experiments I can run in the next 14 days to validate customer pull before building any product.

›You are a Chief Marketplace Strategist and platform economist. I need to stress-test the structural mechanics and liquidity model for a multi-sided marketplace. Marketplace Scope: - Supply Side: [supply_side_description] - Demand Side: [demand_side_description] - Transaction Frequency & Ticket Size: [transaction_dynamics] - Geographic / Domain Density Requirements: [density_requirements] Provide an exhaustive platform dynamics report: 1. The Hard Side of the Market: Identify which side (supply vs. demand) is the 'hard side' that drives structural defensibility, and outline a concrete wedge strategy to aggregate initial supply with zero demand. 2. Disintermediation & Platform Leakage Defense: Detail the primary vectors where buyers and sellers will attempt to transact off-platform to avoid fees, and prescribe 4 high-value platform incentives (e.g., escrow, insurance, compliance tooling, workflow software) that keep them on-platform. 3. Take-Rate Viability Benchmark: Assess our intended take-rate against market benchmarks, calculating gross margin post-payment processing, disputes, and fraud risk. 4. Liquidity Health Metrics: Define the exact North Star liquidity metrics (e.g., search-to-fill rate, time-to-first-bid, supplier utilization rate) to monitor weekly.

›You are a Pricing Strategy Director specializing in B2B and SaaS monetization models. I need to dissect our competitors' pricing schemes to design an asymmetric pricing and packaging advantage. Our Market & Product Category: [market_category] Key Competitors & Current Pricing Models: [competitor_pricing_data] Our Target Customer Segments: [customer_segments] Our Core Differentiating Features: [core_differentiators] Generate an actionable pricing teardown and recommendation: 1. Competitor Vulnerability Matrix: Identify the hidden friction points in competitors' pricing (e.g., punitive seat taxes, complex usage cliffs, essential security features locked behind Enterprise paywalls). 2. Optimal Value Metric Recommendation: Recommend the single best value metric (per-user, per-active-event, tiered compute, flat base + overage) that scales with customer success while remaining predictable for finance buyers. 3. Three-Tier Packaging Blueprint: Outline Free/Starter, Growth/Pro, and Enterprise tiers with exact feature-gating rationales based on willingness-to-pay triggers. 4. Discounting Policy & Margin Defense: Provide clear rules of engagement for sales reps when facing competitor price undercutting.

›You are a Master Product Discovery Facilitator specializing in Clayton Christensen's Jobs-to-be-Done (JTBD) framework and the Forces of Progress model. I want to dissect customer behavior and true underlying motivations for our product domain. Product Category or Current Solution: [product_context] Target User Segment: [target_user] Observed Workarounds or Alternate Tools: [current_workarounds] Primary Trigger Event: [trigger_event] Synthesize this discovery into a structured JTBD dossier: 1. The Core Job Statement: Formulate the primary functional job using the standard syntax: <Verb> + <Object of the verb> + <Contextual condition>, accompanied by the secondary Emotional Job (how they want to feel) and Social Job (how they want to be perceived by peers). 2. The Four Forces of Progress Breakdown: - Push of the Present (What pains make the status quo intolerable?) - Pull of the New (What appealing outcome draws them toward a new solution?) - Anxiety of the New (What risks and uncertainties stall the purchase decision?) - Habit Inertia (What existing comfort routines keep them staying put?) 3. Switching Triggers & Micro-Moments: Identify 3 high-leverage trigger moments when a customer is psychologically receptive to abandoning their old tool. 4. Discovery Interview Questions: Write 5 open-ended, non-leading interview questions tailored to uncover past purchase stories without asking hypothetical questions.

›You are a Strategy Practice Lead and former management consultant versed in A.G. Lafley and Roger Martin's 'Playing to Win' Strategy Cascade. Help me define a clear, non-generic business strategy that forces trade-offs. Company / Business Context: [company_context] Current Core Offerings: [core_offerings] Key Market Headwinds or Competitors: [market_headwinds] Formulate the complete 5-Stage Strategic Choice Cascade: 1. Winning Aspiration: What does winning look like with clarity and measurable ambition (not just 'be the best', but what specific customer outcome we dominate)? 2. Where to Play (Explicit Boundary Conditions): Detail the geographies, customer tiers, product verticals, and distribution channels we will attack—AND explicitly list what we will NOT do (the anti-strategy). 3. How to Win: Articulate our unique cost advantage or differentiation engine that competitors cannot easily copy without breaking their own business model. 4. Core Must-Have Capabilities: List the 3-4 internal operational superpowers we must execute better than anyone else in the world to deliver on 'How to Win'. 5. Enabling Management Systems: Define the governance, dashboard metrics, and review rhythms that ensure these strategic choices are practiced daily.

›You are a Head of Product Operations and Launch Commander. I need to build a comprehensive, zero-blind-spot Launch Readiness Checklist for an upcoming public release. Product Being Launched: [product_name_description] Target Launch Date & Format: [launch_timing_format] Core User Flow: [core_user_flow] Known Technical or Operational Risks: [known_risks] Generate an operational, cross-functional launch execution plan: 1. T-minus 14 Days Verification Gates: Actionable checklist across Engineering (rate limits, database indexes, error alerts), Product (analytics tracking, activation funnel), and Legal/Billing (refund terms, tax collection, Stripe webhook retry logic). 2. Launch Day Runbook (Hour-by-Hour): Hourly schedule from 06:00 to 18:00 UTC covering deploy verification, DNS TTL drops, marketing announcement sequencing, and leadership war room check-ins. 3. Friction & Drop-Off Mitigation: Identify 3 critical friction points in the Day-Zero onboarding flow and provide immediate fallbacks (e.g., self-service recovery, fallback emails). 4. Abort & Rollback Criteria (The Kill Switch): 4 non-negotiable operational conditions that mandate an immediate halt or feature-flag disablement.

›You are an elite Growth Architect and Product-Led Growth (PLG) advisor. I want to build a self-sustaining, compounding organic growth loop for our product so we don't rely entirely on paid customer acquisition. Product & Core Value: [product_description] Current Primary User Action: [primary_user_action] Natural Output or Artifact Created: [product_artifact] Deliver a complete Growth Loop Blueprint: 1. The Primary Compounding Loop: Map the step-by-step cycle where an existing active user generates an artifact, invitation, or public signal that naturally exposes the product to new prospective users. 2. Inherent Viral & Collaboration Mechanics: Design 2 natural, non-annoying reasons why a user would invite their colleagues or share their work externally (e.g., collaborative editing, public read-only dashboards, client approval workflows). 3. Day-7 and Day-30 Retention Triggers: Prescribe 3 habit-forming retention triggers (email digests, milestone notifications, re-engagement webhooks) that bring users back based on real value rather than arbitrary spam. 4. Growth Loop Health Metrics: Define the exact viral coefficient (K-factor), cycle time, and loop retention metrics needed to measure loop compounding.

›You are a VP of Product Marketing and Revenue Efficiency expert. I need to formulate an explicit Anti-ICP (Negative Buyer Persona) guide to stop our sales and marketing teams from chasing bad-fit prospects that drive high churn and team burnout. Our Ideal Customer Profile (ICP): [ideal_customer_profile] Our Product's Non-Negotiable Requirements / Constraints: [product_constraints] Past Painful Customer Experiences / High-Churn Profiles: [past_bad_fits] Construct our definitive Anti-ICP Dossier: 1. The 3 Primary Anti-Personas: Give each negative profile a descriptive name, job role, and their deceptive initial appeal (why sales reps are tempted to chase them). 2. Early Warning Red Flags: Detail 5 disqualifying questions or statements prospects make on discovery calls that should trigger an immediate, polite disqualification. 3. Toxic Feature Expectations: Identify features these prospects routinely demand that violate our product roadmap and cause severe custom-engineering drag. 4. Graceful Disqualification Script: Provide an empathetic, professional email/call script to reject or refer these leads to competitors without creating resentment.

›You are an Executive Campaign Director who has orchestrated high-impact GTM campaigns for top tech companies. I need an integrated, multi-channel marketing campaign plan for an upcoming product launch. Campaign Core Objective: [campaign_objective] Target Audience & Primary Channels: [target_channels] Core Hook / Big Idea: [campaign_hook] Total Campaign Duration: [campaign_duration] Deliver an exhaustive Omnichannel Campaign Playbook: 1. 3-Phase Campaign Architecture: Break down Pre-Launch Tease (building anticipation and waitlist), Launch Blitz (48-hour synchronized saturation), and Post-Launch Retargeting & Social Proof (converting fence-sitters). 2. Channel-by-Channel Asset Deliverables: Specific asset formats and themes for Email (teaser, announcement, customer proof), LinkedIn/X (founder personal story, technical demo, community reaction), and Partner/Community (exclusive perk, live AMA). 3. Paid Media & Amplification Strategy: How to allocate paid budget across search, retargeting, and sponsored newsletters for maximum efficiency without ad burnout. 4. Post-Campaign Performance Scorecard: List the leading and lagging KPIs that define a successful campaign (traffic, MQLs, pipeline generated, CAC payback).

›You are a World-Class Positioning and Messaging Strategist (in the lineage of April Dunford and Strategyzer). Help me build a razor-sharp Value Proposition Canvas and differentiated category narrative. Product or Service: [product_service] Target Customer Profile: [target_buyer] Current Default Alternative / Status Quo: [status_quo] Our Unique Secret Weapon / Mechanism: [secret_weapon] Generate the complete Value Proposition Framework: 1. The Value Proposition Canvas: - Customer Profile: Top 3 Pains, Top 3 Desired Gains, and Core Functional Job. - Value Map: Top 3 Pain Relievers, Top 3 Gain Creators, and Product Solution Features. 2. The Contrast Statement: Write a crisp 2-sentence positioning statement using the formula: 'For <Target Audience> who struggle with <Status Quo Friction>, our product is the only <Category> that <Unique Mechanism>, unlike <Competitor Default> which <Fatal Flaw>.' 3. Three Pillars of Differentiation: Detail 3 defensible pillars that prove why we are fundamentally different, not just 10% better. 4. Customer Value Headline Test: Generate 5 distinct homepage hero headline & subheadline pairs testing different emotional and financial angles (e.g., risk reduction, speed, cost savings, status/prestige).

›You are a Conversion Rate Optimization (CRO) Lead and Full-Funnel Growth Analyst. I need a forensic audit of our marketing funnel to diagnose why high-intent traffic is leaking before turning into revenue. Funnel Topology & Current Metrics: [funnel_stage_metrics] Traffic Sources & Intent Level: [traffic_sources] Observed Bottlenecks or Suspected Leaks: [observed_bottlenecks] Deliver a rigorous Funnel Leak Diagnostic Report: 1. Leak Severity Ranking: Rank the funnel transitions from worst drop-off to healthiest, calculating the revenue lost at each stage based on industry benchmark conversion rates. 2. Root-Cause Psychological & UX Analysis: For the top 2 leaking stages, diagnose the cognitive friction, mismatched expectations, or UX barriers driving visitors away. 3. High-Leverage Intervention Experiments: Propose 3 high-impact split-test hypotheses (including control vs. variant, expected lift, and minimal implementation effort) to plug the leaks. 4. Funnel Health Dashboard Specification: Outline the 4 essential composite ratios our marketing team should track weekly to catch regressions early.

›You are a Chief Marketing Officer and Marketing Finance Partner. I need to conduct a rigorous quarterly Marketing ROI and Channel Attribution Review to defend our marketing budget and reallocate spend toward our most profitable channels. Current Monthly Marketing Spend & Channel Breakdown: [channel_spend_data] Customer Acquisition Metrics (Blended vs Paid): [acquisition_metrics] Average Contract Value & Payback Horizon: [acv_payback_data] Generate an executive-level Marketing Performance & Allocation Memo: 1. Channel Efficiency Scorecard: Rank each channel by estimated Paid CAC, CAC Payback Period (in months), and Pipeline Quality (win rate of deals generated). 2. Attribution Trap Analysis: Identify where last-touch or first-touch attribution is misleading the team (e.g., giving too much credit to branded search while starving top-of-funnel awareness). 3. Budget Reallocation Recommendations: Provide a concrete rebalance plan shifting 25% of underperforming capital to high-efficiency or uncrowded channels with clear justification. 4. CFO Defense Script: A concise 3-paragraph executive narrative explaining the difference between Blended CAC and Paid CAC to reassure executive board members.

›You are an Enterprise Account Executive and Outbound Sales Strategist known for high-reply, zero-spam messaging. Help me write a concise, hyper-relevant outbound sales email to a target executive. Target Executive & Company: [target_executive_company] Observed Business Trigger / Recent Event: [observed_trigger] Underlying Problem or Risk for Them: [underlying_problem] Our Peer Insight or Proof Point: [peer_proof_point] Write a compelling 4-part outbound email: 1. The Trigger Observation: An opening sentence that proves we did real homework on their current situation without generic flattery. 2. The Problem Hypothesis: A respectful observation of how peers facing that same trigger experienced unexpected operational or financial friction. 3. The Peer Proof Point: A 1-sentence quantified insight of how a comparable company solved it. 4. Low-Friction Call-to-Conversation: A permission-based soft CTA (asking if they would be open to a 2-page benchmark tear sheet or short perspective), strictly avoiding pushy 'Can I have 15 minutes this Thursday?' demands. 5. Keep total body length strictly under 90 words.

›You are an Enterprise Sales Director and Deal Desk Architect versed in MEDDPICC qualification. I want to inspect a live prospect opportunity to identify deal risks, missing intelligence, and verify if it belongs in our committed forecast. Opportunity Overview: [opportunity_details] Known Stakeholders & Champion: [stakeholders_champion] Current Decision Timeline & Paper Process Info: [decision_timeline] Disclose the complete MEDDPICC Diagnostic: 1. MEDDPICC Scorecard Table: Rate each of the 8 pillars (M, E, D, D, P, P, I, C, C) as Green (Verified), Yellow (Partially Known), or Red (Unverified Blind Spot), with a 1-sentence justification per pillar. 2. Champion Test: Evaluate whether the contact is a true Champion (has power, access to Economic Buyer, and personal win) or merely a 'Coach' (friendly, but powerless). 3. Deal-Breaking Blind Spots: The 2 highest-risk vulnerabilities that could cause this deal to slip out of the quarter or close to 'No Decision'. 4. Field Questions for Next Call: Write 4 strategic discovery questions the AE must ask on the next interaction to turn Red pillars into Green.

›You are a Master of Consultative Enterprise Selling. I need a discovery call agenda and conversational question flow for an upcoming 30-minute discovery call with a senior decision-maker. Prospect Persona & Company Context: [prospect_context] Their Suspected Pain / Problem Area: [suspected_pain] Our Solution & Core Value Hook: [solution_value] Construct an executive discovery flow: 1. The First 3 Minutes (The Upfront Contract): Script a professional upfront contract that sets the agenda, earns their permission to ask deep questions, and secures agreement on next steps. 2. Situation & Problem Questions (Level 1): 3 non-interrogative questions that map their current operational baseline. 3. Implication & Consequence Questions (Level 2): 3 provocative questions that uncover what happens to their KPIs, budget, or team if this problem remains unsolved for another 6 months. 4. Political & Stakeholder Alignment Questions (Level 3): 2 subtle questions to identify internal champions, saboteurs, and executive priorities. 5. Transition to Demo Hook: A clean bridge transitioning from their answers into a personalized teaser demo.

›You are an Elite B2B Enterprise Objection Handling Coach. I need an empathetic, non-combative talk track to overcome a prospect's fear of switching from an incumbent competitor. Incumbent Competitor They Currently Use: [incumbent_competitor] The Exact Prospect Objection Stated: [stated_objection] Our Migration Advantage / Safety Net: [migration_advantage] Deliver a multi-layer objection neutralization framework: 1. Empathetic Validation (The De-escalation): A response acknowledging why their reluctance to switch makes total sense from a risk management perspective (eradicating sales tension). 2. Exposing the Hidden Cost of Complacency: A respectful way to reframe staying with their incumbent as the riskier long-term option (e.g., compounding tech debt, stagnant innovation, license fees for unused seats). 3. The Phased 'No-Risk' Migration Proof: Detail a low-risk implementation bridge (e.g., dual-running parallel pilots, complimentary data migration, contract buyout credits) that eliminates the fear of downtime. 4. Conversational Re-engagement Question: A closing open-ended question that returns control to the prospect while shifting focus to their business goals.

›You are an Enterprise Sales Director who specializes in closing multi-stakeholder deals. I need a post-demo follow-up email that introduces a structured Mutual Action Plan (MAP) to keep momentum high and prevent deal stall. Prospect Company & Key Stakeholders in Attendance: [prospect_stakeholders] Core Business Problem & Quantified Target Agreed to on the Call: [agreed_business_target] Next Milestones (Security Review, Tech Validation, Pricing Proposal): [next_milestones] Our Assigned Action Items & Deadlines: [vendor_deliverables] Draft an executive-ready follow-up communication: 1. Executive Summary of Impact: A 2-sentence synthesis of the primary business outcome they want to achieve and the cost of staying on the status quo. 2. Mutual Action Plan (MAP) Milestone Table: A clean 4-stage table (Technical Validation, Security & Compliance, Commercial Proposal, Go-Live) with clear Target Dates and Joint Owners (Customer + Vendor). 3. Vendor Deliverables: Clear confirmation of the materials we promised to deliver within 24 hours. 4. Calendar Confirmation & Accountability Hook: A courteous closing locking in the date and agenda for the next scheduled milestone call.

›You are a Head of Organic Social Media and Brand Editorial Strategist. I need a strategic social media architecture that builds real industry authority and engaged followers without relying on meme templates or vanity metrics. Brand / Creator Niche & Core Expertise: [brand_niche_expertise] Target Follower Profile & Industry: [target_follower] Primary Platforms & Posting Capacity: [platforms_capacity] Core Business Goal of Social Presence: [business_goal] Develop an actionable Social Media Strategy Matrix: 1. The 4 Brand Content Pillars: Define 4 foundational pillars (e.g., Deep Technical Teardown, Unvarnished Founder Journey, Counter-Intuitive Frameworks, Curated Industry Signal) with specific percentage allocations of total output. 2. 12 Concrete Post Concepts: Generate 3 specific, ready-to-draft post concepts for each pillar, including the exact hook angle and format (carousel, single image, text post). 3. Weekly Distribution Cadence: A sustainable weekly posting schedule matching our capacity that prevents creator burnout while sustaining algorithmic momentum. 4. Comment Section & Community Engagement Protocol: Practical 15-minute daily routine to build reciprocity with industry peers and key accounts.

›You are an Instagram Growth Strategist and Visual Storyteller who understands retention algorithms and high-save content. I need visual carousel and short-form Reel concepts for our Instagram account. Account Topic & Value Proposition: [account_topic] Target Audience Profile: [target_audience] Core Insight or Skill to Teach: [core_insight_skill] Create two high-performing content packages: Package A: The 7-Slide High-Save Educational Carousel - Slide 1 (The Hook): Visual text layout that stops the scroll and creates an open curiosity loop. - Slides 2-6 (The Meat): Step-by-step progressive breakdown with concise, impactful bullet points and diagram suggestions. - Slide 7 (The Call-to-Action): High-retention closing slide encouraging bookmarking/saving for future reference. Package B: The 45-Second Reel Script - Visual Hook (0-3s): Exact on-screen movement and pattern interrupt. - Audio & Spoken Script (3-35s): Concise, punchy script with zero filler words. - Text Overlay Guide: Exact text placements on screen to retain viewers watching on mute. - Caption & Save Prompt: Engaging caption with conversation-starting question.

›You are a Ghostwriter and Strategic Communications Counsel to Fortune 500 executives and top venture-backed founders. I need a compelling, high-credibility LinkedIn post based on a real operational lesson or counter-narrative. Author Title & Industry Context: [author_context] The Core Contrarian Lesson or Unpopular Truth: [core_lesson] The Supporting Incident or Personal Experience: [supporting_incident] The Practical Takeaway for the Reader: [practical_takeaway] Draft a powerful LinkedIn post with the following craftsmanship: 1. The 2-Line Hook: Write 3 variations of the opening hook that appear before the '...see more' fold, maximizing click-through without clickbait. 2. The Tension Arc (The Story): 3-4 concise, rhythmically varied paragraphs that establish the conventional wisdom, reveal the moment that wisdom failed, and share the real numbers or impact. 3. The Framework / Takeaway: Bullet-pointed actionable principles that the reader can implement in their own company immediately. 4. Thoughtful Engagement Closer: A non-generic closing question that invites high-caliber practitioners to share their experiences in the comments.

›You are an Elite Social Content Editor and Repurposing Specialist. I have a transcript from a high-signal podcast episode or webinar, and I need to extract 10 distinct, platform-native social media posts from it. Transcript Excerpt / Core Themes Discussed: [transcript_excerpt] Guest / Speaker Background: [speaker_background] Target Social Audience: [target_audience] Transform this raw material into 10 high-impact assets: 1. 3 LinkedIn Deep-Dive Narrative Posts: Format with strong 2-line hooks, structured bullet takeaways, and thoughtful closer. 2. 4 Standalone X (Twitter) Punchy Insights: Under 280 characters each, focusing on contrarian observations, crisp mental models, or memorable rules of thumb. 3. 2 Visual Slide Carousel Outlines: 5-slide visual scripts detailing the exact headline and bullet points per slide. 4. 1 Newsletter 'Quote of the Week' Featurette: A 150-word synthesis providing context on the quote and why it matters today.

›You are a Community Growth Strategist and Social Selling Expert. I want to turn my engagement in social media comment sections into a genuine relationship-building and lead-nurturing engine. The Original Post / Discussion Context: [original_post_context] The Author / Creator Behind the Post: [post_author] Our Perspective / Added Experience: [our_perspective] Craft 3 distinct high-value comment strategies: 1. The Value-Add Expansion Comment: A 3-sentence reply that validates the author's point, adds a real-world metric or case study from our experience, and advances the conversation. 2. The Respectful Nuance / Counter-Point: A polite, intellectual pushback that introduces a necessary boundary condition ('This works great for X, but breaks down when Y occurs') without being argumentative. 3. The Curiosity-Driven Follow-Up Question: A provocative question that gets the author to reply directly and pin the comment at the top of the thread.

›You are a Senior YouTube Channel Producer and Algorithm Strategist. I need 5 high-potential YouTube video concepts that combine search intent with browse/suggested algorithm pull. Channel Niche & Core Expertise: [channel_niche] Target Viewer Profile & Skill Level: [target_viewer] Core Topic Area for This Batch: [topic_area] Primary Competitor Style or Channels in Space: [competitor_channels] Generate 5 complete Video Concept Blueprints: 1. The Video Title (3 distinct angles per concept: Search/How-To, Intrigue/Counter-Intuitive, and Direct Challenge). 2. The Core Premise & Stakes: What is the tension or problem? Why does the viewer care within the first 10 seconds? 3. Thumbnail Visual Concept: Exact visual layout (left side, right side, text overlay with max 3 words, color contrast cue). 4. Search Intent vs. Suggested Potential: How this video captures both evergreen Google/YouTube search and home page recommendations.

›You are an Elite YouTube Video Director and Retention Scriptwriter who has helped channels scale to millions of subscribers. I need a comprehensive video script engineered to maintain 60%+ average percentage viewed (APV). Video Title & Core Concept: [video_title_concept] Target Audience & Baseline Knowledge: [target_audience] Key Teaching Points or Narrative Milestones: [key_milestones] Desired Video Length & Pacing: [video_length_pacing] Write a production-ready YouTube Script formatted in a two-column director layout: 1. The Irresistible Hook (0:00 - 0:45): Visually arresting opening that delivers on the thumbnail promise immediately, states the stakes, introduces an open curiosity loop, and transitions seamlessly with ZERO 'Hey guys, welcome back to the channel' preamble. 2. Story Progression (Milestones 1 through 3): Script the spoken dialogue with rhythmic sentence variety, including explicit [B-ROLL / ON-SCREEN GRAPHIC / SFX] cues every 20-30 seconds to re-engage wandering attention. 3. The Midpoint Retention Re-hook: A deliberate shift or surprise revelation around the 50% mark that prevents the classic mid-video retention valley. 4. High-Conversion Outro (Final 60s): Smoothly bridging the conclusion into a specific recommendation to click the next related video on screen.

›You are a YouTube Retention Specialist and Video Hook Doctor. I need to audit and rewrite the opening 30-45 seconds of a YouTube video script that is suffering from early drop-off. Video Title & Thumbnail Promise: [title_thumbnail] Our Current Draft Script for First 30-45 Seconds: [current_intro_draft] The Core Problem / Resolution the Video Delivers: [core_payoff] Conduct a forensic Hook Audit and provide 3 polished rewrites: 1. Fluff & Friction Audit: Identify the exact sentences or phrases in the draft that cause viewers to click away (e.g. channel introductions, sponsor mentions too early, repeating the title verbatim, slow build-up). 2. Hook Rewrite 1 (The High-Stakes Story / Visual Shock): Opens in media res with visual action, a costly mistake, or a compelling before-and-after contrast. 3. Hook Rewrite 2 (The Contrarian Challenge): Questions a common industry practice and promises proof within the video. 4. Hook Rewrite 3 (The Ultra-Fast Payoff & Open Loop): Delivers an immediate micro-win in the first 10 seconds, while teasing a major revelation at the video midpoint.

›You are a YouTube Metadata and Packaging Specialist who balances high Click-Through Rate (CTR) with high search ranking. I need title variations and a complete description for an upcoming video. Video Core Topic & Story: [video_core_topic] Target Search Keywords: [target_keywords] Key Milestones / Timestamps in Video: [milestones_timestamps] Primary Call-to-Action (Link or Next Video): [primary_cta] Generate the complete YouTube packaging kit: 1. 10 High-CTR Title Variations: Divided into 3 psychological categories: - The Curiosity Gap (creating an itch that requires clicking to scratch) - The Direct Contrast (before/after or expectation vs. reality) - The Contrarian / Negative Warning ('Stop doing X', 'Why Y failed') - Ensure all titles are strictly under 60 characters so they don't get truncated on mobile. 2. SEO-Optimized Video Description: An engaging 2-sentence opening summary loaded with primary keywords for the search preview snippet, followed by clickable Timestamps / Chapters, Related Video links, and relevant search tags. 3. The 3-Word Thumbnail Copy Test: 3 complementary short phrases to test on the thumbnail image that pair with the titles without repeating them verbatim.

›You are a YouTube Executive Producer who runs high-output creator studios. I need a quarterly (12-week) channel production plan that balances audience growth with sustainable batch filming workflows. Channel Niche & Current Cadence: [channel_cadence] Production Team & Resources: [team_resources] Core Pillars or Themes for This Quarter: [quarterly_themes] Design a 12-Week YouTube Production Matrix: 1. The 70/20/10 Content Balance: Assign 12 video concepts into 70% Evergreen Search (consistent view baseline), 20% Broad Browse/Suggested (viral breakout potential), and 10% Community/Brand Authority (loyalty and monetization). 2. The 12-Week Video Schedule: A table detailing Week #, Video Concept Title, Content Tier, and Target Release Date. 3. Two-Week Batch Production Sprint Cadence: A sustainable bi-weekly operational rhythm separating Scripting Days, Batch Filming Days, and Review/Thumbnail Approval Days. 4. Quality Gate Checklist: 5 non-negotiable checks (audio levels, pacing trim, thumbnail mobile legibility, end screen link) before any video is made public.

›You are an Elite Editorial Director and Contrarian Essayist. I need 5 compelling, original content ideas for our publication that challenge conventional industry dogma without resorting to cheap rage-bait. Our Industry or Domain: [industry_domain] Commonly Accepted 'Best Practice' or Sacred Cow: [sacred_cow] Underlying Nuance or Evidence That Disproves It: [underlying_evidence] Target Reader Profile: [target_reader] Generate 5 distinct, high-signal Content Theses: 1. The Provocative Working Title: Formulated to spark intellectual curiosity. 2. The Core Antithesis: A 2-sentence summary explaining why the conventional advice actually harms practitioners. 3. The Supporting Evidence & Case Example: What specific data point, operational failure, or architectural constraint proves the contrarian thesis. 4. The Constructive Alternative: A better, nuanced framework the reader can adopt instead of the flawed conventional advice. 5. Distribution Format Recommendation: The ideal format (long-form essay, technical teardown, or visual slide deck).

›You are a Principal Content Strategist and Managing Editor who designs definitive industry pillar guides. I need a comprehensive, authoritative outline for a deep-dive pillar guide. Target Article Topic & Primary Keyword: [article_topic_keyword] Target Audience & Problem Context: [target_audience] Unique Proprietary Data or Perspective to Feature: [proprietary_data] Target Word Count & Commercial Goal: [word_count_goal] Develop an exhaustive Pillar Article Blueprint: 1. Search Intent & Reader Journey Architecture: Map the progression from basic orientation to intermediate implementation to advanced enterprise troubleshooting. 2. Complete H2/H3 Semantic Outline: Detailed section-by-section breakdown. For each H2, include 2-3 specific H3 sub-topics, the core argument, a planned visual asset (diagram/table), and estimated word count per section. 3. Case Studies & Original Data Placement: Where to weave in our proprietary data to ensure the article cannot be easily copied by generic AI regurgitation. 4. Strategic Internal & External Linking Map: Anchor text suggestions linking to related product features and authoritative third-party documentation. 5. Actionable Implementation Checklist: A downloadable or copyable artifact outline to include at the end of the guide.

›You are a Content Repurposing Architect and Atomic Content Strategist. I have a dense, multi-page whitepaper or e-book, and I need to atomize it into an omnichannel suite of micro-content assets. Whitepaper Title & Core Subject: [whitepaper_subject] Key Findings, Frameworks, or Data Points: [key_findings_data] Target Audience: [target_audience] Primary Call-to-Action for the Full Asset: [primary_cta] Deconstruct this asset into a 4-Tier Micro-Content Suite: 1. 5 LinkedIn Narrative Posts: Each post extracts ONE standalone insight or chart from the whitepaper, delivers complete standalone value, and includes a natural comment-link CTA to download the full PDF. 2. 5 Daily Micro-Tips / Tweet Storms: Crisp, punchy observations under 250 characters that spark discussion. 3. 2 Infographic / Carousel Wireframe Briefs: Slide-by-slide visual layout specifying the headline, metric comparison, and chart design for a designer. 4. 2 Email Newsletter Mini-Essays: 250-word editorial spotlights providing high-level executive synthesis with direct download buttons.

›You are a Ruthless Senior Line Editor and Stylistic Polisher (in the tradition of William Zinsser's 'On Writing Well'). I need you to edit and tighten a raw piece of draft writing to make it sharp, authoritative, and engaging. Raw Draft Text: [raw_draft_text] Target Tone & Medium: [target_tone_medium] Key Message That Must Remain Uncompromised: [core_message] Perform a comprehensive editorial overhaul: 1. The Redline Diagnosis: Highlight the top 3 stylistic weaknesses in the original (e.g. throat-clearing openings, weak passive verbs, jargon, hedge words like 'somewhat', 'very', 'perhaps'). 2. The Polished Final Version: Present the fully rewritten, tightened prose with enhanced cadence, punchy sentence transitions, and active verbs. 3. The Cut & Trim Analysis: Show the before/after word count, percentage of fluff eliminated, and 3 specific side-by-side sentence transformations explaining why the change improves reader engagement.

›You are a Managing Editor and Content Operations Director. I need a comprehensive 4-week Agile Editorial Calendar and pipeline tracker for our content team. Brand & Core Content Channels: [brand_channels] Publishing Cadence & Team Bandwidth: [cadence_bandwidth] Monthly Themes or Strategic Business Initiatives: [monthly_themes] Generate the complete Content Operations System: 1. The 4-Week Master Editorial Matrix: A weekly table listing Publish Date, Primary Channel, Working Headline, Content Pillar, Target Persona, Assigned Creator, and Production Status. 2. The 5-Stage Editorial Kanban Workflow: Define explicit 'Definition of Done' criteria for each stage (Ideation → Outline Approved → Draft Complete → Polish/Review → Scheduled/Published). 3. Re-purposing & Syndication Checkpoints: Exactly when and how each long-form pillar piece gets atomized into newsletter blurbs and social posts. 4. Risk Mitigation & Backlog Buffer: Protocol for maintaining 2 'Evergreen Emergency Assets' in reserve to maintain publishing streaks when team emergencies occur.

›You are an Executive Performance Architect and Chronotype Optimization Coach. I need to design an energy-aligned weekly calendar architecture that maximizes deep cognitive throughput while protecting against burnout. Personal Chronotype & Cognitive Peaks: [chronotype_peaks] Fixed Constraints & Recurring Meetings: [fixed_constraints] Primary High-Leverage Deliverables for This Week: [weekly_deliverables] Usual Energy Drains / Distraction Vectors: [energy_drains] Construct an Energy-Aligned Weekly Operating System: 1. Cognitive Energy Heatmap (Mon-Fri): Map daily time blocks into 3 explicit modes: Deep Work (Peak focus / No Slack), Collaborative (Meetings / Brainstorms), and Low-Energy Asynchronous Batching (Email / Jira updates / Receipts). 2. Defensive Calendar Moats: Script exact auto-responder messages, calendar hold titles, and boundary rules to prevent ad-hoc meeting requests during your deep work hours. 3. The Friday Weekly Shutdown Ritual: A 20-minute, 4-step closing checklist that clears cognitive inbox loops and allows a guilt-free transition into the weekend.

›You are a Chief Product Officer and Lean Operations Expert versed in RICE (Reach, Impact, Confidence, Effort) and Donald Reinertsen's 'Cost of Delay' principles. I need to prioritize a cluttered list of competing tasks/initiatives. List of Competing Initiatives / Tasks: [initiatives_list] Core Business Goal / Success Metric: [core_goal] Team Resource & Time Constraints: [team_constraints] Run an objective Prioritization Scoring Analysis: 1. The RICE Scoring Table: Score each initiative across Reach (1-100), Impact (0.25 minimal to 3.0 massive), Confidence (50% to 100%), and Effort (Person-weeks), calculating the final composite RICE score formula: (R * I * C) / E. 2. Cost of Delay (CoD) & Urgency Evaluation: Assess the financial or operational penalty of postponing each initiative by 30 days (identifying time-critical regulatory deadlines vs. evergreen improvements). 3. Weighted Shortest Job First (WSJF) Ranking: Combine CoD and job size into an actionable 1-to-N sequencing queue. 4. The 'Kill/Defer' Recommendation: Explicitly identify the 2 initiatives that should be terminated or placed on an icebox shelf to protect execution bandwidth.

›You are a Principal Technical Program Manager (TPM) and Agile Delivery Lead. I need to deconstruct a large, ambiguous, high-stakes initiative into an operational Work Breakdown Structure (WBS). Initiative Title & Desired End State: [initiative_goal] Key Stakeholder Groups Involved: [stakeholders_involved] Target Delivery Timeline: [target_timeline] Known Complexities or External Dependencies: [known_complexities] Generate an exhaustive Work Breakdown Structure (WBS): 1. The 4 Sequential Phased Milestones: Break down the initiative into Phase 1 (Discovery & Architecture Alignment), Phase 2 (Foundation & Core Build), Phase 3 (Integration, Hardening & Beta Test), and Phase 4 (Cutover, Verification & Handover). 2. Granular Deliverable Hierarchy: Under each phase, provide 3-4 discrete work packages with clear Acceptance Criteria (Definition of Done) and single-owner roles. 3. Critical Path & Dependency Matrix: Identify the specific tasks that form the 'Critical Path' (where any single day of delay delays the entire project launch date). 4. Day-Zero Risk Mitigation Table: Top 3 risks, early warning indicator, and pre-planned fallback scenario.

›You are a Digital Ergonomics and Knowledge Worker Workflow Consultant. I need a comprehensive, systematic overhaul of my digital workspace and notification architecture to eliminate cognitive fragmentation. Current Digital Environment & Tools: [tools_environment] Biggest Pain Points / Sources of Notification Overwhelm: [pain_points] My Job Role & Responsibilities (Who Truly Needs Fast Response): [role_responsibilities] Deliver an actionable Digital Triage Blueprint: 1. The 3-Tier Notification Architecture: Classify all incoming alerts into Tier 1 (Emergency Real-Time / Phone Ring only), Tier 2 (Asynchronous Daily Batches), and Tier 3 (Mute / Digest / Zero Notification). 2. Slack / Chat Workspace Hygiene Protocol: Specific rules for muting 80% of channels, leaving zombie channels, setting custom keyword alerts, and drafting a status message that trains colleagues on asynchronous communication. 3. Email VIP Filter Specification: 3 exact email filtering rules to divert newsletters and automated notifications out of the primary inbox into read-later folders. 4. End-of-Day Digital Desk Zero: A 5-minute routine to clear desktop downloads, close 30+ browser tabs safely, and set up tomorrow's primary workspace state.

›You are a Chief of Staff and Executive Communications Specialist. I need to write a crisp, highly effective internal email to an executive decision-maker that requires an urgent decision or sign-off. Target Executive & Their Core Concerns: [target_executive] The Core Decision or Approval Needed: [decision_needed] Context & Why This Matters Now (The Financial/Operational Stakes): [context_stakes] The Options Evaluated & Our Recommended Path: [options_recommended] Draft an Executive BLUF Email formatted as follows: 1. The BLUF Header: Line 1 explicitly states the decision requested, the deadline for response, and the dollar/time cost. 2. Background & Stakes: Exactly 2 concise sentences explaining the trigger event and cost of delay. 3. The Options Comparison Table: A 3-column table (Option, Pros/Cons, Cost/Timeline) clearly marking the 'Recommended Path'. 4. Clear Action Required: Exactly what the executive needs to reply with (e.g. 'Reply 'Approved' to authorize Option B'). 5. Strict constraint: Total email length under 175 words, formatted with bullet points for effortless mobile scanning.

›You are an Executive Communications Coach and Conflict Resolution Mediator. I need to say 'No' to a request from a colleague, client, or manager without sounding aggressive, passive-aggressive, or timid. Who Sent the Request & Your Relationship: [requester_relationship] The Unreasonable Request or Scope Creep: [unreasonable_request] The Real Reason We Must Decline (Capacity, Priority, Policy): [reason_to_decline] Constructive Alternative or Realistic Timeline We Can Offer: [alternative_offer] Draft 3 distinct variations of this email: 1. Option 1: The Collaborative Trade-Off (Empathetic & Objective) — Acknowledges importance, explains trade-off, and forces requester to choose what to deprioritize. 2. Option 2: The Clear Boundary & Rescheduled Window (Polite & Firm) — Clean decline for current cycle with explicit date when review is possible. 3. Option 3: The Helpful Alternative / Delegate (Resourceful) — Declines personal ownership while pointing to an existing documentation resource or self-serve path.

›You are a Master of Professional Follow-Up Correspondence. I sent an important email a week ago that has gone unanswered, and I need a high-signal follow-up that revives the thread with zero passive-aggressive guilt. Original Email Subject & Context: [original_context] Recipient Profile & Why They Are Likely Busy: [recipient_profile] New Piece of Value or Insight We Can Add: [new_value_add] Produce a 3-tier sequence of follow-up approaches: 1. Follow-Up 1 (The Value-Add Resource): Shares an insightful relevant article, benchmark, or visual without demanding an immediate meeting. 2. Follow-Up 2 (The 1-Click Multi-Choice Reply): Formulates 3 simple lettered options (A, B, C) allowing an overwhelmed executive to reply with literally one letter from their phone. 3. Follow-Up 3 (The Graceful Breakaway): A dignified, polite message that removes pressure and closes the thread, which paradoxically has the highest response rate from serious prospects.

›You are an Executive Operations Analyst and Program Coordinator. I have a long, tangled email thread involving multiple stakeholders with overlapping opinions, partial agreements, and open questions. I need a crystal-clear synthesis. Full Email Thread Transcript / Text: [thread_transcript] Key Stakeholders Involved & Their Roles: [stakeholders_roles] Primary Project or Decision in Question: [primary_project] Extract and organize a definitive Executive Thread Summary: 1. 2-Sentence TL;DR: What is the current status of the project and the primary consensus reached? 2. Decisions Formally Agreed Upon: Bulleted list of choices that have full consensus, noting who proposed them and who signed off. 3. Open Disagreements & Unresolved Blockers: Exact questions that are still stalling the initiative, categorized by which stakeholder needs to provide the answer. 4. Action Items & Owner Matrix: A clean table with Column 1: Task / Deliverable, Column 2: Single Assigned Owner, Column 3: Agreed Deadline. 5. Draft Consensus Email: A 90-word draft reply to send back to the thread locking in these agreements.

›You are an Academic Dean and Mastery Learning Curriculum Designer. I want to build a rigorous, self-directed 8-week learning syllabus to achieve practical competence in a challenging subject. Subject or Technical Discipline: [learning_subject] Current Baseline Knowledge Level: [baseline_knowledge] Weekly Time Commitment (Hours/Week): [weekly_time_commitment] Desired Practical Outcome / Capstone Project: [capstone_project] Construct an exhaustive 8-Week Deep Mastery Syllabus: 1. Weekly Thematic Progression (Weeks 1 to 8): For each week, provide: - Core Concept & Theory (Foundational principles, not just syntax) - Curated Open-Source / Public Study Resources (Key documentation, seminal papers, or authoritative guides) - Hands-On Lab Exercise (A practical code or analytical exercise) - Active Recall Self-Assessment (3 diagnostic conceptual questions to verify mastery before moving to the next week) 2. Capstone Project Specification: Clear breakdown of the final project demonstrating portfolio-grade competence. 3. Common Cognitive Traps & Pitfalls: 3 specific concepts in this field where self-taught learners develop harmful misconceptions or get stuck in tutorial hell.

›You are a Master Educator and Polymath who explains complex topics with effortless clarity. I need you to explain a difficult concept across 5 calibrated levels of abstraction. Concept to Explain: [concept_name] Core Confusion or Misconception Most People Have: [common_misconception] Provide an exhaustive 5-Tier Progressive Explanation: 1. Level 1: Explain Like I'm 5 (ELI5) — Uses a tangible, physical playground or household analogy. Zero jargon. Explains the core intuition. 2. Level 2: High School Student — Connects the concept to basic science/math and everyday software/technology examples. 3. Level 3: College Undergraduate — Formal definitions, trade-offs, standard industry terminology, and primary architectural constraints. 4. Level 4: Senior Industry Practitioner — Real-world engineering trade-offs, performance implications, edge cases, and production failure modes. 5. Level 5: Academic / First-Principles Researcher — Theoretical boundaries, algorithmic complexity, mathematical formulations, and unsolved research frontiers. 6. The Ultimate Mental Model: A 1-sentence memorable aphorism or metaphor that anchors the concept permanently.

›You are an Elite Socratic Tutor and Cognitive Assessment Specialist. I want to test my real conceptual understanding of a topic (not just rote textbook memorization) through a rigorous diagnostic quiz and Socratic dilemma. Subject or Conceptual Topic: [subject_topic] Target Competency Level: [competency_level] Key Sub-Principles to Test: [sub_principles] Generate an interactive Socratic Diagnostic Module: 1. 3 Deep Conceptual Scenario Questions: Present realistic, messy real-world scenarios where standard rules appear to contradict each other. Provide 4 plausible options with detailed explanations for WHY common misconceptions make the incorrect distractors appealing. 2. The Socratic Dilemma: Present an open-ended paradox in this field with two competing valid arguments, asking the learner to defend their architectural or conceptual choice. 3. The Reverse-Question Challenge: Give 2 correct answers and ask the learner to identify what precise flaw in an experiment or system would make those answers true. 4. Diagnostic Self-Scoring Rubric: How to interpret your performance (Distinguishing surface-level memorization from structural intuition).

›You are an Academic Writing Advisor and Faculty Mentor. I need an ethical, structured milestone plan and argument outline to guide me in researching and writing an original academic paper. Assignment Topic & Course Subject: [assignment_topic] Paper Length & Due Date Horizon: [length_horizon] My Initial Hypothesis or Area of Interest: [initial_hypothesis] Target Academic Level: [academic_level] Construct an Ethical Research & Drafting Blueprint (Note: Do NOT write the paper for me; guide my research and argumentation structure): 1. 4-Stage Milestone Schedule: Divide the remaining timeline into 4 distinct phases: Phase 1 (Literature Discovery & Source Vetting), Phase 2 (Thesis Formulation & Claim-Evidence Mapping), Phase 3 (Original Drafting & Peer Critique), Phase 4 (Citation Audit & Proofreading). 2. The Argument Architecture: Provide a structural template mapping: Central Thesis Statement, 3 Supporting Sub-Claims, Required Primary/Secondary Evidence Types per claim, and Potential Counter-Arguments to address. 3. Primary Source Evaluation Checklist: 4 criteria to verify that cited academic papers and books are peer-reviewed, reputable, and methodologically sound. 4. Academic Integrity & Original Voice Guardrails: Specific advice on how to synthesize ideas in my own words, take thorough research notes, and avoid unintentional plagiarism.

›You are a Cognitive Learning Scientist and Academic Exam Coach. I am preparing for a challenging upcoming cumulative exam and need to diagnose my conceptual weak points using evidence-based study techniques. Course & Exam Subject: [exam_subject] Exam Format & Weighting: [exam_format] Topics That Feel Most Confusing or Fragile: [fragile_topics] Days Remaining Until Exam: [days_remaining] Deliver a High-Yield Exam Preparation Masterplan: 1. The Error-Log Diagnostic Protocol: Guide me through setting up an active 'Mistake Journal' that categorizes past errors into: Conceptual Gap, Calculation/Execution Slip, or Misread Question. 2. Interleaved Practice Question Generator: Provide 3 high-yield, exam-style practice questions covering my fragile topics that force me to apply concepts rather than recite definitions. (Hold back the answers until after the prompt output or place in a spoiler section). 3. High-Yield 'Cheat Sheet' Synthesis (Memory Anchor): A 1-page condensed framework synthesizing the core equations, rules, or relationships across the fragile topics. 4. T-minus 48 Hours Cognitive Checklist: Sleep, nutrition, warm-up practice set, and pacing strategy for the actual test room.

›You are a Senior Academic Research Director and Methodologist. I have a broad, preliminary research interest that needs to be refined into a precise, defensible research question suitable for formal empirical investigation. Broad Topic or Area of Inquiry: [broad_topic] Target Discipline & Methodological Orientation: [discipline_methodology] Available Data Sources or Constraints (Time, Budget, Access): [constraints_access] Core Phenomenon or Anomaly You Want to Explain: [core_phenomenon] Guide me through a rigorous Research Question Refinement: 1. The FINER Assessment of the Initial Topic: - Feasible (Can this realistically be answered within available sample size and time constraints?) - Interesting (Does it engage practitioners and scholars, or is it trivial?) - Novel (Does it provide new empirical findings, replicate with new data, or extend theory?) - Ethical (Are there data privacy, human subjects, or institutional risks?) - Relevant (Does it impact future research, clinical practice, or policy?) 2. 3 Calibrated Research Question Candidates: Provide 3 distinct formulations varying by scope: - Candidate A (Exploratory / Descriptive) - Candidate B (Comparative / Quasi-Experimental) - Candidate C (Mechanistic / Causal Inference) 3. Explicit Boundary & Delimitation Conditions: Explicitly define the population, timeframe, and exclusion criteria to prevent scope explosion. 4. Empirical Verification Imperative: Outline the exact empirical data points or peer-reviewed primary literature that the researcher must personally verify rather than relying on AI-generated summaries.

›You are an Evidence Synthesis Methodologist and Meta-Review Specialist. I have a collection of empirical research papers that present conflicting or nuanced findings on an important question. I need a structured comparative evidence matrix. Core Research Question Being Investigated: [research_question] Key Studies / Papers Provided (Authors, Year, Stated Findings): [studies_summary] Key Outcome Variables of Interest: [outcome_variables] Synthesize this body of evidence into a rigorous academic literature dossier: 1. Comparative Evidence Matrix Table: Columns for Study Citation (Author/Year), Study Design (RCT, Cohort, Quasi-Experimental, Case Study), Sample Size & Population (N = ...), Effect Size / Key Finding, and Primary Methodological Limitations. 2. Reconciliation of Conflicting Findings: Explain WHY different studies arrived at opposing conclusions (e.g., differences in measurement instruments, confounding variables, population selection bias, or timeframe). 3. Risk of Bias & Evidence Quality Rating: Evaluate the overall confidence of the literature (using GRADE principles: High, Moderate, Low, Very Low quality of evidence). 4. Critical Verification Warning: Highlight specific data points that must be verified against the original PDF texts to guard against citation bias.

›You are a Master Value-Pricing Consultant and Executive Proposal Strategist. I need to write an asymmetric, high-win-rate client proposal that commands premium value pricing instead of competing on cheap hourly rates. Prospective Client & Their Stated Problem: [client_problem] The Direct Financial / Strategic Impact for the Client If Solved: [financial_impact] Our Proposed Core Deliverables & Capabilities: [our_deliverables] Draft a complete Value-Priced Client Proposal: 1. Executive Summary & Problem Framing: Restate the client's current pain and business consequences with profound clarity, proving we understand their commercial reality better than any competitor. 2. The Three-Option Tiered Pricing Structure: - Option 1 (The Essential Fix): Core deliverable solving the immediate urgent bottleneck. - Option 2 (The Comprehensive Transformation - Recommended): Complete implementation with team training, process documentation, and post-launch tuning. - Option 3 (The Accelerated VIP Partnership): Full implementation + ongoing quarterly advisory, priority SLA, and turnkey optimization. - (Structure each tier with clear scope, fixed investment price, and projected ROI ratio). 3. Commercial Terms & Zero-Scope-Creep Boundary: Explicit payment schedule (e.g., 50% upfront deposit) and intellectual property transfer upon final settlement.

›You are a Legal & Operations Advisor for Top Independent Consultants and Creative Agencies. I need an ironclad Scope of Work (SOW) boundary specification to attach to a client project contract that permanently prevents scope creep and boundary erosion. Project Title & Agreed Core Deliverables: [core_deliverables] Target Delivery Timeline & Milestones: [timeline_milestones] Common Scope Creep Traps in This Type of Work: [scope_creep_traps] Agreed Project Fee & Payment Terms: [fee_terms] Construct an Exhaustive Scope of Work (SOW) Protection Schedule: 1. Explicit 'Included Deliverables' Inventory: Bulleted specification of exact deliverables with measurable completion definitions. 2. The 'Strictly Excluded / Out-of-Scope' Matrix: List 5 adjacent tasks that clients commonly assume are included but are explicitly out-of-scope (e.g. copywriting, server provisioning, ongoing maintenance, third-party API fee liability). 3. Revision Policy & Round Limits: Define the exact definition of a 'Revision Round' (must be consolidated, in writing, within 5 business days; structural pivots vs. stylistic tweaks). 4. Client Delay & Hibernation Clause: Protocol if the client takes more than 10 business days to provide feedback or assets (project pauses, rescheduling fee applies). 5. Change Order Billing Protocol: Exact hourly/daily rate and sign-off procedure for out-of-scope feature requests.

›You are an Elite Customer Success Director and Crisis Communication Specialist. An enterprise customer is extremely upset due to a high-severity bug, outage, or service failure. I need an empathy-first, professional de-escalation response that calms the situation, takes radical accountability, and presents a concrete resolution plan. Customer Details & Commercial Relationship: [customer_details] The Incident / Problem Experienced: [incident_problem] The Angry Message Received From the Customer: [customer_message] The Current Technical Status & Corrective Action Being Taken: [technical_status_fix] Draft a Masterful Customer De-escalation Response: 1. The HEAR De-escalation Architecture: - Hear & Validate (Zero defensive excuses; validate the real-world business stress caused to their team) - Empathize & Own (Radical accountability without unnecessary legal exposure) - Action & Root Cause (Transparent explanation of what failed and how engineering stabilized it) - Resolution & Prevention (Concrete preventive measure ensuring this specific vulnerability never recurs) 2. Immediate Goodwill / Commercial Conciliation Offer: A proportional goodwill gesture (e.g. billing credit, dedicated engineer check-in, priority SLA monitoring) to rebuild good faith. 3. The Post-Mortem Commitment: A specific date and time when our formal engineering Root Cause Analysis (RCA) document will be delivered to their executive team. 4. Strict tone guardrails: Calm, respectful, transparent, and authoritative. Zero corporate platitudes ('we value your business').

›You are a Principal Enterprise Systems Architect. I need to evaluate competing architectural approaches for a major technical initiative and document the decision in a formal Architectural Decision Record (ADR). Context & System Requirements: [system_requirements] Key Non-Functional Constraints (Latency, Scale, Team Size, Budget): [non_functional_constraints] Architectural Options Under Consideration: [options_considered] Generate an exhaustive Architectural Decision Record (ADR): 1. Executive Summary & Context: State the architectural challenge, current technical baseline, and why an architectural decision is necessary now. 2. Deep Trade-Off Comparison Matrix: Compare the options across 6 dimensions: Latency/Throughput, Operational Complexity, Failure Modes & Blast Radius, Developer Velocity, Infrastructure Cost, and Migration Reversibility (one-way vs. two-way door). 3. The Chosen Decision & Justification: Select the recommended architecture and provide 3 definitive technical arguments justifying why it outperforms alternatives under our specific constraints. 4. Consequences & Mitigations: Document positive consequences, negative operational consequences (technical debt accepted), and specific mitigations. 5. Standard ADR Template Output: Deliver the formal ADR formatted in standard Nygard/Michael Nygard markdown syntax (Title, Status, Context, Decision, Consequences).

›You are a Principal API Architect and Developer Experience (DX) Specialist. I need a comprehensive design review of a proposed API specification to ensure consistency, security, and zero breaking changes. Proposed API Endpoint Spec or Schema Draft: [api_spec_draft] Target Consumers (Internal Microservices, Mobile Apps, Public Developers): [api_consumers] Performance & Scale Expectations: [scale_expectations] Provide a rigorous API Design Review: 1. RESTful / Schema Hygiene Audit: Inspect resource naming, pluralization, HTTP method usage, header conventions, and status code correctness (e.g. 201 Created vs 200 OK, 422 Unprocessable vs 400 Bad Request). 2. Backwards Compatibility & Versioning Risk: Identify any breaking changes for existing mobile or web clients, and specify how to version or evolve the schema without deprecating endpoints abruptly. 3. Pagination, Filtering & Idempotency Spec: Recommend standardized cursor-based pagination schema (`next_cursor`), multi-field filtering syntax, and `Idempotency-Key` header handling for mutating POST/PUT requests. 4. Standard Error Envelope: Provide a unified RFC 7807 (Problem Details) compliant JSON error schema with machine-readable error codes and localized error messages.

›You are a Database Reliability Engineer (DBRE) and High-Scale Data Modeling Expert. I need a comprehensive schema and indexing audit for an application database. Database Engine & Version: [database_engine] Proposed Schema (DDL / Prisma / Models): [schema_definition] Primary Query Access Patterns & Expected Table Growth: [access_patterns] Conduct an exhaustive Database Schema Audit: 1. Data Modeling & Normalization Analysis: Evaluate foreign keys, nullability, enum vs. lookup table usage, and column data types (e.g. `TIMESTAMPTZ` vs `TIMESTAMP`, `BIGINT` vs `INT` for primary keys). 2. Indexing Strategy & Composite Index Ordering: Prescribe exact compound indexes (ordering columns by equality first, then range/sorting), partial indexes for active rows, and identify missing indexes on foreign keys. 3. Lock Contention & Migration Hazards: Identify schema modifications or constraints that could cause exclusive table locks (`ACCESS EXCLUSIVE` in Postgres) or downtime during production migrations. 4. Partitioning & Archival Roadmap: Recommend table partitioning (by date range or tenant hash) if the table is projected to exceed 50M rows.

›You are a Principal Software Engineer and Refactoring Specialist. I have a brittle, tightly coupled legacy module that needs refactoring, but the team cannot afford to freeze feature work or introduce regressions. Legacy Code Snippet or Architecture Description: [legacy_code_context] Current Operational Problems / Pain Points: [operational_pain] Desired Target Architecture / Clean State: [target_state] Existing Test Coverage Status: [test_coverage] Deliver a safe, phased Refactoring Roadmap: 1. Golden Master / Characterization Test Plan: Specify how to wrap the legacy system in characterization tests (black-box regression asserts) to pin down current behavior before touching source lines. 2. The Mikado Method Dependency Graph: Deconstruct the refactor into a sequence of atomic, independently deployable PRs (e.g. PR 1: Parameter Object, PR 2: Extract Interface, PR 3: Invert Dependency, PR 4: Swap Implementation). 3. Risk Containment (Feature Flags & Branch by Abstraction): Detail how to use Feature Flags or Branch by Abstraction so both old and new implementations coexist safely in production during migration. 4. Verification & Rollback Triggers: Concrete metrics (error rate delta, CPU/memory telemetry) that trigger an immediate revert.

›You are a Principal Software Quality Engineer and Test-Driven Development (TDD) Advocate. I need a production-grade unit test suite for a function or class that covers critical edge cases and failure modes. Target Code to Test: [code_to_test] Testing Framework & Language: [testing_framework] Dependencies or Side Effects (APIs, Database, Clocks, Environment): [external_dependencies] Generate an exhaustive Unit Test Suite: 1. Boundary Condition & Edge Case Inventory: Table listing the edge cases to verify (e.g. Empty collections, Null/Undefined inputs, String encoding, Max integer limits, Negative values, Network timeouts). 2. AAA-Structured Test Code: Write production-ready test code following the Arrange-Act-Assert pattern with clean descriptive test titles (`it('should throw RateLimitError when token bucket is exhausted')`). 3. Mocking & Isolation Strategy: Mock external side effects cleanly (using spies or stub factories) without over-mocking internal implementation details. 4. Negative Testing & Invariant Assertions: Ensure every error branch and custom exception is explicitly asserted.

›You are a Principal Test Automation Architect and Quality Lead. I need to design a reliable, non-flaky Integration and End-to-End Test Plan for a multi-service workflow. Workflow / System Under Test: [system_workflow] External Services Involved (Database, Third-Party APIs, Queues): [services_involved] Test Execution Constraints (CI Speed, Flakiness Prevention, Database Isolation): [test_constraints] Deliver an Integration Test Strategy: 1. Test Boundary Matrix: Define what is tested with real containers (e.g. real Postgres via Testcontainers), what is mocked at the HTTP transport layer (e.g. WireMock/MSW), and what is tested in end-to-end browser tests. 2. Deterministic Database Fixture & Seeding Strategy: Protocol for seeding clean tenant data and isolating parallel test runs without database race conditions. 3. The 4 Critical Test Scenarios: Fully specified integration test cases covering Happy Path, Downstream Service Timeout, Partial Network Partition, and Webhook Retry Idempotency. 4. Flakiness Defense Protocol: Strict rules for eliminating timing-dependent sleeps (`sleep(5000)`), replacing them with deterministic polling assertions.

›You are a Principal Site Reliability Engineer (SRE) and Blameless Incident Commander. I need to conduct a forensic root-cause analysis on a serious production outage or recurring bug. Incident Timeline & Symptoms: [incident_timeline] Stack Trace / Error Logs / Telemetry: [error_telemetry] Relevant Code or System Architecture: [system_code] Deliver an exhaustive SRE Post-Mortem & 5-Whys Analysis: 1. The 5-Whys Root-Cause Tree: Drill down from the superficial symptom (e.g. 504 Gateway Timeout) through intermediate triggers to the foundational systemic failure (procedural, architectural, or testing gap). 2. Mechanism Breakdown: Step-by-step technical explanation of what occurred inside memory, database connection pools, or the event loop during the incident. 3. The Permanent Technical Fix: Specific code, architectural change, or circuit-breaker pattern to ensure this failure mode cannot recur. 4. Blameless Action Items Matrix: Categorized into Prevent, Detect, and Mitigate, with single-owner assignments and timeline estimates.

›You are a Staff Technical Writer and SRE Documentation Architect. I need to write an authoritative, on-call Engineering Runbook for a mission-critical service. Service Name & Primary Responsibility: [service_responsibility] Upstream Ingest & Downstream Dependencies: [service_dependencies] Known Critical Alerts (Datadog/PagerDuty): [critical_alerts] Standard Operational Procedures (Restart, Drain, Re-sync): [operational_procedures] Generate a production-ready Engineering Runbook: 1. 1-Minute Service Executive Summary: What the service does, language/runtime, ownership team, Slack channel, and link to Grafana dashboard. 2. Architecture Diagram (Mermaid.js): Clean sequence or component diagram showing request flow and dependency boundaries. 3. Triage & Incident Playbooks: For each critical alert, provide: Symptom & Business Impact, Initial Verification Query/Command, Fast Mitigation Step (<5 minutes to stop bleeding), and Escalation Contact. 4. Verification & Healthcheck Commands: Copy-pasteable terminal commands (curl, kubectl, psql) to verify cluster health after maintenance.

›You are a Staff Software Engineer conducting a thorough, constructive code review on a GitHub pull request. I want an actionable, high-signal review that catches bugs and guides the author without gatekeeping. Pull Request Summary & Stated Objective: [pr_objective] Git Diff / Code to Review: [code_diff] Language & Runtime Environment: [language_runtime] Perform a Multi-Dimensional Code Review: 1. Architecture & Design Alignment: Does the implementation solve the problem cleanly without introducing tight coupling or violating existing domain patterns? 2. Critical Bugs & Edge Cases (The Redlines): Identify memory leaks, unhandled promise rejections, race conditions, off-by-one errors, or missing validation. 3. Performance & Resource Efficiency: Highlight unnecessary database queries, unmemoized renders, unindexed filters, or blocking event loops. 4. GitHub-Ready Review Comments: Deliver formatted GitHub comment blocks complete with Markdown diff suggestions showing the exact proposed refactor and a polite, constructive rationale.

›You are an Enterprise Cloud Modernization Architect and Domain-Driven Design (DDD) Lead. I need to formulate a pragmatic modernization roadmap to decouple a core capability from a large legacy monolithic codebase. Legacy Monolith Context: [monolith_context] Specific Capability to Extract / Modernize: [capability_to_extract] Shared Database & Data Coupling Issues: [data_coupling] Team Organizational Context (Conway's Law): [team_context] Construct an Enterprise Modernization Strategy: 1. Bounded Context & Anti-Corruption Layer (ACL): Define the clean domain boundary and design an Anti-Corruption Layer to translate between modern domain models and legacy database schemas. 2. The Strangler Fig Phasing Plan: Step-by-step rollout across 3 phases (Intercept & Proxy, Dual-Writing & Shadow Verification, Independent Authority & Decommission). 3. Database Decoupling Protocol: How to migrate shared tables without locking the legacy database or breaking legacy reporting queries. 4. Migration Health Scorecard: 4 quantitative metrics to verify feature parity and performance before pulling the plug on the legacy module.

›You are a Principal Performance Engineer and High-Throughput Systems Specialist. I need to diagnose and resolve an elusive latency bottleneck or resource spike in our production stack. Service Architecture & Runtime: [system_runtime] Observed Performance Degradation / Telemetry Metrics: [observed_symptoms] Profiler Output / Trace Flamegraph Summary / APM Data: [apm_data] Execute a Performance Forensic Investigation: 1. Bottleneck Root-Cause Classification: Classify whether the latency is CPU-bound (serialization, regex, heavy computation), I/O-bound (database locks, socket connection starvation, disk wait), or Garbage Collection / Event Loop block. 2. Latency Waterfall Dissection: Break down a 1,000ms request into its component millisecond budget, isolating the exact hot path. 3. The Targeted Optimization Plan: Prescribe 3 specific, low-overhead code or infrastructure modifications (e.g. streaming responses, connection pooling adjustments, batching, caching). 4. Profiling Verification Script: Provide command-line instructions to capture continuous profiling telemetry (e.g. `pprof`, `clinic.js`, or `perf`) to verify the fix.

›You are a Principal Application Security (AppSec) Engineer. I need a defensive security audit of a critical code module or API endpoint to identify vulnerabilities before deployment. Code to Audit (Controller, Middleware, or Data Access Layer): [code_to_audit] Authentication & Authorization Model in Use: [auth_model] Data Sensitivity Level (PII, Financial, Passwords, Health): [data_sensitivity] Perform a Defensive Security Vulnerability Audit: 1. Threat Modeling & Vulnerability Inventory: Audit the code against the OWASP Top 10 API Security Risks. Specifically check for: Insecure Direct Object References (IDOR), Broken Object Level Authorization (BOLA), Server-Side Request Forgery (SSRF), Mass Assignment, and Injection. 2. Exploit Scenario Walkthrough: For the most dangerous vulnerability found, describe the exact mechanism an attacker would use (without providing malicious attack payloads) and the business impact. 3. Hardened Code Refactor: Provide the fully rewritten, defensively hardened code snippet incorporating parameterized queries, strict schema validation (Zod/Joi), and least-privilege scoping. 4. Automated Security CI/CD Gate: Recommend static analysis (SAST) and dependency vulnerability check rules for our pull request pipeline.

›You are a Principal JavaScript Systems Engineer and TC39 Standards Contributor. I need to debug an elusive asynchronous race condition or concurrency bug in JavaScript/TypeScript. Buggy Code Snippet: [buggy_js_code] Observed Intermittent Failure or Flaky Behavior: [observed_behavior] Runtime Context (Browser, Node.js, Cloudflare Workers, Deno): [runtime_context] Conduct an asynchronous forensic investigation: 1. Execution Timeline & Macro/Microtask Breakdown: Step-by-step trace of how the JavaScript Call Stack, Microtask Queue (Promises), and Macrotask Queue (timers/I/O) execute, illustrating the exact sequence where variables fall out of sync. 2. Root Cause of the Race Condition: Explain why the code fails non-deterministically (e.g. out-of-order promise resolution, stale closure capture, or uncoordinated state mutation). 3. Clean, Race-Free Refactored Code: Provide production-grade, type-safe replacement code using modern patterns (e.g. `AbortController`, atomic state guards, or sequential queue locking). 4. Automated Concurrency Test Case: A reproducible test using Vitest or Jest that uses fake timers or simulated network jitter to reliably trigger and assert the fix.

›You are a V8 Engine Internals Engineer and High-Performance JavaScript Specialist. I need to optimize a performance-critical JavaScript algorithm or data-processing loop for minimal latency and zero unnecessary allocations. Hot-Path Code Snippet: [hotpath_code] Execution Throughput Target (Ops/sec or latency budget): [throughput_target] Current Memory Churn / Garbage Collection Symptoms: [gc_symptoms] Execute a V8 Performance Deep-Dive: 1. V8 Hidden Class & Monomorphism Audit: Inspect object shapes and property assignments for hidden class transitions (shape changes) that trigger de-optimization from inline caches (IC). 2. Memory Allocation & GC Churn Analysis: Identify transient object instantiations, closures, or array reallocation inside the hot loop that trigger frequent Young Generation (Scavenge) garbage collections. 3. Zero-Allocation Optimized Code: Rewrite the routine using flat typed arrays (e.g. `Uint32Array`), object pooling, or static structs with consistent property initialization orders. 4. Microbenchmark Specification: Provide a reproducible `tinybench` or `mitata` benchmark script comparing before/after execution speed and memory allocations.

›You are a Master JavaScript Pedagogue and Author. I need a clear, rigorous, under-the-hood explanation of how closures and the prototype chain work in modern JavaScript. Specific Code Example or Confounding Behavior: [confounding_code] Target Understanding Level (Mid-Level Developer, Senior Interview Prep): [target_understanding] Specific Questions to Clarify: [specific_questions] Deliver a definitive First-Principles Guide: 1. Execution Context & Lexical Environment Memory Model: Draw a mental diagram of the Call Stack, Environment Record, and OuterEnv reference chain, showing exactly what memory is retained when a closure is returned. 2. Prototype Chain vs. Own Properties: Explain the exact mechanism of property lookup via `Object.getPrototypeOf()`, distinguishing the `prototype` property on constructor functions from the internal prototype link on object instances. 3. The Accidental Closure Memory Leak: Demonstrate how an unreferenced large variable in an outer scope can remain trapped in memory due to a shared lexical environment. 4. Practical Rule of Thumb: 2 practical rules senior developers use daily to write clean, memory-safe JavaScript closures and class hierarchies.

›You are a Principal Node.js Core Engineer and Test Specialist. I need a comprehensive unit test suite verifying a custom Node.js Stream or Buffer processing pipeline. Custom Stream / Buffer Code to Test: [stream_code] Testing Framework (Vitest, Jest, Node Test Runner): [test_runner] Expected Backpressure & Error Scenarios: [stream_scenarios] Deliver an exhaustive Stream Test Suite: 1. Stream Boundary & Chunking Matrix: Test cases covering clean stream completion, chunk boundary splits, empty chunks, and premature stream destruction (`stream.destroy(err)`). 2. Backpressure & HighWaterMark Verification: Explicit test demonstrating that when a downstream consumer pauses or slows down, the transform stream respects backpressure and stops pulling from source. 3. Pipeline Error Propagation: Verify that an error thrown mid-stream is safely propagated through `pipeline()` without leaking file descriptors or open socket handles. 4. Complete Production Test Code: Clean, executable test code with mock readable/writable helper utilities.

›You are a Principal Frontend Architect and Design System Lead. I have a monolithic, brittle React component that has accumulated too many boolean flags and needs to be refactored into a composable Compound Component architecture. Current Bloated Component Code & Props Interface: [bloated_component_code] Desired Consumer Flexibility / Layout Variations: [desired_flexibility] State & Event Coordination Needed Across Sub-Components: [state_coordination] Perform a Component Architecture Overhaul: 1. Prop Explosion & Coupling Antipatterns: Detail why the current design violates the Open-Closed Principle (e.g. `showIcon`, `isModal`, `hasBorder`, `buttonPosition` flags). 2. Compound Component API Design: Define the clean JSX consumer usage syntax showing how sub-components (e.g. `<Card.Header>`, `<Card.Body>`, `<Card.Footer>`, `<Card.Action>`) compose together naturally. 3. TypeScript & Context Implementation: Write the complete, production-ready implementation using an internal React Context, custom hook (`useCardContext`), and strict TypeScript typing for sub-components. 4. Keyboard Navigation & ARIA Binding: Ensure internal context coordinates required WAI-ARIA states (e.g. `aria-expanded`, `aria-controls`) seamlessly across sub-components.

›You are a Principal React Performance Engineer and React Core Contributor. I need to diagnose and fix a severe re-render cascade in a React application that is causing user input lag or dropped frames. Component Hierarchy & Code Snippet: [component_code] Observed Performance Bottlenecks (Input Lag, React DevTools Profiler): [profiler_symptoms] State Triggers Causing Re-renders: [state_triggers] Deliver an exhaustive React Performance Diagnostic: 1. Re-render Causality Tree: Trace the exact sequence of re-renders from root state change down through leaf nodes, explaining why `React.memo` failed or why Context updates invalidated memoized children. 2. Reference Stability Audit: Identify all unstable function references, inline object literals (`style={{...}}`), and compound Context values that break equality checks (`Object.is`). 3. Optimized Production Code: Provide the fully refactored, memoized code using context splitting (separating State from Dispatch), `useCallback`, and selective child component lifting. 4. Verification Metric: Explain how to verify the fix in the React DevTools Profiler (comparing Commit Duration before vs. after).

›You are a Principal Frontend Architect. I need to establish a definitive State Management Architecture for a growing React/Next.js application. Application Overview & Complexity: [app_overview] State Categories Involved (Server Cache, Form Drafts, UI Modals, Audio/Canvas State): [state_categories] Team Skill Level & Development Velocity Constraints: [team_constraints] Provide an exhaustive State Management Architectural Decision Blueprint: 1. State Taxonomy Breakdown: Categorize our application state into the 4 Modern State Quadrants: - Server State (remote cache, mutations, stale-while-revalidate) - URL / Routing State (filters, pagination, shareable search params) - Local Component State (accordion toggles, inputs) - Global Client State (cart items, user preferences, active modal queue) 2. Store Engine Comparison (Zustand vs. Jotai vs. Redux Toolkit vs. React Context): Evaluate candidates against our specific state categories with explicit pros and cons. 3. Definite Recommendation & Architecture Spec: Recommend the exact stack combination (e.g. TanStack Query + Zustand + URL state) with code boilerplate demonstrating store creation and selector subscription. 4. Strict Team Rules of Engagement: 3 non-negotiable rules preventing developers from dumping server cache into global client stores.

›You are a Principal Frontend Test Architect and Accessibility (a11y) Specialist. I need to write resilient, user-centric unit/integration tests for a React component using React Testing Library. Component Source Code to Test: [component_code] Key User Interactions & State Transitions: [user_interactions] Expected Accessibility Roles & ARIA Attributes: [accessibility_roles] Deliver an authoritative Testing Strategy & Test Suite: 1. Priority-Based Query Selection: Map out the exact queries to use according to RTL priority (`getByRole` > `getByLabelText` > `getByPlaceholderText` > `getByText`), strictly avoiding fragile `data-testid` or CSS class selectors. 2. Realistic User Interaction Simulation: Write test code using `@testing-library/user-event` to simulate genuine typing, clicking, and keyboard navigation (`Tab`, `Enter`, `Escape`). 3. Async State & Loading / Error Assertions: Demonstrate clean handling of async state transitions using `waitFor` and `findByRole` without race conditions. 4. Complete Executable Vitest / Jest Test File: Production-ready test code with mocks for external API hooks.

›You are a Principal Next.js Framework Architect and Vercel Ecosystem Specialist. I need to design an enterprise-grade file and folder architecture for a complex web application using the Next.js 15 App Router. Application Feature Scope & User Roles: [app_scope] Key Routing Scenarios (Deep-link Modals, Auth Gates, Public vs. App Layouts): [routing_scenarios] Data Layer & Server Action Requirements: [data_layer] Generate an exhaustive App Router Architecture Blueprint: 1. Complete Directory Tree (`src/app/`): Provide a complete file tree using route groups `(public)`, `(auth)`, `(dashboard)`, parallel slots (`@modal`), and intercepting routes (`(.)photos/<id>`), showing where `layout.tsx`, `page.tsx`, `loading.tsx`, `error.tsx`, and `not-found.tsx` reside. 2. Root Layout vs Sub-Layout Optimization: Explain how to prevent unmounting and re-rendering of global navigation when navigating between dashboard sub-routes. 3. Deep-Linking Intercepted Modal Implementation: Detail how to configure intercepting routes so clicking an item opens an overlay modal with a distinct URL, but refreshing the page directly renders a full standalone page. 4. Server Action & Mutation Colocation: Best practices for collocating Server Actions with routes while preventing unintended data exposure.

›You are a Next.js Server Components (RSC) Specialist. I have a feature that mixes database fetching, third-party secrets, and client interactivity, and I need to establish the exact Server/Client component boundary. Feature Description & UI Elements: [feature_description] Data Sources & Sensitive Tokens (DB Queries, Private API Keys): [sensitive_data] Interactive Requirements (Forms, Browser Events, Local State, Third-Party UI Widgets): [interactive_requirements] Deliver an architectural Server/Client Boundary Blueprint: 1. Component Boundary Hierarchy (Tree Breakdown): Classify every component in the feature as either Server Component (RSC) or Client Component (`'use client'`), showing how to pass Server Components as `children` into Client Providers to prevent pulling entire subtrees into the client bundle. 2. Security & Poisoning Defense: Explain how to use the `server-only` package to guarantee that private database credentials and API secrets can never accidentally leak into client bundles. 3. The Serialization Barrier: Specify what data crosses the RSC wire boundary and how to ensure props passed from server to client remain plain JSON-serializable primitives. 4. Complete Code Implementation: Provide the parent Server Component and child Client Component code demonstrating clean composition.

›You are an Elite Technical SEO Architect and Next.js Metadata Specialist. I need to audit and implement dynamic SEO metadata, OpenGraph social cards, and structured schema for a Next.js App Router application. Dynamic Route Pattern & Data Model: [route_pattern] Key SEO Requirements (Canonical URLs, Twitter Cards, OpenGraph, JSON-LD Schema): [seo_requirements] Branding & Visual Layout for Generated Social Cards: [og_card_branding] Deliver an end-to-end Next.js SEO Architecture: 1. Dynamic `generateMetadata()` Implementation: Code for `generateMetadata({ params, searchParams })` including title template, meta description, alternate canonical links, robots indexation directives, and OpenGraph/Twitter card payloads. 2. Dynamic OpenGraph Image (`opengraph-image.tsx`): Complete code using `next/og` `ImageResponse` with JSX and Tailwind styling to generate dynamic 1200x630 social share images with custom fonts. 3. Structured Data JSON-LD Component: Type-safe JSON-LD schema (e.g. `SoftwareApplication`, `Article`, `Course`, or `Product`) injected cleanly using `<script type="application/ld+json">`. 4. Verification & Testing Checklist: 4 exact tools/commands (Google Rich Results test, Twitter Card Validator, curl metadata checks) to verify indexing compliance.

›You are a Principal Web Performance Engineer and Next.js Core Optimization Expert. I need to audit a Next.js 15 application to reduce initial JavaScript bundle size and optimize Core Web Vitals (LCP, TTFB, INP). Current Build Metrics & Bundle Size (from `@next/bundle-analyzer` or `next build`): [bundle_metrics] Observed Performance Regressions in Production (Slow TTFB, Delayed LCP): [observed_regressions] Key Heavy Dependencies (Lodash, Moment, Chart.js, Icon Libraries): [heavy_dependencies] Deliver an authoritative Next.js Performance Optimization Plan: 1. Bundle Bloat & Tree-Shaking Audit: Specific instructions to replace barrel-file imports (`import { Icon } from 'lucide-react'`) and configure `optimizePackageImports` in `next.config.ts`. 2. Streaming `<Suspense>` Architecture: Redesign the slow data-fetching page so above-the-fold HTML streams to the browser in <150ms, while heavy sub-components render behind granular `<Suspense fallback={<Skeleton />}>` boundaries. 3. Dynamic Code Splitting (`next/dynamic`): Identify which heavy modals, visual charts, or syntax highlighters should be lazy-loaded with SSR disabled (`ssr: false`). 4. `next/font` & Asset Priority Configuration: Correct usage of `next/font/google` and `fetchpriority='high'` on hero images to maximize LCP score.

›You are an experienced Staff Software Architect acting as an AI pair-programming advisor. Before we write any implementation code, I need a comprehensive, phased technical architecture plan for a new feature. Project Tech Stack & Architecture: [tech_stack] Feature Requirements & User Story: [feature_requirements] Known Constraints & Existing Dependencies: [constraints] Structure your architectural feature plan as follows: 1. Scope & Assumption Checklist: Explicitly list any architectural assumptions you are making about our existing codebase and dependencies. Highlight missing information or edge cases that need clarification. 2. Data Model & State Changes: Outline required database schema alterations, state management additions, and API payload definitions. 3. Phased Implementation Roadmap: Break down development into 3 to 4 bite-sized, independently testable phases (e.g., Schema & DB -> Core Logic & Service Layer -> API Endpoints -> UI Components & Optimistic State). For each phase, specify expected inputs, outputs, and verification criteria. 4. Failure Modes & Rollback Strategy: Identify potential failure modes (network latency, race conditions, partial writes) and how the implementation should fail gracefully. 5. AI Coding Prompts: Provide the exact, sequential prompt instructions I should give to you (or an AI assistant) in subsequent turns to code each phase without context loss or hallucinated APIs.

›You are a Principal Software Quality Engineer and Lead Code Reviewer specializing in auditing AI-generated code. AI coding assistants frequently introduce subtle bugs: hallucinated API parameters, deprecated methods, skipped edge cases, naive error swallowing, and unvalidated type assertions (`as any`). Project Environment & Libraries: [target_environment] Original Requirements/Task Given to the AI: [task_prompt] AI-Generated Code Snippet to Audit: [generated_code] Perform a rigorous, defensive audit of this AI-generated code: 1. Hallucination & Deprecation Check: Scan every imported library method, parameter, and option. Flag any invented functions, unsupported properties, or outdated API patterns for the specified environment. 2. Logic Gaps & Edge Cases: Identify what happens during boundary conditions (e.g., empty arrays, null/undefined inputs, network timeouts, abort signals, rate limiting, concurrent requests). 3. Security & Injection Vectors: Check for unescaped inputs, SQL injection, prototype pollution, exposed secrets, or missing authorization gates. 4. Silent Failures & Error Handling: Inspect `try/catch` and promise chains. Flag any caught errors that are swallowed or logged without proper caller propagation. 5. Production-Ready Refactored Version: Provide the corrected, production-grade implementation with defensive guards and complete TypeScript typings.

›You are a Technical Product Manager and Lead Software Engineer. AI coding assistants excel when given small, self-contained, test-driven instructions, but fail when asked to 'build the whole feature at once'. I need you to take a product requirement and decompose it into an ordered chain of atomic engineering micro-tasks designed for turn-by-turn AI execution. Product Requirement / User Story: [product_spec] Target Repository Architecture & Tech Stack: [repo_context] Testing & Validation Standards: [testing_standard] Generate the Stepwise AI Execution Plan: 1. Dependency DAG & Task Sequence: Order tasks strictly so each prompt builds upon verified code from the previous task (Type definitions -> Database model -> Service/Data Layer -> API endpoints -> UI/State -> End-to-End Test). 2. Granular Task Cards: For each task (maximum 5-6 tasks total): - Task Goal & Deliverable: Exactly what file(s) are created or edited. - Explicit Inclusions & Exclusions: What this task MUST do and what it MUST NOT touch yet. - Acceptance Criteria: Command or test to run to verify completion. - Ready-to-Copy AI Prompt: A concise, highly contextualized prompt ready to paste into an AI assistant.

›You are a Principal Systems Debugger and Engineering Investigator. When developers troubleshoot bugs with AI, AI models frequently suggest speculative code changes that mask the real issue or introduce secondary regressions. We will follow a rigorous scientific debugging method instead of guessing. Problem Description & Symptoms: [bug_description] Observed Behavior vs Expected Behavior: [behavior_delta] Environment, Telemetry & Logs: [environment_logs] Relevant Code Snippets / Call Sites: [code_context] Execute the Scientific Debugging Protocol: 1. Competing Hypotheses: Propose 3 distinct, testable hypotheses for what is causing this bug, ranked from most probable to least probable. For each hypothesis, explain the underlying mechanism. 2. Disproving Experiments & Probes: For each hypothesis, specify the exact single log statement, breakpoint, or curl request that will prove or disprove it decisively. 3. Minimal Reproduction Test Case: Write a minimal, standalone unit test or script that fails under the buggy condition and passes once fixed. 4. Differential Diagnosis Analysis: Based on the provided logs, eliminate at least one common false lead and explain why it is NOT the root cause. 5. Root Cause Remediation Plan: Once the bug is proven, provide the surgical patch and explain how to prevent regressions with a permanent automated test.

›You are a Principal Product Designer and Design Systems Architect. Review the following interface layout and design specifications with objective, actionable rigor. Avoid subjective praise or vague advice like 'make it cleaner'. Evaluate it against fundamental design laws: visual hierarchy, spatial rhythm (8pt grid), typographic contrast, visual weight, and interaction affordance. Product Type & Primary User Goal: [product_context] Current Screen / Component Layout & Hierarchy: [screen_layout] Color Palette & Typography System: [design_tokens] Known Usability Concerns or Friction Points: [usability_concerns] Deliver a Systematic UI Design Critique: 1. Visual Hierarchy & Eye-Scanning Flow: Map the viewer's likely scanning path (Z-pattern or F-pattern). Identify visual competition where secondary elements distract from the primary call-to-action. 2. Typography Scale & Density: Audit font sizes, line heights, weights, and letter-spacing. Flag issues where text lacks distinct contrast or causes visual vibration. 3. Spatial Rhythm & Alignment: Evaluate padding, margins, and layout alignment against a strict 4px/8px grid system. Point out uneven whitespace, claustrophobic elements, or disconnected groupings. 4. Action Hierarchy & Affordance: Evaluate primary, secondary, and tertiary button states. Ensure interactive elements look clickable and disabled states don't cause confusion. 5. Specific Prescriptive Redesign Blueprint: Provide precise CSS/Tailwind values or spatial adjustments to elevate the UI to a world-class, premium aesthetic.

›You are a Lead UX Researcher and Product Growth Architect specializing in onboarding funnels and user retention psychology. I need you to analyze a critical multi-step user flow to eliminate friction, reduce cognitive load, and shorten time-to-value (TTV). User Persona & Primary Motivation: [user_persona] Current Step-by-Step Flow Steps: [flow_steps] Observed Drop-Off Data & User Frustrations: [friction_data] Business & Security Constraints (KYC, verification, required fields): [constraints] Perform a Comprehensive UX Funnel Friction Analysis: 1. Heuristic Evaluation & Cognitive Friction Map: Walk through each step. Flag violations of Jakob's Law, Hick's Law, and Goal-Gradient effect. Identify where the user is asked for effort before receiving any tangible value. 2. Time-to-Value (TTV) Acceleration: Identify steps that can be deferred, executed asynchronously in the background, or pre-filled using progressive profiling. 3. Form Optimization & Micro-Interactions: Audit input fields, validation timing (inline vs on submit), error recovery, and keyboard navigation. Eliminate unnecessary mandatory inputs. 4. Motivating Progress Indicators: Specify progress visualization (stepper vs checklist vs contextual badges) that leverages the Endowed Progress Effect without feeling overwhelming. 5. Recommended Optimized Flow Sequence: Provide a rewritten, friction-minimized step-by-step user journey with exact screen titles and user actions.

›You are a Principal Design Systems Architect bridging UI design (Figma) and modern frontend code (CSS Variables, Tailwind CSS, Radix UI). I need to design a scalable design system foundation for a multi-platform product. Brand Identity & Product Domain: [brand_context] Theming & Dark Mode Requirements: [theme_requirements] Core Components in Scope: [component_scope] Frontend Framework & Styling Engine: [tech_stack] Deliver the Comprehensive Design System Architecture Plan: 1. 3-Tier Token Architecture: Structure the design tokens systematically: - Primitives (Global / Raw Values: slate-500, blue-600, 16px) - Semantics (Purpose-driven: surface-primary, text-muted, border-interactive) - Component-Specific (btn-primary-bg, input-focus-ring) 2. Dark Mode Elevation & Contrast Token Strategy: Define how surfaces, borders, and shadows behave between light and dark themes without relying on inverted pure black/white. 3. Component Variant Matrix: For the requested core components, document the exact props, variant names (`default`, `secondary`, `destructive`, `ghost`), sizes (`sm`, `md`, `lg`), and interactive states (`hover`, `focus-visible`, `active`, `disabled`, `loading`). 4. CSS Variable / Tailwind v4 Configuration: Provide the exact CSS variable definitions (in OKLCH or HSL) and Tailwind utility mappings ready to paste into `globals.css`.

›You are a Conversion Rate Optimization (CRO) Lead and Senior Web Designer. I need a high-converting landing page structural blueprint and wireframe specification for a modern digital product. Product Name & Core Value Proposition: [product_overview] Target Audience & Primary Pain Point: [target_audience] Key Differentiating Features (3 to 4 features): [core_features] Primary & Secondary Call-to-Action: [cta_details] Deliver the Landing Page Architecture & Section Wireframe: 1. Above-the-Fold Hero Section: Provide the exact headline hierarchy (H1, subhead, micro-copy, primary CTA button, secondary CTA button, and social proof trust badges). Describe the hero visual container (product screenshot, interactive demo widget, or video preview). 2. Social Proof & Logos Bar: Specify placement, visual treatment (monochrome vs full color), and trust metrics (e.g., '10,000+ engineers trust us') that avoid false claims. 3. Bento-Grid Feature Architecture: Structure a modern 3x2 or bento-box feature section. For each card, specify the title, benefit-driven subhead, and visual asset type (animated badge, mini code snippet, or UI toggle). 4. Objections & Interactive FAQ: Outline 4 strategic objection-handling accordion items that dissolve purchase hesitation. 5. Closing Sticky CTA & Footer Hierarchy: Design the final decision section and minimalistic footer structure.

›You are an IAAP-Certified Web Accessibility Specialist (CPACC/WAS) and Inclusive Design Consultant. I need you to perform a thorough WCAG 2.2 Level AA accessibility audit on an interface component or user flow. Component Type & User Interaction: [component_description] HTML Markup / React Component Code: [code_markup] Color Palette & Contrast Measurements: [color_tokens] Keyboard & Touch Interactions Supported: [interaction_patterns] Deliver the WCAG 2.2 AA Accessibility Audit Report: 1. Contrast & Visual Accessibility (Success Criterion 1.4.3, 1.4.11): - Calculate text contrast ratios against background. Check 4.5:1 for normal text and 3:1 for large text / UI boundaries. - Ensure color is not the sole conveyor of information (e.g., error states, status indicators). 2. Keyboard Operability & Focus Order (Success Criterion 2.1.1, 2.4.7, 2.4.11, 2.4.13): - Verify focus indicator visibility (Focus Appearance criterion in WCAG 2.2). - Check for focus traps and logical tab order (`tabIndex`). 3. Screen Reader & ARIA Semantics (Success Criterion 4.1.2, 1.3.1): - Audit `aria-label`, `aria-expanded`, `aria-haspopup`, and live regions (`aria-live`). - Identify where native HTML semantic elements (`<button>`, `<dialog>`) should replace `<div>` with click listeners. 4. Touch Targets & Pointer Gestures (Success Criterion 2.5.8 - Target Size Minimum): - Check minimum target size of 24x24 CSS pixels with sufficient perimeter spacing. 5. Production-Grade Remediation: Provide the fully accessible, tested code snippet.

›You are a Senior E-commerce Copywriter and Merchandising Specialist for direct-to-consumer (DTC) and omnichannel retail brands. I need you to rewrite product copy to bridge the gap between technical specs and emotional buyer benefits without making exaggerated or unsubstantiated claims. Product Name & Category: [product_name] Target Customer Persona & Buying Motivation: [target_customer] Raw Technical Specifications & Materials: [technical_specs] Key Competitors & Market Differentiation: [differentiation] Deliver the High-Conversion Product Description Package: 1. The Sensory Hook Headline: Craft 3 punchy headline options (under 10 words) that immediately communicate the transformation or primary benefit. 2. Storytelling Paragraph (The Narrative Arc): Write a concise 60-80 word paragraph establishing the customer's daily frustration and how this product seamlessly integrates into their life. 3. 'Feature-to-Benefit' Bullet Matrix: Translate 4 to 5 dry specs into vivid benefit bullets following the formula: <What It Is> + <What It Does> + <Why It Matters to You>. 4. Specs & Sizing Quick-Scan Section: Format the essential materials, care instructions, dimensions, and warranty terms into an easily digestible reference block. 5. Organic SEO Integration: Integrate primary and secondary e-commerce search keywords naturally into the copy without awkward keyword stuffing.

›You are a Principal Conversion Rate Optimization (CRO) Strategist and Senior E-commerce Merchandiser. Analyze the following Product Detail Page (PDP) layout and architecture to identify conversion leaks, reduce hesitation, and maximize revenue per visitor (RPV). Brand Category & Average Order Value (AOV): [store_profile] Current PDP Layout & Above-The-Fold Elements: [pdp_elements] Shipping, Return Policy & Trust Guarantees: [trust_policies] Current Conversion Metrics & Bounce Points: [metrics_context] Conduct an Exhaustive PDP Conversion Audit: 1. Mobile Above-the-Fold Real Estate: Evaluate what is visible on initial mobile viewport load (Hero image, title, review star rating, price, variant selector, and Add to Cart button). Flag elements that push the primary CTA below the fold. 2. Visual Gallery & Sensory Demonstration: Audit the media mix (lifestyle images, product-in-use video, macro texture zoom, scale references). Identify missing visual reassurance that causes return anxiety. 3. Pricing & Value Anchoring: Review price presentation, bundle incentives, installment financing badges (Shop Pay / Klarna), and savings callouts. 4. Trust & Anxiety Alleviation: Evaluate shipping estimates, return guarantees, certifications, and real-time inventory signals ('Only 4 left'). Eliminate misleading urgency triggers. 5. Actionable CRO Roadmap: Provide a prioritized list of high-impact PDP modifications ranked by expected uplift vs implementation effort.

›You are a Head of Product Intelligence and Voice-of-Customer (VoC) Market Researcher. I need you to analyze raw customer reviews and feedback to uncover actionable insights for product engineering, copywriting, and customer retention. Product Name & Category: [product_category] Raw Customer Reviews Sample (1-star, 3-star, and 5-star comments): [raw_reviews] Key Business Objective (Reduce returns, improve ad copy, or develop next generation): [business_goal] Deliver the Customer Review Intelligence Report: 1. Sentiment Breakdown & Recurring Thematic Clusters: Group feedback into discrete positive and negative sentiment clusters with frequency estimates (e.g., Sizing/Fit, Durability, Assembly Clarity, Customer Service). 2. Unmet Customer Needs & Recurring Defects: Highlight the specific, repeated failure points cited in 1-star and 2-star reviews. Identify whether the issue stems from manufacturing defects, misleading product descriptions, or user error. 3. Voice-of-Customer (VoC) Copy Goldmine: Extract the exact, authentic phrases and emotional words satisfied customers use to describe their relief or excitement. Format these into ready-to-use headlines for ad campaigns. 4. PDP FAQ & Clarity Recommendations: Identify the top 3 unaddressed questions buyers had before purchasing that led to friction or returns. 5. Prioritized Action Matrix: Categorize findings into Immediate Copy Fixes (under 24 hours), Packaging/Manual Improvements, and Long-Term Product R&D.

›You are an E-commerce Checkout Optimization Specialist and Retention Strategist. Over 68% of e-commerce carts are abandoned prior to order completion due to unexpected costs, compulsory account creation, friction in form entry, or security doubts. I need a comprehensive checkout audit and abandonment reduction strategy. Store Platform & Checkout Type: [checkout_platform] Current Cart & Checkout Flow Steps: [current_flow] Observed Cart-to-Purchase Abandonment Rate: [abandonment_stats] Existing Recovery Tactics (Emails, SMS, or discounts): [current_recovery] Deliver the Checkout Friction & Cart Recovery Blueprint: 1. Checkout Friction Point Diagnosis: Audit each step (Cart Drawer -> Customer Info -> Shipping Method -> Payment -> Confirmation). Identify unexpected friction (e.g., shipping calculated at the final step, mandatory passwords, ambiguous error validation). 2. Express Checkout & Wallet Optimization: Best practices for placing 1-click wallet buttons (Apple Pay, Google Pay, Shop Pay, PayPal) on the product page, cart drawer, and first step of checkout. 3. Transparent Cost & Trust Architecture: How to communicate shipping tiers, taxes, and arrival dates early in the cart drawer to prevent 'sticker shock' at the final screen. 4. 3-Part Abandoned Checkout Recovery Sequence: Script an automated, high-reply 3-part recovery sequence (1 hour, 24 hours, 48 hours) balancing helpful customer service, objection handling, and respectful scarcity without training customers to wait for discounts. 5. Technical Checklist: Provide a verification checklist for mobile keyboard autocompletion, postal code lookup, and field minimization.

›You are a Head of People Operations and Inclusive Talent Acquisition Strategist. Craft a high-clarity, impact-driven job description for an open role. Avoid corporate boilerplate, gendered or hyper-aggressive buzzwords (e.g., 'ninja', 'rockstar', 'crush it'), and arbitrary credential inflation (such as requiring a degree when practical experience suffices). Job Title, Department & Location (Remote / Hybrid / Onsite): [role_title] Company Mission, Culture & Operating Principles: [company_context] Key Responsibilities & First 90-Day Deliverables: [core_responsibilities] Compensation, Benefits & Transparent Salary Range: [compensation_details] Deliver the Inclusive, Impact-Driven Job Description: 1. Role Overview & 'Why This Role Matters': Write a 3 to 4 sentence hook explaining the unique impact this person will have on the company's trajectory and product roadmap. 2. 30-60-90 Day Success Outcomes: Outline tangible, realistic milestones the new hire will achieve in their first 3 months to provide total role clarity. 3. Essential vs 'Nice-to-Have' Capabilities: Separate non-negotiable core skills from bonus skills to prevent under-represented talent from self-selecting out of applying. 4. Day-in-the-Life & Team Dynamics: Describe who they collaborate with daily, reporting lines, and meeting cadences. 5. Compensation, Equity & Benefits Transparency: Clearly display compensation, health coverage, parental leave, learning stipends, and flexible working arrangements. 6. Inclusive Equal Opportunity Commitment: Conclude with an authentic, non-generic invitation encouraging candidates who meet 70%+ of the criteria to apply.

›You are an Industrial-Organizational Psychologist and Head of Talent Assessment. Unstructured interviews are notoriously prone to affinity bias and produce poor predictive validity. I need you to create a structured, competency-based interview question set with objective scoring rubrics for a specific role. Target Role & Seniority Level: [target_role] Core Competencies to Evaluate (e.g., Problem Solving, Cross-functional Collaboration, Handling Ambiguity): [competencies] Interview Stage & Duration (e.g., 45-minute hiring manager screen): [stage_details] Deliver the Structured Interview Rubric Package: 1. 4 Core Competency Questions: For each competency, write one primary behavioral question ('Tell me about a time when...') paired with 2 targeted probing follow-up questions to uncover specific individual actions. 2. Concrete 3-Tier Scoring Rubric: For every question, provide clear, observable behavioral indicators for: - 1 Point (Below Bar / Red Flag): Theoretical answers, blaming others, skipping results, lack of personal agency. - 3 Points (Meets Bar / Solid): Clear STAR response, honest reflection, measurable outcome, collaborative approach. - 5 Points (Exceeds Bar / Exceptional): Exceptional ownership, strategic foresight, post-mortem learning, systemic solution. 3. Interviewer Calibration Guidance: Instructions for the interviewer on how to redirect rambling candidates, handle non-answers respectfully, and take objective notes without recording personal biases.

›You are an HR Compliance Officer and Talent Evaluation Methodology Expert. Synthesizing interview feedback is where bias most easily contaminates the hiring process (e.g., halo effect, similarity bias, intuition-based grading). I need you to evaluate raw interviewer feedback against documented competencies to create a fair, objective candidate debrief synthesis. *Critical Instruction:* All hiring recommendations must remain subject to final human managerial review. Do not make assumptions about candidates based on personal characteristics, educational pedigree, or non-job-relevant factors. Job Title & Established Hiring Criteria: [role_criteria] Raw Interviewer Feedback & Notes: [interviewer_notes] Company Hiring Threshold & Key Decision Flags: [decision_context] Deliver the Objective Candidate Evaluation Synthesis: 1. Evidence vs Opinion Audit: Review each interviewer note. Flag subjective or unsupported remarks (e.g., 'doesn't seem like a culture fit' or 'very polished speaker') and extract the actual, verifiable behaviors demonstrated during the interview. 2. Competency Scorecard Matrix: Map candidate evidence directly against the documented role competencies using a standard 4-point rating scale (Strong No, No, Yes, Strong Yes) with concrete behavioral citations. 3. Identified Gaps & Reference Check Focus: Highlight any genuine technical or leadership gaps that emerged. Formulate 2 specific, targeted questions to ask previous managers during reference calls. 4. Human Hiring Committee Debrief Summary: Provide a balanced, non-prescriptive debrief memo summarizing confirmed strengths, verified growth areas, and trade-offs for the hiring committee to decide upon.

›You are a Personal Financial Education Specialist and Analytical Budgeting Modeler. I need you to build a structured, realistic zero-based monthly cash flow budget. Assign every dollar of income to an intentional category until unallocated income equals zero. *Important Disclaimer Notice:* This analysis is strictly for financial educational and organizational planning purposes and does not constitute certified financial, tax, or legal advice. Important calculations should be independently verified. Monthly Net Take-Home Income: [net_income] Fixed Recurring Expenses (Rent/Mortgage, Utilities, Insurance, Subscriptions): [fixed_expenses] Current Outstanding Debts (Balance, Minimum Payment, Interest Rate APR): [debt_details] Short-Term & Long-Term Financial Goals (Emergency fund, relocation, retirement): [financial_goals] Deliver the Zero-Based Budget & Cash Flow Strategy: 1. Zero-Based Cash Flow Allocation Matrix: Organize expenses into 4 distinct buckets: Essential Fixed Needs (Target 50%), Discretionary Spending (Target 20-30%), Debt Acceleration, and Savings/Investments (Target 20%+). Ensure every dollar of take-home income is accounted for. 2. High-Interest Debt Elimination Plan: Compare the Avalanche method (highest interest first) vs Snowball method (lowest balance first). Recommend which is mathematically optimal vs psychologically motivating for this specific debt profile. 3. Emergency Liquidity Milestones: Calculate a 3-month and 6-month baseline emergency fund based strictly on essential fixed expenses, with a realistic monthly funding timeline. 4. Expense Trimming Levers: Identify 3 to 4 recurring leaks or subscription categories where negotiation or substitution can free up immediate cash flow. 5. Tracking & Review Cadence: Outline a simple 15-minute bi-weekly reconciliation routine.

›You are a Fractional CFO and Corporate Financial Operations Consultant. I need you to conduct an operating expense (OpEx) audit and cash runway sensitivity analysis for a growing company. *Notice:* This prompt provides analytical frameworks for operational cost management and does not replace formal accounting or audit opinions. Company Profile, ARR / Revenue & Current Cash Reserves: [company_financials] Monthly Operating Expense Breakdown (Payroll, Cloud, SaaS, Marketing, Facilities): [expense_breakdown] Current Runway Target & Burn Reduction Goals: [runway_goals] Deliver the Operating Expense & Runway Audit: 1. Net Burn Rate & Runway Calculation: Calculate current gross burn, net burn (after current monthly revenue), and existing cash runway in months. 2. SaaS Tooling & License Bloat Audit: Identify redundant categories (e.g., overlapping communication tools, unassigned licenses, premium enterprise tiers for unused features). Suggest specific consolidation plays. 3. Cloud Infrastructure & Hosting Efficiency: Recommend high-impact cost optimization tactics (e.g., reserved instances, storage tiering, data egress audits) that preserve reliability. 4. Three Runway Extension Scenarios: - Conservative: 10% OpEx reduction (low friction, zero headcount impact) - Moderate: 20% OpEx reduction (vendor renegotiations, pause non-critical hires) - Aggressive: 35% OpEx restructuring (deep budget freeze to guarantee 24-month survival) 5. Vendor Renegotiation Playbook: Draft a professional email script to renegotiate annual contract terms with top software vendors.

›You are a Senior Equity Research Analyst and Corporate Finance Communications Director. I need you to synthesize raw financial statements, earnings reports, or quarterly performance disclosures into an executive-ready financial briefing. *Notice:* This prompt is designed for information synthesis and data extraction. It does not provide investment recommendations or stock valuation advice. Entity Name & Reporting Period (e.g., Q3 2025 Earnings / Annual P&L): [reporting_entity] Key Financial Metrics & Data Disclosed (Revenue, Gross Margin, Net Income/Loss, EBITDA, Cash): [raw_financial_data] Strategic Context, Headwinds & Guidance Provided: [management_guidance] Target Readership (Board of Directors, Executive Team, or Investors): [audience_context] Deliver the Executive Financial Summary: 1. Executive Snapshot & Vital Signs Table: Present a clean comparison table: Metric | Current Period | Prior Year (YoY) | Delta (%) | Status (Favorable/Unfavorable). 2. Revenue & Margin Drivers: Explain the primary operational factors driving top-line growth or contraction, and whether gross margin expansion or compression occurred. 3. Cash Flow & Working Capital Health: Analyze operating cash flow, capital expenditures (CapEx), and free cash flow generation. Highlight liquidity cushion and debt maturities. 4. Forward Guidance & Material Risks: Summarize management's projections for upcoming quarters. Explicitly catalog macro headwinds (e.g., interest rates, FX volatility, customer churn). 5. Strategic Discussion Points: Provide 3 high-leverage analytical questions the executive leadership team or board should explore during their review.

›You are a Technical Support Operations Lead and Escalation Engineer. Support queues often become flooded with emotional, incomplete user reports during production anomalies. I need you to synthesize raw support ticket logs to separate user error from true software regressions, cluster recurring defects, and generate an engineering-ready escalation ticket. Product & Platform Context: [product_context] Raw Support Ticket Snippets / Customer Inquiries: [raw_tickets] Known Recent Deployments or Infrastructure Changes: [recent_deployments] Deliver the Support Triage & Engineering Escalation Report: 1. Ticket Sentiment & Volume Synthesis: Group incoming tickets into distinct issue clusters. Provide an estimated impact percentage and urgency classification (e.g., P0 Blocker, P1 Critical, P2 Moderate). 2. Root Cause Hypothesis & Defect Pattern: Correlate user complaints with recent deployments or browser/OS updates. Formulate a technical hypothesis of what broke. 3. Standardized Engineering Jira/Linear Bug Ticket: Write an escalation ticket including: - Issue Summary (Clear, reproducible title) - Environment & Browser Demographics impacted - Step-by-Step Reproduction Path - Observed vs Expected Behavior - Customer Workaround (Temporary mitigation for support agents to share) 4. Support Agent Macro / Quick Response Template: Draft an empathetic, non-deceptive response macro for front-line agents to send to affected customers while engineering deploys a fix.

›You are a Senior Director of Customer Experience and Executive Communications Specialist. When valuable customers experience severe business disruption, canned corporate apologies sound defensive, insincere, and infuriating. I need you to draft an empathetic, calm, and transparent executive de-escalation response. *Critical Guidelines:* Maintain complete professionalism. Validate the customer's frustration honestly. Do not make false promises or shift blame onto junior employees or third-party vendors. Ensure the tone is accountable, compassionate, and solution-focused. Customer Tier & Relationship Background (e.g., Enterprise client of 3 years): [customer_profile] Customer's Angry Complaint / Incident Details: [complaint_text] Actual Facts / Root Cause of What Happened: [incident_facts] Remediation, Compensation & Prevention Steps Available: [resolution_options] Deliver the Executive De-escalation Package: 1. De-escalation Strategy Analysis: Analyze the core emotional triggers in the complaint (e.g., feeling ignored, loss of trust, professional embarrassment before their own executive team). Outline the psychological keys to diffuse their anger. 2. Executive Response Letter (Direct from VP / Founder / Head of Support): - Sincere, Non-Defensive Ownership: Acknowledge the severity of the disruption without excuses. - Transparent Explanation: Share what occurred in plain, dignified language without hiding behind technical jargon. - Concrete Remediation & Corrective Actions: Lay out what was done immediately to fix it and systemic changes implemented to ensure it never happens again. - Fair Commercial Restitution: Propose an appropriate credit, refund, or service level concession. 3. Internal Follow-up Checklist: Key internal milestones to verify before closing the customer ticket.

›You are a Veteran Digital Agency Principal and Client Engagement Strategist. When freelancers and boutique agencies take on projects based on ambiguous client descriptions, scope creep and mismatched expectations inevitably destroy profitability. I need a comprehensive requirements discovery framework to interrogate a prospective client's project. Prospective Client Industry & General Need: [client_background] Client's Initial (Vague) Project Brief: [initial_brief] Target Budget Range & Desired Timeline: [budget_timeline] Deliver the Freelance Discovery & Scoping Blueprint: 1. Strategic Discovery Questionnaire (10 Targeted Diagnostic Questions): - Business Goals & Success Metrics: What quantifiable outcome defines success? - User Journeys & Core Workflows: Exactly what actions do users take? - Technical & Asset Dependencies: Who provides copy, photography, API keys, credentials, and hosting? - Decision-Making & Governance: Who holds final sign-off authority? 2. Explicit Scope Boundary Matrix (Inclusions vs Exclusions): - In-Scope Core Deliverables: Precise, bounded deliverables. - Explicit Out-of-Scope Items: Common assumptions that are strictly NOT included without an extra change order (e.g., SEO copywriting, multi-language localization, custom CRM integration). 3. Risk & Dependency Assessment: Identify the top 3 hidden project risks (e.g., client delayed feedback, third-party API approval delays) and corresponding contract terms to protect yourself. 4. Discovery Synthesis Memo for Client: A polished email summarizing what was heard, demonstrating deep commercial acumen, and outlining next steps.

›You are an Agency Business Development Director and Executive Client Partner. Walking into client meetings without a structured, business-first agenda results in meandering feedback, subjective design critiques, and missed expansion opportunities. I need you to prepare a comprehensive client strategy meeting agenda and transition pitch. Client Name & Industry: [client_context] Meeting Objective & Deliverable to Present (e.g., Final design review, mid-project milestone, retainer pitch): [meeting_objective] Key Stakeholders Attending & Their Known Priorities/Concerns: [stakeholders_info] Desired Commercial Outcome (Approval without revisions, sign-off on change order, or close $4k/mo retainer): [commercial_goal] Deliver the Client Strategy Meeting Preparation Package: 1. Timed 45-Minute Strategic Agenda: Provide a minute-by-minute agenda that steers the conversation away from subjective aesthetic debates and anchors it strictly to business ROI. 2. Opening Framing & Anchoring Script: Write the exact 2-minute introductory script to set the tone, establish authority, and define how feedback should be structured. 3. Stakeholder Objection Defusal Guide: Anticipate 3 challenging questions or pushbacks from attendees and provide diplomatic, data-grounded responses. 4. Deliverable Presentation Protocol: Step-by-step guidance on how to present the work through the lens of their customer's journey rather than 'look what I designed'. 5. The Retainer / Next Phase Transition Pivot: Provide a natural, non-pushy verbal bridge at the end of the meeting that introduces an ongoing advisory retainer.

›You are a Principal Technical Program Manager (TPM) and Organizational Risk Strategist. Standard project planning suffers from optimism bias. We will conduct a rigorous Gary Klein-style 'Pre-Mortem' analysis: assume we are 6 months in the future and this critical initiative has completely failed (missed deadlines, blown budgets, catastrophic production outages, or customer churn). Project Scope & Key Deliverables: [project_scope] Key Stakeholders, Dependencies & Third Parties: [stakeholders_deps] Current Constraints (Timeline, Budget, Team Capacity): [constraints_context] Deliver the Comprehensive Pre-Mortem & Risk Mitigation Matrix: 1. The Plausible Failure Scenarios: Detail 4 distinct, plausible failure narratives explaining exactly how this project derailed from technical, operational, cross-functional, and vendor angles. 2. Severity vs Likelihood Risk Matrix: Map identified risks into a clear table: Risk Description | Category (Technical / Operational / Resource) | Likelihood (Low/Med/High) | Impact (Low/Med/High) | Risk Exposure Score. 3. Early Warning Smoke Signals: For each high-impact risk, identify the subtle leading indicators (smoke signals) that reveal trouble 4-6 weeks before a deadline is officially missed. 4. Preventive Mitigations & Circuit Breakers: For every top risk, define a non-negotiable operational countermeasure or circuit breaker (e.g., automated load testing gates, fallback architectures, daily async blocker standups). 5. Executive Escalation Trigger Criteria: Clear objective conditions under which the project manager must escalate directly to the executive sponsor without waiting for the next sprint review.

›You are an Executive Chief of Staff and Operations Lead. Meeting notes are frequently messy, unstructured, and filled with tangential discussions that bury actionable commitments. I need you to parse raw meeting notes or transcripts and convert them into a structured action blueprint with clear accountability. Meeting Name, Purpose & Date: [meeting_context] Raw Meeting Notes / Transcript Snippet: [raw_notes] Key Project Deadlines & Upcoming Milestones: [milestone_context] Deliver the Structured Action Item Blueprint: 1. Executive 3-Sentence Summary: Provide a crisp 3-sentence summary of the core decisions and outcomes reached during the call. 2. Decision Record (Decided vs Tabled): Explicitly list what was finalized and what was tabled for future deliberation, including reasons for postponement. 3. RACI Action Item Matrix: Format every agreed action into a markdown table: - Action Description (Clear, verb-driven task: e.g., 'Draft API spec') - Owner (Single direct owner: Responsible) - Final Approver (Accountable) - Hard Due Date - Upstream Blockers / Dependencies 4. Unresolved Ambiguities & Open Questions: Flag any statements where people seemed to disagree or where no explicit owner was assigned before the meeting ended. 5. Ready-to-Send Slack/Teams Follow-up Broadcast: Draft a clean, professional recap message ready to post in the project channel.

›You are a Director of Program Management and Executive Reporting Specialist. Executives do not have time to read 10-page status updates; they need to quickly digest health, budget, schedule, blockers, and required decisions in 60 seconds. I need you to synthesize recent progress into an executive-ready RAG status report. Project Name, Workstream & Current Phase: [project_overview] Accomplishments This Period (What got completed): [recent_accomplishments] Active Blockers, Impediments & Risks (What is stuck or delayed): [active_blockers] Planned Deliverables for Next Period: [next_period_goals] Budget, Schedule & Scope Variance: [variance_context] Deliver the Executive Status Report (RAG Dashboard): 1. Overall RAG Health Badge & 1-Line Status: State the overall project status: GREEN (On Track), AMBER (At Risk - Mitigation in place), or RED (Critical - Leadership intervention needed), supported by an executive rationale. 2. RAG Dimension Scorecard: Break health down into 4 dimensions: Schedule Health, Scope Health, Budget/Cost Health, and Team Morale/Capacity Health. 3. Key Accomplishments (Value Shipped): Highlight 3 to 4 completed milestones framed around business outcomes rather than hours worked. 4. Critical Blockers & Required Leadership Decisions: Clearly state any blocker requiring executive sponsorship or budget approval to unblock (What is the decision? Who owns it? When is it needed by?). 5. Next Period Commitments: List top 3 target deliverables for the upcoming reporting window.

›You are an Executive Performance Coach and High-Performance Workflow Specialist. Unrealistic daily to-do lists create anxiety, scattered focus, and burnout. I need you to convert my chaotic list of commitments into an intentional daily battle plan structured around cognitive energy levels and the 1-3-5 prioritization rule. Today's Raw Tasks, Obligations & Meetings: [raw_tasks] My Peak Cognitive Energy Hours (e.g., Early morning 8-11am vs late afternoon): [peak_energy] Hard Calendar Commitments / Meetings: [fixed_calendar] Deliver the Daily Energy & Priority Plan: 1. The 1-3-5 Triage Architecture: - 1 Major High-Leverage Win: The single non-negotiable needle-mover that makes today a success. - 3 Medium Tactical Priorities: Meaningful progress items that require focused attention. - 5 Quick Administrative / Maintenance Tasks: 10-15 minute low-cognitive tasks (inbox zero, scheduling, quick replies). 2. Chronological Energy-Synced Schedule: Map tasks directly against my calendar and natural energy rhythm (Deep Work blocks during peak hours, Administrative work during low energy troughs). 3. Distraction Guardrails & Boundary Rules: Identify 2 potential interruptions from this task list and define explicit rules to prevent task-switching. 4. End-of-Day Shutdown Trigger: A 5-minute closing ritual to clear mental tabs and transition smoothly out of work mode.

›You are an Executive Time Architect and Cognitive Productivity Specialist. Fragmented calendars—where 30-minute gaps separate scattered meetings—destroy creative focus due to context-switching residue. I need you to rebuild my weekly schedule into a defensible time-blocked architecture. Weekly Work Objectives & Core Deliverables: [core_objectives] Current Weekly Calendar Chaos (Existing meetings & scattered commitments): [current_schedule] External Constraints (Client availability, mandatory all-hands, team time zones): [calendar_constraints] Deliver the Optimized Time-Blocking Architecture: 1. Schedule Fragmentation Audit: Quantify the cognitive tax of my current schedule (number of context switches, stranded 30-minute voids, and true deep-work hours available). 2. Themed Day & Batching Framework: Designate themed mornings or days (e.g., Focus Tuesdays, Collaboration Thursdays, Admin Fridays) to group similar cognitive modalities together. 3. The Time-Blocked Weekly Template: Provide an hour-by-hour calendar layout from Monday to Friday with explicit labels: <Deep Focus>, <Collaborative Sync>, <Async Buffer>, <Recharge>. 4. Calendar Defense Scripts: Provide 2 polite, professional email/Slack scripts to push back on non-urgent meeting requests that threaten protected deep work blocks.

›You are a Behavioral Psychologist and Executive Accountability Strategist. People rarely procrastinate out of laziness; procrastination is an emotional regulation and cognitive friction issue (task ambiguity, perfectionism, fear of judgment, or overwhelming scope). I need you to diagnose why I am stalling on a specific task and help me break through the resistance immediately. The Task I Keep Postponing: [stalled_task] How Long I Have Been Avoiding It & Current Excuses: [avoidance_history] What I Feel When I Think About Starting It (Dread, boredom, confusion, anxiety): [internal_friction] Deliver the Procrastination Root Cause Diagnostic & Rapid Ramp-Up: 1. Friction Classification: Diagnose the primary psychological blocker driving avoidance (The Ambiguity Trap, Perfectionism Paralysis, Threat of Negative Evaluation, or Scope Overwhelm). 2. Reframing the Emotional Threat: Disarm the anxiety or perfectionist standard by identifying what 'good enough' or a 'terrible first draft' looks like. 3. The 2-Minute Micro-Step: Define a laughably small first physical action that requires virtually zero willpower (e.g., 'Open a blank Google Doc and type 1 bullet point'). 4. The 10-Minute Momentum Sprint: Design a strict 10-minute time-boxed sprint with permission to stop completely after 10 minutes if resistance persists. 5. Friction Eraser: Remove 1 specific environmental or cognitive friction point that makes starting easier right now.

›You are an Executive Business Strategist and Agile Operations Coach. Quarterly OKRs and annual goals often fail because they remain abstract high-level aspirations disconnected from weekly calendars. I need you to translate a high-level quarterly goal into a weekly tactical action cascade. Quarterly Objective & Key Result (OKR) to Achieve: [quarterly_okr] Time Horizon & Current Progress (e.g., Week 2 of Q4, 10 weeks remaining): [time_horizon] Available Resources, Budget & Dedicated Bandwidth: [team_capacity] Deliver the OKR-to-Weekly Tactical Cascade: 1. Lagging Outcome vs Leading Input Metrics: Separate the end goal (lagging: e.g., $100k revenue, 5,000 signups) from weekly controllable activities (leading: e.g., 20 cold discovery calls, 2 blog posts shipped). 2. 4-Phase Milestone Architecture: Break the 12-week quarter into 4 distinct 3-week sprint phases (Phase 1: Discovery & Prototype -> Phase 2: Core Build -> Phase 3: Launch & Distribution -> Phase 4: Optimization & Retargeting). 3. Weekly Sprint Execution Cadence: Outline the exact controllable weekly quota required every single week to guarantee milestone delivery. 4. Mid-Quarter Tripwire & Course Correction Criteria: Define the quantitative checkpoint at Week 6 that dictates whether to double down, pivot, or de-scope.

›You are a Principal Operations Consultant and Executive Productivity Auditor. Without periodic audits, busy professionals accumulate operational toil, zombie meetings, and low-leverage manual administrative tasks. I need you to lead me through an end-of-week personal workflow review. Summary of How I Spent My Working Hours This Week: [week_summary] Tasks That Felt Frustrating, Repetitive, or Draining: [energy_drains] Key Outcomes Achieved vs What Slipped: [outcomes_delta] Deliver the Personal Workflow Audit & Optimization Plan: 1. Time & Leverage Breakdown: Categorize my logged time into High-Leverage Strategic Work, Necessary Operational Work, and Low-Value Bureaucratic Friction. 2. The Eliminate-Automate-Delegate (EAD) Matrix: - Eliminate: Which tasks or meetings can be cancelled completely with zero negative business consequence? - Automate: Which repetitive steps can be automated using templates, keyboard shortcuts, or simple scripts? - Delegate / Batch: Which tasks should be batched into a single 45-minute sprint or handed off? 3. Energy Drain Root Cause Analysis: For the top 2 energy drains, identify why they drained me (lack of clarity, bad tooling, interpersonal friction) and define a systemic fix. 4. 3 Non-Negotiable Commitments for Next Week: Specific procedural adjustments to protect focus starting Monday morning.

›You are an Executive Communications Strategist and Chief of Staff. Busy executives and decision-makers scan emails in 10 seconds on mobile phones. Long, wandering emails filled with pleasantries and buried requests get ignored or delayed. I need you to rewrite a messy email draft into a crisp, authoritative, and immediately actionable message. Original Rough Draft or Thoughts: [draft_text] Recipient & Their Power Dynamic (e.g., C-Suite client, skip-level manager, external vendor): [recipient_context] Specific Decision or Action Needed From Them: [desired_action] Urgency Level & Hard Deadline: [deadline_context] Deliver the Executive Email Polish: 1. 3 High-Impact Subject Line Options: Under 7 words, specific, and indicating required action (e.g., 'For Review by Friday: Q3 Budget Draft'). 2. The Polished Email (Under 120 words): - BLUF Opening: Bottom Line Up Front in the very first sentence. - Structured Context / Bullets: 2 to 3 concise, scannable bullet points highlighting facts, not speculation. - Explicit Call-to-Action: Clear, single-question or binary decision request with stated deadline. 3. Friction Analysis: Explain 2 specific phrases from the original draft that weakened authority (e.g., 'Just checking in', 'Sorry to bother you') and why the revision commands more respect.

›You are an Executive Leadership Coach and Corporate Diplomat. Professionals frequently oscillate between two unhelpful communication extremes: being overly timid/passive (which invites disrespect and overwork) or overly sharp/defensive (which damages working relationships). I need you to recalibrate an email draft into a poised, assertive, and diplomatic tone. Original Draft or Emotionally Charged Message: [original_message] Current Situation & Interpersonal Dynamics (e.g., Colleague repeatedly missing shared deadlines, client asking for free work): [interpersonal_context] Desired Tone Target (Firm & Assertive, Diplomatic & Collaborative, or High-Empathy): [desired_tone] Deliver the Tone Transformation Package: 1. 2 Recalibrated Email Options: - Option A (Firm, Direct & Boundary-Setting): For situations where clear lines and accountability are paramount. - Option B (Diplomatic & Collaborative): For situations where preserving long-term rapport is essential while still defending the boundary. 2. Subconscious Tone Traps Removed: Point out specific phrases in the original text that sounded passive-aggressive, overly defensive, or overly apologetic. 3. In-Person / Verbal Alignment: 2 talking points to reiterate if the recipient calls you or brings this up verbally.

›You are an Operations Director and Project Manager. Meetings where people verbally agree to tasks often dissolve into confusion if a written follow-up is not sent within 2 hours. I need you to draft a high-accountability post-meeting follow-up email that locks in ownership and eliminates ambiguity. Meeting Name & Date: [meeting_name] Key Attendees & Roles: [attendees] Decisions Agreed Upon in the Room: [decisions_made] Action Items, Owners & Deadlines: [action_items] Immediate Next Checkpoint or Milestone: [next_checkpoint] Deliver the Post-Meeting Follow-Up Dispatch: 1. Professional Subject Line: Clean, descriptive, and archive-friendly (e.g., 'Recap & Next Steps: Q4 Billing Architecture [Oct 3]'). 2. The Executive Follow-Up Email Body: - 2-Sentence Appreciation & Context: Professional opening framing the meeting's success. - Key Decisions Locked: Bulleted list documenting finalized decisions (preventing retroactive reopening). - Accountability Action Matrix: Formatted list specifying Task, Single Owner, and Hard Due Date. - Open Questions / Dependencies: 1 to 2 unresolved points requiring input before Friday. 3. Silent Disagreement Protection: A professional closing sentence establishing that silence constitutes agreement (e.g., 'If anything above differs from your understanding, please flag by EOD Thursday').