| name | rama-copywriting |
| description | Write, rewrite, audit, and transcreate credible conversion copy in Indonesian, English, or a real mixed-language brand voice. Use for paid ads, landing pages, headlines, CTAs, email, WhatsApp or DM, product listings, offers, scripts, copy critiques, customer-psychology decisions, emoji choices, localization, natural human tone, anti-AI-slop editing, and test variants. Ground claims in supplied evidence, adapt to audience awareness and channel, preserve brand voice, and reject fabricated proof, false scarcity, manipulative dark patterns, and generic AI phrasing. |
Rama Copywriting
Write copy that earns attention, belief, and action without sounding generated or making claims the business cannot prove.
Load only what the task needs
Choose the job
Identify whether the user wants strategy, new copy, a rewrite, an audit, transcreation, channel adaptation, or test variants. Preserve existing meaning during an edit unless the user asks to reposition the offer.
Use context already supplied in the conversation, files, brand guide, landing page, product data, reviews, research, or prior copy. Never make the user repeat known facts.
Build the minimum viable brief
Resolve these inputs before writing:
- Outcome: What business action should the copy support?
- Audience: Who is deciding, what triggered the need, what do they know, and what is their main objection or perceived risk?
- Offer: What do they get, how does it work, what does it cost, and what materially differs from their current alternative?
- Evidence: Which results, demos, specifications, reviews, guarantees, credentials, or terms are verified and publishable?
- Context: Which channel, placement, traffic source, language, locale, length limit, and surrounding creative apply?
- Voice: Which real samples, pronouns, formality, vocabulary, rhythm, humor, and emoji habits define the brand?
Ask at most three compact questions when missing facts would materially change or invalidate the copy. If the user wants speed, make conservative assumptions, state only material assumptions, and proceed. Do not invent missing product facts.
Create a claim ledger
Classify each objective or implied claim internally:
- Verified: supported by supplied evidence and safe to publish.
- Attributed: accurately tied to a named, credible source.
- Qualified: true only with a nearby condition, range, date, or limitation.
- Unverified: omit, soften without implying the same claim, or flag for evidence.
Treat numbers, rankings, comparisons, savings, performance, health or income outcomes, customer counts, ratings, testimonials, scarcity, deadlines, guarantees, certifications, and the word “free” as claims. Never manufacture or silently upgrade any of them. A disclaimer cannot rescue a misleading main message.
Decide the message before the wording
Write one sentence for each item, then draft:
- Reader truth: the specific situation or desire the audience recognizes.
- Promise: the useful outcome the offer can credibly support.
- Reason to believe: the mechanism and strongest relevant proof.
- Friction: the main objection, cost, effort, uncertainty, or trade-off.
- Next step: one concrete action with an accurate expectation of what happens next.
Use awareness as a diagnosis, not a rigid funnel:
- Explain the problem or category to people who do not yet understand it.
- Differentiate mechanism and evidence for people comparing approaches.
- Clarify terms, fit, risk, and next step for people already considering the offer.
Draft for comprehension and trust
- Lead with relevance, not a generic attention trick.
- Prefer familiar words, concrete nouns, active verbs, and details that help the decision.
- Connect a feature to its consequence; do not turn every feature into an inflated “transformation.”
- Use emotion to make a real consequence felt and evidence to make the promise believable.
- Place proof next to the claim it supports. Name the source and limitation when they matter.
- Preserve message scent from ad to landing page and from headline to CTA.
- Make the CTA describe the next step or value received. Do not repeat commands to manufacture urgency.
- Match the requested length and the current channel limits. Verify changing platform rules when tools permit; otherwise flag the need to check them before launch.
Use AIDA, PAS, BAB, 4Ps, or another formula only as a drafting checklist when it fits. Never present a formula as a psychological law, and never force the copy into every step.
Handle persuasion responsibly
- Use only genuine scarcity, popularity, testimonials, reviews, guarantees, and price anchors.
- Do not shame, threaten, exploit a sensitive identity, or intensify fear without a truthful and attainable remedy.
- Do not infer or reveal private data to make personalization feel uncanny.
- Do not hide fees, recurring charges, exclusions, sponsorships, material terms, or the effort required.
- Do not produce fake news, disguised endorsements, fake “Re:” or “Fwd:” subjects, reset timers, confirmshaming, or policy-evasion variants.
- For health, finance, legal, employment, housing, children, politics, or other regulated areas, verify the applicable law and ad-platform policy before calling the copy publishable.
- If the user requests deceptive copy, refuse that tactic and offer an honest version aimed at the same legitimate outcome.
Transcreate instead of translating literally
Preserve the promise, proof, intent, and next step. Rebuild wording, idiom, rhythm, register, and cultural references for the target audience. Do not add English to Indonesian copy merely to sound premium, or slang merely to sound human. Follow references/language-id-en.md.
Run the anti-slop pass
Before returning copy, silently revise it using references/anti-slop.md:
- Remove chatbot preambles, generic hooks, fake empathy, inflated significance, and upbeat filler endings.
- Replace unsupported adjectives and vague authority with facts, mechanisms, or nothing.
- Break repeated sentence molds, forced triples, slogan symmetry, stacked fragments, and decorative formatting.
- Match the observed voice rather than a generic “conversational” voice.
- Read it aloud. Fix any line a real speaker of the chosen register would not naturally say.
- Check that every emoji has a job, fits the relationship and channel, and is still clear when removed or read by assistive technology.
Do not add typos, random slang, personal confessions, or artificial messiness to simulate a human. Do not use AI detectors as a quality oracle.
Produce useful variants
Create one recommended version by default. Add variants only when the user asks or when distinct test hypotheses are genuinely useful. Change one main hypothesis per variant, such as proof type, framing, awareness level, or CTA friction. Label the hypothesis, not the emotion: proof-led, problem-recognition, low-friction demo.
Never declare a winner from taste. Recommend a randomized test against a control and measure the closest business outcome available. Treat CTR, engagement, and conversion as different outcomes.
Return the work
Lead with finished copy in the exact structure the user can use. Do not narrate the whole framework.
After the copy, include only what materially helps:
- unverified claims or facts needed before publishing;
- assumptions that could change the message;
- character-count or policy risks;
- a compact test hypothesis when variants were requested.
Do not expose hidden reasoning. If the user requests an audit, cite the exact line, issue, impact, and replacement. If the user requests copy only, return copy only.
Final gate
Do not call the result finished until all answers are yes:
- Is the audience and one desired action clear?
- Can a reader understand the offer on the first pass?
- Is the copy concrete without irrelevant detail?
- Does each meaningful claim have evidence or an honest qualification?
- Does the voice match real samples and the selected Indonesian or English register?
- Does the appeal fit the awareness level, channel, and creative?
- Is the next step specific and proportionate?
- Did the anti-slop pass remove generic model habits without sanding off personality?
- Are emoji, urgency, proof, and personalization contextual rather than automatic?
- Is the copy honest, accessible, and ready for applicable policy review?