# AIE PRD v4 Stitch Design — Independent Review

Design source: `https://stitch.withgoogle.com/projects/11564566555273931507`  
Local package: `/root/projects/aieditorrsp/design/aie-prd-v4-stitch-20260610/`  
Reviewed against:
- `/root/.hermes/reports/aieditorrsp-prd-v4-standardization-20260610/design-acceptance-contract.md`
- `/root/.hermes/reports/aieditorrsp-prd-v4-standardization-20260610/seo-copy-freeze-route-index-contract.md`

## Verdict

`DESIGN_NO_GO_FOR_FRONTEND`

This is a fresh official Stitch package and the visual direction is no longer the stale dark SaaS version. However, the prior `DESIGN_CONDITIONAL_GO` is too generous. The package has route-role, SEO-copy, nav active-state, and content-depth problems that should be fixed before frontend implementation.

## Critical issues

### 1. Navigation active state is wrong on multiple pages

Evidence from exported HTML:

- `/` desktop: `Prompt Library` is active/highlighted. Homepage should have no catalog active state or an explicit Home active state if Home exists in nav/footer.
- `/` mobile: `RSP Prompts` is active/highlighted. Wrong route.
- `/ai-photo-editing-prompts`: `Prompt Library` is active/highlighted. Wrong route. This route is the SEO guide/hub, not the catalog.
- `/prompts/[slug]` desktop: `RSP Prompts` is active/highlighted. This may be acceptable only if detail pages are intentionally under RSP Prompts, but current detail is a generic prompt detail and should probably mark `Prompt Library` or no active state depending IA.
- `/prompts/[slug]` mobile: nav collapses to only `menu AI Editor RSP Sign in`; no visible IA state.

This directly supports Owner concern. Frontend should not inherit these active states.

### 2. Homepage is too thin and too catalog-like

Contract requires `/` to support the primary keyword `AI Editor RSP Editing Prompts`, 900–1,200 visible/collapsible words, H2 blocks for trend capture, providers, categories, apply flow, safety, FAQ.

Current Home only has:
- H1
- short intro
- one editor/provider card
- `Featured Prompt Recipes`
- a small safe-use note / FAQ-like area

Missing or weak:
- required H2 structure: viral RSP trends, provider copy, category browse, apply flow, safety, FAQ
- provider cluster links: Gemini / ChatGPT / Nano Banana / Bing
- use-case links: boy, girl, couple, bike, cinematic, headshot, product photo
- clear homepage narrative explaining relation between library, guide, editor, pricing

Visual result: it feels like a prompt-library teaser, not a real SEO landing homepage.

### 3. `/ai-photo-editing-prompts` does not carry enough SEO guide content

Contract says this route is Guide / SEO Hub, with:
- 40–70 word definition above fold
- prompt formula
- 9–12 curated examples
- category routing
- provider routing
- FAQ / AEO blocks
- primary CTA `Browse the full prompt library`

Current page has:
- H1 `AI Photo Editing Prompts`
- `The RSP Prompt Formula`
- only 3 curated cards
- FAQ
- CTA to library

Missing or too weak:
- 9–12 curated examples
- provider routing section
- category routing section
- richer guide copy / AEO depth
- clear differentiation from RSP-only framing; the intro says “India-first RSP-style prompt library”, narrowing a broad `AI photo editing prompts` hub too much

This suggests SEO freeze was only partially read.

### 4. `/prompt-library` is visually good but too shallow for Full Catalog contract

Contract requires full catalog with search/filter/sort, category/provider/use-case filters, supporting copy, FAQ, and card fields: title, provider tags, prompt excerpt, best_for, avoid_if, variables, safety note, Copy Prompt, Open in Editor.

Current desktop page has:
- search
- sort chips
- 3 visible cards
- Copy / Editor actions

Problems:
- no H2 blocks at all in exported HTML
- no FAQ/supporting content visible
- only 3 cards, far from the design expectation of a dense catalog impression
- filter taxonomy is under-specified; missing many required categories/providers/use cases
- desktop card primary button appears as short `Copy`, not `Copy Prompt`
- card fields do not visibly cover variables + safety note + avoid_if consistently

