30 Claude Prompts for Course Outlines You Still Teach

<context> I have outcomes. I need modules with one job each. This is a written curriculum map, not a designed course homepage and not a lesson script. </context> <inputs> - Course topic: [COURSE TOPIC] - Outcome list: [OUTCOME LIST] - Learner: [LEARNER] - Time budget: [TIME BUDGET] - Max modules I can record: [MAX MODULES] - Notes: [PASTE NOTES] </inputs> <task> Group [OUTCOME LIST] into at most [MAX MODULES] modules. For each: one-sentence job, outcomes it owns, a time share that sums to [TIME BUDGET], the first lesson title, and the exit proof. If an outcome fits nowhere, leave it UNPLACED. Do not invent a bonus module. </task> <constraints> - One job per module. Topic labels are not jobs. - Do not add outcomes I did not list. - Do not create a welcome module unless an outcome requires orientation. - If [MAX MODULES] is too small, say which outcomes must drop. Do not squash five jobs into one module. </constraints> <format> Module cards (job, outcomes, time, first lesson, exit proof), then UNPLACED outcomes, then a one-line course spine. </format>

<context> My module names read like a syllabus. I need promise names [LEARNER] can finish, not topic labels. Do not invent a punchy name that claims a result I cannot teach. </context> <inputs> - Course topic: [COURSE TOPIC] - Learner: [LEARNER] - Module list with jobs: [MODULE LIST] - Words I never use: [BANNED PHRASES] - Platform character limit if I have one: [NAME LIMIT OR NONE] </inputs> <task> Rename each item in [MODULE LIST]. Give 2 name options per module: a short promise and a longer classroom title. Each name must match the module job and stay inside what I can teach. Flag any option that overclaims. Honor [BANNED PHRASES] and [NAME LIMIT]. </task> <constraints> - Do not use unlock, masterclass, or secret unless I already use those words. - Do not name a result I cannot prove in that module. - Do not number modules as Module 1 unless I asked. - Keep names speakable on camera in one breath. </constraints> <format> Table: old name, short promise, classroom title, overclaim flag. Then a recommended set in teaching order. </format>

<context> I need a module order with real dependencies. If a student skips a module, I need to know what breaks. Do not invent a prerequisite I did not list. </context> <inputs> - Course topic: [COURSE TOPIC] - Module list: [MODULE LIST] - Outcome list: [OUTCOME LIST] - Starting skill: [STARTING SKILL] - Optional modules I might skip: [OPTIONAL MODULES OR NONE] </inputs> <task> Order [MODULE LIST]. For each module: required prior modules, the skill that must already be true, what breaks if skipped, and whether it can be optional. If two modules have no dependency, say they can swap. Do not add a foundation module I did not list. </task> <constraints> - Do not invent a tool-setup module to paper over a thin start. - If [STARTING SKILL] cannot enter module one, flag the hole. Do not invent a prep course. - Keep optional tags rare. Most skippable modules should stay PARK, not fake-optional. </constraints> <format> Ordered list with prior, must-already-be-true, skip risk, optional tag. Then swap pairs and a hole list. </format>

<context> I will record and teach this myself. Minutes must add up. Do not invent extra weeks, live calls, or a TA I do not have. </context> <inputs> - Course topic: [COURSE TOPIC] - Module list: [MODULE LIST] - Time budget: [TIME BUDGET] - Lesson length I can record: [LESSON LENGTH] - Live calls I can host: [LIVE CALLS OR NONE] - Days I have to record: [DAYS I HAVE] </inputs> <task> Budget each module: teaching minutes, number of lessons at [LESSON LENGTH], practice minutes, and whether a live call is required. Sums must fit [TIME BUDGET] and [DAYS I HAVE]. If the list does not fit, cut scope, do not add days. Note modules that need a live call I did not offer. </task> <constraints> - Do not invent a 12-week calendar if [TIME BUDGET] is six hours. - Do not add office hours I did not list. - Recording time is not the same as student time. Show both if they differ. - If a module needs more than I can film in [DAYS I HAVE], mark CUT OR SPLIT. </constraints> <format> Budget table (teach, lessons, practice, live, record days), totals, then CUT OR SPLIT rows. </format>

<context> I need a hard not-in-this-course list so the outline and the sales page stay honest. Do not fill the gaps with a bonus module I will not record. </context> <inputs> - Course topic: [COURSE TOPIC] - Kept outcomes: [OUTCOME LIST] - Tempting extras: [TEMPTING TOPICS] - Time budget: [TIME BUDGET] - Adjacent courses I might sell later: [LATER COURSES OR NONE] - Audience confusion I already hear: [CONFUSION I HEAR] </inputs> <task> Write a scope memo: (1) in-scope in one sentence, (2) adjacent topics I will mention in one slide only, (3) topics I will not teach and why, (4) a spoken scope line for lesson one, (5) a sales-page line that matches. Park [TEMPTING TOPICS] that belong in [LATER COURSES]. Answer [CONFUSION I HEAR] without adding scope. </task> <constraints> - Do not invent a later course title I did not list. - Do not keep a tempting topic because a competitor teaches it. - The spoken line and the sales line must match. - Specific excludes, not everything else. </constraints> <format> Five headed sections, then a one-line scope I can put above the outline. </format>

<context> I need one module turned into lessons I can record. Each lesson has one job. This is a written breakdown, not a full script and not HTML. </context> <inputs> - Course topic: [COURSE TOPIC] - Module name and job: [MODULE NAME] - Module outcome: [MODULE OUTCOME] - Learner: [LEARNER] - Lesson length I can record: [LESSON LENGTH] - Notes: [PASTE NOTES] </inputs> <task> Break [MODULE NAME] into lessons that fit [LESSON LENGTH]. For each: one job, open in one line, teach block, practice, close, and the file name I should use. Lessons must sum to the module job. If [PASTE NOTES] cannot support a lesson, write NEEDS NOTES instead of filling it. </task> <constraints> - Do not write the spoken script in this pass. - Do not add a recap lesson that restates the module. - Do not invent an example that is not in [PASTE NOTES]. - Prefer fewer lessons that finish over a pile of 8-minute fragments. </constraints> <format> Numbered lessons with job, open, teach, practice, close, file name. Then NEEDS NOTES rows. </format>

<context> I need a single lesson outline I can teach from. Not a teleprompter dump. Not a designed slide deck. I will record it later in my voice. </context> <inputs> - Lesson topic: [LESSON TOPIC] - Module outcome it serves: [MODULE OUTCOME] - Lesson length: [LESSON LENGTH] - Learner: [LEARNER] - Example I can actually show: [EXAMPLE I HAVE] - Notes: [PASTE NOTES] </inputs> <task> Outline one lesson: (1) open that names the job, (2) teach beats with talking points from [PASTE NOTES], (3) the worked [EXAMPLE I HAVE], (4) a practice the student can finish before the close, (5) a close that restates [MODULE OUTCOME], (6) a minute map that sums to [LESSON LENGTH]. Leave a hole where notes are thin. </task> <constraints> - Do not invent a case, screenshot, or number I did not paste. - Do not write every spoken sentence. Talking points only. - If [EXAMPLE I HAVE] cannot carry the teach block, say so and stop. - No welcome-back or like-and-subscribe filler. </constraints> <format> Minute map, then open / teach / example / practice / close, then holes I must fill before I record. </format>

<context> I need a spoken open and close for one lesson. I will say these lines on camera or live. Do not invent a student story to make the hook land. </context> <inputs> - Lesson topic: [LESSON TOPIC] - Module outcome: [MODULE OUTCOME] - Learner: [LEARNER] - Proof I can show in the first 20 seconds: [PROOF I CAN SHOW] - Voice: [DIRECT / WARM / CALM] - Lesson length: [LESSON LENGTH] </inputs> <task> Write 5 open options (8 to 20 seconds) and 3 close options (15 to 30 seconds). Each open must name the job and use only [PROOF I CAN SHOW]. Each close must restate [MODULE OUTCOME] and point to the practice, not to a new topic. Mark any line I cannot say in one breath. </task> <constraints> - Do not invent a student name, quote, or result. - No hey-everyone or welcome-back. - The close must not introduce a new outcome. - If [PROOF I CAN SHOW] is NONE, open on the job, not on a fake result. </constraints> <format> Ranked opens with seconds and proof tag, ranked closes, then two pairs I should record first. </format>

<context> I have notes I already trust. I need talking points for one lesson, not new research and not a full script. Thin notes stay thin. </context> <inputs> - Lesson topic: [LESSON TOPIC] - Notes or transcript I already have: [PASTE NOTES] - Module outcome: [MODULE OUTCOME] - Example I can show: [EXAMPLE I HAVE] - Claims I will not make: [OFF-LIMITS CLAIMS] </inputs> <task> Turn [PASTE NOTES] into numbered talking points in teaching order. Each point: the claim, the source line, the example if present, and a check I can ask out loud. If a point needs a fact I did not paste, write NEEDS NOTES. Honor [OFF-LIMITS CLAIMS]. </task> <constraints> - Do not invent a study, tool tip, or statistic. - Do not expand a one-line note into a three-act story. - Do not write the full spoken paragraph unless a line is a definition I must say exactly. - If the notes cannot support [MODULE OUTCOME], say the lesson is not ready. </constraints> <format> Numbered talking points with source tags, then NEEDS NOTES, then a not-ready note if the outcome cannot stand. </format>

<context> I will record these lessons myself. I need a shoot plan: order, runtime, retakes, and B-roll I can actually film. Do not invent a studio, editor, or stock library. </context> <inputs> - Lesson list: [LESSON LIST] - Lesson length I want on the student side: [LESSON LENGTH] - Days I have: [DAYS I HAVE] - B-roll I can film: [B-ROLL I CAN FILM] - Tools on my desk: [TOOLS I HAVE] - Face on camera: [YES / NO] </inputs> <task> Build a recording plan: shoot order, target runtime, buffer for retakes, B-roll from [B-ROLL I CAN FILM] only, and a same-day checklist. If a lesson needs B-roll I do not have, mark TYPE ONLY. Sums must fit [DAYS I HAVE]. Do not add a shoot day. </task> <constraints> - Do not invent a second camera, a set, or an editor. - Do not request stock footage. - If [FACE ON CAMERA] is NO, plan voice-over plus the B-roll I named. - Prefer fewer honest files over a shot list I cannot finish. </constraints> <format> Day-by-day shoot table, TYPE ONLY lessons, then a same-day checklist I can print. </format>

<context> I need one practice exercise students can finish after a lesson. I will run it live or on video. Do not invent a dataset, tool login, or client file I do not have. </context> <inputs> - Lesson topic: [LESSON TOPIC] - Outcome it proves: [OUTCOME] - Learner: [LEARNER] - Time they have: [EXERCISE TIME] - Assets I can give them: [ASSET LIST] - Tools they already have: [TOOLS THEY HAVE] </inputs> <task> Design one exercise: goal in one sentence, steps, the file or prompt they start with (from [ASSET LIST] only), the done look, a common fail, and a 2-minute teacher walkthrough outline. If an asset is missing, write NEEDS ASSET and stop. Stay inside [EXERCISE TIME]. </task> <constraints> - Do not invent a spreadsheet, API key, or sample client. - Do not require a paid tool that is not in [TOOLS THEY HAVE]. - Do not write a group exercise if I did not say I host a cohort. - The walkthrough must be something I can record once. </constraints> <format> Goal, steps, start file, done look, fail, walkthrough outline, then NEEDS ASSET if blocked. </format>

<context> I need a worksheet that follows one lesson. Blanks, a worked example I already have, and no invented numbers. This is copy I can paste into a doc, not a designed PDF. </context> <inputs> - Lesson topic: [LESSON TOPIC] - Notes: [PASTE NOTES] - Worked example I can show: [EXAMPLE I HAVE] - Outcome: [OUTCOME] - Time: [EXERCISE TIME] - Blanks I want: [BLANK COUNT] </inputs> <task> Write a worksheet: title, one-line why, the worked [EXAMPLE I HAVE], then [BLANK COUNT] student blanks that mirror the example, and a self-check of 4 questions. Use only facts in [PASTE NOTES]. If the example cannot support a blank, write NEEDS EXAMPLE DATA. </task> <constraints> - Do not invent a data row to make the sheet look complete. - Do not add a second example I did not paste. - Keep instructions short enough to read on a phone. - This is a written worksheet, not HTML. </constraints> <format> Worksheet copy in teaching order, then NEEDS EXAMPLE DATA rows, then a 30-second teacher note. </format>

<context> I need a capstone brief that proves the kept outcomes. Students must finish it with time and tools I already named. Do not invent a client, a dataset, or a portfolio piece I will not review. </context> <inputs> - Course topic: [COURSE TOPIC] - Outcome list I kept: [OUTCOME LIST] - Learner: [LEARNER] - Time they have after the lessons: [TIME BUDGET] - Tools they have: [TOOLS THEY HAVE] - Sample I can show: [SAMPLE I MADE OR NONE] </inputs> <task> Write a capstone brief: promise in one sentence, deliverables mapped to [OUTCOME LIST], steps, timebox, tools, a done look, and what I will not review. If an outcome cannot appear in the deliverable, tag UNPROVABLE and recommend dropping it from the course promise. If [SAMPLE I MADE] is NONE, list the sample I must record first. </task> <constraints> - Do not invent a partner company or a live client. - Do not require a tool I did not list. - Do not write a 40-hour capstone if [TIME BUDGET] is four hours. - The brief must be teachable in one live session. </constraints> <format> Brief, outcome-to-deliverable map, UNPROVABLE rows, then the sample I must record. </format>

<context> I need a rubric I can score in one pass, live or on a recording. Levels must be visible in the student file. Do not invent a grade curve or a student sample score. </context> <inputs> - Exercise name: [EXERCISE NAME] - Outcome: [OUTCOME] - Notes or brief: [PASTE NOTES] - Levels I use: [LEVELS] - Time I have to score one file: [SCORE TIME] - Must-fail errors: [MUST FAIL] </inputs> <task> Write a rubric with [LEVELS] (for example miss / approaching / pass / strong). Each cell: what I will see in the file, in one line. Add a must-fail list from [MUST FAIL]. Keep the whole rubric scorable inside [SCORE TIME]. No points unless I asked for points. </task> <constraints> - Do not invent a student name or an example score. - Do not add a criterion that is not in [PASTE NOTES] or [OUTCOME]. - Avoid taste words (creative, professional) unless you define a visible tell. - I will teach this rubric on camera. Keep the language I can say out loud. </constraints> <format> Rubric table, must-fail list, then a 60-second spoken version I can record. </format>

<context> I need reusable feedback lines for one exercise, by rubric level. I will paste them and then record a short fix. Do not invent a student, a score, or a private detail. </context> <inputs> - Exercise name: [EXERCISE NAME] - Rubric I already have: [RUBRIC] - Outcome: [OUTCOME] - Common fails I already see: [COMMON FAILS] - Voice: [DIRECT / WARM] - Words I never use: [BANNED PHRASES] </inputs> <task> For each level in [RUBRIC], write 3 comments I can paste: what is true, what to fix next, and a pointer back to the lesson. Add 3 comments for each item in [COMMON FAILS]. Leave a [NAME] token I will replace. Do not write a full video script. </task> <constraints> - Do not invent a student story. - Do not praise work I have not seen. - Honor [BANNED PHRASES]. - Keep each comment under 60 words so I can say it on a Loom. </constraints> <format> Comments grouped by level and by common fail, each with a one-line record cue. </format>

<context> I am close to opening the cart. I need a checklist of assets I said I have, not a motivational launch plan. Missing files stay missing. </context> <inputs> - Course topic: [COURSE TOPIC] - Platform: [PLATFORM] - Module list: [MODULE LIST] - Assets I already have: [ASSET LIST] - Offer dates: [OFFER DATES] - Live calls I will host: [LIVE CALLS OR NONE] </inputs> <task> Build a pre-launch checklist: lessons recorded, exercises attached, capstone brief, welcome, sales page outline, emails, and live-call slots. Mark each item HAVE, MISSING, or NOT NEEDED. If [OFFER DATES] arrive before MISSING lesson files, say DELAY. Do not invent an asset to look ready. </task> <constraints> - Do not add a community, a Slack, or a bonus I did not list. - Do not mark a module HAVE unless it is in [ASSET LIST]. - Platform setup steps must match [PLATFORM] only. - If live calls are NONE, do not schedule a kickoff I will not host. </constraints> <format> Checkbox groups, then MISSING blockers, then a GO / DELAY line tied to [OFFER DATES]. </format>

<context> I need a waitlist plan and the first week after someone buys. Emails and one live session I can actually host. Do not invent a 12-email sequence I will not send. </context> <inputs> - Course topic: [COURSE TOPIC] - Learner: [LEARNER] - Platform: [PLATFORM] - First week goal: [FIRST WEEK GOAL] - Emails I will send: [EMAIL COUNT] - Live session I can host: [LIVE CALLS OR NONE] - Dates: [OFFER DATES] </inputs> <task> Write: (1) waitlist emails up to [EMAIL COUNT], (2) the day-zero access email, (3) a first-week calendar that hits [FIRST WEEK GOAL], (4) one live session outline if I named a call, (5) a do-not-send list. Every email is an outline with subject, 5 bullets, and a CTA I can keep. No invented proof. </task> <constraints> - Do not invent a testimonial or a seat count for urgency. - Do not write 12 emails if I said 4. - If live calls are NONE, the first week must work asynchronously. - Subjects must be sendable. No fake Re: or Fwd:. </constraints> <format> Waitlist outlines, day-zero email, first-week calendar, live outline or NONE, then do-not-send. </format>

<context> I have a module and lesson list. I need a calendar I can shoot against. Do not invent extra studio days, an editor, or a second instructor. </context> <inputs> - Module list: [MODULE LIST] - Lesson list: [LESSON LIST] - Lesson length: [LESSON LENGTH] - Days I have: [DAYS I HAVE] - Hours I can record per day: [HOURS PER DAY] - Hard dates I cannot move: [HARD DATES] </inputs> <task> Turn the lists into a recording calendar that fits [DAYS I HAVE] and [HOURS PER DAY]. Batch similar lessons. Put retake blocks on the same day. Honor [HARD DATES]. If the math does not fit, cut lessons or shorten [LESSON LENGTH]. Do not add a day. </task> <constraints> - Do not assume I can record 8 finished hours in one day. - Do not schedule a lesson I did not list. - Show student runtime and estimated shoot time as two numbers. - If I must cut, name the lesson and the outcome it orphans. </constraints> <format> Calendar by day, shoot vs student time, then cuts required to fit. </format>

<context> I need an onboarding outline so a new student can reach the first win without a support thread. Written steps for [PLATFORM]. I will record the welcome myself. </context> <inputs> - Course topic: [COURSE TOPIC] - Platform: [PLATFORM] - First week goal: [FIRST WEEK GOAL] - Tools they must install: [TOOLS THEY HAVE] - Welcome I can record: [WELCOME LENGTH] - Support I actually offer: [SUPPORT I OFFER] </inputs> <task> Outline onboarding: welcome video beats that fit [WELCOME LENGTH], tool check, where to click on [PLATFORM], the first lesson, the first exercise, and how [SUPPORT I OFFER] works. Include a stuck path with 3 replies I can reuse. Do not promise a Slack, a community, or office hours I did not list. </task> <constraints> - Do not invent a setup I cannot screenshot. - Do not add a personality quiz or a long survey. - The first win must be [FIRST WEEK GOAL], not a tour of the whole curriculum. - Keep steps numbered and short enough to film as on-screen cards. </constraints> <format> Numbered onboarding, welcome beats, stuck-path replies, then a do-not-promise list. </format>

<context> I need a launch-week comms outline I can actually send and record. Posts, emails, and one live slot. Do not invent a partner blast, a waitlist size, or a fake countdown. </context> <inputs> - Course topic: [COURSE TOPIC] - Offer dates: [OFFER DATES] - Channels I will use: [CHANNEL LIST] - Emails I will send: [EMAIL COUNT] - Live slot I can host: [LIVE CALLS OR NONE] - Proof I can show: [PASTE PROOF] </inputs> <task> Write a day-by-day launch week: which channel, the job of the message, 5 bullets, and the CTA. Use only [PASTE PROOF]. If a day wants a proof I do not have, mark ASK ME FOR PROOF and give a weaker honest angle. Include one live outline if I named a call. </task> <constraints> - Do not invent a seat cap, a testimonial, or a closing-in-3-hours line unless I pasted that rule. - Do not add a channel that is not in [CHANNEL LIST]. - Do not write more emails than [EMAIL COUNT]. - I will record one launch video. Outline it once, do not write five scripts. </constraints> <format> Day-by-day table, launch-video outline, live outline or NONE, then ASK ME FOR PROOF days. </format>

<context> I need a sales-page outline from outcomes I can teach, not a designed landing page and not HTML. Empty proof stays empty. I will record a walkthrough later. </context> <inputs> - Course topic: [COURSE TOPIC] - Outcome list I kept: [OUTCOME LIST] - Learner: [LEARNER] - Price: [PRICE] - Proof I have: [PASTE PROOF] - Refund rule: [REFUND RULE] - Words I never use: [BANNED PHRASES] </inputs> <task> Outline the sales page in order: promise, who it is for, who it is not for, outcome list, module teaser, proof from [PASTE PROOF] only, offer at [PRICE], [REFUND RULE], FAQ stubs. For any section that wants a testimonial or enrollment count I did not paste, write ASK ME FOR PROOF. </task> <constraints> - Do not invent a student name, quote, or result. - Do not invent a seat count or a bonus. - Honor [BANNED PHRASES]. - This is an outline I will type into my page builder. Not HTML. </constraints> <format> Numbered page sections with bullets, then ASK ME FOR PROOF, then a one-line promise I can also say on camera. </format>

<context> I need a promise line and a proof stack for the sales page and the sales video. Every proof must already sit in my paste. Do not write a bigger win to fill a third slot. </context> <inputs> - Course topic: [COURSE TOPIC] - Outcome list: [OUTCOME LIST] - Proof I have: [PASTE PROOF] - Learner: [LEARNER] - Claims I will not make: [OFF-LIMITS CLAIMS] </inputs> <task> Write 5 promise options that stay inside [OUTCOME LIST], then a proof stack of up to 3 lines from [PASTE PROOF]. Rank promises by honesty, not punch. For each proof line: the source tag and a risk note if it implies a job I did not teach. If I have fewer than 3 proofs, leave slots empty. </task> <constraints> - Do not invent a metric, logo, or student. - Do not turn a personal result into they will get this. - Honor [OFF-LIMITS CLAIMS]. - If no proof is honest enough to lead, say so and stop at a descriptive title. </constraints> <format> Ranked promises with risk notes, recommended pick, then the proof stack with empty slots left blank. </format>

<context> I need a curriculum teaser for the sales page and a webinar. Name promises, not every lesson file. A full dump trains people to steal the outline and skip the buy. </context> <inputs> - Course topic: [COURSE TOPIC] - Module list: [MODULE LIST] - Lesson list I must not dump: [LESSON LIST] - Learner: [LEARNER] - Minutes I have to say it: [TEASER MINUTES] </inputs> <task> Write a teaser: one line per module as a promise, a spoken version that fits [TEASER MINUTES], and a page version of 80 to 140 words. Do not list items from [LESSON LIST] unless a lesson is the first win I must name. Add a not-in-this-teaser line so I do not overshare on a live call. </task> <constraints> - Do not invent a bonus module. - Do not turn the teaser into a full syllabus. - Do not add a result the module cannot prove. - Keep the spoken version sayable without slides if needed. </constraints> <format> Module promise list, spoken teaser, page teaser, then not-in-this-teaser. </format>

<context> I need FAQ copy for the sales page and a live Q&A. Answer only with facts I pasted. Do not invent a refund story, a job outcome, or a time-to-result I did not measure. </context> <inputs> - Course topic: [COURSE TOPIC] - Objections I already hear: [OBJECTIONS] - Notes and facts I can use: [PASTE NOTES] - Refund rule: [REFUND RULE] - Time budget of the course: [TIME BUDGET] - Who it is not for: [NOT FOR] </inputs> <task> For each item in [OBJECTIONS], write: a short page answer, a longer spoken answer, and CANNOT ANSWER FROM NOTES if the paste is empty. Include [REFUND RULE], [TIME BUDGET], and [NOT FOR] only where they belong. Do not invent a fourth objection to look complete. </task> <constraints> - Do not invent a student who had the same objection. - Do not promise a job, a raise, or a client. - Do not soften [NOT FOR] to win a maybe-buyer. - Keep page answers under 70 words. </constraints> <format> FAQ pairs (page / spoken), then CANNOT ANSWER rows I must fill before publish. </format>

<context> I need offer and guarantee lines that match the price and refund rule I already have. Do not invent a bonus, a payment plan, or a stronger guarantee I will not honor. </context> <inputs> - Course topic: [COURSE TOPIC] - Price: [PRICE] - What is in the offer: [OFFER CONTENTS] - Refund rule: [REFUND RULE] - Bonuses I will actually deliver: [BONUS LIST OR NONE] - Words I never use: [BANNED PHRASES] </inputs> <task> Draft 4 offer lines and 3 guarantee lines. Each must name only items in [OFFER CONTENTS] and [BONUS LIST], at [PRICE], under [REFUND RULE]. Flag any line that implies a result the outline does not teach. Give one recommended pair I can put on the page and say on a sales call. </task> <constraints> - Do not invent a bonus to sweeten the line. - Do not write a lifetime or risk-free line unless [REFUND RULE] says that. - Do not add a payment plan I did not name. - Honor [BANNED PHRASES]. </constraints> <format> Offer lines with risk notes, guarantee lines with risk notes, then the recommended pair. </format>