---
name: zebrafish-web-content
description: Shape, write, critique, and improve source-grounded website content with clear page jobs, information hierarchy, proof, voice, search intent, and rendered-page review.
---

# Zebrafish Web Content

Use for homepages, landing pages, product and feature pages, pricing pages,
campaign pages, about pages, navigation, conversion copy, and related web
content. A single page, one section, or a complete site content system is valid.

This skill owns content strategy and words, not frontend implementation or
visual interface design. Pair it with the relevant design or engineering
guidance when layout, components, code, or interaction behavior must change.
Use Deslopification alongside it when the content is correct but generic,
templated, or indistinct.

Follow the shared production kernel from the Zebrafish root. This skill owns web
content judgment; the current job owns its brief, sources, page inventory,
content model, drafts, variants, locales, approvals, and delivery format.

## Load by Need

| Need | Read |
|---|---|
| Establish audience, page job, source truth, intent, proof, and action | [Shape](references/shape.md) |
| Design site relationships, page flow, section jobs, links, and metadata | [Structure](references/structure.md) |
| Write headlines, body copy, proof, CTAs, navigation, and microcopy | [Write](references/write.md) |
| Review source, DOM, metadata, links, and actual rendered page states | [Critique](references/critique.md) |
| Diagnose and repair weak content without flattening what works | [Polish](references/polish.md) |

Load only the modules needed for the requested work. References are one level
deep and self-contained.

## Non-Negotiables

- Trace factual, product, customer, legal, performance, pricing, and comparison
  claims to supplied or Project sources. Mark gaps instead of filling them with
  plausible copy.
- Give every page and section a real job. Do not force every site into a hero,
  benefits, testimonials, FAQ, and CTA template.
- Preserve the visitor's entry knowledge, likely question, and next useful
  action. Search intent is an input when relevant, not a reason to repeat
  keywords or create pages without a user need.
- Keep proof close to the claim it supports. Distinguish demonstrated fact,
  sourced assertion, customer evidence, and creative promise.
- Judge content in its actual rendered context when available. A copy document
  alone cannot prove hierarchy, truncation, responsive reading order, link
  behavior, or first-viewport comprehension.
- Preserve accessibility, legal qualifiers, navigation clarity, and transaction
  truth during any simplification or stylistic repair.
- Deliver the exact reviewed revision. State what was inspected and any
  unrendered, inaccessible, dynamic, localized, or source-unverified gap.

Stop rather than guess when material claims lack sources, the page's purpose or
target action is irreconcilably unclear, required rendered states cannot be
inspected, or publishing would exceed the user's authorization.