---
name: zebrafish-deslopification
description: Diagnose and remove generic AI-shaped language, structure, and visual direction while preserving truth, useful conventions, domain quality, and distinctive strengths.
---

# Zebrafish Deslopification

Use when an artifact is broadly correct but feels generic, templated,
overwritten, interchangeable, mechanically polished, or shaped by default AI
patterns. It can refine web content, briefs, scripts, storyboards, prompts,
presentations, image direction, video direction, and other creative work.

This is a cross-domain refinement skill, not a content type. Load the matching
Zebrafish content skill first or alongside it. That skill defines what good work
must accomplish; Deslopification identifies generic decisions and repairs them
without overriding source truth, usability, accessibility, or domain
conventions.

Follow the shared production kernel from the Zebrafish root for evidence,
revision identity, and honest delivery state. The current job owns its artifact,
purpose, sources, voice references, constraints, and approved degree of change.

## Load by Need

| Need | Read |
|---|---|
| Determine whether the problem is genericness, a domain failure, or weak inputs | [Diagnose](references/diagnose.md) |
| Repair abstract, repetitive, canned, or counterfeit language | [Language](references/language.md) |
| Repair template rhythm, equal weighting, duplication, or predictable sequencing | [Structure](references/structure.md) |
| Repair style soup, stock imagery, default staging, camera, motion, or prompt direction | [Visual Direction](references/visual-direction.md) |
| Apply the smallest coherent repair and compare the actual revision | [Polish](references/polish.md) |

Load only the modules implicated by evidence. References are one level deep and
self-contained.

## Non-Negotiables

- Do not use a banned-word list, AI detector score, or personal taste as proof.
  Name the observable pattern, its local effect, and why it weakens this work.
- Preserve facts, qualifications, accessibility, navigation, legal language,
  product truth, continuity, and successful domain conventions.
- Do not manufacture anecdotes, statistics, specificity, brand voice,
  asymmetry, humor, edge, or visual quirks to make work appear human.
- Common language and familiar structures are not automatically slop. Keep them
  when they are the clearest fit for the audience and task.
- Repair upstream causes such as vague source material, equal weighting, absent
  point of view, or conflicting direction before line-editing every symptom.
- Review the actual revised artifact. Preserve named strengths and state any
  limitation that cannot be fixed without better sources or a clearer decision.

Stop when the only path to distinctiveness would invent facts, impersonate an
unsupported voice, obscure necessary meaning, or exceed the authorized scope.