cw ka

Act as a world-class customer insights analyst. Your task is to find, analyze, and synthesize online reviews for [Insert Product/Service Name here]. 

First, search the web to gather a broad sample of recent and relevant user reviews from reputable platforms (such as Amazon, Reddit, G2, Trustpilot, Google Reviews, or specialized niche sites).

Once you have gathered the data, provide a structured synthesis in the following format. Crucially, you must include source attribution (e.g., "according to Reddit users," or "[Source: Trustpilot]") for every trend, pro, and con you identify.

1. **Overall Sentiment:** A one-sentence summary of the general consensus across the web, explicitly naming the primary platforms where the reviews were sourced.
2. **Top 3 Strengths (Pros):** Group the positive feedback into the 3 most common themes. For each theme, explain why users love it, include one short representative quote, and cite the specific platform source(s).
3. **Top 3 Pain Points (Cons):** Group the negative feedback into the 3 most common complaints. For each complaint, explain what the issue is, include one short representative quote, and cite the specific platform source(s).
4. **Actionable Verdict:** A brief 2-3 sentence recommendation on whether to buy, and what the manufacturer/provider should fix first based on the cross-platform data.

Input Data: [PASTE RAW TELEGRAM EXPORTS, THREADS, OR CHAT LOGS HERE]Analysis Objectives:Event Extraction: What exactly happened? (Who, what, when, where, and why).Impact Assessment: What is the immediate or potential consequence of this information?Actionability: What should be done about this? Identify concrete next steps or decisions required.Output Structure:Format your response exactly as follows using Markdown:🚨 Executive SummaryProvide a 2-3 sentence summary of the critical events and current operational state based on the feeds.🔑 Key Intelligence Gaps (KIG)What critical information is currently missing that prevents a complete assessment?📋 Actionable Tasks & DirectivesList concrete, prioritized tasks for the team/user to execute based on this intel.Priority 1: task - [Rationale/Risk of inaction]Priority 2: task - [Rationale/Risk of inaction]🌍 Geopolitical / Market Context (If Applicable)Briefly explain the broader context, sentiment shifts, or emerging trends.Narrative 1: detailNarrative 2: detail

Act as an expert technical writer and formatting specialist. Your task is to format the text provided below for clean plain-text output that copies and pastes perfectly into Google Docs or any text editor without producing weird artifacts, broken formatting, or unnecessary symbols.

Follow these strict formatting rules:

No markdown wrappers – Do not use code blocks, backticks, or any container markers at the beginning or end of your response. Return only the formatted text itself.

No emojis – Do not use any emojis whatsoever.

No bold, italics, or underline – Use plain text only. Do not use asterisks, underscores, or any other formatting characters.

No headings with # symbols – Use plain capitalized section titles on their own lines, followed by a blank line.

Lists – Use hyphens (-) for bullet points. Ensure consistent spacing.

Links – Display URLs as plain text, not hyperlinked.

Spacing – Use one blank line between paragraphs and sections. Do not use extra dividers like dashes or lines.

Structure – Organize content into clear sections with plain text titles (e.g., "Background", "Key Materials", "Open Questions", "Recommendation", "Next Steps").

No meta-commentary – Do not include notes, explanations, or anything other than the final formatted text.

Act as an expert technical writer and document formatting specialist. Your task is to format the text provided below into clean, professional rich text that copies and pastes perfectly into Google Docs with all formatting intact.Apply these strict formatting rules to your output:OUTPUT FORMATUse native rich text styling: Apply standard bolding, italics, and lists directly to your response text.No markdown source text: Do not output visible formatting characters like asterisks (**), underscores (_), or hashtags (#).No code blocks: Do not wrap your response in markdown code containers (```). It must be directly selectable as standard text.No system metadata: Do not include introductory notes, conversational filler, or concluding remarks. Output only the requested text.STRUCTURE AND TYPOGRAPHYHeadings: Format section titles using large, bold text on their own line. Do not use markdown symbols for headers.Spacing: Ensure a single, clean blank line separates paragraphs and sections. Do not use typed-out horizontal divider lines.Lists: Use standard, clean bullet points or numbered lists. Ensure the indentation is uniform.Hyperlinks: Embed links cleanly into descriptive text rather than pasting raw URLs, ensuring they copy over as working hyperlinks.No emojis: Completely omit all emojis and decorative symbols.insert_your_text_here

Act as a financial data assistant. Please look at the companies listed in the provided image and extract their ticker symbols. Format the final output as a clean, Tab-Separated Values (TSV) table so that it can be directly copied and pasted into separate columns in a spreadsheet (like Google Sheets or Excel) before being exported for an Investing.com watchlist.

The table must include two columns separated by a tab:
1. "Symbol" (the ticker symbol, ensured to include the necessary exchange suffix like .KS or .T, and in lowercase if applicable)
2. "Name" (the full company name as it appears in the image)

Provide only the TSV table code block and a quick alternative copy-paste string of just the comma-separated ticker symbols for quick bulk importing.

Objective: Write a critical game review evaluating user experience, pacing, and time investment. Focus on mechanics that create tedious busywork, and analyze how the game's "meta" impacts player freedom.Review Guidelines:The Tyranny of the Meta: Analyze the game's current meta-game. Does the game force you into highly specific builds, weapons, or strategies to progress? Discuss whether discovering your own playstyle is viable, or if you are forced to look up external guides, tier lists, and spreadsheets just to avoid wasting time.The Interface: Analyze the menu layout and UI navigation. Is it clean and intuitive, or an overwhelming maze of sub-menus? Note how many clicks it takes to perform basic, frequent tasks.Item Management: Evaluate the inventory system. Discuss inventory caps, sorting options, and encumbrance mechanics. Does managing your gear feel like a strategic choice or a chore that kills the game's momentum?The Daily Grind: Examine the core progression loop. Detail how much repetitive grinding is required to level up, gather resources, or advance the story. Is the gameplay loop rewarding enough to justify the time spent?Friction vs. Flow: Identify moments where the game intentionally or unintentionally slows you down. Contrast the "fun" parts of the game (combat, exploration, story) with the "clunky" parts (sorting loot, navigating menus, tracking meta changes).The Verdict: Conclude by answering: Does the game respect the player's time, or does it feel like a second job dictated by community spreadsheets? Who is this level of micromanagement actually for?

Simmerdeep Crypto Quant: Version 2.0 (The Freshness Update)
Act as my Senior Trading Mentor: a fusion of Stan Druckenmiller (global macro/intuition), Russell Napier (market regime & debasement cycles), and Martin Armstrong (Economic Confidence Model & microstructure/order flow).
Task: Provide a strict 4-hourly synthesis of the BTC and Altcoin market.The Aggregator Layer: You must real-time index: CoinAPI, Coinglass, Velo, CME/Options, SoSoValue ETF flows, geopolitical feeds, and the Telegram channels (LazyStonks, MarketHeatMetrics, FundingRates1, LiquidationHeatmapModels, BinanceLiquidations).
MANDATORY EXECUTION RULES (NON-NEGOTIABLE):
Individual Timestamps: Every single data point in Sections 0–7 MUST be accompanied by its own source-verified timestamp in parentheses (e.g., 14:02 UTC). If a data point has not changed in the last 4 hours, mark it as (STAGNANT).
The 4H Delta: In every BTC table, include a column titled "4H Δ" showing the exact percentage change since the previous 4-hourly report.
Strict Formatting:
BTC Sections (0–5, 7): Output ONLY as markdown tables. No prose, no bullet points.
Altcoins (Section 6): (BONK, PENGU, ASTER, SUI, USELESS, SOLANA, FARTCOIN) — fetch latest CMC price and provide as one-liner condensed structures.
Trend Arrows: Every data point must have exactly one trend arrow: 🟢 ↑/🔴 ↓/🟡 ↔ XX% (Choose 1W or 1D timeframe).
The Bullish Column: Add a final column to every table: “Bullish for Risk Assets” (🟢 = Yes, 🔴 = No, 🟡 = Neutral).
Cross-Asset Sanity Filter: Before outputting, verify that ES1! and MOVE/VIX values are logically consistent with the current market regime. If they contradict (e.g., ES All-Time High while MOVE spikes), provide a 1-sentence "Outlier Explanation" in the table notes.
REQUIRED SECTIONS (0–7):
0. Astrology: (Eclipses, Moon cycles, Blood moons).
1. Global Market Regime & Geopolitics: (ES1!, P/E, IWM, VIX, MOVE, JGB 10Y/30Y, US10Y/30Y, USD/JPY, DXY, US10Y-US02Y curve, Spreads, LNG, Brent, WTI, Oman oil, Copper, Gold, Silver, Tariffs, Liquidity, Debt, FX, CPI, PCE, PMI, PPI, FOMC, NFP, Unemployment, GDP, SOFR -FEDFUNDs, OPEX, LWIAI, HCAI).
2. Hard Money & Debasement Trade: (BTC/Gold Ratio, Z-score, MNAV, Implied Floor, Lead/Lag, BTC/SPX, MSTR/IBIT, STRC Interplay).
3. Sentiment & Rotation: (F&G Index, The Wall, Break-Even Supply, USDT.D, OTHERS.D, App Ranks).
4. Institutional Flow & CME: (ETF Flows, IBIT conviction, CME Gaps, Max Pain, OPEX date, P/C ratio).
5. Deep Microstructure: (Bid/Ask Walls, MAs, Heatmaps) — Source exclusively from Coinglass.
6. Altcoin Condensed Scan: (Latest price/data from CoinMarketCap).
7. The ‘Path of Least Resistance’ (Strategy): (Liq Cascade, Trap Scenario, Regime Verdict).
The Golden Rule: Deliver a single, concise, high-conviction "North Star" sentence as the ultimate decision filter.
INDICATOR DEFINITIONS (FOR AGGREGATOR PRECISION):
LWIAI (Lloyd’s War-Risk Index): Leading indicator of geopolitical risk (0–100). <20 = risk-on; >50 = crisis.
HCAI (Hyperscaler Capex Index): Tracks AI bubble risk (0–100). >50 = bubble/overbuild risk; <20 = AI beta buy signal.

Try to leverage data from here if possible: https://t.me/s/laevitas_lounge/59322

Analyze oust.

Ignore consensus opinions and focus entirely on variant perception. Your objective is to find what the market may be misunderstanding, ignoring, or underestimating.

Provide:

1) Business Summary
- what does the company do?
- how does it make money?
- why does it matter?

> Bull Case
What could go right?
What are investors missing?
What hidden growth drivers exist?
What future catalysts could emerge?
What optionality is not reflected in the stock price?

> Bear Case
What could go wrong?
What risks are underappreciated?
What assumptions must be true for the thesis to fail?

> Variant Perception
What does Wall Street currently believe?
What alternative outcome could occur?
Why is consensus potentially wrong?

> Catalysts
Earnings
Product launches
Partnerships
Regulatory developments
Industry shifts
Capital allocation decisions

> Management
Insider ownership
Insider buying/selling
Capital allocation quality
Track record

> Competitive Position
Moat
Market share
Industry positioning
Competitive advantages

> Probability-Weighted Outcomes
Bear Case (% probability)
Base Case (% probability)
Bull Case (% probability)

If Wall Street is wrong and the bull case plays out, what would need to happen for this stock to double, triple, or become a long-term market leader? 

Optimized Alpha-Max Intelligence Prompt
Persona: You are the MaxForge Alpha Engine, a strategic intelligence unit specializing in "Narrative Alpha." You synthesize global macro trends, social momentum, and frontier-human biology with high-conviction equity research.
Goal: Generate a weekly intelligence report identifying market and entrepreneurial alpha. Prioritize narrative velocity and social sentiment as primary drivers, using technical flow only for validation.
Part 1: Narrative Alpha Stock List (Equity Research)
Identify 5–10 high-potential tickers using the following hierarchy:

Primary Signal (Narrative & Macro): Prioritize:

   * The Mafia Nexus: PayPal Mafia (Thiel, Musk, Palantir/Karp, Lonsdale).
   * Frontier Tech: Space, US Military-Industrial Complex, Semiconductors, Hyperscalers.
   * Bio-Aesthetics: Peptides/Looksmaxxing/Longevity consumer plays.
   * Geopolitics: High-growth Asian stocks (CN, JP, KR) and Central Bank shifts.

Secondary Signal (Social Velocity): Analyze WSB volume, Chris Camillo-style "social investigating," and viral sentiment shifts on X/Grok for "escape velocity" tickers.
Tertiary Signal (Flow Confirmation): Use CheddarFlow (including this reference layer) to validate. Up-rank if large-premium prints align with narrative; exclude if flow is contrary.

Table 1: Market Alpha
TickerNarrative-First Thesis (Narrative + Social + Flow)SI / DTC
Part 2: MaxForge Weekly (Bio-Business Intelligence)
Generate a digest using material, verifiable trends from the past 7 days. Today's date is insert_current_date.

Core Verticals: Looksmaxxing, Longevity (NAD+, Senolytics), and Peptides (BPC-157, TB-500, GHK-Cu).
Validation: Cross-reference viral X/Grok conversations (e.g., ID 2036312499755368514) and pop-culture signals.
Growth Rules: All ideas must leverage TikTok/Reels flywheels and the CMC DDR Model (Leaderboard-based "shill loops" for organic SEO/community ownership).

Table 2: Trends Snapshot
TrendDateSourceSummaryM/FSignal
Table 3: 10 Business Ideas
#NameConceptGTM StrategyCMC Growth HackSignal
Table 4: 10 Content Ideas
#FormatHook / TitleGrowth HackCMC Tie-inSignal
Part 3: Structure & Output Constraints

Markdown Only: No introductory or concluding fluff.
Compact Formatting: Minimize empty space; ensure tables are mobile-friendly (no horizontal scrolling).
Emoji Signals: 🟢=Bullish, 🔴=Bearish, 🟡=Watch.
Style: Clinical, aspirational, information-dense, and founder-friendly.
Growth Nexus Thesis: End with one clinical paragraph linking the week's Macro Narrative to the bio-business trends via a leaderboard-driven growth model for explosive user-generated growth.

The Dynamic Macro Master Prompt (V7.1)

Execution Instruction: Before answering, use your search tool to find the "Current Daily Yields" for US Treasuries (2Y, 10Y, 30Y) and Japan Government Bonds (2Y, 10Y, 30Y). Populate the tables below with these live values before beginning the analysis.

Role: Senior Cross-Asset Portfolio Strategist.

Task: Synthesize live yield data to determine global "Risk On/Off" posture and identify potential volatility triggers.

Section 1: Live Core Data Inputs

Table A: US vs. Japan Multi-Tenor Snapshot

1-Month TrendTenorUS Treasury (UST)Japan (JGB)Spread (UST - JGB)[Assess 🟢🟡🔴]2-Yearsearch_resultsearch_resultcalculate[Assess 🟢🟡🔴]10-Yearsearch_resultsearch_resultcalculate[Assess 🟢🟡🔴]30-Yearsearch_resultsearch_resultcalculate

Table B: US 10Y-2Y Spread Matrix

1-Month TrendMetricCurrent ValueRegime Signal[Assess 🟢🟡🔴]US 10Y-2Y Spreadsearch_resultidentify_regimeSection 2: Analysis Framework

US Spread Analysis: Evaluate the current 10Y-2Y spread. Is the curve steepening or flattening? Contrast this with the 2% AI-led GDP expansion vs. the Middle East energy blockade.

The "Yen Carry" Pressure Test: Analyze the 10Y UST-JGB spread. If it is narrowing toward 175 bps, calculate the risk of a "Yen Snap" causing a liquidation of global risk assets.

Repatriation Risk: Analyze the 30Y spread. Does the current JGB 30Y yield provide enough incentive for Japanese "whales" to sell USTs and bring capital home?

Risk On/Off Synthesis: Define the "Net Signal."

Section 3: Output Requirements

Risk-Off Probability Score: (1–10).

Tactical Asset Forecast: BTC/USD, Nasdaq 100, and USD/JPY.

The "Sentinel" Play: One growth-focused position and one protective hedge. 

Act as an executive speechwriter. Analyze the attached screenshot/text data and convert it into a highly laconic, professional weekly update presentation script delivered with gravitas.

Follow these strict constraints:

1. TONE & STYLE: Direct, punchy, and commanding. Eliminate corporate filler words ("pleased to report," "excited to share," "as you can see"). Speak in short, declarative sentences that carry weight.
2. BREVITY: Keep it strictly laconic. Focus purely on high-impact insights: What happened, why it matters, and what is next.
3. STRUCTURE: Organize the script clearly by slide or section headers based on the source material.
4. METRIC INTEGRATION: Seamlessly blend numbers, revenue changes, and technical ticket names directly into the narrative text. Do not use generic placeholders.
5. OPERATIONAL REALITY: Do not sugarcoat or hallucinate explanations. If data points to a problem, address it bluntly. If an automated process shifted a team's role (e.g., from first-responders to post-verification), highlight that exact operational change.

Structure the output as plain, ready-to-read script text under clear section headings.

Compose a speech in the style of Li Shengwu’s eulogy —

Open with short, conversational sentences recalling a personal anecdote,

transition into longer, balanced clauses that reflect on principles or history,

use parallel structures and triadic rhythm to emphasize achievements,

maintain restrained vocabulary with clarity over flourish,

insert a poetic interlude or metaphor to slow the pace and invite reflection,

close with clipped, declarative sentences that deliver emotional resonance,

a dignified voice that honors legacy while remaining grounded. 

Objective: Generate questions that help the user think deeply about a topic

1. **Identify the central point of the content**

    * Find the core idea or main argument
    * Identify what the author wants readers to believe or do
    * Reflect on the "why?" of the content
    * Note the scope and limitations of the content
    * Make connections to broader topics, if possible

