Browse Prompts
3317 prompts available · Page 37 of 277
Bear Canister Backpacking Food Planner: Calories per Day, Ounces per Day, Canister Volume Fit, Resupply Split, and Scented Item Storage Plan
Plan a multi day backpacking menu that fits inside the bear canister your route requires: calorie and weight targets per hiker, a day by day menu, a packing order that actually fits the canister volume, a resupply split, and where every scented item goes at night.
Act as a backpacking trip planner who has packed many bear canisters for wilderness permits that require them, builds menus by calories and ounces per day, and checks that every day of food and every scented item truly fits. Inputs: - Route, number of days and nights, park or forest, and the food storage rule on your permit: [RouteAndRule] - Hikers with body weight, pace, and calorie needs if known: [Hikers] - Canister model and stated volume in cubic inches or liters: [Canister] - Foods you like, foods you avoid, allergies, and stove or no cook: [FoodPrefs] - Resupply options (cache, trailhead car, none): [Resupply] - Scented items you carry (toothpaste, sunscreen, lip balm, trash, medications): [ScentedItems] - Output format: [Format] Generate: 1. Daily targets per hiker from Hikers: calories per day and ounces of food per day, aiming for about 100 to 125 calories per ounce, and the total food weight for the trip. 2. A day by day menu: breakfast, lunch and snacks, dinner, and drink mixes, with calories per day and per item, using FoodPrefs. 3. A volume check against Canister: estimated volume per day of food, and whether all days fit; if not, show what to repackage, swap, or carry to the resupply. 4. A packing order for the canister: last day at the bottom, first night on top, flattened bags, and where the scented items sit. 5. A resupply split from Resupply: which days go in the cache or car and when to swap. 6. A scented items plan from ScentedItems: what goes in the canister at night, what stays in the cook area, and how to handle trash. 7. A camp setup note: canister placement distance from tents and cooking, and not to hang or tie it, per RouteAndRule. 8. A shopping and repackaging list with quantities. Constraints: - Food storage rules come from RouteAndRule; where missing, write [check permit rules]. - Use realistic calorie values and say "estimate" for anything not from a package label. - Not medical advice for allergies or diabetes. Practical tone. No em dashes.
Cocktail Menu Layout Spec for Bars and Restaurants: Section Order, Price Alignment Without Dollar Signs, Type Sizes for Low Light, Paper Stock, and Print Proof Checklist
Turn a bar's drink list into a layout spec a designer and printer can follow: section order and hierarchy, how to set names, ingredients, and prices, minimum type sizes for dim rooms, page size and stock, allergen and ABV notes, and a proof checklist before print.
Act as a hospitality menu designer who lays out cocktail and wine menus for bars and restaurants, sets type for reading by candlelight, and writes specs that a printer and the bar manager can sign off on. Inputs: - Venue concept, room lighting, and how guests receive the menu (table card, clipboard, bar top, QR backup): [VenueAndLighting] - The full drink list with names, ingredients, glass, and price, grouped as the bar manager wants: [DrinkList] - Brand assets: typefaces you own licenses for, colors, logo usage: [BrandAssets] - Page size, page count, and binding or holder limits: [FormatLimits] - Required notes: allergens, alcohol free options, local rules on price display or service charges: [RequiredNotes] - How often the list changes and who updates the file: [UpdateCadence] - Output format: [Format] Generate: 1. A section order and hierarchy from DrinkList with the reasoning (for example signatures first, classics second, zero proof given equal weight, not a footnote). 2. An entry style: drink name, ingredient line, and price placement, with whether to drop dollar signs and how to align prices so guests read the drink before the price. 3. A type spec from BrandAssets: typeface, size in points, leading, and weight for section heads, drink names, ingredient lines, and notes, with a minimum ingredient line size suited to VenueAndLighting. 4. A grid and spacing plan for FormatLimits: margins, columns, gutter, and how many entries fit per page without crowding. 5. Color and contrast rules for low light, including a minimum contrast and a warning about thin weights and metallic inks. 6. A paper and finish recommendation for the holder in FormatLimits, with spill and reprint cost in mind. 7. RequiredNotes placement: allergen key, alcohol free marker, service charge line, and any price display rule. 8. An update workflow from UpdateCadence: template file setup, locked styles, and a print proof checklist (spelling of spirits and producers, prices, bleed, crop marks, color proof). Constraints: - Use only drinks and prices given in DrinkList; never invent producers or ABV figures. - Only use typefaces listed in BrandAssets. - Practical designer tone. No em dashes.
Cottage Food Sales Planner: State Allowed Foods Check, Sales Venue and Revenue Cap Rules, Required Label Statement, and Permit Steps for Home Bakers
Check whether your home made products fit your state's cottage food rules, which venues and revenue caps apply, what the label must say (including the made in a home kitchen statement and allergens), and the registration, permit, and training steps before your first sale.
Act as a cottage food consultant who helps home bakers and small food makers read their state's cottage food law, sort products into allowed and not allowed, and set up compliant labels and sales channels before the first farmers market. Inputs: - State and county or city, plus any cottage food law text, agency FAQ, or rule excerpts you have: [StateAndRules] - Products you want to sell with full recipes or ingredient lists and how each is stored: [Products] - Where you plan to sell (farmers market, home pickup, online, shipping, cafe wholesale): [SalesVenues] - Expected yearly gross sales: [ExpectedRevenue] - Kitchen setup: pets, well water, shared kitchen, rental or HOA limits: [KitchenSetup] - Business name and contact details to print: [BusinessDetails] - Output format: [Format] Generate: 1. An allowed foods check per item in Products: allowed, not allowed, or needs review, with the reason (for example cream cheese frosting or fresh fruit pies that need refrigeration), citing StateAndRules. 2. A sales venue table from SalesVenues: allowed or not under StateAndRules, plus any condition such as direct to consumer only or no shipping across state lines. 3. A revenue cap check against ExpectedRevenue, or [confirm cap] if the cap is not in StateAndRules. 4. Required label elements per product: product name, business name and address, net weight, ingredients in descending order by weight, major allergens, and the exact home kitchen statement from StateAndRules. 5. A sample label for one product laid out in print order. 6. Registration, permit, and training steps in order, with any fee and renewal only if given in StateAndRules. 7. Kitchen and HOA notes from KitchenSetup that could block approval or need a fix. 8. Questions to send the state or county agency where the rules are unclear. Constraints: - Rules vary by state and change; use only what is in StateAndRules and mark gaps [confirm with agency]. - Never call a refrigerated or low acid canned item safe to sell without an explicit rule allowing it. - Not legal advice. Friendly, practical tone. No em dashes.
Creator Media Kit and Rate Card Builder: Audience Snapshot, Deliverable Pricing, Usage Rights and Exclusivity Add Ons, and Brand Deal Terms
Build a one page creator media kit and a rate card from your real analytics: audience snapshot, past brand work, priced deliverables per platform, add on fees for paid usage, whitelisting, and exclusivity, plus payment and revision terms for brand deals.
Act as a creator partnerships manager who has priced hundreds of sponsored posts, builds media kits from real analytics exports, and writes rate cards that separate the content fee from usage rights, whitelisting, and exclusivity. Inputs: - Creator niche, handles, and platforms: [CreatorProfile] - Analytics from the last 90 days per platform: followers, average views or reach, engagement, top countries, age and gender split: [AnalyticsExport] - Past brand partnerships with deliverables and, if shareable, results: [PastPartnerships] - Current or target rates and the lowest fee you will accept: [RateFloor] - Deliverables you offer (Reel, TikTok video, YouTube integration, Story set, newsletter mention): [Deliverables] - Terms you want: payment timing, revisions, approval windows, categories you will not promote: [DealTerms] - Output format: [Format] Generate: 1. A media kit one pager: short bio, niche, and an audience snapshot using only AnalyticsExport figures with the date range stated. 2. A why brands work with me section built from PastPartnerships, with results only where provided. 3. A rate card per deliverable from Deliverables and RateFloor, showing the base content fee and a one line description of what is included. 4. Add on pricing for paid usage rights (by duration), whitelisting or Spark Ads access, exclusivity (by category and length), raw footage, and rush turnaround, each as a fee or percentage of base. 5. A bundle option that combines deliverables at a package price. 6. Brand deal terms from DealTerms: deposit and payment timing, number of revision rounds, approval window, FTC disclosure requirement, cancellation fee, and excluded categories. 7. A short pitch email to a brand that attaches the media kit. 8. A negotiation note: where to hold firm, where to trade (for example longer usage for more fee), and what to do if a brand offers product only. Constraints: - Use only figures in AnalyticsExport and PastPartnerships; never invent follower counts, engagement rates, or campaign results. - Every sponsored deliverable carries a clear #ad or paid partnership label. - Confident, plain tone. No em dashes.
Oral History Interview Planner: Narrator Pre Interview, Open Question Guide, Release and Restriction Terms, and Timed Transcript Index for an Archive
Plan an oral history interview the way archives expect: a pre interview summary, a chronological open question guide with follow up probes, a plain language release with restriction options, recording notes, and a timed index and metadata record for the finished recording.
Act as an oral historian who prepares interviews for a community archive, writes open ended question guides that let narrators tell their own story, and delivers recordings with a release, an index, and catalog metadata the archive can accept. Inputs: - Project scope and the collecting repository (historical society, library, university archive) with any of its intake requirements: [ProjectAndRepository] - Narrator background from the pre interview call: life dates, places, roles, topics they want to talk about and topics to avoid: [NarratorBackground] - Research questions or themes for this collection: [ResearchThemes] - Recording setup and session length: [RecordingSetup] - Release terms the repository allows (copyright transfer, Creative Commons, closed until a date, name redaction): [ReleaseOptions] - A rough transcript or notes with timestamps from the session, if already recorded: [SessionNotes] - Output format: [Format] Generate: 1. A pre interview summary from NarratorBackground: a short life timeline and the topics the narrator agreed to cover or asked to skip. 2. A question guide in rough chronological order, tied to ResearchThemes, with open questions ("Tell me about...", "What do you remember about...") and two follow up probes each. 3. A sensitive topics plan: how to approach topics that came up in NarratorBackground, and how to offer the narrator a pause or skip. 4. A recording slate and checklist from RecordingSetup: what to say at the start, room tone, levels check, and session length. 5. A plain language release draft built only from ReleaseOptions, with checkboxes for each restriction option the narrator can choose. 6. A timed index from SessionNotes: segment start times, a short synopsis, keywords, and names and places mentioned. 7. A catalog metadata record (title, narrator, interviewer, date, place, duration, subjects, restrictions, format) for the repository. 8. Follow up items: spellings to confirm, photographs or documents the narrator offered, and a thank you note. Constraints: - Do not add facts to the narrator's life story that are not in the inputs. - Do not draft release terms the repository did not list in ReleaseOptions. - Respectful, neutral interviewer tone. No em dashes.
On-Call Shift Handoff Note Writer: Open Incidents, Silenced Alerts, Pending Changes, Watch Items, and Escalation Contacts for the Next Engineer
Turn the end of an on-call shift into a handoff note the next engineer can act on in five minutes: open incidents with status and next action, silences that will expire, pending changes and freezes, things to watch, and who to call.
Act as a site reliability engineer who has run many on-call rotations and writes shift handoff notes that the incoming engineer can read in five minutes and act on without asking a single follow up question. Inputs: - Rotation details: team, shift window and time zone, outgoing and incoming engineer: [RotationDetails] - Open and recently resolved incidents with ticket IDs, severity, current status, and what was tried: [Incidents] - Alerts that are silenced, acknowledged, or flapping, with silence expiry times: [AlertState] - Deploys, migrations, maintenance windows, or change freezes in the next shift: [PendingChanges] - Rough notes, chat excerpts, or anything the outgoing engineer is worried about: [ShiftNotes] - Escalation paths and contacts for dependent teams and vendors: [EscalationContacts] - Output format: [Format] Generate: 1. A three line top summary: overall state, the single most important thing to do first, and any time sensitive deadline in the incoming shift. 2. An open incidents table from Incidents: ID, severity, status, what was tried, next action, and owner. 3. A silences and alerts section from AlertState: every silence with exact expiry in the shift time zone, and what to do if the alert fires again after expiry. 4. A changes calendar from PendingChanges in time order, with who is driving each change and a rollback note. 5. Watch items pulled from ShiftNotes: things that are not incidents yet, with the metric or dashboard to check and the threshold that should trigger action. 6. An escalation block from EscalationContacts in the order to call, with when to use each. 7. Loose ends: tickets to update, postmortems to schedule, and questions for the team lead. 8. A short handoff checklist the incoming engineer confirms out loud or in chat. Constraints: - Use only facts from the inputs; mark anything unclear as [confirm with outgoing]. - Write times with time zone, never "later" or "soon". - No blame language. Plain, terse tone. No em dashes.
Audio Drama Script Writer: Scene Headings, SFX and Music Cues, Voice Only Exposition, Cast and Sound Lists for Fiction Podcasts
Write a fiction podcast episode script built for the ear: scene headings with location sound, numbered SFX and music cues, dialogue that tells listeners who is speaking and where they are without narration dumps, plus a cast list and a sound effects list for the editor.
Act as an audio drama writer and sound minded script editor who writes fiction podcast episodes for the ear, marks every sound and music cue for the editor, and makes sure listeners always know who is talking and where they are. Inputs: - Series premise, tone, and genre: [SeriesPremise] - Episode summary, beats, and target runtime in minutes: [EpisodeBeats] - Characters in this episode with voice notes (age, accent, pace, verbal tics): [CastNotes] - Locations and their sound beds (rain on tin roof, ship engine hum, office HVAC): [LocationSounds] - Production limits: number of actors, remote or in studio recording, music library or composer, budget for SFX: [ProductionLimits] - Output format: [Format] Generate: 1. A cold open of about 30 to 60 seconds that hooks with sound before dialogue. 2. The full script in audio drama format: numbered scenes with headings (INT/EXT, location, time), an AMBIENCE line from LocationSounds, character names in caps, and parentheticals only where delivery matters. 3. Numbered SFX and MUSIC cues inline (SFX 1, MUSIC 1 IN, MUSIC 1 OUT) placed where the editor needs them. 4. Voice only exposition: characters reveal names, places, and actions through natural dialogue and sound, with no narrator unless SeriesPremise uses one. 5. A runtime check: approximate minutes per scene at about 140 to 160 spoken words per minute, against EpisodeBeats. 6. A cast list with lines per character and voice notes from CastNotes, flagging scenes that need actors in the same room under ProductionLimits. 7. A sound list for the editor: every SFX and ambience with scene number, whether it is library or needs foley. 8. A clarity pass: lines where a listener could lose track of who is speaking, with fixes. Constraints: - Keep the cast within ProductionLimits. - Do not describe visuals that only a camera could show. - Original writing only; no lyrics or scenes from existing works. No em dashes.
Law Firm Advertising Rule Reviewer: State Bar Rule 7.1 to 7.3 Checks for Websites, Google Ads, Results Pages, Testimonials, and Required Disclaimers
Review law firm website pages, paid search ads, case results, and client testimonials against the professional conduct advertising rules your state bar adopted, flag misleading or unverifiable lines, list the disclaimers each placement needs, and rewrite risky copy.
Act as a legal marketing compliance reviewer who checks law firm advertising against the state bar version of Model Rules 7.1 to 7.3, catches misleading claims and unverifiable superlatives, and hands the responsible attorney a marked up draft before anything goes live. Inputs: - State or states where the firm is licensed and advertises, plus any rule text or bar opinion excerpts you have: [StateRules] - Practice areas and the responsible attorney named for advertising: [PracticeAndResponsibleAttorney] - The copy to review, pasted by placement (home page, practice page, Google Ads headline and description, results page, email, billboard, social post): [CopyByPlacement] - Case results you want to feature, with the gross amount, fees and costs, and the facts of each matter: [CaseResults] - Testimonials, awards, ratings, and certifications you plan to mention, with who issued them: [EndorsementsAndAwards] - Output format: [Format] Generate: 1. A line by line claim table from CopyByPlacement: quoted line, placement, issue type (misleading, unverifiable comparison, implied guarantee, specialist claim, solicitation, missing disclaimer, fine), and risk level. 2. Comparison and superlative flags: lines like "best", "top", "most experienced", or "aggressive" that cannot be factually substantiated, with the reason. 3. A case results review from CaseResults: whether each result needs a past results disclaimer, whether the amount should be gross or net, and whether the facts are described fairly enough that the result is not misleading out of context. 4. An endorsements check from EndorsementsAndAwards: who issued each award, whether the selection method can be stated, and whether a specialist or certified claim matches a certifying body named in StateRules. 5. Required disclaimers per placement, such as "Attorney Advertising", the responsible attorney name and office address, and a no guarantee statement, each tied to the rule excerpt in StateRules or marked [confirm rule]. 6. Solicitation notes for any email, text, or social message aimed at a specific prospective client. 7. Compliant rewrites for every flagged line that keep the selling point. 8. A filing and retention note: whether the state requires filing ads with the bar and how long copies must be kept, or [confirm with bar]. Constraints: - Use only rules and opinions given in StateRules; where a rule is not provided, say [confirm rule] instead of quoting one from memory. - Never invent case results, verdicts, or award criteria. - Not legal ethics advice; the responsible attorney makes the final call. Plain reviewer tone. No em dashes.
Claude Extended Thinking Budget Planner: budget_tokens vs max_tokens, Tool Use with Thinking Blocks Passed Back, Streaming Thresholds, Caching Effects, and a Cost Test Plan
Plan how to turn on extended thinking in the Claude API for a real feature: choose a budget_tokens and max_tokens pair per task, keep thinking blocks intact across tool calls, know which parameters stop working, decide when to stream, and test cost and quality before rollout.
Act as an LLM platform engineer who adds extended thinking to Claude API features in production, sets thinking budgets per task from test data, and keeps tool use, caching, and billing behavior correct. Inputs: - The feature and its task types (for example contract clause analysis, multi step data question answering, code review), with current model and settings: [FeatureAndTasks] - Current request shape: system prompt size, typical input tokens, max_tokens, temperature, tool definitions, and tool_choice: [CurrentRequest] - Whether the feature uses tool calls in a loop and how the conversation history is stored: [ToolLoop] - Latency and cost limits per request and per month: [Limits] - Whether prompt caching is enabled and where the cache breakpoints are: [CachingSetup] - Output format: [Format] Generate: 1. A task by task decision on whether extended thinking is worth enabling for FeatureAndTasks, with the reason. 2. A budget table per task: starting budget_tokens, max_tokens, and why, keeping budget_tokens at the documented minimum or above and below max_tokens unless interleaved thinking applies [confirm in Anthropic docs]. 3. Parameter conflicts in CurrentRequest that change when thinking is on: temperature and top_k changes, forced tool_choice, and assistant prefill, with the fix for each [confirm in Anthropic docs]. 4. A tool loop plan from ToolLoop: pass the thinking blocks, including their signatures, back unchanged in the assistant turn that holds the tool_use, and whether interleaved thinking between tool calls is needed. 5. A streaming rule: when max_tokens is large enough that streaming should be used, and how the UI handles thinking deltas. 6. A caching note from CachingSetup: what changing the thinking budget does to cached prefixes and where to keep breakpoints. 7. A billing note: thinking tokens are billed as output tokens, and on newer models the returned thinking may be a summary while billing covers the full thinking [confirm per model]. 8. A cost and quality test plan against Limits: a fixed eval set, two or three budgets per task, and the metrics to log (usage.output_tokens, latency, pass rate). Constraints: - Do not invent prices, model names, or limits; mark them [confirm in Anthropic docs]. - Never suggest editing or removing thinking blocks mid tool loop. - Plain engineer tone. No em dashes.
Commercial Lease Letter of Intent Comparison for Small Business Tenants: Side by Side Terms, Net Effective Rent Math, Guaranty and Exclusive Use Risks, and a Counter Proposal
Compare two or three landlord letters of intent for retail, restaurant, or office space side by side: base rent and escalations, free rent, tenant improvement allowance, CAM estimates, personal guaranty, exclusive use, and contingencies, with net effective rent worked out from your numbers and a counter proposal for the space you prefer.
Act as a tenant representation broker who helps small business owners compare landlord letters of intent before a lease is drafted, shows the rent math step by step, and points out the terms that cost the most later. Inputs: - Each LOI's key terms pasted or summarized: premises size, base rent per square foot, escalations, lease type (NNN, modified gross), term, free rent, TI allowance, CAM and tax estimates, security deposit: [LoiTerms] - Non money terms from each LOI: personal guaranty, exclusive use, permitted use, delivery condition, renewal options, assignment and subletting, signage: [LoiConditions] - The business and how it uses the space (restaurant needing a hood and grease trap, salon, retail, office): [BusinessUse] - The build out budget estimate from a contractor, if any: [BuildOutEstimate] - Must haves and deal breakers: [MustHaves] - Output format: [Format] Generate: 1. A side by side comparison table of every commercial lease letter of intent, built from LoiTerms and LoiConditions, one column per LOI. 2. Rent math for each LOI: base rent by year with escalations, total base rent over the term, free rent value, TI allowance total, and net effective base rent per square foot per year, showing each calculation. 3. An occupancy cost line for year one: base rent plus estimated CAM and taxes per LOI. 4. A build out gap from BuildOutEstimate: TI allowance versus cost, and what the tenant pays out of pocket. 5. A risk table of non money terms: personal guaranty scope, missing exclusive use, delivery condition that leaves work for the tenant, permit contingency, and assignment limits, rated for BusinessUse. 6. A MustHaves check marking which LOI meets each item. 7. A recommended letter of intent and a counter proposal list for small business tenants with specific asks in priority order. 8. Questions to ask the landlord and items for an attorney to review before signing anything. Constraints: - Use only the numbers in LoiTerms and BuildOutEstimate; show the math and round to cents only at the end. - Note that an LOI is usually non binding except where it says otherwise, and flag any binding clauses. - Not legal or tax advice. Plain broker tone. No em dashes.
EPA Section 608 Technician Certification Practice Item Writer: Core, Type I, Type II, and Type III Questions with Rule Based Answer Keys, Distractor Logic, and a Weak Area Drill Plan
Write original multiple choice practice items for the EPA Section 608 refrigerant technician exam sections, each tied to a rule or concept from your course materials, with an answer key that explains why every distractor is wrong and a drill plan for the areas students miss most.
Act as an HVAC trade school instructor and item writer who prepares students for the EPA Section 608 technician certification, writes original multiple choice items from the course's own rule summaries, and never copies questions from proctored exams. Inputs: - Exam sections to cover (Core, Type I small appliances, Type II high pressure, Type III low pressure) and how many items each: [SectionsAndCounts] - Rule summaries or textbook pages the items must be based on, pasted or summarized: [CourseRules] - Topics students missed most on the last practice round: [WeakAreas] - Student level (first year apprentice, career changer, experienced tech renewing knowledge): [StudentLevel] - Exam format notes from your certifying organization (items per section, passing score, open or closed book): [ExamFormatNotes] - Output format: [Format] Generate: 1. A blueprint table: section, topic, number of items, and the CourseRules line each topic comes from. 2. Practice items for SectionsAndCounts, each with a stem, four options A to D, one correct answer, and the section tag. 3. An answer key that cites the rule from CourseRules for the correct answer and gives one line on why each distractor is wrong (wrong threshold, wrong refrigerant class, wrong equipment type, or a common shop myth). 4. Distractor logic notes: which misconception each wrong option targets, so the instructor can spot patterns. 5. Extra items weighted toward WeakAreas, at least two per weak topic. 6. A reading level check for StudentLevel: plain stems, no double negatives, units stated (psig, inches of mercury, pounds of charge). 7. An ExamFormatNotes summary for students with each fact marked [confirm with certifying organization]. 8. A drill plan: which items to repeat, in what order, over the week before the exam. Constraints: - Base every correct answer on CourseRules; if a rule is not in CourseRules, do not write the item and add it to a needs source list. - Do not reproduce items from any proctored exam or commercial question bank. - Plain instructor tone. No em dashes.
Hospital Discharge Instructions Plain Language Writer: Clinician Orders to Patient Steps, Medication Schedule Table, Warning Signs by Urgency, Follow Up List, and Teach Back Questions
Turn the discharge orders a nurse or physician has already written into patient instructions at about a sixth grade reading level: what to do at home, a medication schedule table, warning signs sorted into call the office and call 911, follow up appointments, and teach back questions for the bedside review.
Act as a nurse educator who rewrites hospital and surgery center discharge orders into plain language patient instructions, keeps every clinical detail exactly as the care team wrote it, and checks understanding with teach back. Inputs: - De-identified discharge orders from the care team: procedure or diagnosis, activity, diet, wound care, bathing, driving, and work rules: [DischargeOrders] - Medications to take at home with dose, timing, and any stopped or changed home medications: [MedicationList] - Warning signs and who to contact, exactly as the care team listed them: [WarningSigns] - Follow up appointments and tests already scheduled or to be booked: [FollowUps] - Patient context that affects how instructions are written (preferred language, caregiver at home, vision or reading needs): [PatientContext] - Output format: [Format] Generate: 1. A short opening that names the procedure or diagnosis from DischargeOrders in everyday words. 2. Home care steps grouped under plain headings (Your incision, Moving around, Eating, Showering, Driving and work), each a short numbered step with any number or time limit kept exactly as written. 3. A medication schedule table from MedicationList: medicine, what it is for in plain words, how much, when (morning, noon, evening, bedtime), and notes, plus a separate Stop taking or Changed list. 4. Warning signs from WarningSigns split into two boxes: Call your care team and Call 911, using the care team's thresholds word for word. 5. A follow up list from FollowUps with what to bring and who books it. 6. A caregiver note if PatientContext mentions one. 7. Three to five teach back questions the nurse can ask before the patient leaves. 8. A clinician check list of every place where the orders were unclear, marked [ask care team]. Constraints: - Never add, change, or drop a medicine, dose, limit, or warning sign. If something is missing, ask; do not fill it in. - Aim for short sentences and common words; explain any medical term once in parentheses. - Not medical advice; the care team reviews the final sheet. Remove any names, dates of birth, or record numbers. No em dashes.