Turn Claude into a powerhouse: 5 marketing codes + 100 for every field ⚡

You are an offer architect using Alex Hormozi's value equation: Value = (Dream Outcome x Perceived Likelihood) / (Time Delay x Effort). Score each of the four parts of my offer out of 10, explain each score in one line, then tell me the single highest-impact lever to pull and exactly how to pull it. Here is my offer:

Rewrite the copy above using the AIDA structure: attention, interest, desire, action. Make the attention line scroll-stopping, build real desire with a specific benefit, and make the action line one clear next step. Keep my voice.

Write me 3 Meta ad variations for this offer. Each one needs a scroll-stopping hook, a tight body, and one clear CTA, and the primary text must be under 125 characters so nothing gets cut off on mobile. No fluff, no emoji salad. Here is my offer:

You are an Instagram hook writer. Give me 100 hooks for this topic, mixing contrarian, curiosity-gap, story-open, question, and bold-claim styles. Each one under 12 words. Then rank them by virality, most to least scroll-stopping, and tell me in one line why your top pick wins. Here is my topic:

Take the idea above and rewrite it 10 completely different ways, each from a different angle or tone (contrarian, emotional, data-led, story, bold claim, and so on). Number them and label the angle of each so I can pick.

Rewrite my copy using the PAS framework. Name the exact problem my customer feels, agitate it by making the cost of not fixing it vivid and specific, then present my offer as the obvious solution. Keep it tight and emotional, not preachy. Here is my offer and audience:

Write me 10 email subject lines for this email, mixing curiosity, benefit, urgency, and pattern-interrupt styles. Keep each under 50 characters so they don't get cut off in the inbox, avoid spammy words that trip filters, and rank them by predicted open rate. Here is my email:

Write me a 30-second UGC-style video script for this product. Open with a relatable problem in the first 3 seconds, show the product as the fix, and end on a soft CTA. Give it to me as spoken lines with a quick note on what to show on screen for each. Sound like a real person, not an ad. Here is my product:

You are a senior frontend engineer reviewing the React component above. Check it against six things: unnecessary re-renders (missing memo, unstable props), accessibility (semantic elements, ARIA, keyboard nav), state that should be derived not stored, missing loading and error states, prop drilling that should be context, and effect cleanup. For each issue, give the line, the fix, and a one-line reason. Flag the component above:

You are a backend engineer designing a REST API. For the feature I describe, output the endpoint table (method, path, purpose), the request and response JSON schema for each, the status codes including error cases (400, 401, 403, 404, 409, 422), idempotency and pagination strategy, and where to put validation versus business logic. Call out anything that should be async or rate-limited. Here is my feature:

You are a DevOps engineer reviewing the Dockerfile or CI config above. Check for: unpinned base images and actions, missing multi-stage builds, secrets baked into layers, running as root, no healthcheck, uncached dependency layers, and missing build caching in CI. Return a corrected version plus a short list of what you changed and why. Review the config above:

You are a QA engineer doing root-cause analysis. From the bug report, reproduction steps, and any logs I give you, produce: the most likely root cause with reasoning, two alternative hypotheses ranked by likelihood, the exact code path or layer to inspect first, a minimal reproduction, and the regression test that should have caught it. Here is my bug:

You are a senior data scientist reviewing the modeling approach above. Check for: target leakage, train and test contamination, class imbalance handling, wrong metric for the problem (accuracy on imbalanced data, etc.), missing baseline, cross-validation that ignores time or groups, and untested assumptions. For each issue give the risk and the correction. Review the approach above:

You are a BI analyst hardening a metric definition. For the metric I give you, return: the exact numerator and denominator, the grain (per user, per session, per day), the filters and exclusions, how to handle nulls and duplicates, the time window and timezone, and two ways this metric is commonly gamed or misread. End with the SQL skeleton. Here is my metric:

You are a data engineer reviewing a pipeline design. For the pipeline I describe, assess: batch versus streaming fit, idempotency and replayability, schema evolution handling, partitioning and late-arriving data, data quality checks and where they sit, and orchestration and backfill strategy. Flag the single biggest reliability risk and how to remove it. Here is my pipeline:

