Skip to content

Skills · experience-design

content-design

Write a content spec for a page or journey from user needs — user-need statements ("As a… I need… so that…"), the questions the page must answer in priority order, the page structure, a plain-language rewrite at a target reading level with a before/after readability check, and an explicit list of what to cut and why. Use when the user wants a content spec, content design, "rewrite this page in plain English", "what should this page say", "our page is too long and nobody reads it", or content for a service or journey.

Pack experience-designTier standardJob Design the experiencev0.1.0

npx skilldrop-cli install content-design
Other ways to install

With the sibling skills it hands off to:

npx skilldrop-cli install content-design --with-related

The whole pack it belongs to:

npx skilldrop-cli install --pack experience-design

By hand, from a clone of the repo:

cp -R packs/experience-design/skills/content-design ~/.claude/skills/

In Claude Code, with the experience-design plugin installed, invoke it as:

/experience-design:content-design

Try it

A realistic prompt from the skill's acceptance evals:

Here's our 'Making a claim' page for Acme Home Insurance. Please make it something people can actually use. Current text: 'Policyholders wishing to initiate a claim in respect of loss or damage to insured property are required to notify Acme Home Insurance at the earliest practicable opportunity and in any event within 30 days of the incident. Notification may be effected via the online portal or by telephone. Claimants will be required to furnish supporting documentation including photographs, receipts and, where applicable, a crime reference number. Acme Home Insurance is committed to delivering market-leading service and has been recognised with numerous industry accolades. Claims are typically assessed within 15 working days of receipt of all documentation.' Most calls we get are 'what do I need to send' and 'how long will it take'.

What a good result looks like

Example output

a council parking permit page, rewritten from user needs · the skill's own worked example, source

Input

Can you redo our resident parking permit page? It's the current text below and we get a lot of calls asking "how long does it take" and "what documents do I need". Our usual proof of address is a council tax bill and for the car it's the V5C logbook. Readers are residents, all ages, lots of them reading on a phone.

Current page (before.md):

Residents' Parking Scheme Information

Northwind Council operates a Controlled Parking Zone (CPZ) scheme in designated areas of the borough in order to prioritise the availability of on-street parking for residents and their visitors. Applications for a resident parking permit may be submitted by any individual whose principal residence is located within a CPZ, subject to the provision of satisfactory documentary evidence of both residency and vehicle ownership or keepership. Permits are issued for a period of twelve months and the applicable charge is determined with reference to the CO2 emissions band of the vehicle in question. Applicants should be aware that the processing of applications may take up to ten working days from receipt of all required documentation. In the event that an applicant does not possess the requisite documentation, the application will be held in abeyance until such time as it is provided.

Output

Content spec: Apply for a resident parking permit

Reader: a resident in a controlled parking zone who wants to park near home, often on a phone · Target level: plain English for a general audience Channel: web page · Assumptions to confirm first: the page is only for resident permits, and visitor permits have their own page.

User needs

#As a…I need…So that…Evidence
1resident in a parking zoneto know if I can get a permitI don't apply for something I can't have[assumption]
2resident applyingto know which documents to have readyI can apply in one go[support calls] "what documents do I need"
3resident applyingto know how long it takesI can plan where to park until it arrives[support calls] "how long does it take"
4resident applyingto know what it costsI can budget for it[assumption]

Questions the page must answer (priority order)

  1. Can I get one? — it decides whether the rest of the page matters
  2. What do I need? — the top call reason, and it's what stops an application
  3. How much is it? — asked before people start
  4. How long does it take? — the other top call reason, but only after they've decided to apply

Structure

OrderHeading (reader's words)AnswersFormat
1Apply for a resident parking permit — first two sentences say who can applyQ1paragraph
2What you needQ2list
3How much it costsQ3paragraph
4How long it takesQ4paragraph

Draft (after.md)

Apply for a resident parking permit

You can apply if you live in a controlled parking zone. A permit gives you priority for parking on the street in your zone.

What you need

  • proof you live at the address, like a council tax bill
  • proof you own or keep the car, like the V5C logbook

How much it costs

The price depends on your car's CO2 emissions band. A permit lasts 12 months.

How long it takes

It can take up to 10 working days. We start counting when we have all your documents. If something is missing, we hold your application until you send it.

Readability (script output, before → after)

Run: python3 scripts/readability.py before.md and python3 scripts/readability.py after.md --max-sentence 20.

before.md
Words: 144  Sentences: 6  Avg sentence: 24.0 words
Long words (3+ syllables): 24.3%
Estimated Flesch-Kincaid grade: 15.1 (heuristic syllables; compare before/after, don't quote as exact)
Sentences over 25 words: 4

after.md
Words: 105  Sentences: 13  Avg sentence: 8.1 words
Long words (3+ syllables): 5.7%
Estimated Flesch-Kincaid grade: 2.7 (heuristic syllables; compare before/after, don't quote as exact)
Sentences over 20 words: none

(The before count includes the title line as a sentence. The four flagged sentences are the four long ones in the source.)

Cut list

What was cutWhyWhere it went
"Northwind Council operates a Controlled Parking Zone (CPZ) scheme…"Organisational message. What a zone does for the reader is kept in one sentence.Shortened into the opening paragraph
"…and their visitors"Visitor permits are a different taskVisitor permits page (confirm it exists)
"subject to the provision of satisfactory documentary evidence"Replaced by the concrete documents"What you need" list
The acronym "CPZ"Readers don't use it; it appeared twice and was never neededRemoved

Kept on purpose: "own or keep the car" keeps "keepership" from the source, because a keeper who isn't the owner can still apply. "Up to 10 working days" keeps the source's limit, not a promise of a shorter time.

Open questions

  • What are the prices per emissions band? The page should show them, or link to them.
  • Is there an "Apply now" link, and does it need a form? If so, its strings go to ux-writing.
  • Which documents count besides a council tax bill and a V5C? List them if there are others.

How it's checked

Measured against plain Claude Code (2026-10-23): it met 100% of its checks, against 75% without it, and a blind judge preferred it. How skills are checked

20 assertions across 3 acceptance evals, and 8 trigger queries. Every skill's checks

What the output must do
  • User-need statements follow 'As a… I need… so that…' with a specific reader and an evidence tag
  • Questions are listed in priority order and the page headings follow that order, written in the reader's words
  • The draft keeps every fact: 30 days, online or phone, photos, receipts, crime reference number where applicable, and 15 working days after all documents
  • No sentence in the draft is over 25 words
  • Before/after readability numbers are reported from the script, or the output says the grade was not computed
  • The cut list includes the 'market-leading service' and 'industry accolades' sentence with a reason
  • Does not invent a phone number, URL, excess amount or other fact not in the prompt; unknowns are placeholders listed as open questions
  • Uses the current policy's facts (income below £21,000, up to 24 months, 2 months of bank statements OR proof of benefit, no bill needed, decision within 10 working days) rather than the old page's figures, and notes that the old page disagreed with the policy
  • Does not carry over the '£900 over 12 months = £100 a month' example uncorrected; either flags that it doesn't add up or replaces it with a correct example
  • Does not promise a decision within 48 hours; keeps the policy's 10 working days and says why the Comms request was not followed
  • The page answers the callers' frequent questions in the reader's words, including that reminder letters and debt collection stop while the application is considered and what happens if payments are missed (two in a row, with 14 days' notice)
  • The rewritten page body is under 350 words
  • Does not invent a phone number, URL, approval rate or any other fact not in the files; the phone number and form link are left as clear placeholders
  • Delivers the finished page rather than stopping to ask questions first
  • The no-food instruction is the most prominent thing on the sheet, since that is the problem the owner described
  • Notices that 'NPO from midnight' and 'no food after 10pm' disagree, and either uses one with a stated reason or asks the clinic to confirm, rather than silently picking one
  • Keeps the other facts: water until 7am, drop-off between 8:00 and 8:30am, bring current medication, possible blood test on arrival, and a call after 2pm about going home
  • Replaces jargon like 'NPO' and 'pre-anaesthetic bloods' with words a pet owner understands
  • Does not invent facts not given, such as different rules for cats, fasting for medication, prices or a phone number
  • Fits in half a printed page (roughly 200 words or fewer)
When it should and shouldn't activate

Should activate:

  • Rewrite our refunds policy page in plain English so customers understand it
  • Write a content spec for the new 'Apply for a grant' page — user needs, what it must answer, what to cut
  • Our benefits page is 2,000 words and nobody reads it. What should it actually say?
  • Work out the content for each page of our account-closure journey from user needs

Should leave to another skill:

  • Write the error messages and button labels for the claim form
  • Turn these setup notes into a step-by-step getting-started guide for new developers
  • Design the navigation and sitemap for our help centre
  • Map the customer's journey from first quote to renewal with emotions at each stage

Hands off to

Related skills

guide-builder, information-architecture, user-journey-map

Source

SKILL.md · the whole folder on GitHub.