This may pass a style check, but it is not enough as a catalog implementation blueprint.

### 5. Mobile library has no H1 / no heading structure

`prompt-library-mobile.html` exported headings:
- no `h1`
- no `h2`
- no `h3`

For a mobile design, visual heading may exist but HTML export indicates no semantic H1. This is a design-to-frontend risk because the page may be implemented without proper SEO hierarchy.

### 6. Editor pages use inconsistent H1 naming and are missing SEO support blocks

Contract says editor route H1 should be `AI Photo Prompt Editor`, with short answer, H2 sections, FAQ, and state explanation.

Current variants use inconsistent H1s:
- `Editor`
- `Prompt Editor`
- mobile: no H1

State coverage visually exists, but SEO/page contract is incomplete:
- no consistent route title
- no obvious explanatory short answer on each state
- missing required support sections: Copy Prompt availability, preview/disabled/live modes, safe application, FAQ

For product-state UI, this is mostly OK. For indexable `/ai-photo-prompt-editor`, it is not enough.

### 7. Prompt detail desktop is decent, mobile is incomplete

Desktop covers key blocks: H1, prompt, variables, best/avoid, related prompts, CTAs.

Gaps:
- H2 structure is sparse: only `The Prompt`, `Related Prompts`
- no clear FAQ block visible
- no explicit provider compatibility/caveats section as H2
- mobile detail lacks related prompts and FAQ in the exported headings; it may be too thin for the detail index gate

### 8. Pricing has one known copy violation and should not be treated as fully accepted

Known issue from prior review:
- `Unlimited copy prompts` must be replaced with `Copy all public prompts` or equivalent.

Additional review:
- page visually does include Free / Pro / Business and transparency blocks
- but the H1 `Simple, Transparent Pricing` is generic; acceptable for pricing UX, but should be checked against final SEO/pricing copy if `/pricing` is indexable
- pricing must not become first-visit dominant; current design is fine on this point

### 9. Header/footer consistency is not strong enough

Header IA appears similar, but exported pages vary:
- some headers include brand text in nav parse, others do not
- mobile prompt detail collapses to only `menu AI Editor RSP Sign in`
- active state varies incorrectly
- footer labels are inconsistent (`Product Info`, legal links only; required main pages/provider/use-case links are not consistently visible)

Contract says header/footer cannot be left for frontend to reinterpret. This should be reworked in design or specified as a non-negotiable component override before frontend.

## Route-by-route decision

- `/`: revise. Fresh style, but not homepage/SEO-complete enough. Active nav wrong.
- `/prompt-library`: revise. Visual direction OK, but catalog depth/SEO support/filter taxonomy/card fields incomplete.
- `/prompt-library` mobile: revise. No heading structure and too few visible taxonomy cues.
- `/ai-photo-editing-prompts`: revise. Too shallow for SEO hub; active nav wrong; only 3 curated examples.
- `/ai-photo-prompt-editor`: conditional. Product states are useful, but route H1/SEO support and naming consistency need correction.
- `/prompts/[slug]`: conditional. Desktop usable; mobile/detail SEO blocks need FAQ/provider caveats/related prompts strengthened.
- `/pricing`: conditional after copy patch.

## Recommended next action

Do not send this directly to frontend as `DESIGN_GO`.

Send a focused design revision task to Moying:

1. Fix nav active-state rules globally.
2. Rebuild Home as real SEO/product landing page using SEO freeze H2/H3 blocks.
3. Expand `/ai-photo-editing-prompts` into true guide/hub: 9–12 examples + provider/category routing + FAQ/AEO.
4. Expand `/prompt-library` catalog density and field completeness; add FAQ/supporting copy lower page.
5. Standardize editor H1 to `AI Photo Prompt Editor` and add SEO support sections for indexable route.
6. Strengthen prompt detail mobile/desktop provider caveats, FAQ, related links.
7. Patch pricing copy: no `Unlimited copy prompts`.

## Bottom line

The design is visually newer and directionally better, but it has not faithfully carried the SEO-copy freeze and navigation contract. Treat it as `DESIGN_REVISION_REQUIRED`, not frontend-ready.