You are an experimentation analyst. For the test I describe, check: whether the primary metric and minimum detectable effect were set before launch, sample size and power, sample ratio mismatch, novelty and primacy effects, multiple-comparison risk across metrics, and whether the unit of randomization matches the unit of analysis. Then give the correct readout and a ship or no-ship call with reasoning. Here is my experiment:

You are a product discovery researcher synthesizing the interview notes above. Separate observed behavior from stated preference, cluster the pains by frequency and severity, map each pain to the job the user was trying to do, flag where the user is designing the solution for you (and what underlying need it hides), and list the three riskiest assumptions left to test. Synthesize the notes above:

You are a senior PM reviewing the PRD above. Pressure-test it for: a problem statement that names a user and a pain (not a feature), success metrics that are measurable and tied to the problem, scope with an explicit non-goals list, edge cases and failure states, dependencies and open questions, and a launch and rollback plan. List what is missing and rewrite the weakest section. Review the spec above:

You are a head of product prioritizing with RICE (reach, impact, confidence, effort). Score each initiative I list, show the math, then sort by score. Call out where confidence is doing too much work, which low-effort high-impact items are being buried, and what you would cut to protect focus this quarter. Here is my initiative list:

You are a product analyst defining the metric that predicts retention. For the product I describe, propose the single activation event and its time window (the "aha moment"), the leading indicators upstream of it, the counter-metric that guards against gaming, and the instrumentation events you need to track it. Justify each choice in one line. Here is my product:

You are a UX researcher designing a study. For the question I give you, recommend the method (usability test, interview, survey, diary study) and why, write the screener criteria, draft a task-based discussion guide that avoids leading questions, set the sample size, and name the bias most likely to corrupt this study and how to control it. Here is my research question:

You are a senior product designer reviewing the flow above. For every screen, check the empty state, loading state, error state, and success state are designed (not just the happy path). Check the primary action is obvious, the cognitive load per step, where the user could get lost, and whether the flow respects platform conventions. List gaps screen by screen. Review the flow above:

You are a brand designer. From the brand description, define the visual system: a type scale and pairing rationale, a color system with accessible contrast pairs, a spacing and grid logic, an imagery and iconography direction, and three adjectives the system should make a viewer feel (with the design choices that deliver each). Here is my brand:

You are a design lead running a critique on the design rationale above. Anchor every comment to the stated user goal and not to taste. Separate feedback into "blocking" (breaks the goal or accessibility), "should fix" (friction), and "polish" (nice to have). End with one sharpening question that makes the designer defend the riskiest decision. Critique the rationale above:

You are a systems administrator hardening the server setup above against the CIS benchmark mindset. Check: SSH config (key-only, no root login, non-default port), firewall default-deny, unattended security updates, service account least privilege, log shipping and retention, time sync, and backup with a tested restore. Return a prioritized fix list, criticals first. Review the setup above:

You are a security analyst running STRIDE on the system I describe. For each component and trust boundary, enumerate spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege risks. Rate each by likelihood and impact, then give the top five mitigations ranked by payoff per effort. Here is my system:

You are a network engineer reviewing the topology or firewall ruleset above. Check for: flat networks that should be segmented, overly broad any-any rules, missing egress filtering, management plane exposed to the internet, no VLAN or subnet isolation for sensitive zones, and single points of failure. Return the tightened ruleset and the segmentation you would add. Review the network above:

You are an incident commander running the response. For the incident I describe, drive it through the phases: contain (stop the bleeding without destroying evidence), eradicate, recover, and the actions for each now. Tell me what to preserve for forensics, who to notify and when, and the three questions the postmortem must answer. Here is my incident:

You are a mechanical design engineer reviewing the part or assembly above. Check: tolerance stack-up on critical fits, GD&T that matches the function (not over-constrained), material and finish suited to load and environment, design for manufacturability and assembly, and likely failure mode under fatigue or thermal cycling. Flag each risk with the dimension or feature and the fix. Review the design above:

You are a structural engineer. For the structure I describe, trace the load path from application to foundation, identify the governing load combination (dead, live, wind, seismic), name the likely critical member and limit state (bending, shear, buckling, deflection, connection), and list the code checks and assumptions to verify before sizing. Flag anything that needs a real calculation, not a rule of thumb. Here is my structure:

You are an electrical engineer reviewing the circuit or power design above. Check: conductor and trace sizing for current and temperature rise, protection coordination (fusing, breakers), grounding and return paths, decoupling and noise on sensitive nodes, voltage drop over distance, and derating for ambient and margin. Return each issue with the value at risk and the correction. Review the design above:

You are a manufacturing process engineer. For the process I describe, find the constraint with a quick capacity view of each step, run a focused root-cause pass on the top defect (fishbone across man, machine, material, method, measurement, environment), propose the SPC characteristic to chart, and give one poka-yoke that prevents the defect rather than catching it. Here is my process:

You are a research scientist synthesizing the literature notes above. Cluster the findings into the current consensus, the active disagreements, and the unexamined assumptions. Build the citation chain for the central claim, flag where evidence is thin or single-source, and name the specific gap that a new study could own. Synthesize the notes above:

You are a research methodologist. For the experiment I describe, check: a falsifiable hypothesis, the controls and what each rules out, independent and dependent variables and confounds, sample size and power, randomization and blinding, and the statistical test chosen before data collection. Name the result that would falsify the hypothesis. Here is my experiment:

You are a technical writer editing the methods or results section above for a peer-reviewed submission. Check it is reproducible (a stranger could repeat it), that every claim is supported by a stated result, that tense and voice are consistent, that units and significant figures are correct, and that figures are referenced and self-explanatory. Mark every passive vague sentence and tighten it. Edit the draft above:

You are a grant reviewer scoring the proposal above on significance, innovation, approach, and feasibility. For each, give a score out of 10 and the one sentence a skeptical panelist would use to reject it. Check the aims are independent (not a house of cards), the budget matches the work, and the impact is concrete. End with the single revision that most raises the funding odds. Review the proposal above:

You are a program manager building a WBS. For the project I describe, decompose it into phases, deliverables, and work packages (each small enough to estimate and own), map dependencies, identify the critical path, and flag the work packages with the most estimate uncertainty. Mark which can run in parallel and where the team will bottleneck. Here is my project:

You are a project risk manager. For the project I describe, build a risk register: each risk as a cause-then-event-then-effect statement, scored by probability and impact, with a response (avoid, mitigate, transfer, accept), an owner, and a trigger that says when to act. Sort by exposure and name the top three that need action this week. Here is my project:

You are a program manager turning the raw update notes above into a stakeholder status report. Lead with a RAG status (red, amber, green) and the one-line headline. Then: progress since last report, what is on track versus at risk, decisions needed (with the cost of delay), and changes to scope, schedule, or budget. Cut anything a busy executive would skip. Write from the notes above:

You are a program manager building a stakeholder engagement plan. For the people I list, place each on a power and interest grid (manage closely, keep satisfied, keep informed, monitor), name what each one cares about and fears, set the right channel and cadence for each, and flag the one misaligned stakeholder most likely to derail the program and how to bring them along. Here is my stakeholder list:

You are a positioning strategist using April Dunford's framework. Map my product against these five components: competitive alternatives, unique attributes, the value those attributes enable, the best-fit customer who cares most about that value, and the market category I should frame myself in. For each component give me one tight line, then write a single positioning statement and name the one component I have not earned yet. Here is my positioning:

You are a seed-stage VC partner reviewing the pitch above. Score it on the standard deck arc: problem, solution, market size, traction, business model, competition, team, and ask. Rate each section red, yellow, or green with one line of reasoning, list the three questions a partner will ask that this deck cannot answer yet, and tell me which slide to cut. Reference the pitch above.

You are a market analyst. Build a bottom-up market sizing from my notes: define TAM, SAM, and SOM, show the unit math for each (population x adoption x price), state every assumption as a separate line I can challenge, and flag the one assumption that swings the model most. Avoid top-down "1% of a big number" logic. Here is my market:

You are a chief of staff setting up an operating rhythm. Based on my context, design a weekly, monthly, and quarterly cadence: which meetings run at each interval, who owns each, the one decision each meeting exists to make, and the metric reviewed. Recommend a single north-star metric and the three input metrics that feed it. Here is my company context:

You are an SDR coach. Rewrite the cold email above to lead with a specific trigger or observation about the prospect, cut every sentence about my company that does not earn the next line, keep it under 90 words, and end with a low-friction interest-based call to action (not a demo ask). Give me the rewrite plus two subject lines under six words. Reference the email above.

You are a sales coach building a discovery call using MEDDIC. From my notes, draft questions that surface each element: metrics, economic buyer, decision criteria, decision process, identified pain, and champion. Flag which of the six I have the weakest signal on and give me the one question that de-risks the deal most. Here is my deal:

You are an account executive writing a proposal. Structure my notes into: the prospect's stated problem in their words, the desired outcome, scope of work, timeline, investment, and the one-line business case for why now. Mirror the buyer's language back, keep pricing framed against the cost of inaction, and flag anything I left vague enough to cause scope creep. Here is my proposal:

You are a sales trainer using the feel-felt-found and reframe approach. For the objection I give you, write three distinct responses: one that acknowledges and reframes, one that isolates whether it is the real blocker, and one that trades a concession for a commitment. Tell me which to lead with and the trap answer that loses the deal. Here is my objection:

You are a financial analyst. From the figures I give you, calculate the core ratios (gross margin, operating margin, current ratio, quick ratio, burn, and runway), show each formula with my numbers plugged in, compare against a healthy benchmark, and name the one metric that should worry me most. Here are my numbers:

You are an FP&A lead building a budget. Turn my assumptions into a driver-based monthly forecast: separate revenue drivers from cost drivers, show the formula linking each driver to an output, build a base, downside, and upside case, and state which single driver the model is most sensitive to. Here are my assumptions:

You are a finance lead writing the monthly management report. Turn my numbers into a tight narrative: actuals versus budget with variance called out in dollars and percent, the three things that moved the result, cash position and runway, and one forward-looking risk. Lead with the headline a busy board member reads first. Here are my numbers:

You are a staff accountant reviewing the books. Scan my transaction list for likely miscategorizations, duplicate entries, expenses that belong in a different period, and anything that should be capitalized rather than expensed. Return a flagged list with the reason for each flag and the correcting entry you would propose. Here are my transactions:

You are an operations analyst. Turn my description into a clean process map: list each step with its owner, input, output, and cycle time, mark the handoffs where work waits, identify the bottleneck step, and propose the one change that removes the most delay. Flag any step that exists only to fix an earlier failure. Here is my process:

You are a documentation specialist writing a standard operating procedure. Turn my rough steps into a numbered SOP with a purpose line, scope, roles, the trigger that starts it, each step written as an action a new hire could follow, and the definition of done. Call out any step where a mistake is costly and add a check there. Here are my steps:

You are a procurement lead running a vendor selection. Build a weighted scorecard across price, quality, lead time, reliability, support, and switching cost, score each vendor I list, show the weighted totals, and name the hidden risk in the option that looks cheapest on paper. Recommend one and state what would change your mind. Here are my vendors:

You are a supply chain planner. From my demand and lead-time data, calculate reorder point, safety stock, and economic order quantity, show each formula with my inputs, flag any SKU at risk of stockout before the next delivery, and tell me where I am holding cash in excess inventory. Here is my data:

You are a recruiting lead writing a job description. From my notes, produce a posting with a one-line mission for the role, the five outcomes the hire owns in year one, must-have versus nice-to-have skills kept honest and short, and an inclusive tone. Cut any requirement that screens out good candidates for no real reason and tell me which ones I should drop. Here is my role:

You are a technical recruiter screening against a role. Compare the resume to the must-have outcomes, rate fit as strong, possible, or no on each requirement with the evidence line that justifies it, list the gaps to probe in a screen, and give me a yes, no, or maybe with one sentence of reasoning. Do not infer skills the resume does not show. Here is the role and resume:

You are an interviewing expert designing a structured loop. For each competency I list, write two behavioral questions, the follow-up probe that separates a real story from a rehearsed one, and a rubric describing what a 1, 3, and 5 answer sounds like. Split the competencies across interviewers so no two cover the same ground. Here is my role:

You are an HR business partner writing a balanced review. Turn my notes into a review organized by what went well, what needs to grow, and impact, anchor every point to a specific example rather than a personality trait, frame growth areas as forward actions, and flag any phrasing that reads as biased or vague. Here are my notes:

You are a strategy consultant framing the engagement. Restate my client's problem as a single sharp question, break it into a MECE issue tree of the drivers that must be true to answer it, state the hypothesis you would test first, and name the one analysis that would confirm or kill that hypothesis fastest. Here is the problem:

You are a consulting manager. For the situation I describe, recommend the two or three frameworks that actually fit (for example Porter's five forces, value chain, 3 Cs, or a profit-tree), explain in one line why each fits this problem and not a generic one, then apply the best fit to my situation with real content rather than empty headers. Here is my situation:

You are a consultant building a deck with the pyramid principle. Turn my analysis into a storyline where each slide title is a full sentence that states the takeaway, the titles read top to bottom as a logical argument, and each slide's body proves only its own title. Give me the action-titled list, flag any slide that is data without a "so what," and name the one slide that carries the recommendation. Here is my analysis:

You are an engagement manager writing a client status update. Turn my progress into a crisp note: the headline answer so far, what we learned this week, decisions we need from the client, risks to the timeline, and next steps with owners. Lead with the answer, keep hedging out, and flag anything the client needs to act on before the next meeting. Here is my progress:

You are a contracts specialist helping me review a draft (this is drafting support, not legal advice). Summarize the key commercial terms, list the obligations and deadlines that fall on each party, flag clauses that are one-sided or missing standard protections (indemnity, limitation of liability, termination, governing law), and give me a question list to raise with counsel. Here is my contract:

You are a legal writer translating contract language. For the clause I give you, explain in clear sentences what it actually requires, who it benefits, the realistic scenario where it bites, and the one word or phrase that carries the most weight. This is comprehension help, not legal advice. Here is my clause:

You are a contract drafter. Turn my intent into clean clause language, write it in defined terms used consistently, keep one obligation per sentence, and offer a fallback version that is more favorable to the other side for negotiation. Note any term that should be defined elsewhere in the agreement. This is drafting support to review with counsel. Here is my intent:

You are a contracts reviewer doing a risk pass on the agreement above. Flag the clauses that create the most exposure (uncapped liability, auto-renewal, broad indemnity, unilateral changes, vague deliverables), rate each as high, medium, or low, and explain the exposure in one line each. Hand me a prioritized list to take to counsel, not a verdict. Reference the agreement above.

You are a customer success manager designing onboarding. From my customer's details, build a first-90-days plan with the outcome they bought toward, the milestones that prove value early, the moment they reach first value, and the risks that cause early churn. Map each milestone to a date and an owner on both sides. Here are my customer details:

You are a senior support agent. Write a reply to the ticket that opens by restating the customer's problem so they feel understood, gives the fix in clear numbered steps, sets an honest expectation if it cannot be solved now, and closes warmly without corporate filler. Give me a short macro version and a fuller version. Here is my ticket:

You are a retention specialist. From my notes on an at-risk account, diagnose the likely root cause of the churn signal, draft a human outreach message that names the issue without being defensive, and propose a concrete save offer or next step matched to the cause. Tell me the one question that reveals whether this account is truly saveable. Here are my account notes:

You are a customer success manager preparing a quarterly business review. Turn my account data into a QBR narrative: value delivered last quarter tied to their goals, usage and adoption trends, wins to celebrate, risks to address, and a forward roadmap with an expansion path. Lead with their business outcome, not our feature list. Here is my account data:

You are an instructional designer using Wiggins and McTighe's Understanding by Design. For my topic, work backward in three stages: (1) name the enduring understanding and 2 essential questions, (2) define the evidence (one performance task plus one quick check for learning), (3) sequence the learning activities to get there. Keep it to one class period and flag the one misconception students most often hit. Here is my topic:

You are an assessment specialist. Build a single-point rubric for my assignment: one column stating the proficient standard for each criterion, with blank space framed for "concerns" (below) and "advanced" (above). Use 3 to 5 criteria written in student-facing language, each tied to an observable behavior, not a vague trait like "effort." Here is my assignment:

You are a writing coach giving feedback on the student work above. Return exactly two glows (specific strengths, quoted from their work) and two grows (the highest-leverage next steps), each phrased as an actionable move the student can make, not a judgment. End with one warm sentence that names their progress. Keep it to a reading level appropriate for the grade I noted.

You are a differentiation coach. Take my lesson and produce three tiers of the same core task: a scaffolded version (sentence starters, chunked steps, word bank), the on-level version, and an extension that deepens thinking without just adding more work. Then suggest one accommodation each for an English language learner and a student who finishes early. Here is my lesson:

You are a patient education writer. Turn my clinical notes into a take-home handout at a grade 6 reading level: what the condition is, what to do at home, which warning signs mean "call us," and which mean "go to emergency." Use short sentences and a "questions to ask your provider" list. Do not add any diagnosis or treatment I did not write. Here are my clinical notes:

You are a clinical documentation assistant. Organize my rough visit notes above into clean SOAP format (Subjective, Objective, Assessment, Plan), keeping every clinical detail I wrote and inventing nothing. Flag any section where I left a gap that the record would normally need, as a bracketed "[missing: ...]" note for me to fill. This is a formatting pass only, not clinical guidance.

You are an allied health documentation assistant helping draft a care plan from the goals I provide. Structure it as: presenting concern, measurable goals (using SMART format), planned interventions I listed, and review date. Keep it to my stated scope of practice and surface anything I wrote that reads as ambiguous so I can clarify. Add nothing clinical that I did not provide. Here are my care goals:

You are a medical front-office assistant drafting patient-facing admin messages. From my details, write a clear, warm message for the situation (appointment reminder, results-are-ready notice, recall, or no-show follow-up). Keep it free of clinical information, include any prep instructions I noted, and end with how to reschedule or reach the clinic. Here are my message details:

You are a real estate copywriter. Write a listing description from my property details with this structure: a hook line on the single best feature, a flowing paragraph that walks the buyer through the home, a bulleted highlights list, and a close on lifestyle and location. Lead with benefits, stay specific to what I gave you, and avoid fair-housing risk language (no references to ideal buyers, family types, or demographics). Here are my property details:

You are a client communication specialist. From my notes, write a clear update to my client that sets expectations, explains what is happening and why, names the next step with a date, and ends with reassurance grounded in fact, not hype. Match the tone to whether this is good news, a delay, or a setback. Here are my situation notes:

You are a market analyst writing for a non-expert audience. Turn my stats (median price, days on market, inventory, list-to-sale ratio) into a short monthly update: one headline on the trend, three bullets on what each number means for a buyer or seller, and one line of practical "what this means for you right now." No predictions stated as certainty. Here are my market stats:

You are a negotiation strategist. From my deal details, map the negotiation: each party's likely priorities and walk-away points, the strongest 3 points I can lead with, the 2 objections most likely to come back at me with a response to each, and a recommended opening position with a fallback. Keep it grounded in the facts I gave. Here are my deal details:

You are a DTC conversion copywriter. Write a product page from my details: a benefit-led headline, two short paragraphs that connect features to outcomes, a five-bullet "why you'll love it" list, an objection-handling FAQ of four questions, and an add-to-cart line. Write to one specific customer, not everyone. Here are my product details:

You are a customer insight analyst. Read the reviews above and extract: the top 5 phrases customers use in their own words, the 3 most repeated benefits, the 3 most common objections or complaints, and the unexpected use cases. Then turn each into a marketing angle I can test, labeled by the emotion it speaks to. Use the customers' language, not marketing speak.

You are an email retention strategist. Design a welcome flow of 4 emails for my product: email 1 (deliver the lead magnet or welcome plus brand story), email 2 (top objection plus social proof), email 3 (best-seller or hero product with use cases), email 4 (time-bound offer). For each, give the goal, subject line, and a one-line body brief. Here are my product and offer:

You are a performance creative strategist. Give me 5 distinct ad concepts for my product, each with a different angle (problem-agitate, founder story, social proof, before-and-after, unexpected hook). For each: the scroll-stopping first 3 seconds, the core message, and the visual direction. Tie every concept to a real benefit, not just a gimmick. Here are my product and audience:

You are a short-form hook writer. Give me 10 hooks for my topic across these patterns: contrarian take, "did you know," mistake-to-avoid, result-in-X-time, and curiosity gap. Keep each under 12 words, front-load the most surprising element, and make a promise the content can actually pay off. Here is my topic:

You are a short-form scriptwriter. Turn my idea into a 45 to 60 second spoken script with a 3-second hook, a quick "why this matters" line, the core value in 3 tight beats, and a single clear call to action. Write the way people talk, in short lines, with no jargon and no filler. Spoken words only, no scene directions. Here is my idea:

You are a repurposing strategist. Take the piece above and adapt it for: an X thread (5 to 7 posts), a LinkedIn post (hook plus story plus takeaway), a carousel outline (slide-by-slide), and a YouTube Shorts script. Keep the core idea intact but rewrite the format and rhythm for each platform's native style, do not just copy and paste.

You are a line editor. Tighten the draft above for clarity and rhythm without changing my voice or meaning: cut filler words, break up sentences that run long, swap weak verbs for strong ones, and fix any passive voice that hides the actor. Return the edited version, then list the 3 most important changes and why you made them.

You are an offer strategist using Alex Hormozi's Grand Slam Offer framework. Take my offer idea and sharpen it across: dream outcome, the core problems it removes, the deliverables that solve each, and risk reversal (guarantee). Then name the offer and propose a price anchored to value, not cost. Flag the weakest part. Here is my offer idea:

You are a curriculum designer. Outline my course as modules built on a learning arc: where the student starts, the transformation they reach, and the milestone at the end of each module. For each module give the title, the one outcome it delivers, and 3 to 5 lessons. Keep every module tied to a result, not just information. Here is my course topic:

You are a sales psychology coach. List the 7 objections my audience is most likely to raise (time, money, "will this work for me," trust, timing, past failures, partner or boss buy-in). For each, give the real fear underneath and a reframe I can use in copy or on a call that is honest, not pushy. Here are my offer and audience:

You are a community strategist. From my details, plan a week of engagement prompts that build belonging and momentum: a Monday win-share, a midweek teaching or hot-take post, a member-spotlight format, and a Friday reflection. For each give the prompt copy and the behavior it is designed to drive. Here are my community details:

You are a guest experience host. From my booking details, write the message for the moment (booking confirmation, pre-arrival info, in-stay check-in, or post-stay thank you). Make it warm and personal, include the practical details the guest needs, anticipate one question before they ask it, and end with a clear point of contact. Here are my booking details:

You are a hospitality copywriter. Write appetizing descriptions for my items (menu dishes or event packages) using sensory language grounded in real ingredients and inclusions, not empty adjectives. For each: a name, a one to two sentence description, and the standout detail that justifies the price. Keep it honest to what is actually served. Here are my item details:

You are an events coordinator. From my event details, draft the vendor brief or message I need: scope, exact timing and load-in details, deliverables, point of contact, and the 3 questions I should confirm before the day. If I am chasing a vendor, write a polite but firm follow-up with a clear deadline. Here are my event details:

You are a guest relations manager responding to the review above. For a positive review, thank them specifically (name what they praised) and invite them back. For a negative one, open with genuine acknowledgment, take ownership without excuses, state the concrete fix, and move further detail offline with a contact. Stay calm, never defensive, and keep the brand's warmth throughout.

You are an executive assistant triaging the emails above. Sort them into respond now, delegate, schedule, and archive, with a one-line reason each. Then draft replies for the "respond now" items in a professional but human tone, leaving a [bracketed blank] anywhere you need a decision or detail only I can provide. Flag anything that looks time-sensitive at the top.

You are a scheduling coordinator. From my details, work out the logistics: propose meeting times that respect every time zone listed, account for buffer and travel between commitments, flag any conflict, and draft the scheduling message with 3 clear options. Note any detail I still need to confirm before sending. Here are my scheduling details:

You are a meeting notes specialist. Turn the raw notes above into a clean summary: key decisions, action items as a table (owner, task, due date), open questions, and a two-line TL;DR at the top. Pull out every commitment someone made, even the ones buried in discussion, and mark anything with no clear owner as "[unassigned]."

You are a travel coordinator. From my trip details, build a clean itinerary: flights, ground transport, accommodation, and meetings in chronological order with time zones, confirmation numbers, and buffer time called out. Add a packing-and-prep checklist tailored to the trip's purpose and climate, and flag any tight connection or gap I should fix. Here are my trip details: