voyager67/Pixelcraft / skills/landing-page-slop-repair
landing-page-slop-repair
VerifiedFixes generic AI-generated landing pages: centered-template heroes, vague value propositions, repetitive feature cards, fake social proof, and weak product demonstrations.
Landing Page Slop Repair
Workflow
- Establish audience, product capability, conversion goal, and actual evidence.
- Inspect hero, navigation, section sequence, CTA, proof, product demo, FAQ, and footer.
- Replace vague headlines with a specific outcome and audience grounded in the product.
- Replace generic feature-card grids with a meaningful workflow, product screenshot, comparison, diagram, or use-case narrative.
- Remove unverified testimonials, customer logos, metrics, certifications, and integrations.
- Use a product-specific hero composition; avoid decorative AI art that obscures the product.
- Ensure CTA hierarchy, keyboard accessible forms, mobile reading order, and real links.
- Verify metadata, image loading, and layout at multiple widths.
Output
Narrative diagnosis, proof audit, section-level repairs, CTA flow, and viewport checks.
Non-negotiable rules
- Judge the interface that exists, not assumptions about who or what produced it. AI authorship cannot be reliably inferred from generic visual patterns alone.
- Treat “AI slop” as a shorthand for observable quality problems: generic patterns, weak hierarchy, arbitrary decoration, vague copy, fabricated-looking content, inconsistent systems, or incomplete states.
- A pattern is a signal, not proof. Record evidence, confidence, and plausible benign explanations. Do not label a screen “AI-generated” as a factual finding.
- Preserve user goals, factual content, product behavior, existing brand assets, and working accessibility unless the evidence supports a change.
- Never invent metrics, reviews, customer logos, endorsements, product claims, features, integrations, or data to make a screen look more convincing.
- Inspect rendered output when tools allow it. If you only inspect source code or a screenshot, state that limitation.
- Make the smallest effective change first. Do not replace an existing coherent visual language just to make the result look different.
- Never expose secrets or private information found in a repository. If a secret is detected, do not repeat its value; report only the file and line, stop short of publishing it, and recommend revocation/rotation.
Completion report
State the signals found, evidence and confidence, fixes made, files changed, checks actually run, and unresolved issues. Distinguish visual review, code review, and runtime testing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |