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

AIDA rewrite (paste after your copy)

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.

Meta ad copy (paste in front of your offer)

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:

Hook generator (paste in front of your topic)

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:

Regen, 10 angles (paste after your idea)

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.

10 email subject lines

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:

UGC video script

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:

API endpoint designer (paste in front of your feature description)

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:

Dockerfile and CI hardener (paste after your config)

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:

Bug root-cause analyzer (paste in front of your bug report)

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:

Metric definition auditor (paste in front of your metric)

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:

Pipeline design reviewer (paste in front of your pipeline description)

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:

A/B test analyst (paste in front of your experiment)

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:

PRD pressure-tester (paste after your spec)

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:

Roadmap prioritizer (paste in front of your initiative list)

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:

Activation metric designer (paste in front of your product description)

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:

UI flow and state critique (paste after your flow description)

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:

Brand and visual system builder (paste in front of your brand description)

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:

Design critique facilitator (paste after your design rationale)

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:

Threat modeler (paste in front of your system description)

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:

Network and firewall reviewer (paste after your network design)

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:

Incident response commander (paste in front of your incident)

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:

Structural load-path checker (paste in front of your structure)

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:

Circuit and power reviewer (paste after your design)

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:

Process and yield improver (paste in front of your process)

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:

Experiment design reviewer (paste in front of your experiment)

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:

Methods section editor (paste after your draft)

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:

Grant proposal reviewer (paste after your proposal)

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:

Risk register builder (paste in front of your 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:

Status report writer (paste after your update notes)

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:

Stakeholder map and comms planner (paste in front of your stakeholder list)

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:

Pitch deck pressure test (paste after your pitch)

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.

TAM, SAM, SOM builder (paste in front of your market notes)

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:

Operating cadence designer (paste in front of your company context)

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:

Discovery call planner (paste in front of your deal notes)

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:

Proposal structurer (paste in front of your proposal notes)

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:

Objection handler (paste in front of your objection)

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:

Driver-based forecast builder (paste in front of your assumptions)

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:

Board reporting writer (paste in front of your monthly numbers)

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:

Bookkeeping cleanup reviewer (paste in front of your transaction list)

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:

SOP writer (paste in front of your rough steps)

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:

Vendor evaluation scorer (paste in front of your vendor options)

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:

Inventory and logistics planner (paste in front of your demand data)

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:

Resume screener (paste in front of your resume and 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:

Interview scorecard builder (paste in front of your role and competencies)

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:

Performance review drafter (paste in front of your notes on a report)

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:

Framework selector (paste in front of your situation)

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:

Slide storyline builder (paste in front of your analysis)

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:

Client update writer (paste in front of your week's progress)

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:

Clause explainer (paste in front of your clause)

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:

Clause drafter (paste in front of your plain-English intent)

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:

Risk flagger (paste after your agreement)

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.

Support reply writer (paste in front of your ticket)

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:

Churn-save outreach (paste in front of your at-risk account notes)

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:

QBR prep builder (paste in front of your account data)

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:

Single-point rubric builder (paste in front of your assignment)

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:

Glow-and-grow feedback writer (paste after your notes on student work)

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.

Differentiation tiering (paste in front of your lesson)

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:

SOAP note structurer (paste after your visit 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.

Care-plan drafter (paste in front of your care goals)

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:

Front-desk comms drafter (paste in front of your message details)

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:

Buyer and seller update writer (paste in front of your situation notes)

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:

Local market update (paste in front of your market stats)

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:

Negotiation prep (paste in front of your deal details)

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:

Review-mining angle finder (paste after your customer reviews)

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.

Email flow architect (paste in front of your product and offer)

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:

Ad concept generator (paste in front of your product and audience)

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:

Video script writer (paste in front of your idea)

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:

Cross-platform repurposer (paste after your piece)

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.

Line editor (paste after your draft)

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.

Curriculum outliner (paste in front of your course topic)

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:

Objection handler (paste in front of your offer and audience)

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:

Community engagement planner (paste in front of your community details)

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:

Menu and package describer (paste in front of your item 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:

Vendor coordination drafter (paste in front of your event 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:

Review response writer (paste after your guest review)

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.

Scheduling logistics solver (paste in front of your scheduling details)

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:

Meeting notes to actions (paste after your raw notes)

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]."

Travel itinerary builder (paste in front of your trip details)

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: