5 added, 12 removed. Audit A to A.
---
name: content-pruning-review
- description: "Review and prune website content. Use for removing generic copy, duplicate sections, weak feature cards, unsupported claims, placeholder content, bloated FAQs, repeated testimonials, excessive prose, stale pages, low-value sections, and AI-generated filler before final visual polish."
+ description: "Remove redundant or unsupported page content."
---
# Content Pruning Review
Use this skill to make the page sharper by deleting what dilutes the main decision path.
## Workflow
- 1. Inspect the page goal, audience, offer/product reality, source copy, proof, IA, forms, SEO/social metadata, brand voice, and verification commands.
+ 1. Inspect the requested copy/content, intended action, source facts and brand conventions; expand to IA, forms or metadata only if affected.
2. Read [Content Pruning Review Guide](references/content-pruning-review-guide.md) before changing headings, sections, CTAs, metadata, labels, or UI copy.
3. Draft from evidence: real product/service facts, proof, objections, user tasks, and constraints.
4. Replace generic claims with specific language or remove them.
- 5. Inspect the rendered page on desktop and mobile for hierarchy, wrapping, repetition, and whether copy still matches the UI.
+ 5. When implementing copy, inspect its affected rendered desktop/mobile states for wrapping and clarity. Copy-only output does not require site changes.
- ## Always Protect
+ ## Scoped execution
- - Inspect before writing or coding: audience, offer, product/service reality, source copy, assets, proof, claims, conversion goal, information architecture, SEO/metadata needs, forms, legal/trust constraints, and available verification commands.
- - Use copy to make the design more specific: every headline, label, CTA, section, and proof point should reduce ambiguity rather than decorate the layout.
- - Avoid generic premium language, vague transformation claims, placeholder testimonials, fake metrics, empty adjectives, and hero copy that could fit any brand.
- - Write in the user's domain vocabulary while keeping language clear, concise, concrete, and scannable.
- - Tie claims to proof: screenshots, artifacts, reviews, credentials, specifications, case studies, pricing terms, process details, or real outcomes.
- - Keep navigation, forms, pricing, FAQs, and CTAs honest and task-focused; do not create dark patterns or hide material terms.
- - Respect accessibility and structure: semantic headings, meaningful link/button text, labeled forms, useful error/help text, readable line lengths, and no critical copy trapped in images.
- - Before delivery, inspect rendered desktop and mobile copy for hierarchy, wrapping, overflow, repetition, and whether the words still match the implemented page.
+ Apply the [shared web contract](../website-operating-rules/references/scoped-web-contract.md) once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.