plugins/skjalden/skills/web-copywriting/SKILL.md
Web copywriting patterns — headlines, CTAs, microcopy, error messages, empty states, and landing page structure. Covers above-fold framework, benefit-driven copy, the Seven Sweeps editing method, and UI text guidelines.
npx skillsauth add hjemmesidekongen/ai web-copywritingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Clarity over cleverness. Benefits over features. Specificity over vagueness. Customer language over company language. One idea per section. Every claim follows: Feature -> Benefit -> Outcome.
Headline: single most important value proposition, outcome-focused, specific. Subheadline: adds clarity in 1-2 sentences. Primary CTA: action verb describing what the user gets ("Start free trial", not "Submit").
Social proof (logos, stats, testimonials) -> Problem articulation -> Solution with 3-5 key benefits -> How it works (3-4 steps) -> Objection handling (FAQ, comparisons, guarantees) -> Final CTA with risk reduction. Never stack features without narrative flow.
Buttons: action verbs, 2-3 words, specific ("Create Project" not "Submit"). Errors: say what happened, why, and what to do next. Empty states: explain what goes here + clear action to populate. Tooltips: under 2 sentences, explain the "why". No exclamation marks in UI. No "Please" — just be direct. Sentence case everywhere except page titles.
Sequential passes on existing copy: (1) Clarity — can the reader understand? (2) Voice — is tone consistent? (3) So What — does every claim answer "why should I care"? (4) Prove It — is every claim backed by evidence? (5) Specificity — are numbers, timeframes, and examples concrete? (6) Emotion — does the copy make the reader feel something? (7) Zero Risk — are barriers to action removed near CTAs?
Kill these on sight: weak intensifiers (very, really, extremely), filler (just, actually, basically), nominalizations ("make a decision" -> "decide"), passive voice, hedging language, marketing speak in UI ("supercharge" -> "speed up"), wall-of-features without benefits, buried CTAs, generic claims ("we help businesses grow").
See references/process.md for page structure templates, CTA formulas, specificity upgrades, word-level editing rules, and the full Seven Sweeps checklist.
development
Creates a brand from scratch through market research and interactive sparring. Runs competitive research via Perplexity, then guides the user through positioning, audience, voice, values, and content pillars. Produces the full brand guideline set at .ai/brand/{name}/. Use when building a new brand, defining brand strategy for a product, or when /våbenskjold:create is invoked.
testing
Loads brand guidelines from .ai/brand/{name}/ and makes them available to the current context. Progressive disclosure: L1 confirms brand exists, L2 loads summary, L3 loads specific files on demand. Use when a downstream skill or user needs brand context, or when /våbenskjold:apply is invoked.
documentation
Guided reinvention of an existing brand guideline. Loads current brand from .ai/brand/{name}/, identifies what to keep vs change, and walks the user through targeted evolution. Preserves brand equity while updating positioning, voice, or values. Use when refreshing a brand or when /våbenskjold:evolve is invoked.
development
Codifies an existing brand from materials, samples, and references. Analyzes provided content to extract voice patterns, values, and positioning. Produces the same guideline format as brand-strategy. Use when a brand already exists but isn't documented, or when /våbenskjold:audit is invoked.