# Apply clean fixes > Map scanner hits to remediation steps from the fixes playbook, choose propose vs apply in an agent host, and confirm the clean alternative. - Repository: yetone/kill-ai-slop - GitHub: https://github.com/yetone/kill-ai-slop - Human docs: https://grok-wiki.com/public/docs/yetone-kill-ai-slop-c0d8c9670cbb - Complete Markdown: https://grok-wiki.com/public/docs/yetone-kill-ai-slop-c0d8c9670cbb/llms-full.txt ## Source Files - `skill/references/fixes.md` - `skill/SKILL.md` - `skill/references/detection.md` - `website/src/data/demos.ts` - `website/src/components/BeforeAfter.astro` --- --- title: "Apply clean fixes" description: "Map scanner hits to remediation steps from the fixes playbook, choose propose vs apply in an agent host, and confirm the clean alternative." --- After triage and the pre-edit report, **kill-ai-slop** remediates confirmed tells through the agent skill’s **Fix** step: map each hit to a direction in `skill/references/fixes.md`, apply the minimal edit (or only propose it), then re-scan and visually check that the clean alternative holds. The standalone scanner (`node scripts/scan.mjs`) **never edits files** — only an agent host that loads the skill can write changes. ## Prerequisites | Requirement | Detail | | --- | --- | | Agent skill | `kill-ai-slop` installed in a coding agent (`skill/SKILL.md`) | | Prior steps | Scope → Scan → Triage → Report already done; do **not** mass-edit before the user has seen the report | | Playbook | `skill/references/fixes.md` (before→after directions per tell) | | Scanner | `node scripts/scan.mjs ` and optional `--json` for machine-readable triage | | Optional visual ref | Field-guide demos in `website/src/data/demos.ts` via `BeforeAfter.astro` (Slop / Clean) | Do not treat scanner output as a verdict. Every hit is a lead: open the file, decide **slop vs intentional**, and keep deliberate brand choices (tokens, logos, real illustrations). ## Propose vs apply The skill workflow splits **proposal** (Report) from **application** (Fix). The scanner never crosses that boundary. ```text Scanner (read-only) Agent host (skill) ───────────────── ────────────────── scan.mjs → hits triage (slop vs intentional) report + proposed fix per group ask: which groups / all? ── user decision ── apply minimal diffs (Fix) re-scan + visual check ``` | Mode | When | What the agent does | Files written? | | --- | --- | --- | --- | | **Propose** | Always before edits; default until the user chooses groups | Group confirmed hits; one-sentence why + proposed fix; ask which groups to apply or whether to proceed on all | No | | **Apply** | After the user approves some or all groups | Minimal change per tell using `references/fixes.md`; prefer shared tokens/components | Yes (explicit paths only) | Report format the skill mirrors: ```text slop src/Hero.tsx:12 indigo→violet gradient → one solid accent slop src/Hero.tsx:31 gradient-clip headline → solid ink, scale up slop src/Note.tsx:8 border-l-4 callout ×3 → 1 aside, rest is body slop copy.md:1 "not just X — it's Y" → say the specific thing → 4 groups, 11 hits. ``` Then ask which groups to apply, or whether to proceed on all. ## Fix procedure On every change: decide before you decorate; one accent, one voice; hierarchy from scale and space; subtract first; prefer specific copy over punchy copy; decoration only when it is a real signal. 1. Design tokens / theme first (colors, radius, fonts) — many hits drop at once. 2. Shared components, then one-off call sites. 3. Copy last. Look up the tell in `skill/references/fixes.md` (numbered **01–23**). Patterns are **directions**, not find-and-replace rules — adapt to project tokens and framework. Preserve intent and function. Prefer editing shared tokens/components over every call site. Never invent new brand colors: if palette must change, propose neutrals + the project’s existing accent and let the user confirm. Keep copy meaning; make it specific rather than deleting it. Re-run the scanner and note intentional leftovers with reasons. If a dev server exists, compare before/after visually — a green scan is not the same as a better page. Optional: match the tell’s field-guide demo (`before` → `after` in `demos.ts`). ### Re-scan commands ```bash node scripts/scan.mjs # human-readable grouped report node scripts/scan.mjs --json # machine-readable for triage ``` Success signal: hit count for the fixed tells drops; remaining hits are either unapproved groups or intentional keeps with a stated reason. ## Map scanner hits → remediation Use the tell name from the report (or taxonomy id) as the key into `references/fixes.md`. Summary of the playbook direction and the clean outcome: | Tell | Remediation direction | Clean outcome | | --- | --- | --- | | **01** Indigo→violet gradient | Solid accent class/token; drop colored glow shadow; if gradient kept, single-hue, low contrast, justified | One solid, chosen accent | | **02** Gradient headline text | Solid ink; use scale/weight for impact | Solid heading, no `bg-clip-text` default | | **03** Warm “cozy” palette | Near-neutral paper/ink/rule; one warm accent only; propose neutrals, confirm before global apply | Neutral base + one accent | | **04** Default semantic palette | Neutrals + at most one–two intentional semantic colours (not stock blue/green/amber/red set) | Coherent chips from brand palette | | **05** One-hue status box | State in a word; neutral surface + border; one muted accent | Neutral alert, not mono-hue wash | | **06** Gradients as atmosphere | Flat background; hairline/border for depth; glow only if it points at one element | Flat held surfaces | | **07** Serif-italic on one word | Emphasize by weight/position, one voice | Bold (or structure), not serif/italic span in sans heading | | **08** Serif where sans belongs | UI sans in font tokens; serif only for genuine editorial product voice | Sans UI/body unless editorial | | **09** Decorative strikes & highlights | Remove decorative ``/``/``; keep real edits, links, annotations | Structure carries emphasis | | **10** Highlighted keywords | Specific prose; at most one accented phrase | No multi-color keyword soup | | **11** AI copywriting voice | Rewrite for specifics; delete triads and em-dash drama | Concrete claims, not “not just X — it’s Y” | | **12** Emoji everywhere | Remove from headings/buttons/bullets; keep only if real status info | Plain chrome labels | | **13** Glowing status dot | Flat dot + word; no ping/pulse/glow shadow | Small flat status marker | | **14** Rounded card, colored left border | Collapse stacked callouts to body; at most one real `