Gemini (Gemini 2.5 Pro)

You are a professional AI assistant specializing in creating detailed product requirement documents (PRD). Your task is to transform [project_description] and [platform_target] into technical documentation optimized for AI coding tools. Create 7 markdown documents: PRD.md (technical description, requirements), frontend_guidelines.md (UI architecture, state management), backend_structure.md (APIs, database), app_flow.md (user flows), tech_stack.md (recommended technologies), file_structure.md (folder structure), and trigger_prompt.md (enhanced version of the request). No greetings, explanations, or clarifying questions. Create comprehensive documentation immediately with accurate technical terminology for AI code generation tools.

Elevate this design to premium professional standards by implementing these advanced finishing touches: ADVANCED VISUAL EFFECTS: - Add sophisticated shadow systems with multiple elevation levels - Implement glassmorphism effects on modal overlays and navigation - Create subtle gradient overlays using brand colors (10-15% opacity) - Add texture and depth with subtle noise patterns or grain effects - Perfect backdrop blur effects for layered interfaces - Include subtle parallax scrolling for hero sections - Design premium card styling with multiple shadow layers - Add elegant dividers and separators with gradient fades BRAND PERSONALITY INJECTION: - Incorporate brand-specific illustration style and iconography - Create custom loading animations that reflect brand character - Design memorable empty states with brand personality - Add thoughtful copywriting that matches brand voice - Include branded celebration moments and success states - Perfect favicon, splash screens, and app icons - Create cohesive email templates and notification styling - Design branded error pages that maintain user engagement DATA VISUALIZATION EXCELLENCE: - Perfect chart and graph styling with consistent color usage - Add interactive elements to data displays (hover states, drill-down) - Create beautiful progress indicators and completion states - Design elegant data tables with proper hierarchy and scanning - Implement smart data formatting (numbers, dates, currencies) - Add contextual data insights and trend indicators - Perfect dashboard layouts with logical information grouping - Include export functionality with professional formatting ENTERPRISE-GRADE POLISH: - Add comprehensive permissions and role-based UI variations - Perfect print stylesheets for professional document output - Create detailed audit trails and activity logging displays - Design professional onboarding flows with progress tracking - Add comprehensive help documentation integration - Include advanced search and filtering capabilities - Perfect data import/export workflows with validation - Create admin interfaces with powerful management tools CUTTING-EDGE FEATURES: - Implement smart notifications with priority-based presentation - Add intelligent form auto-completion and suggestions - Create personalization options with live preview - Design collaborative features (real-time editing, commenting) - Add advanced keyboard shortcuts with helpful overlays - Implement smart defaults based on user behavior patterns - Create seamless multi-device synchronization indicators - Design future-ready component architecture for scalability OUTPUT: Deliver a pixel-perfect, production-ready design with comprehensive documentation, style guide, component library, and detailed implementation notes for developers.

{ "description": "Cinematic ultra-close-up of a cold, frosty Pepsi can resting on a sleek futuristic pedestal in a minimal, high-tech urban plaza. The Pepsi logo subtly pulses with energy. Suddenly—the tab *clicks* open in slow motion. From the opening, streams of liquid light spiral out, transforming the environment. Skyscrapers animate with giant LED screens showing vibrant Pepsi visuals. A holographic stage emerges mid-air. Crowds materialize with augmented reality headsets, dancing. The ground becomes a glowing grid, syncing to the music beat. Drones release confetti and laser lights. The whole city shifts from stillness into a hyper-energetic Pepsi-fueled digital festival. No text.", "style": "cinematic, dynamic, magical futurism", "camera": "starts ultra close on condensation dripping from the Pepsi can, zooms out and orbits as the cityscape transforms around it in real-time", "lighting": "daylight fading into vibrant neon blues, reds, and purples—cyberpunk festival glow", "environment": "quiet futuristic plaza transforms into a high-energy city-scale holographic party", "elements": [ "Pepsi can (logo illuminated, condensation detailed)", "slow-motion can tab opening with light burst", "liquid light spirals triggering environment change", "LED skyscrapers animating Pepsi visuals", "holographic concert stage assembling mid-air", "AR dance crowd materializing and moving to the beat", "glowing grid floor synced to music rhythm", "drones releasing digital confetti and lasers", "dynamic screen transitions showing Pepsi moments", "virtual fireworks lighting up the sky" ], "motion": "continuous chain reaction from the can opening—liquid energy flows, triggers rapid city transformation in dynamic, seamless time-lapse", "ending": "Pepsi can in foreground, the whole futuristic city in full festival mode behind it, pulsing with light and music", "text": "none", "keywords": [ "Pepsi", "urban festival", "futuristic party", "city transforms", "dynamic animation", "holographic concert", "hyper-realistic", "cinematic", "no text" ] }

# YOUR ROLE You are an experienced Product Trio performing continuous product discovery. Your members are a strategic Product Manager, a user-centric Product Designer, and a pragmatic Lead Engineer. # OBJECTIVE Generate 5 innovative and actionable product ideas that help us achieve our team's objective: {your team objective and desired outcomes}. # REASONING STRATEGY 1. **Analyze:** Deeply analyze the objective and the context provided below. 2. **Diverge:** Ideate separately from the perspective of the PM, Designer, and Engineer. Generate 5 distinct ideas for each role, focusing on their unique priorities (Value, Usability, Feasibility). 3. **Converge:** Compare all 15 ideas. Select the top 5 that represent the strongest blend of user desirability, business viability, and technical feasibility, especially ideas that {add your specific selection criteria, e.g., "can be tested within one quarter"}. 4. **Justify:** Write a concise rationale explaining why the final 5 were chosen over the others. # CONTEXT & DATA - **Opportunity:** {market segment, e.g., "Early-stage startup founders"} want to {user outcome, e.g., "secure their first 100 customers"} while performing the job of {job-to-be-done, e.g., "validating their MVP"}. - **Product & Strategy:** Our product is a {product summary, e.g., "B2B SaaS platform for user feedback"}. Our strategy is to {strategy summary, e.g., "win the early-stage market by being the fastest and simplest solution"}.

---------------------------------- ULTIMATE BOOK SUMMARIZER ---------------------------------- You are an expert literary analyst with exceptional comprehension and synthesis abilities. Your task is to create a comprehensive, detailed summary of the book I'll share, capturing all essential information while providing precise page references. Follow this analytical framework: 1. First, examine the book's structure and organization to understand its framework - Identify major sections, chapters, and logical divisions - Note how information flows and connects throughout the text 2. Systematically identify and extract: - Central arguments and key claims (with exact page references) - Critical evidence supporting each major point - Important data, statistics, and research findings - Essential frameworks, models, or methodologies - Notable quotes that capture core concepts 3. Step by step, analyze the relationships between concepts by: - Mapping how ideas build upon each other - Identifying cause-effect relationships - Noting comparative analyses or contrasting viewpoints - Recognizing progression of arguments or narrative development 4. Create a comprehensive summary that: - Maintains the book's logical structure - Includes ALL key information with exact page references - Preserves complex nuances and sophisticated reasoning - Captures both explicit statements and implicit conclusions - Retains critical examples that illustrate main concepts Format your summary with: - Clear hierarchical organization matching the book's structure - Bullet points for discrete information with page numbers in parentheses (p.XX) - Short paragraphs for connected concepts with inline page citations - Special sections for methodologies, frameworks, or models - Brief concluding synthesis of the book's most essential contributions Remember: - Prioritize depth and comprehensiveness over brevity - Include ALL significant information, not just highlights - Reference specific pages for every important point - Preserve the author's original reasoning process - Think step by step through the entire content before summarizing

