write-app-store-copy

Files (2)

• SKILL.md
• principles.md · references/

SKILL.md (first lines)

# Write app store copy

Write for the person deciding whether to install the product. Do not write for the team that built
it.

## Research before drafting

1. Inspect the shipping product, requirements, and current listing. Make a private fact sheet of:
   - intended audience and use occasion;
   - primary job or outcome;
   - main workflows, capabilities, and constraints;
   - credible differentiators;
   - price, purchases, ads, accounts, connectivity, and privacy facts;
   - unsupported or future capabilities.
2. Browse current official guidance for every target store. Store rules and field limits change.
3. Read at least five current listings in the same category. Identify the questions buyers need
   answered and the phrases competitors have worn out. Never copy their language.
4. When reviews are available, sample positive and negative reviews of established alternatives.
   Extract the outcomes people value and the friction they resent. Treat reviews as audience
   evidence, not facts about the product being marketed.
5. Read [references/principles.md](references/principles.md).

If product evidence cannot support a claim, omit it or ask for evidence. Never turn a planned
capability into present-tense copy.

## Choose the message

Write one private positioning sentence before writing store fields:

`For [specific audience], [product] is [category or use] that [distinct outcome], proven by [fact].`

Rank facts by their value to the buyer. Lead with the use case and outcome. Follow with the product
details that prove them. Do not paste the positioning sentence into the listing by default.

## Draft the fields

- Make the opening understandable before a reader taps "More."
- State the category in plain words. Do not stuff keywords or repeat the product name.
- Translate capabilities into use: what a person can accomplish, in which situation, and with what
  effort or constraint.
- Prefer concrete nouns and verbs over praise. Describe the action and result instead of calling the
  experience `seamless`, `powerful`, or `intuitive`.
- Use short headings that match questions a buyer actually has.
- End on a desirable outcome, use occasion, or direct next step. Do not add a slogan merely to
  create a final line.
- Adapt one positioning strategy to each store's field limits. Do not invent a different product
  story for each platform.

## Reject bad copy

Delete or replace any line that does one of these:

- Claims table stakes: "finished," "functional," "high quality," "works," or "fully featured."
- Talks about development status, implementation effort, architecture, or the team's intentions.
- Plants a concern merely to deny it.
- Uses empty superiority: "best," "ultimate," "beautiful," "modern," "premium," or "perfect."
- Uses a vague emotional command such as "rediscover the joy," "experience the magic," or "get
  ready."
- Treats price as the product. State price only when it resolves a purchase concern, and connect it
  to the experience a person receives.
- Narrates completeness instead of naming included capabilities.
- Makes a competitor comparison without verifiable evidence.
- Repeats information the storefront already displays.
- Could describe ten unrelated products after changing the name.

## Run the reader-inference test

For every sentence, answer:

1. What does this tell the buyer?
2. Why should the buyer care?
3. What doubt does this wording accidentally introduce?
4. Which product fact makes it credible?

Delete a sentence if questions 1, 2, or 4 lack a specific answer. Rewrite it if question 3 exposes
an unwanted implication.

## Verify

1. Check every claim against the shipping product.
2. Count characters exactly for constrained fields.
3. Read the first three sentences alone. They must identify the product, core use, and strongest
   reason to choose it.
4. Read headings and bullets alone. They must form an accurate scan of the experience.
5. Remove repeated claims, filler, keyword blocks, and unsupported superlatives.
6. Perform the reader-inference test again on the opening and closing lines.
7. Where the console supports it, recommend a controlled store-listing experiment for meaningful
   alternatives. Do not claim that a draft will convert better before testing it.

Return paste-ready fields with character counts and a short claim-evidence note. Keep the private
fact sheet and positioning sentence out of the answer unless the user asks for them.

From yokuze/aix-config, MIT.

More from yokuze/aix-config