# Project and De-Slop Audit

Complete this reference before a redesign. Support findings with evidence and prioritize them by impact, risk, and effort.

## Project inventory

- Record the framework, versions, rendering model, build system, and deployment context.
- Distinguish public, private, administrative, dynamic, and broken routes.
- Inventory the component structure, global styles, design tokens, and recurring UI patterns.
- Review navigation, information architecture, internal linking, and responsive variants.
- Inventory copy, images, video, fonts, icons, and brand assets.
- Locate forms, authentication, APIs, state management, data flows, and critical interactions.
- Identify analytics, consent, tracking, and third-party scripts.
- Review titles, descriptions, canonicals, robots directives, structured data, and the sitemap.
- Review indexability, client-rendered core content, and obvious crawling obstacles.
- Review keyboard operation, focus, contrast, labels, landmarks, and reduced-motion behavior.
- Review LCP, INP, and CLS risks, image delivery, fonts, bundles, and render-blocking resources.

## Finding categories

Assign every finding to one primary category:

- **Functional:** broken workflows, links, forms, states, or integrations
- **Visual:** hierarchy, consistency, readability, responsiveness, or brand alignment
- **Content:** unclear, redundant, generic, or unsupported claims
- **SEO and crawling:** metadata, URLs, internal links, indexing, or structured data
- **Performance:** loading, interaction, or layout problems
- **Accessibility:** semantic, visual, or interactive barriers
- **AI slop:** interchangeable patterns without project-specific or functional justification

## Common AI-slop patterns

Do not remove these blindly. First determine whether the brand, content, or functionality justifies the pattern.

- interchangeable hero section with a large heading, paragraph, two buttons, and an arbitrary illustration;
- pervasive gradients, glows, blurred light fields, or glassmorphism;
- excessive rounded cards, pills, badges, shadows, or floating elements;
- unmotivated bento grids and repeated three-card sections;
- meaningless icon collections or emoji in place of a consistent icon system;
- animation without functional value or artificial asymmetry;
- too many font sizes, colors, accent treatments, or radii;
- oversized spacing without information value;
- interchangeable stock imagery or generic AI-generated imagery;
- fabricated statistics, testimonials, customer logos, ratings, or trust badges;
- generic claims such as “revolutionize your business,” “unlock your potential,” “seamless solutions,” or “innovation reimagined”;
- buzzword chains, excessive dashes, and promotional filler;
- repeated claims without new information;
- unclear or competing calls to action;
- navigation or footer structures with empty, duplicate, or useless items.

## Replacement logic

- Justify decoration through content, structure, typography, and real product details.
- Use repeated cards only for genuinely comparable information units.
- Use icons only when they improve recognition or operation.
- Limit animation to orientation, feedback, or understandable state changes.
- Make claims specific or remove them; never simulate missing evidence.
- Establish one clear primary user action per context.
- Derive linguistic and visual distinctiveness from the real brand, audience, and product logic.