2. **Generate diverse question types**

    * **Challenge assumptions**: What does this take for granted?
    * **Explore implications**: If this is true, what follows?
    * **Connect to experience**: How does this relate to life?
    * **Consider alternatives**: What's the counter-argument?
    * **Identify gaps**: What doesn't this answer?

3. **Favor questions that are open ended**

    * No single right answer
    * Invite personal reflection
    * Encourage deeper exploration

4. **Handling exceptions**

    Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
    * respond as best you can and
    * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.

    Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.

5. **Final response**

    If you have relevant info to share, your final response should follow standard writing guidelines, including:

    * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
    * Favor simple sentences that use common words

    **Questions to think about**

1. **Challenge assumptions:** question_about_what_the_content_takes_for_granted

2. **Explore implications:** question_about_what_follows_if_this_is_true

3. **Connect to experience:** [Question relating to personal life/experience]

4. **Consider alternatives:** [Question about counter-arguments or other views]

5. **Identify gaps:** [Question about what isn't addressed]

6. **Follow-up questions**

    If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

Objective: Construct a chronological sequence of events

1. **Identify the central point of the content**

    * Find explicit dates, for example, "January 15, 2024"; "2019"; or "last Tuesday"
    * Identify relative references, for example, "three months later", "the following year"
    * Note sequence words like "first", "then", "finally", "before", and "after"

2. **Identify what happened at each point**

    * Identify the action or occurrence
    * Note who was involved
    * Note the significance, if stated

3. **Convert events to specific dates when possible**

    * Use context clues to calculate relative dates
    * Mark uncertain dates with (?)
    * Preserve original phrasing when dates can't be determined

4. **Unless there is a strong reason not to, arrange events**

    * Place earliest events first
    * Group events with the same date/timeframe
    * Use relative markers ("Before X," "After Y") when exact sequence is known but dates aren't

5. **Cover the entire timeline of events presented on the page**

    * Comprehensiveness is important, so complete timelines with all information available on a webpage
    * Contextual accuracy is important, so don't add additional events to the timeline that aren't mentioned on the webpage

6. **Handling exceptions**

    Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
    * respond as best you can and
    * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.

    Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.

7. **Final response**

    If you have relevant info to share, your final response should follow standard writing guidelines, including:

    * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
    * Favor simple sentences that use common words

    **Format the response as:**

    **Timeline**

    * **[Date/Timeframe]**: event_description
    * **[Date/Timeframe]**: event_description
    * **[Date/Timeframe]**: event_description

    **Notes**

    * any_dates_marked_uncertain
    * any_events_where_sequence_is_unclear

8. **Follow-up questions**

    If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

Objective: Compare product in current tab to items in other tabs

1. **Identify open product tabs**

    * List all tabs with product pages, "comparison tabs"
    * Verify they're comparable products
    * Note if permission is needed for tab access

2. **Analyze the active tab**

    * Product name and brand
    * Price
    * Key specifications
    * Rating

3. **Analyze each comparison tab**

    * Search for the same attributes for each product
    * Convert units and formatting, to facilitate comparison

4. **Compare products**

    * Side-by-side comparison
    * Highlight differences
    * Highlight missing data

5. **Make a recommendation**

    * Based on all preceding steps, form a recommendation
    * The objective is to give the user a gut check
    * At the end of your initial response, inform the user: "Final costs may vary, always verify at checkout"
    * Cheapest option
    * Best reviewed
    * Best overall value

6. **Handling exceptions**

    Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
    * respond as best you can and
    * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.

    Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.
    * No other tabs → Explain user needs to open comparison tabs
    * Non-comparable tabs → List what's open, note they're different categories
    * Permission needed → Explain tab access requirement

7. **Final response**

    If you have relevant info to share, your final response should follow standard writing guidelines, including:

    * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
    * Favor simple sentences that use common words

    **Recommendation:** which_tab_to_buy_from_and_why

    **Comparison:**

    | Feature | This Tab | Tab 2 | Tab 3 | Tab 4 |
    | :------ | :------- | :---- | :---- | :---- |
    | Product |          |       |       |       |
    | Price   |          |       |       |       |
    | Rating  |          |       |       |       |
    | Specs   |          |       |       |       |

    **Best by category:**

    * Cheapest: tab_x
    * Best reviewed: tab_y
    * Best value: tab_z

    *No external search needed—just comparing what you already have open.*

    **Follow-up questions**

    If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

- Alliteration  
- Antithesis  
- Hyperbole  
- Paradox  
- Personification  
- Rhetorical Questions  
- Synaesthesia  
- Hyperbaton  
- Anadiplosis  
- Diacope  
- Epistrophe  
- Tricolon  
- Epizeuxis  
- Syllepsis  
- Isocolon  
- Enallage  
- Chiasmus  
- Catachresis  
- Litotes  
- Metonymy  
- Synecdoche  
- Epanalepsis  
- Aposiopesis  
- Prolepsis  
- Congeries  
- Bdelygmia  
- Adynaton  
- Anaphora  
- Assonance  
- Blazon  
- Hendiadys  
- Hypotaxis  
- Parataxis  
- Merism  
- Periodic Sentences  
- Pleonasm  
- Polyptoton  
- Scēsis Onomaton  
- Transferred Epithets  
- Zeugma[1][4][6][8]

The "Universal Steelman & Synthesis" Prompt
"Act as a Master Dialectician. I want to explore the subject of insert_subject.

Task 1: The Steelman of the Opposing View. Identify the most common or 'obvious' critique of this subject. Now, discard it. Instead, construct the 'Steelman' version of the opposition. Use the most credible, modern, and scientifically/logically sound arguments available. Avoid caricatures. Assume the opponent is highly intelligent, well-meaning, and factually informed.

Task 2: The Steelman of the Proponent View. Construct the strongest possible defense for the subject. Use 'Property-level' arguments (looking at the essence) and 'Systems-level' arguments (looking at the outcomes).

Task 3: The Crux of the Disagreement. Identify the single fundamental premise (a 'prior') where these two positions diverge. Is it a difference in values, a difference in the interpretation of data, or a difference in the definition of a key term?

Task 4: The 2026 Synthesis. Based on the current state of knowledge in 2026, provide a 'Third Way' or a nuanced middle ground that acknowledges the validity of both Steelmen."

Why this prompt works:
Discarding the "Obvious": Most people argue against the weakest version of an idea (the Strawman). This prompt explicitly tells the AI to ignore those and look for the "Boss Level" arguments.

The "Crux" Identification: Most debates are circular because people are arguing about symptoms. This prompt forces the AI to find the root cause—the "Prior"—which is usually a deep philosophical or moral disagreement (e.g., "Liberty vs. Security" or "Absolute vs. Relative").

Property vs. System: It forces a distinction between what something is (Property) and what something does (System), which provides a 3D view of the topic.

You are an expert innovation strategist specializing in "Echoes & Horizons" synthesis.

**Task**: Generate number innovative concepts / solutions / products / strategies for [specific problem/domain/opportunity].

**Step 1: Historical Analogs (Echoes)**
- Identify 3-5 relevant historical analogs from different eras and geographies.
- For each analog, extract:
  - Core pattern/mechanism that drove success or failure
  - Key enabling conditions at the time
  - Major risks, unintended consequences, and why it declined or succeeded
  - Transferable principles (what made it powerful)

Focus on analogs from:
- Ancient history & classical civilizations
- Industrial revolutions
- 20th century business/technological shifts
- Cultural or social movements
- Military/strategic history (where relevant)

**Step 2: Modern Trends (Horizons)**
- Identify 4-6 current and emerging trends relevant to the domain.
- Categorize them:
  - Technological (AI, biotech, energy, etc.)
  - Behavioral/Social (demographics, values shifts, attention economy)
  - Economic/Platform (creator economy, tokenization, decentralization)
  - Geopolitical/Regulatory
  - Environmental/Climate
- For each trend, note acceleration signals, second-order effects, and convergence potential.

**Step 3: Cross-Pollination Matrix**
Create a synthesis by mapping historical principles against modern trends.
Ask:
- How can this old pattern be supercharged or protected by new technologies?
- What new failure modes emerge from combining them?
- Where does the historical analog expose blind spots in current trends?
- What "missing ingredient" from history could make the modern trend more robust/sustainable/ethical?

**Step 4: Innovation Concepts**
Generate [X] concrete, original concepts. For each:
- Name (memorable and evocative)
- Core Idea (one-sentence punch)
- Historical Root + Modern Engine (explicit linkage)
- Value Proposition & Target Users
- Potential Impact (scale, defensibility)
- Key Risks & Mitigation (informed by historical lessons)
- First-Principles Validation (why this should work now but not before)

**Step 5: Evaluation & Stress Testing**
Score each concept on:
- Novelty (vs. obvious recombinations)
- Feasibility (technical + adoption)
- Resilience (drawing from historical durability)
- antifragility (benefits from volatility)
- Ethical/Societal Fit

**Step 6: Actionable Next Steps**
Provide a 30-90 day validation roadmap, including cheap experiments, key assumptions to test, and signals to watch.

**Output Format**:
- Use clear sections and tables where helpful (especially for the matrix).
- Be specific, evidence-based, and avoid fluff.
- Prioritize depth over breadth.
- Highlight non-obvious insights.

Domain/Problem: insert_here
Additional constraints/context: insert_here

Objective: Construct a compelling counter-argument

1. **Identify the central point of the content**

    * Find the core idea or main argument
    * Identify what the author wants readers to believe or do
    * Reflect on the "why?" of the content
    * Note the scope and limitations of the content

2. **Identify the counter-position**

    * Determine what a thoughtful critic would argue
    * Find the strongest objections you can
    * Identify shared ground and points of departure

3. **Show genuine understanding**

    * Start by stating what the original argument gets right
    * Identify valid concerns the original argument addresses
    * Demonstrate respect for the position you're arguing against

4. **Build a strong opposing case**

    * Present 2-3 compelling counter-points with reasoning
    * Use evidence and logic, not emotion or dismissal
    * Anticipate and address likely rebuttals

5. **Explain the fundamental disagreement**

    * Identify the key assumption or value difference
    * Show why reasonable people might disagree
    * Avoid straw-man fallacy or bad-faith interpretation

6. **Handling exceptions**

    Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
    * respond as best you can and
    * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.

    Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.

7. **Final response**

    If you have relevant info to share, your final response should follow standard writing guidelines, including:

    * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
    * Favor simple sentences that use common words

    **Format the response as:**

    **The original position:** one_sentence_summary_of_what_the_page_argues

    **What this gets right:** genuine_acknowledgment_of_valid_points

    **A counter argument**

1. [Counter-point with reasoning]

2. [Counter-point with reasoning]

3. [Counter-point with reasoning]

    **The core disagreement:** explanation_of_the_underlying_value_or_assumption_difference

8. **Follow-up questions**

    If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

Objective: Advice on whether you should buy or not

1. **Product background**

    * Product name, brand, and model
    * Price and any variations
    * Key specifications

2. **Identify positive attributes**

    * Features that stand out
    * What reviewers praise
    * Value proposition

3. **Identify drawbacks**

    * Common complaints in reviews
    * Missing features
    * Quality or durability issues

4. **Determine fit for user**

    * Ideal buyer profile
    * Who should skip this product
    * Use cases it serves well vs. poorly

5. **Evaluate value**

    * Is this price typical for the category?
    * Should the user wait for a sale?
    * Are there better value alternatives?

6. **Make a recommendation**

    * Based on all preceding steps, form a recommendation
    * The objective is to give the user a gut check
    * At the end of your initial response, inform the user: "Final costs may vary, always verify at checkout"
    * ✅ Buy it
    * ⚠️ Buy, but things to consider
    * 🤔 Consider alternatives
    * ❌ Skip it

7. **Final response**

    If you have relevant info to share, your final response should follow standard writing guidelines, including:

    * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
    * Favor simple sentences that use common words

    **In short:** [Your recommendation, and why. Then one sentence—what is this and who is it for?]

    **Pros**

    * [What's good]
    * what_reviewers_love

    **Cons:**

    * [What's not great]
    * what_reviewers_complain_about

    **Who should buy this:** ideal_buyer
    **Who should skip this:** [Not right for...]

    **Price check:** [Fair? Wait for sale?]

8. **Follow-up questions**

    If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

Act as an expert travel planner. Help me plan a detailed trip with the following criteria. 



**Trip Basics**

- **Destination**: 

- **Dates**: 

- **Travelers**: 2 seniors, 1 adult

- **Trip style**: family



**Budget & Logistics**

- **Total budget**: $amount for everything, or $amount/day per person. Include flights.

- **Currency to use**: [SGD/USD/etc]

- **Accommodation preference**: [Hotel, Airbnb, Hostel, Resort, 4-star+]. Area to stay in if any: [___]

- **Transport**: [Public transport only, Rent a car, Mix, Rideshare/Grab, Walking]



**Interests & Constraints**

- **Must-dos**: please_recommend

- **Interests**: [Food, Museums, Nature, Shopping, History]

- **Avoid**: hiking

- **Pace**: flexible



**Output Format I Want:**

1. **Overview**: Best time to go, weather for my dates, any local events/holidays to know.

2. **Day-by-day itinerary**: Morning / Afternoon / Evening, with travel time between spots. Include 1 backup indoor option per day.

3. **Food**: 2-3 local dishes to try + 5 restaurant/cafe recs at different price points.

4. **Budget breakdown**: Flights, lodging, food, transport, activities, total + buffer.

5. **Logistics**: Visa requirements for passport_nationality, SIM/eSIM, airport to city transport, tipping norms, safety tips.

6. **Packing list**: Tailored to weather + activities.

7. **Booking timeline**: What to book now vs later.



Make it realistic for travel from singapore. Keep transit times honest and don’t pack days too tightly.

Objective: Summarize many reviews

1. **Process available reviews**

    * Note the number of reviews and remember that value as "number_reviews"
    * Overall rating
    * Rating distribution if visible
    * It's possible there aren't any reviews, for example if a product is new or out of stock. If that's the case, don't include any review analysis in your response.

2. **Identify repeated patterns**

    * Common positive themes
    * Common complaints
    * Frequency of each theme

3. **Support themes with evidence**

    * Representative quotes for major themes
    * Specific examples that illustrate points

4. **Evaluate trustworthiness**

    * Do reviews seem genuine?
    * Suspicious patterns (all 5-star, generic language)
    * Verified purchase indicators

5. **Summarize overall sentiment**

    * Would most reviewers buy again?
    * Who loves it vs. who hates it?

6. **Handling exceptions**

    Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
    * respond as best you can and
    * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.

    Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.

7. **Final response**

    If you have relevant info to share, your final response should follow standard writing guidelines, including:

    * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
    * Favor simple sentences that use common words
    If number_reviews is 0, your response should mention that there aren't any reviews and you should jump to the follow-on question.

    **Overview:** [X] reviews, [Y] average rating

    **Pros**

    | Theme | Frequency | Example |
    | :---: | :---: | :---: |

    **Cons**

    | Theme | Frequency | Example |
    | :---: | :---: | :---: |

    **Quality of reviews:** [Do they seem genuine?]

    **Bottom line:** [Would most reviewers buy again?]

8. **Follow-up questions**

    If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

Take this shopworn, cliché, or overly familiar idea: "[INSERT CLICHÉ HERE]".

Ruthlessly subvert it. Pervert the wholesome, safe, or sentimental core into something raw, transgressive, and deliberately shocking. Infuse it with taboo elements—moral decay, body horror, sexual deviance, existential dread, political incorrectness, sacrilege, or visceral grotesquery—while keeping a twisted echo of the original concept so the subversion hits harder.

Rules for the output:
- Amplify shock value through unexpected juxtapositions, bodily fluids, violence, erotic violation, psychological cruelty, or societal taboos.
- Embrace bad taste. Be grotesque, blasphemous, or uncomfortably arousing where it fits.
- Avoid sanitized irony or gentle twists—go for the throat. Make it disturbing, seductive in its wrongness, or blackly hilarious.
- Heighten contrast: keep some visual or thematic remnants of the original cliché (soft lighting, pastel colors, nostalgic framing, etc.) but corrupt them.
- Use vivid, sensory, unflinching detail. No moralizing or disclaimers.

Style: [Insert desired style, e.g., hyper-realistic, dark surrealism, Goya meets modern photography, cyberpunk body horror, etc.]

Additional flavor (optional): [e.g., add extreme close-ups of decaying flesh, dripping fluids, demonic undertones, sexualized violence, etc.]

"Create a detailed efficiency guide for game_name. 
The guide should focus on minimizing wasted effort and maximizing progression. 
Organize the content by chapters/levels/major story beats, and include:

1. **Chapter/Level Sequencing**
   - List the optimal order of events, quests, or missions.
   - Highlight critical checkpoints that unlock new mechanics or areas.
   - Note any optional content worth doing early for long-term benefits.

2. **Skill Tree Optimization**
   - Recommend which skills to unlock first in each chapter.
   - Show how skill priorities evolve as new abilities become available.
   - Provide alternative builds for different playstyles (e.g., stealth, ranged, melee).

3. **Weapons & Gear**
   - Identify the best weapons available in each chapter.
   - Explain how to acquire them efficiently.
   - Suggest upgrade paths and resource-saving strategies.

4. **Upgrades & Crafting**
   - Prioritize upgrades by chapter (e.g., ammo pouches first, armor later).
   - Recommend farming spots for resources.
   - Warn against low-value upgrades that waste materials.

5. **Progression Strategy**
   - Efficient leveling routes (main quests vs side quests).
   - Exploration tips to maximize loot and avoid backtracking.
   - Key hidden mechanics or unlockables that change gameplay efficiency.

6. **Endgame Preparation**
   - Outline late-game skill builds.
   - Best-in-slot weapons and armor.
   - Strategies for final bosses, challenges, or achievements.
"