---
name: agency-web-humanizer
description: Analyze existing websites and web applications from their actual code, content, and feature set; reorganize their design; remove generic AI and template patterns; humanize editorial copy; and improve the current project directly. Use when an agent must audit, redesign, de-slop, modernize, or technically and editorially improve an existing web project, including information architecture, responsive design, SEO, LLM readability, WCAG 2.2 AA accessibility, Core Web Vitals, and quality assurance, without inventing facts, damaging working logic, or rebuilding unnecessarily.
---

# Agency Web Humanizer

## Mission

Improve an existing website or web application until it reads and behaves like an intentionally designed, project-specific digital product. Start from the actual project and treat design, language, and engineering as one system.

Follow these rules:

- Respect the existing technology stack, working logic, data flows, integrations, project conventions, and brand assets.
- Do not perform an unnecessary full rewrite.
- Do not invent content, references, metrics, ratings, customer logos, legal claims, or company facts.
- Do not remove features or change business-critical logic without evaluating the consequences.
- Preserve existing user changes and do not overwrite a mixed working tree.
- Treat SEO, accessibility, performance, privacy, and maintainability as part of the design.
- When implementation is requested, make the changes rather than stopping at recommendations.
- Explain decisions briefly without burdening the user with avoidable questions.

## Required architecture decision

Before changing navigation, page structure, routing, or fundamental layout architecture, obtain a clear architecture decision from the user:

1. **Single page** — for a clearly bounded offer, campaign, or primary conversion goal.
2. **Multi-page** — for several services, audiences, locations, or topics with independent SEO value.
3. **Hybrid** — for a central landing page plus detail pages, case studies, a blog, documentation, or legal pages.
4. **Another structure** — for example, a web application with a public marketing site, dashboard, portal, shop, directory, or custom information architecture.

Explain the alternatives in the context of the actual project and present the recommended option first with a reason. Leave the final decision to the user. Before that decision, perform inventory, auditing, and reversible preparation, but do not execute an irreversible architecture restructure.

## Resolve missing context

First infer the following from the repository, existing UI, copy, configuration, and assets:

- product objective, primary audience, and primary user action;
- offer, product, or service;
- existing brand, brand assets, and intended impression;
- relevant languages and regions;
- content and functionality that must be preserved;
- suitable page architecture.

Ask only when information cannot be inferred reliably or is business-critical. Ask no more than three concise questions at once. For selection questions, provide meaningful options, consequences, and a justified recommendation.

## Workflow

### 1. Preserve and understand the project state

Before editing:

1. Read repository instructions and existing documentation.
2. Check Git status and preserve existing user changes.
3. Identify the framework, rendering model, build system, and package manager.
4. Inventory routes, pages, components, global styles, design tokens, content, and media.
5. Locate forms, authentication, APIs, tracking, consent, and other critical functions.
6. Determine the existing build, lint, typecheck, and test commands.
7. Read [references/audit-and-deslop.md](references/audit-and-deslop.md) for the complete inventory and de-slop audit.

Classify findings separately by functionality, visual design, content, SEO and crawling, performance, accessibility, and AI slop. Then prioritize a concise action plan by impact, risk, and effort.

### 2. Develop a visual direction and system

Derive a recognizable design direction from the content, brand, product, and audience. Do not create a collage of trends.

- Define clear visual hierarchy and a coherent design rationale.
- Treat color, typography, spacing, radii, grids, and components as a consistent system.
- Design desktop, tablet, and mobile intentionally; do not merely shrink the desktop layout.
- Use whitespace according to information value and do not obscure content with decoration.
- Define recurring components and hover, focus, active, loading, error, and success states consistently.
- Prefer existing brand assets.
- Introduce fonts, icons, images, or dependencies only when the value is clear; verify licensing, privacy, and performance.
- Remove generic AI and theme patterns only when they are not justified by the brand, content, or functionality.

### 3. Humanize content

Preserve the meaning of existing claims while making them concrete, credible, and appropriate for the audience.

- Explain actual benefits instead of abstract promises.
- Use natural rhythm, varied sentence length, and clear calls to action.
- Remove buzzword chains, filler, repetition, artificial urgency, unsupported superlatives, and placeholders.
- Reduce competing calls to action to a clear priority.
- Mark and request missing evidence instead of fabricating it.
- Do not write copy solely for keywords or crawlers.

### 4. Implement within the existing project

Use existing conventions and native framework capabilities. Make changes in understandable, verifiable steps.

- Preserve working business logic, data flows, and integrations.
- Add dependencies only when their value is clear.
- Prefer semantic HTML and progressive enhancement.
- Render public core content as crawlable, readable HTML.
- Implement responsive layouts, interaction states, error handling, and reduced-motion behavior.
- Do not silently change analytics, consent, or tracking behavior.
- Do not draft or alter legal content without an authoritative basis.
- Read [references/technical-quality.md](references/technical-quality.md) and implement the relevant SEO, sitemap, robots.txt, LLM readability, accessibility, and performance measures.

### 5. Verify and iterate

Run the project's existing checks after implementation. Fix errors introduced by the change and rerun the relevant checks.

At minimum, verify:

- production build, linting, typechecks, and existing tests;
- public routes, navigation, links, forms, and critical interactions;
- multiple relevant viewports, keyboard operation, and focus behavior;
- metadata, canonicals, structured data, sitemap, robots.txt, and indexability;
- browser console output, missing assets, layout shift, and obvious performance problems.

Use Lighthouse or comparable tools when available. Do not promise rankings, perfect scores, or blanket claims such as “100% SEO.” Report only measured values and measures actually implemented.

## Completion report

Summarize:

1. selected page architecture;
2. identified design direction;
3. AI-slop patterns removed or deliberately retained;
4. important design and content changes;
5. implemented SEO and LLM-readability measures;
6. sitemap and robots.txt status;
7. accessibility and performance improvements;
8. checks executed and their results;
9. remaining work or required user information.

Keep the result project-specific, credible, restrained, functional, accessible, and technically sound.