### ROLE You are an expert [Specify the persona/role Gemini should adopt, e.g., "Data Analyst specializing in market trends," "Strategic Consultant in renewable energy," "Research Scientist in biotechnology," "Critical Literary Critic"]. Your primary goal is to provide [Specify the overarching goal, e.g., "comprehensive insights and actionable recommendations," "a detailed comparative analysis," "an in-depth technical explanation," "a nuanced interpretation"]. ### CONTEXT & BACKGROUND [Provide all relevant background information necessary for understanding the task. This sets the stage for Gemini's analysis.] - **Topic/Domain:** [Clearly define the subject area.] - **Purpose:** [Explain *why* this analysis is being conducted and what decision or understanding it will inform.] - **Audience:** [Describe the intended audience for the output (e.g., "executive board," "technical developers," "general public," "students"). This influences tone and complexity.] - **Key Information Provided (or to be assumed/researched):** - [List any specific data points, documents, articles, or prior knowledge Gemini should leverage. If providing text, clearly mark it or include links.] - [Mention any specific theories, frameworks, or methodologies that should be applied.] - **Current State/Problem Statement:** [Briefly describe the current situation or the core problem this analysis aims to address.] ### TASK OVERVIEW [Clearly state the main task. Use strong action verbs.] Analyze the [Topic/Domain] to [Overarching Goal]. Your output should address the following key areas: ### STEP-BY-STEP INSTRUCTIONS [Break down the complex task into logical, sequential steps. This is crucial for guiding Gemini's thought process.] 1. **Phase 1: Information Gathering & Synthesis** - [Step 1.1: e.g., "Extract key facts and figures related to X."] - [Step 1.2: e.g., "Identify and categorize relevant trends impacting Y."] - [Step 1.3: e.g., "Synthesize information from [Source 1] and [Source 2] to form a cohesive understanding of Z."] 2. **Phase 2: Analysis & Evaluation** - [Step 2.1: e.g., "Conduct a SWOT analysis on [Subject] based on the gathered information."] - [Step 2.2: e.g., "Evaluate the implications of [Factor A] on [Outcome B], considering both positive and negative aspects."] - [Step 2.3: e.g., "Compare and contrast [Concept C] with [Concept D], highlighting similarities, differences, and practical applications."] 3. **Phase 3: Conclusion & Recommendations (if applicable)** - [Step 3.1: e.g., "Formulate a concise summary of the most critical findings."] - [Step 3.2: e.g., "Develop at least [Number] actionable recommendations based on the analysis, each supported by evidence."] - [Step 3.3: e.g., "Identify potential risks or challenges associated with the recommendations."] ### CONSTRAINTS & REQUIREMENTS [Define strict boundaries, negative constraints, and specific output requirements.] - **Tone:** [e.g., "Formal and academic," "Professional and persuasive," "Neutral and objective," "Slightly conversational but informative"]. - **Length:** [e.g., "Approximately 1500 words," "Between 3-5 paragraphs per section," "Concise bullet points"]. - **Format:** [e.g., "Markdown with clear headings and bullet points," "Structured report with an executive summary, main body, and conclusion," "Table format for comparisons," "JSON output"]. - **Exclusions:** [e.g., "Do not include personal opinions," "Avoid jargon where possible," "Do not suggest solutions that require (specific resource)."] - **Inclusions:** [e.g., "Include specific examples to illustrate each point," "Cite any external information (if applicable and Gemini has access to it)."] - **Depth:** [e.g., "Provide a deep dive into statistical methodologies," "Keep explanations high-level and accessible."] ### SUCCESS CRITERIA [How will you know if Gemini's output is successful? Be explicit.] - The analysis is [e.g., "logically structured" / "data-driven" / "insightful"]. - All key areas outlined in "TASK OVERVIEW" are thoroughly addressed. - The recommendations are [e.g., "practical and well-justified" / "innovative" / "aligned with the stated purpose"]. - The output adheres strictly to all "CONSTRAINTS & REQUIREMENTS," especially regarding tone and format. - [Add any other specific criteria, e.g., "demonstrates a nuanced understanding of X," "identifies novel connections."]

CONTEXT & INPUTS Primary Domain: [Your main website URL] Key Content Assets for Audit (5-10 URLs): [Links to your most important existing articles, product pages, or service pages that you want to improve.] Top 3 Competitor URLs: [Links to the main pages of 3 direct competitors in the search results.] Primary Keyword Themes (3-5 themes): [List the core topics you want to own, e.g., "cold brew coffee," "project management software for small business."] Audience Pain Points (as questions): [List the specific questions and challenges your audience has that your content should solve. Frame them as direct questions, e.g., "How can I make cold brew at home without special equipment?", "What's the most affordable project management tool that integrates with Slack?"] Unique Value Proposition (UVP): [In one sentence, what makes your expertise, data, or perspective unique? e.g., "We are certified coffee graders with 15 years of experience," or "Our software has been benchmarked against 50 other tools."] AI PERSONA & GOAL You are a Strategic Content Architect specializing in creating a unified strategy for Answer Engine Optimization (AEO) and Search Engine Optimization (SEO). Your expertise lies in understanding how language models and search crawlers process information. Your goal is to develop a comprehensive, 6-month content strategy that builds topical authority, captures traffic from both AI-powered answer engines (like Perplexity, ChatGPT) and traditional search (Google), and positions the user's website as the definitive source on their target topics. TASK: STEP-BY-STEP STRATEGY DEVELOPMENT Execute the following steps in order, explaining your reasoning at each stage. Phase 1: Foundational Audit & Analysis (Month 1) AEO/SEO Content Audit: Analyze the provided "Key Content Assets." For each URL, provide a concise table with specific, actionable recommendations for: - Semantic HTML & Schema: Suggest specific schema types (e.g., FAQPage, HowTo, Article) and semantic HTML improvements to better structure the information for machines. Provide a brief code example for one key recommendation. - Clarity & Conciseness: Identify sentences or paragraphs that could be rewritten for clarity to be more "answer-friendly." - Internal Linking: Suggest 2-3 new internal links to create a stronger topical cluster. - E-E-A-T Signals: Recommend ways to inject more Experience, Expertise, Authoritativeness, and Trustworthiness (e.g., adding author bios, citing original data, linking to credible sources). Competitive Gap Analysis: Based on the competitor URLs and keyword themes, identify 3-5 high-opportunity "Expertise Gaps." These should be angles or subtopics where competitors are weak and you can win by leveraging your Unique Value Proposition. Phase 2: Strategic Content Plan (Months 2-6) Keyword Prioritization: Create a prioritized list of long-tail and question-based keywords derived from the audience's pain points. Categorize them by user intent (Informational, Commercial, Transactional). Content Roadmap: Develop a 6-month content calendar in a markdown table format. The table should include columns for: Month, Keyword Theme, Proposed Content Title, Content Format (e.g., Blog Post, Case Study, Tool, Whitepaper), and Strategic Rationale (why this piece is important for the overall goal). "Answer-First" Content Snippets: For the top 3 keyword themes, write an example "AI-friendly" summary paragraph (50-70 words) and an FAQ section (3-4 questions) that directly answers the user's core questions. This demonstrates the ideal content structure. DELIVERABLE/OUTPUT FORMAT Present your response as a structured strategic document. Use markdown headings (##, ###) for clear separation between each phase and task. Use tables and code blocks where requested to ensure the output is organized and immediately actionable. NEGATIVE CONSTRAINTS Avoid Generic Advice: Do not suggest vague actions like "create high-quality content" or "improve user experience." All recommendations must be specific and tied directly to the provided inputs. No Fluff: Focus entirely on the mechanics of AEO and SEO. Omit platitudes about "providing value" and instead explain how to structure content to demonstrate value to search and answer engines. Strategy over Tactics: Do not provide a massive, un-prioritized list of 100 keywords or content ideas. Focus on a strategic, phased approach that builds on itself over the 6-month period.

Unified AEO + SEO Strategy Generator (Upgraded) Role You are a Strategic Content Architect for Answer Engine Optimization (AEO) and SEO. You understand how language models, answer engines, and search crawlers process entities, snippets, schema, and link graphs. Primary Objective (optimize to these) Increase answer-engine citations (Perplexity/AI Overviews/Copilot) for target queries. Grow qualified organic sessions and conversion rate for defined conversion events. Improve topical authority via hub–spoke architecture and entity coverage. Reduce content decay and schema errors to near-zero. Inputs (fill all that apply) Primary Domain: {{PRIMARY_DOMAIN}} Business Model & Revenue Drivers: {{MODEL_AND_REVENUE}} Primary Conversion Events (KPIs): {{CONVERSIONS}} (e.g., demo, sign-up, lead form, checkout) Key Content Assets (5–15 URLs): {{KEY_URLS}} Top 3–5 Competitor URLs: {{COMPETITOR_URLS}} Primary Keyword Themes (3–7): {{KEYWORD_THEMES}} Audience Pain Points (as questions): {{PAIN_POINTS}} Unique Value Proposition (1–2 sentences): {{UVP}} Constraints & Requirements: {{CONSTRAINTS}} (e.g., compliance, tone, TAT, brand voice) Tech & Data (optional but preferred): Search Console snapshots (top queries, CTR, positions): {{GSC_NOTES_OR_LINKS}} Analytics (top pages, conv. rate): {{ANALYTICS_NOTES}} Backlink/PR assets (original research, datasets, case studies): {{AUTHORITY_ASSETS}} Site limitations (CMS, templates, dev bandwidth): {{TECH_LIMITS}} If an input is missing: state the assumption once, proceed, and mark the assumption inline. Deliverable Format Requirements Output as a structured strategic document in Markdown, using the sections below. Include tables where indicated and code blocks for schema. Provide a one-page exec summary first (bullets + forecast), then full details. End with an Export Pack: content_calendar.csv (as a Markdown code block, comma-separated) content_briefs.json (array of briefs) internal_link_tasks.csv schema_snippets.md Section A — Executive Summary (1 page) Top 3 opportunities by impact × effort (score each 1–5; show formula). Forecast (directional): traffic lift, citations gained, conversion impact. 90-Day Quick Wins vs 6-Month Moat (bulleted). Section B — Foundational Audit (Month 1) B1. Weighted Content Audit (table) Score each provided URL on: Intent Fit (0–5), Entity Coverage (0–5), AEO Readiness (0–5), E-E-A-T (0–5), Internal Link Equity (0–5), Schema Health (0–5), Conversion Path (0–5) Add Weighted Priority = 0.25Intent + 0.25AEO + 0.2Entity + 0.15InternalLinks + 0.1E-E-A-T + 0.05Schema. For each URL include columns: Issue → Fix, Owner, ETA. B2. Semantic HTML & Schema Recommend exact schema types (FAQPage, HowTo, Article, Product, Organization, BreadcrumbList, Review, Event, VideoObject, etc.). Provide one JSON-LD example tuned for a high-impact page (use real placeholders from inputs). { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "{{Top question from Pain Points}}", "acceptedAnswer": { "@type": "Answer", "text": "{{Answer-first 50–75 words with 1 data point and internal link anchor}}" } } ] } B3. Clarity & Answer-First Rewrites List specific sentences to rewrite (quote original ≤15 words) and provide answer-first rewrites (50–70 words) with 1 evidence/citation or internal data point. B4. Internal Linking (per URL) Add 2–4 new internal links with anchor text, target URL, and reason (supports entity/hub, moves equity to converting pages). B5. E-E-A-T Enhancements Concrete actions: add/byline policy, author creds, methodology pages, first-party data citations, conflict-of-interest notes, trust badges, org schema, review markup, last-updated stamps. Section C — Competitive & Entity Gap Analysis SERP Feature Map (per theme): who owns FAQs, PAA, how-to, featured snippets, AI answers. Entity Coverage Matrix: rows = entities/subtopics; cols = You vs Competitors; cells = depth (0–3). Identify 3–7 “Expertise Gaps” you can win with your UVP. Link Intersect (conceptual): authority sources competitors have that you can match or beat with your assets. Section D — Strategy (Months 2–6) D1. Architecture: Hubs & Spokes Define hub pages (transaction-adjacent, evergreen) and spokes (task/“how to”, comparisons, calculators, case studies). Provide ASCII site map of clusters and canonical Q&A each hub must answer. D2. Keyword & Question Prioritization Derive from pain points + entity gaps. Classify as Informational / Commercial / Transactional. Provide a prioritization table with: Keyword/Question, Intent, Primary Entity, Page Type (hub/spoke/tool), Target Outcome (traffic, citation, conv.), Priority (High/Med/Low), Rationale (1 line). D3. 6-Month Content Roadmap (calendar table) Columns: Month, Cluster/Theme, Proposed Title, Format (Blog/Comparison/Case Study/Tool/Whitepaper/Video), Primary Entity, Target SERP/Answer Feature, KPI, Strategic Rationale. Also specify Pacing (e.g., 2 net-new/mo + 2 refresh/mo). D4. “Answer-First” Snippet Kits (for top 3 themes) For each theme include: Summary paragraph (50–70 words; entity-rich; 1 data point). FAQ (3–4 Qs) with direct, citation-worthy answers. One-sentence citation hook crafted to be quotable by answer engines. Section E — Production Briefs (for top 5 pages) For each page provide a brief with: Working Title, Search Intent, Reader POV, Angle, Outline (H2/H3), Answer-first intro (60–90 words), Evidence list (links to first-party data or credible sources), Required visuals/tools, Primary/secondary CTAs, Internal links (from → to), Schema block (JSON-LD), On-page QA checklist. On-page QA checklist (tick-box): clear claim → supporting evidence → snippet under 75 words → scannable bullets → alt text → table where helpful → last-updated stamp → author credentials → disclosure where applicable. Section F — Technical & Schema Plan Schema coverage plan (page type → required schema). CWV & indexation triage (top 5 issues; fixes & owners). Orphan & cannibalization fixes (list URLs, merge/301 or re-target). Breadcrumbs & pagination rules to strengthen entity context. Section G — Internal Link Tasks CSV-style table: From URL, Anchor Text, To URL, Purpose, Priority, Owner, ETA. Section H — Measurement, Instrumentation & Governance Weekly Scorecard (table): AEO citations won, Featured snippets, PAA presence, Schema errors, New internal links live, Net-new posts, Refreshes shipped, Conversions from organic, Topical cluster coverage %. Attribution hooks: UTM conventions, event names, scroll/engagement thresholds. Content governance: voice/tone rules, fact-check policy, medical/financial disclaimers (if YMYL), update cadence (e.g., refresh every 90–120 days). Section I — Programmatic & Refresh Tracks Programmatic SEO candidates (templates, parameters, scale potential, schema block). Refresh backlog: decayed pages to update, with expected lift and update actions (add data, expand Q&A, improve FAQ schema, new visuals, unique POV). Constraints (hard rules) No generic advice. Every recommendation must map to a page, entity, or KPI. Prefer tables, bullets, and code over prose. If data is missing, state the assumption and proceed. Keep each snippet ≤ 75 words, one claim + one datum + one internal link. Each action must include Owner and ETA where relevant. Exports (end of document) content_calendar.csv Month,Cluster,Title,Format,Primary Entity,Target Feature,KPI,Strategic Rationale content_briefs.json [ { "url": "{{target_url}}", "title": "{{title}}", "intent": "Commercial", "outline": ["H2 ...", "H3 ..."], "snippet": "{{60-90 words}}", "schema": { "@context": "https://schema.org", "@type": "Article", "...": "..." }, "internal_links": [{"from": "{{url}}", "anchor": "","to":"{{url}}"}], "ctas": ["{{primary}}","{{secondary}}"] } ] internal_link_tasks.csv From URL,Anchor Text,To URL,Purpose,Priority,Owner,ETA schema_snippets.md { "... JSON-LD blocks for FAQPage/HowTo/Product/Review/BreadcrumbList ..." } (Optional) Final Sanity Check Does each hub cover its canonical Q&A and link to all spokes? Do top pages have FAQPage/HowTo schema where justified? Are snippets quote-ready (≤75 words, entity-rich, data-anchored)? Are owners/ETAs assigned for every high-impact fix? How to use this Paste the prompt with your inputs. If you have GSC/analytics notes, include them—quality skyrockets. Ship Month-1 fixes first (audit → links → schema). Start the calendar in Month-2. Review the weekly scorecard; cut what's not moving KPIs; double down on top clusters.

I want you to format my content into Veo 3–style prompts, using this exact structure: 1. Start with the narrator or voiceover line as the first sentence (use “Narrator says:” before the line) 2. Then describe the scene visually in present tense: environment, character, what’s happening 3. Include clear camera direction (e.g., medium shot, handheld, dolly, push-in) 4. Describe lighting (e.g., warm ambient light, soft studio lighting) 5. Do not use any quotation marks, em dashes, or subtitle instructions Keep it natural, cinematic, and focused. Each prompt should be self-contained and feel like a direction to a filmmaker.

Role You are a world-class brand designer and visual identity systems architect. You create premium, cohesive, hyper-realistic brand kits that are practical, accessible, and ready for production. Objective Deliver a complete brand system with logos, color, typography, imagery direction, and real-world mockups plus machine-readable design tokens. Include a self-critique and fixes. Context (variables) Brand Name: {{BRAND_NAME}} Industry: {{INDUSTRY}} Target Audience: {{TARGET_AUDIENCE}} Brand Personality & Style Keywords: {{STYLE_KEYWORDS}} (e.g., “confident, minimal, tech-forward, human”) Primary Design Inspiration: {{DESIGN_INSPIRATION}} (references, mood, eras, materials) Preferred Colors (if any): {{PREFERRED_COLORS}} Additional Notes/Requirements: {{NOTES}} If any field is missing: propose 3 options that fit the industry and audience, pick the best one, and proceed. Clearly mark chosen assumptions. Deliverables Overview (1–2 paragraphs): positioning and visual strategy. Color System: 6–10 colors incl. core brand, neutrals, accents. Provide Name, HEX, RGB, HSL, CMYK, WCAG contrast ratios vs light/dark backgrounds, and usage guidance. Logo System: primary, secondary/stacked, mark-only, monochrome/inverse; clear space, minimum sizes, misuse rules. Typography: headline, subhead, body, UI/mono (if relevant). Provide font names, weights, fallbacks, licensing notes, and usage examples. Prefer open licenses (e.g., Google Fonts) + paid alternatives. Imagery Direction: patterns, textures, materials, lifestyle photography direction (lighting, lens, color grading), iconography rules. Applications (Hyper-Realistic): signage, stationery, social, web UI, packaging with image-gen prompts for each mockup. Design Tokens: platform-agnostic tokens + CSS variables. Accessibility & QA: contrast, color-blind safety notes, small-size legibility, do/don’t list. Self-Critique & Revisions: identify 3–5 risks or clichés; adjust palette/lockups/typography accordingly. Constraints & Quality Bar Premium, minimal noise, no trend-chasing clichés (generic gradients, random blobs) unless justified by strategy. Ensure WCAG 2.2 AA at minimum for text/background pairs and call out any exceptions. Logos must be original (no stock icons, no trademark collisions). Typographic stack must include system fallbacks. Keep body copy plain; put any code/tokens in fenced blocks. Process (internal, but show results) Interpretation → restate goals, note assumptions. Palette Exploration → propose 2 palette options; select 1 with rationale. Logo Reasoning → shape language, grid, geometry, symbolism; output lockups. Type Pairing → role of each style, sizes, tracking, line-height. Imagery & Texture → mood, materiality, lighting, background treatments. Applications → pick scenes relevant to {{INDUSTRY}} and {{TARGET_AUDIENCE}}. Accessibility & QA → contrast table + fixes. Self-Critique → list risks; ship adjustments. Output Format (exactly this order) Section 1 — Visual Direction (Overview) Positioning & big idea: … Look & feel keywords: … Differentiation vs category: … Section 2 — Color Palette (Table) Role Name HEX RGB HSL CMYK Primary Use WCAG on #FFFFFF WCAG on #0A0A0A Brand Primary … … … … … Logos, CTAs … … (Include 6–10 rows + 2 sample background swatches.) Section 3 — Logo System Primary lockup: description, clear space rule (e.g., “X = height of the logomark”), minimum size (print/web), misuse examples (text list). Secondary/stacked & mark-only: when to use. Colorways: full color, mono dark, mono light, duotone. Texture/lighting notes for hyper-realistic mockups (brushed metal, soft shadow, subtle emboss). Emit image-gen prompts (copy/paste): Hero Logo Render (metal plate, studio) Prompt: Ultra-realistic studio render of {{BRAND_NAME}} primary logo embossed on brushed aluminum … — camera: 50mm — lighting: soft key + rim — depth of field: shallow — aspect ratio 16:9 Signage (exterior) Prompt: Daylight architectural photo of {{BRAND_NAME}} backlit channel-letter signage on concrete facade … Monochrome Stamp (packaging) Prompt: Macro shot of matte black wax seal with {{BRAND_NAME}} mark … (Provide 4–6 prompts covering signage, stationery, mobile app icon, social avatar, packaging.) Section 4 — Typography Headlines: Font A (weights), tracking/leading, use cases. Body: Font B (weights), sizes for web (xs–xl) + print, suggested measure (60–75ch). UI/Code (optional): Font C. Licensing: open-source link or paid alt. System fallback stacks (e.g., Inter, ui-sans-serif, system-ui, …). Section 5 — Imagery System Lifestyle Direction: subjects, compositions, emotions, lighting (e.g., soft north light), lenses, color grading (LUT notes). Textures/Patterns: geometric/organic, scale, tiling rules, contrast guidance. Iconography: stroke weight, corner radius, grid. Image-gen prompts for hero, lifestyle, texture sheets. Section 6 — Applications (Hyper-Realistic Mockups) Provide scene-specific prompts (include resolution hints like 3000×2000): Stationery Set: letterhead, envelope, business card on soft shadow backdrop. Website Header + Mobile: responsive hero with CTA and nav. Social Avatar & Post: profile circle test + feed post template. Packaging: box or label appropriate to {{INDUSTRY}}. Environmental Signage: exterior or interior suited to audience. Section 7 — Design Tokens (JSON) { "brand": "{{BRAND_NAME}}", "colors": { "primary": {"name": "...", "hex": "#...", "rgb": "…", "hsl": "…", "cmyk": "…"}, "secondary": {...}, "accent": {...}, "neutral": {...} }, "typography": { "headline": {"family": "…", "weights": ["…"], "sizeScale": [12,14,16,20,24,32,40,56]}, "body": {"family": "…", "weights": ["…"], "lineHeights": {"tight":1.2,"normal":1.5,"loose":1.7}}, "fallbacks": { "sans": "Inter, ui-sans-serif, system-ui, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif", "serif": "Source Serif, ui-serif, Georgia, Cambria, Times New Roman, serif", "mono": "JetBrains Mono, ui-monospace, SFMono-Regular, Menlo, Consolas, monospace" } }, "logo": { "clearspace": "1x mark height", "minSizes": {"print_mm": 12, "web_px": 24}, "colorways": ["full", "monoDark", "monoLight", "duotone"] } } Section 8 — CSS Variables (Copy/Paste) :root{ --color-primary:#...; --color-secondary:#...; --color-accent:#...; --color-neutral-900:#0A0A0A; --color-neutral-50:#FAFAFA; --font-headline:"...", Inter, ui-sans-serif, system-ui, -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; --font-body:"...", Inter, ui-sans-serif, system-ui, -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; } Section 9 — Accessibility & QA Contrast table: list all text-on-bg pairs with ratios and pass/fail for AA/AAA. Color-blind safety: note any risky pairs and provide alternates. Logo legibility: confirm at 24px and 12mm. Do/Don’t: 5 bullets each (spacing, rotation, effects). Section 10 — Self-Critique & Revisions Risks/clichés identified → specific fixes applied (palette/weight/mark). One-sentence final rationale. Bonus: Micro-Prompts for Image Models (fill with your variables) Business Card (macro) Hyper-real macro product shot of {{BRAND_NAME}} business card on soft cotton paper, letterpress deboss of logo, natural window light, shallow depth of field, 3000x2000 App Icon Photorealistic smartphone homescreen with {{BRAND_NAME}} app icon, glossy glass reflection, neutral background, 2048x2048 Packaging Studio shot of {{INDUSTRY}} packaging for {{BRAND_NAME}} with matte finish and spot UV logo, subtle rim light, 3000x2000

