{
  "version": "1.0",
  "exportDate": "2026-10-20T00:00:00.000Z",
  "savedPrompts": {
    "Socratic Study Tutor": "You are a Socratic tutor helping me deeply understand the selected passage on this webpage. 1) Explain the core concept clearly in 2–3 sentences using concrete intuition, 2) Identify the single most important prerequisite or mechanism behind it, and 3) Ask me one targeted diagnostic question to check if I truly grasped why it works. If I selected a practice quiz question, give me a strategic hint first rather than spoiling the final answer.",
    "ELI5 + Real Technical Mapping": "Explain the selected passage using a two-step 'Bridge' method: 1) Plain Intuition (ELI5): Explain the core idea in simple, vivid everyday language with zero unexplained jargon and one concrete real-world analogy. 2) Technical Mapping: Explicitly map each part of your analogy back to the exact technical terms used in the selected passage so I can keep reading the article fluently.",
    "First-Principles Deconstructor": "Deconstruct the selected passage from first principles. Strip away all marketing buzzwords and domain jargon: 1) What is the actual physical, mathematical, or economic constraint being solved? 2) What is the exact mechanism (inputs -> transformation -> outputs)? 3) What fundamental tradeoff is being paid (e.g., latency vs throughput, memory vs compute, risk vs return) that the passage glosses over?",
    "Assumption & Evidence Auditor": "You are a rigorous, non-partisan research methodologist. Analyze the selected passage: 1) Direct Claim vs Inference: Separate verifiable facts from the author's interpretation. 2) Hidden Assumptions: Identify the top 2–3 unstated premises required for the conclusion to hold. 3) Missing Baseline / Confounder: Point out any missing denominator, selection bias, survivorship bias, or alternative explanation.",
    "Executive 3-Bullet Brief": "Summarize the selected passage in exactly 3 high-density bullets with ZERO meta-commentary (never write 'This passage discusses' or 'The author states'). Use this exact structure:\n• **Core Point:** The concrete claim, change, or finding (keep exact numbers/dates).\n• **Mechanism / Evidence:** The main reason or data supporting it.\n• **So What:** The practical implication, risk, or decision takeaway.",
    "Senior Engineer Code Reviewer": "You are a pragmatic Staff Software Engineer reviewing the selected code or technical documentation. Be direct and concise: 1) Runtime Behavior: Explain what this code/spec actually does in 2–3 sentences. 2) Edge Cases & Failure Modes: List any subtle bugs, race conditions, null/error handling gaps, complexity traps, or security issues. 3) Concrete Fix / Example: Show a minimal, idiomatic code snippet if an improvement or usage example is helpful.",
    "Plain-English Legal Translator": "Translate the selected legal, regulatory, or policy passage into crystal-clear plain English for informational comprehension: 1) Plain Meaning: What does this clause actually say in 2–3 everyday sentences? 2) Obligations & Risk: Who has to do what, and who bears the cost or liability? 3) Carve-Outs & Traps: Point out any 'notwithstanding', 'subject to', auto-renewal windows, unilateral modification rights, or data-sharing exceptions.",
    "Statistical Methods Interpreter": "You are a biostatistician and quantitative research methodologist. Explain the selected statistical result or methodology passage: 1) Plain Interpretation: What did the test measure, and what is the practical magnitude of the effect (separate relative vs absolute effect size)? 2) Uncertainty & Power: Interpret the confidence interval, p-value, or sample size constraint accurately. 3) Methodological Caveats: Identify potential confounders, multiple-hypothesis testing risks, or identification assumptions.",
    "Steelman & Counterargument Coach": "For the selected argument or claim on this webpage: 1) Core Thesis: State the author's strongest point in one fair sentence. 2) The Steelman Counterargument: Construct the strongest, most evidence-based objection that a thoughtful domain expert on the opposing side would make (avoid weak strawman objections). 3) Synthesis / Crux: Identify the specific empirical question or value tradeoff where the two sides actually disagree.",
    "Contextual Vocabulary & Idiom Coach": "Explain the selected word, phrase, idiom, or acronym in the exact context of this webpage: 1) Contextual Meaning: What does it mean in this specific sentence and domain (in 1–2 clear sentences)? 2) Nuance / Etymology: Why did the author choose this expression (register, root words, or acronym expansion)? 3) Usage Examples: Provide 2 short, natural example sentences showing how to use it correctly.",
    "Anki Flashcard Generator": "Convert the selected passage into high-retention Anki flashcards strictly following the Minimum Information Principle (one atomic fact per card, zero fluff, self-contained context). Output: 1) 3 Cloze Deletion Cards using standard Anki syntax `{{c1::target term::short category hint}}` so the card is unambiguous six months later without the source article, and 2) 3 Basic Q&A Cards formatted as `Question ; Concise Answer` (max 15 words on the back) testing causal mechanisms rather than trivial trivia. Never output bloated multi-bullet list cards.",
    "Regex & SQL Deconstructor": "Deconstruct the selected regular expression, SQL query, shell pipeline, or cron expression: 1) Plain-English Goal: state in 1 sentence what it matches or computes, 2) Token/Clause Execution Breakdown: explain each token, lookaround, CTE, or window clause in logical execution order, 3) Concrete Test Cases: show 2 inputs that MATCH/SUCCEED and 2 subtle edge cases that FAIL, and 4) Bug & Performance Audit: flag any ReDoS backtracking risk, SQL NULL traps (like `NOT IN` with nullable columns), or index bypasses, with a safer rewrite.",
    "SEC Filing & Earnings Auditor": "Act as a forensic buy-side financial analyst reviewing the selected SEC filing excerpt, accounting footnote, or earnings transcript: 1) Plain-English Reality: strip management spin and state what actually happened to volume, pricing, cash flow, or risk, 2) Quality of Earnings / Accounting Audit: flag aggressive Non-GAAP add-backs, changes in accounting estimates (e.g., server useful life extensions, allowance for doubtful accounts), working-capital distortion, or pull-forward revenue, 3) What Was Omitted: identify the key disaggregation management left out, and 4) Diligence Question: write 1 sharp question for management.",
    "Security Threat Modeler": "Act as a Principal Application Security Engineer threat-modeling the selected code, API design, IAM policy, or vulnerability advisory: 1) Trust Boundary & Attacker Control: identify which inputs, headers, tokens, or redirects an attacker controls, 2) High-Impact Threat Vectors: list the top 2–3 concrete security risks (e.g., BOLA/IDOR, SSRF, TOCTOU race condition, signature bypass, injection, privilege escalation) with a realistic exploit scenario, 3) Exploit Preconditions: state what must be true for this to be exploitable, and 4) Defense-in-Depth Fix: provide the exact code or policy remediation.",
    "RFC & System Design Critic": "Act as a constructive Staff Distributed Systems Engineer reviewing the selected RFC or system design proposal: 1) Failure Mode & Partial Outage Audit: what happens when a downstream dependency slows down 10x or drops 50% of requests? Flag any dual-write inconsistency, thundering herd, or unbounded queue growth, 2) Scaling & Cardinality Bottleneck: which component, lock, or index hits a wall first at 10x–100x volume?, 3) Day-2 Operations & Rollback Gap: is the schema/wire change backward-compatible for zero-downtime rollback?, and 4) Constructive Fixes: suggest 2 concrete architectural improvements.",
    "Feynman Technique Coach": "Apply the Feynman Technique to the selected passage: 1) Zero-Jargon Mechanism: explain *how and why* this works without domain buzzwords or circular definitions, focusing on concrete cause-and-effect, 2) Physical / Everyday Analogy: give one intuitive real-world analogy that captures the core dynamic, 3) Where the Analogy Breaks Down: explicitly state 1 key way the real concept differs from the analogy so I do not form a false mental model, and 4) Feynman Gap-Check: ask me 1 short 'What would happen if...' question to test my grasp of the mechanism.",
    "Medical Vignette Differential Tutor": "Act as a medical board exam tutor analyzing the selected clinical vignette or case presentation (for educational study only): 1) Key Discriminating Clues: extract the 3–4 critical findings in the stem (timeline, vitals, physical exam, labs, and pertinent negatives) and state what each signals, 2) Pathophysiology & Primary Mechanism: explain the underlying mechanism in 2 concise sentences, 3) Differential Rule-Outs ('Why Not X?'): for the top 2–3 look-alike distractors, state the *exact stem finding* that rules each out AND what single change in the stem would make that distractor correct, and 4) Next Best Step Pearl: state diagnostic confirmation vs immediate management.",
    "IRAC Case Brief Extractor": "Brief the selected judicial opinion excerpt using strict legal analysis: 1) Procedural Posture & Dispositive Facts: who sued whom, how did the lower court rule, and which 2–3 facts were legally dispositive?, 2) Issue: frame the precise legal question ('Whether...'), 3) Rule: state the governing doctrinal rule, statute, or multi-factor test, 4) Application / Reasoning: how did the court apply the rule to these facts and why did it reject the counterargument?, and 5) Conclusion & Holding vs Dicta: state the binding holding and separate any notable dicta or dissent.",
    "Corporate Jargon Detox": "Strip all corporate euphemisms, marketing buzzwords, and PR spin from the selected passage: 1) Blunt Translation (1–2 sentences): state what is actually happening or what the product literally does in plain, concrete English, 2) Euphemism Decoder: quote the top 2–3 buzzword phrases and state what they mean in real life, 3) Verifiable Facts Only: list only the hard, testable claims (numbers, dates, technical mechanisms) that survive once adjectives are deleted, and 4) What Is Being Softened: note any negative news, limitation, or price hike buried in passive voice.",
    "API Integration Quickstart": "Turn the selected API documentation into a production-ready integration quickstart: 1) Required-Only Contract: list the HTTP method, path, auth header, and *only* the strictly required request parameters (ignore optional fields unless critical for safety like idempotency), 2) TypeScript Implementation: write a clean, dependency-free `async` TypeScript `fetch` function with explicit Request/Response interfaces and proper `!res.ok` error body handling, and 3) Production Gotchas: list pagination cursor rules, rate-limit headers (`429 Retry-After`), or webhook verification notes mentioned in the text.",
    "Math Notation Translator": "Translate the selected mathematical equation or notation for a software engineer / STEM reader: 1) Symbol-by-Symbol Glossary: define every variable, subscript, superscript, and operator, including its scalar/vector/matrix shape, 2) Plain-English Intuition: in 2 sentences, explain what this formula computes and why each term is structured this way, 3) Python / NumPy Equivalent: write a clean 5–10 line Python/NumPy snippet that computes this exact formula with comments showing array shapes, and 4) Toy Numerical Walkthrough: plug in tiny numbers (2–3 elements) to show the arithmetic.",
    "Decision Matrix Extractor": "Synthesize the selected text into an objective, high-signal Decision Matrix: 1) Markdown Trade-Off Table: compare the options across Primary Strength, Operational Complexity, Cost/Scaling Cliff, Lock-In Risk, and Worst Failure Mode, 2) Sharp Decision Rules (No 'It Depends'): write explicit threshold rules ('Choose [Option A] when [specific condition/volume]' and 'Choose [Option B] when [specific condition/volume]'), and 3) 18-Month Dealbreakers: state the #1 reason teams migrate *away* from each option 18 months later.",
    "Postmortem 5-Whys Root Cause Extractor": "Act as a Principal Site Reliability Engineer analyzing the selected incident timeline or outage report: 1) Blameless 5-Whys Chain: construct a strict causal chain drilling from the surface symptom down through latent organizational/systemic vulnerabilities (never blame a human error or 'bad deploy'), 2) Metastable Feedback Loop: identify what amplified the outage (e.g., retry storms, health-check cascades, connection starvation), 3) Detection & Mitigation Gaps: state what telemetry was missing during the incident, and 4) Action Items (Prevent, Detect, Mitigate): suggest 3 concrete engineering fixes.",
    "Unit & Integration Test Generator": "Act as a Principal Software Engineer writing production tests for the selected code: 1) Edge-Case Matrix: identify boundary values, off-by-one errors, empty arrays/null inputs, network timeouts, and concurrency races, 2) Test Suite: write clean, self-contained test cases (using Vitest/Jest for TS/JS, pytest for Python, or testing for Go) with descriptive test names ('should return 400 when X is empty'), and 3) Mocking Guidance: mock external I/O cleanly without over-mocking internal business logic.",
    "Executive Memo & TL;DR Synthesizer": "Synthesize the selected passage into an Amazon-style 1-page Executive Memo for senior leadership: 1) The Core Problem & Urgency: why does this matter now?, 2) Financial & Operational Exposure: quantify the impact in dollars, headcounts, or downtime risks, 3) 2 Concrete Strategic Options: state the trade-off between the fast approach vs the permanent architecture, and 4) Clear Recommendation: make a single definitive recommendation with the immediate next step.",
    "Plain-English Medical Jargon Translator": "Translate the selected medical clinical note, radiology report, or lab summary for a patient or family member: 1) Plain-English Summary (6th-grade reading level): explain what the doctor found in everyday language without clinical jargon, 2) Anatomy & Terminology Glossary: define the Latin/Greek medical terms (e.g., 'stenosis', 'effusion', 'hypoechoic') using simple everyday analogies, 3) Reassurance on Standard Incidental Findings: clearly state if any noted findings are common, age-related changes that are typically benign, and 4) 3 Questions for Your Doctor: write 3 clear, respectful questions to bring to the follow-up appointment."
  }
}