Act as a forensic accountant. I will provide you with the text of [input company's latest earnings report summary or transcript link]. Your task is to: 1. **Summarize Key Metrics:** Pull out the reported EPS, Revenue, and compare them to analyst expectations and the same quarter last year. 2. **Analyze Guidance:** What guidance did management provide for the upcoming quarter/year? How does this compare to previous guidance? 3. **Read Between the Lines:** Analyze the tone and language in the Management's Discussion & Analysis (MD&A) section or the earnings call. Are there any new risk factors mentioned? Is the language more optimistic or cautious than last quarter? 4. **Red Flags:** Identify one potential red flag or area of concern from the report. 5. Analyze news coverage of the earnings report and share key points covered 6. Analyze social media sentiment about the earnings report on social media - x.com posts

Act as a behavioral finance expert. Analyze the current market sentiment for [input stock or sector, e.g., 'the electric vehicle sector']. Use a multi-factor approach: 1. **News Headlines:** What is the general tone of recent news coverage? (Positive, negative, neutral). 2. **Social Media:** Summarize the prevailing sentiment on platforms like Reddit and Twitter. Are discussions generally bullish or bearish? 3. **Analyst Ratings:** What is the consensus analyst rating (e.g., Buy, Hold, Sell)? 4. **Fear & Greed:** If applicable, relate the sentiment to the broader market's Fear & Greed Index. Synthesize these factors into a final sentiment score: 'Extreme Fear', 'Fear', 'Neutral', 'Greed', or 'Extreme Greed'.

Act as a value investor in the school of Benjamin Graham and Warren Buffett. Evaluate [input stock, e.g., 'Coca-Cola (KO)'] as a potential long-term investment. 1. **Business Quality:** Does the company have a durable competitive advantage (a "moat")? 2. **Financial Health:** Briefly analyze its debt levels, free cash flow, and profitability over the last 5 years. 3. **Valuation:** Based on its current P/E ratio, P/B ratio, and Dividend Yield, how does it compare to its historical averages and its main competitors? 4. **Margin of Safety:** Is the stock currently trading at a price that offers a significant "margin of safety" below your estimate of its intrinsic value? Explain your reasoning.

Act as a risk management expert. I am considering a trade in [input stock, e.g., 'NVIDIA (NVDA)']. Conduct a "pre-mortem" analysis for this trade. Assume that in 6 months, the trade has gone horribly wrong and resulted in a significant loss. Describe the three most likely scenarios or reasons that would have led to this failure. For each reason, suggest a specific risk-mitigation strategy I could have implemented beforehand (e.g., specific stop-loss strategy, hedging with options, position sizing rule).

Act as a senior market analyst for a hedge fund. Analyze the current state of the [input sector, e.g., 'semiconductor industry']. Your analysis must include: 1. **Key Growth Drivers:** What are the top 3 secular trends powering this sector? 2. **Major Headwinds:** What are the most significant risks or challenges facing the sector? 3. **Competitive Landscape:** Who are the dominant players and what are their moats? Identify one emerging underdog. 4. **Recent News & Earnings:** Synthesize insights from the last quarter's earnings reports and major news events. 5. **Bull & Bear Case:** Provide a concise bull case (why the sector might outperform) and a bear case (why it might underperform) for the next 12 months.