# AI Editor RSP — SEO-led Product PRD v3

Date: 2026-06-05
Task: t_793779b1
Site: https://aieditorrsp.net
Repo: /root/projects/aieditorrsp
Tenant: aieditorrsp-seo-led-product-reposition-20260605

Upstream sources:
- SEO/SERP baseline: /root/.hermes/reports/aieditorrsp-seo-led-product-reposition-20260605/seo-serp-intent-baseline.md
- India-first SEO supplement: /root/.hermes/reports/aieditorrsp-seo-led-product-reposition-20260605/india-trend-seo-supplement.md
- Owner SEO correction: /root/.hermes/reports/aieditorrsp-seo-led-product-reposition-20260605/owner-correction-brief.md
- Owner hero correction: /root/.hermes/reports/aieditorrsp-seo-led-product-reposition-20260605/hero-layout-owner-correction.md
- Original product brief: /root/.hermes/reports/aieditorrsp-product-reposition-20260605/owner-product-brief.md

## 0. Decision

PRD verdict: GO for repositioning, but only as an SEO-led prompt/effect library, not as a generic AI image editor SaaS.

Final positioning:

AI Editor RSP is an unofficial India-first RSP-style AI photo editing prompt library + upload-to-edit entry point.

Product promise:

Users can find viral or practical AI photo editing effects, see before/after examples, copy the exact prompt, open/apply it in the editor, and clearly understand whether generation is live, preview-only, or provider-unavailable.

Non-negotiable product order:
1. Find a concrete effect.
2. See before/after or sample preview.
3. Copy prompt immediately.
4. Open/apply prompt in editor.
5. If generation provider is unavailable, show honest preview/waitlist state before expectation is created.

This PRD fully adopts the product-side repositioning and integrates SEO/SERP/page-matrix inputs upfront. No priority split is used; items marked required are required for this repositioning round.

## 1. Upstream assumptions

### 1.1 SEO-led correction

Owner correction is accepted:
- SEO must shape PRD and IA before content/design/frontend.
- SEO is not a post-implementation optimization layer.
- Product advice is adopted fully, but page matrix and IA must inherit the SEO baseline.

### 1.2 India-first trend correction

The keyword `ai editor rsp` is not a mature generic SaaS keyword. It is an India-led rising trend:
- Google Trends screenshot: India=100, Nepal=10, Bangladesh=2, Saudi Arabia=1.
- Past-7-day spikes suggest social/short-video search loops.
- Users likely saw Reels/Shorts/WhatsApp/Telegram prompt instructions and then searched Google.

PRD implication:
- Start with India-first RSP/social prompt intent.
- Preserve broader AI photo editing prompt library IA from the main SEO baseline.
- Do not define RSP as “Reusable Style Prompt” unless independently verified.
- Use wording like “RSP-style AI photo editing prompts” and “unofficial RSP-style prompt hub”.

### 1.3 Existing product correction

Current site over-indexes on:
- professional industrial editor shell;
- console/protocol language;
- too few template cards;
- weak before/after and copy-prompt dominance;
- pricing/provider/credit states that can distract from first-session value.

Required product shift:
- from “AI Image Editor With Prompt Templates”
- to “AI Photo Editing Prompt Library + Upload-to-Edit Tool”.

## 2. Search intent map

### 2.1 `ai editor rsp` / `ai editor rsp editing`

Intent:
- navigational/social-search phrase from India-first creator ecosystem;
- user wants prompt text, same-effect recipe, or entry point shown by a Reel/Short;
- not a user trying to learn an abstract prompt protocol.

Required product response:
- homepage and metadata include `AI Editor RSP Editing` or close search-language variant;
- above fold explains RSP-style prompts in plain language;
- first fold is task entry: title → explanation → editor/generator module;
- no generic hero CTA button group.

### 2.2 AI photo editing prompts

Intent:
- copy-paste prompt examples;
- category/effect browsing;
- before/after proof;
- prompt formula and safety constraints;
- optional upload/apply flow.

Required product response:
- `/ai-photo-editing-prompts` must be a hub with concrete prompts, not a thin article;
- `/prompt-library` must be the crawlable effect catalog;
- each prompt card includes Copy Prompt and Open/Apply in Editor.

### 2.3 Gemini / ChatGPT photo editing prompts

Intent:
- provider-specific copy-paste prompts;
- viral style replication;
- limitations and face/product preservation instructions;
- no expectation of official affiliation.

Required product response:
- dedicated provider cluster pages;
- provider-specific caveats;
- external-use hints;
- no “official Gemini/ChatGPT integration” wording.

### 2.4 India social/festival/use-case prompts

Intent:
- boy/girl/couple/bike/cinematic/double-exposure/3-layer effects;
- festival and event prompts: Holi, Eid, IPL, Ram Navami, Diwali, Republic Day;
- fast copy and share loop.

Required product response:
- India-first filters and page clusters;
- prompt cards with variables for name, outfit, bike/car, team, festival, background, mood;
- updated date and unofficial disclaimer on trend/festival pages;
- noindex thin categories until they have enough real cards.

## 3. Product positioning

### 3.1 April Dunford positioning

Competitive alternatives:
- Tier 1 direct: rspediting.com, aieditingprompt.in, PromptPlum, Media.io prompt pages, Picsart prompt article.
- Tier 2 adjacent: generic AI photo editors, Gemini/ChatGPT native image tools, Pixelbin, Fotor, Canva/Adobe-style editors.
- Tier 3 current behavior: searching Instagram/YouTube captions, DM/comment for prompt, manually rewriting prompt, asking ChatGPT/Gemini from scratch.

Unique attributes:
- India-first RSP/social-search vocabulary.
- Copy Prompt always available.
- Effect cards tied to before/after and provider compatibility.
- Upload-to-edit entry point without hiding provider state.
- Structured effect catalog suitable for SEO and product UI.

Value mapping:
- India-first terms → captures rising social-search intent.
- Copy Prompt → user gets value without signup/generation/payment.
- Before/after → user trusts the effect before copying/applying.
- Provider state contract → avoids disappointment and credit distrust.
- Effect schema → content/design/frontend can scale the library without ad-hoc pages.

Best user:
- India/South Asia social creators and everyday users who saw a viral AI photo edit and want the same prompt quickly.
- Secondary users: creators, founders, sellers, students, job seekers, ecommerce sellers needing practical photo prompts.

Market category:
- AI photo editing prompt library + lightweight upload-to-edit tool.

Trend overlay:
- rising India-led RSP/social prompt demand, Gemini/ChatGPT image-editing virality, and copy-paste prompt libraries ranking in SERP.

Positioning statement:

FOR India-first social creators and everyday users who saw an RSP-style AI photo edit and want the same result fast, AI Editor RSP is an AI photo editing prompt library with a lightweight upload-to-edit workflow that lets them find viral effects, copy prompts, and try them with their own photo. Unlike generic AI image editors or noisy prompt blogs, AI Editor RSP starts with concrete effects, before/after proof, provider compatibility, and honest generation availability.

### 3.2 Messaging hierarchy

Primary H1 options:
- AI Editor RSP Editing Prompts
- AI Photo Editing Prompts You Can Copy or Apply

Recommended homepage H1:

AI Editor RSP Editing Prompts

Recommended homepage short explanation:

Find RSP-style AI photo editing prompts seen on Reels and Shorts. Browse viral prompt recipes, copy the text, customize details like outfit or background, then try the edit in your preferred AI photo tool or in the AI Editor RSP editor.

Benefit messages:
1. Find the exact effect faster: browse RSP-style, Gemini, ChatGPT, boy, girl, couple, bike, cinematic, and festival prompt cards.
2. Copy value immediately: every active effect includes a ready prompt, variables, best-for, avoid-if, and provider notes.
3. Preview before applying: major effects include before/after or sample preview before users upload.
4. Trust the provider state: Upload-to-Edit is active only when provider generation is live; Copy Prompt remains available in every state.

Forbidden framing:
- official RSP editor;
- official Gemini/ChatGPT/Nano Banana integration;
- RSP officially means Reusable Style Prompt;
- professional creative suite;
- unlimited generation;
- generation guarantee while provider is disabled;
- abstract protocol-first explanation above concrete effects.

## 4. Core user flows

### 4.1 Flow A — Find effect → copy prompt

Steps:
1. User lands from Google/social on home, RSP hub, category, provider, or detail page.
2. User sees effect cards in search-language titles.
3. User filters or opens a card.
4. User sees before/after or sample preview.
5. User clicks Copy Prompt.
6. UI shows copy success and suggested next step.

Acceptance:
- Copy Prompt works without login, upload, credits, checkout, or provider availability.
- Prompt is not hidden in long article text.
- Card/detail page includes `best_for`, `avoid_if`, variables, and provider tags.

### 4.2 Flow B — Find effect → open/apply in editor

Steps:
1. User clicks Open in Editor / Try in Editor from card/detail.
2. Editor opens with effect slug and prompt preloaded.
3. User uploads photo or edits prompt variables.
4. UI shows provider mode before generation expectation.
5. If provider live: user can generate and see loading/result/error/quota states.
6. If provider disabled/preview: user sees preview/waitlist message and can still copy prompt.

Acceptance:
- Deep link preserves selected effect and prompt.
- Provider status appears before generation click.
- No fake “Generate now” path if provider is disabled.
- Failed provider calls do not charge credits.

### 4.3 Flow C — Use external provider

Steps:
1. User opens provider page or effect detail.
2. User copies provider-compatible prompt.
3. User reads platform-specific usage hint.
4. User opens preferred external tool manually or via non-affiliating guidance link.

Acceptance:
- External CTA text is factual: “Use this prompt with Gemini/ChatGPT” rather than “official integration”.
- Provider notes mention caveats, prompt length, upload requirements, and identity/product preservation constraints.

### 4.4 Flow D — India trend/festival prompt discovery

Steps:
1. User searches an India/social query such as “rsp editing ai boy”, “Gemini IPL AI photo editing prompt”, “Holi bike car AI prompt”.
2. User lands on matching category/detail page.
3. User sees updated date, prompt cards, variables, copy button, and safety note.
4. User copies prompt or opens editor.

Acceptance:
- Trend/festival pages have at least 3 real prompt cards before indexation.
- Thin/future pages are noindex and excluded from sitemap.
- Pages include India-first language, but not misleading official claims.

## 5. Information architecture and route contract

All routes below are inherited from the SEO baseline or India supplement. Do not delete them from PRD scope without a new SEO/Product decision.

### 5.1 Primary navigation

- `/` — homepage / router / first task entry
- `/rsp-editing-prompts` — India-first RSP prompt hub
- `/prompt-library` — full effect catalog
- `/ai-photo-prompt-editor` — upload/apply/copy workflow
- `/ai-photo-editing-prompts` — broad AI photo prompt hub
- `/pricing` — lower-priority commercial page; must not dominate first session

Footer/legal:
- `/privacy`
- `/terms`
- `/refund`
- `/cookie-policy` if present

### 5.2 Required page matrix

| Path | Primary keyword | Role | Index policy | Required unique asset/value |
|---|---|---|---|---|
| `/` | AI Editor RSP Editing Prompts | homepage/router | index | vertical hero + main editor/generator entry + above-fold effect cards |
| `/rsp-editing-prompts` | RSP editing prompts | India-first hub | index when cards ready | filters for boy/girl/couple/bike/cinematic/festival + prompt cards |
| `/prompt-library` | AI photo editing prompt library | catalog | index | searchable/filterable CollectionPage + ItemList |
| `/ai-photo-prompt-editor` | AI photo prompt editor | tool/editor | index | upload, prompt import, copy mode, provider state |
| `/ai-photo-editing-prompts` | AI photo editing prompts | broad prompt hub | index | prompt formula + categories + cards |
| `/chatgpt-photo-editing-prompts` | ChatGPT photo editing prompts | provider cluster | index | ChatGPT-specific cards/caveats |
| `/gemini-photo-editing-prompts` | Gemini photo editing prompts | provider cluster | index | Gemini-specific cards/caveats |
| `/nano-banana-photo-editing-prompts` | Nano Banana photo editing prompts | provider cluster | index if legal/product permits | provider notes + cards; no affiliation claim |
| `/bing-image-creator-prompts` | Bing image creator prompts | provider cluster | index if enough cards | provider notes + cards |
| `/capcut-template-recipes` | CapCut template recipes | adjacent recipe cluster | index only if real recipes | recipe cards, no unsafe downloads |
| `/lightroom-preset-recipes` | Lightroom preset recipes | adjacent recipe cluster | index only if real recipes | recipe cards, no unsafe downloads |
| `/professional-headshot-prompts` | professional headshot prompt | use-case cluster | index | identity-preserving headshot cards |
| `/linkedin-headshot-prompts` | LinkedIn headshot prompt | use-case cluster | index | LinkedIn/resume variants |
| `/product-photo-prompts` | product photo prompt | ecommerce cluster | index | product label/background/shadow cards |
| `/youtube-thumbnail-prompts` | YouTube thumbnail prompt | creator cluster | index | thumbnail prompt cards |
| `/instagram-photo-editing-prompts` | Instagram photo editing prompts | social cluster | index | flash/collage/aesthetic trend prompts |
| `/background-swap-prompts` | background swap prompt | utility cluster | index | background cards |
| `/photo-enhance-prompts` | photo enhance prompt | utility cluster | index | HD/sharpen/lighting cards |
| `/couple-photo-editing-prompts` | couple photo editing prompt | social/use-case cluster | index | couple prompt cards |
| `/boy-ai-photo-editing-prompts` | boy AI photo editing prompts | India/social cluster | index when ready | boy portrait/style prompt cards |
| `/girl-ai-photo-editing-prompts` | girl AI photo editing prompts | India/social cluster | index when ready | girl portrait/style prompt cards |
| `/bike-ai-photo-editing-prompts` | bike AI photo editing prompts | India/social cluster | index when ready | bike/car prompt cards |
| `/cinematic-ai-photo-editing-prompts` | cinematic AI photo editing prompts | style cluster | index | cinematic prompt cards |
| `/double-exposure-ai-photo-editing-prompts` | double exposure AI photo prompt | style cluster | index | double-exposure cards |
| `/instagram-milestone-poster-prompts` | Instagram milestone poster prompt | social cluster | index when ready | milestone prompt cards |
| `/holi-ai-photo-editing-prompts` | Holi AI photo editing prompts | India/festival cluster | index when in season and ready | Holi cards + updated date |
| `/ipl-ai-photo-editing-prompts` | IPL AI photo editing prompts | India/festival cluster | index when ready | IPL/team variables + cards |
| `/eid-ai-photo-editing-prompts` | Eid AI photo editing prompts | India/festival cluster | index when ready | Eid cards + safety note |
| `/ram-navami-ai-photo-editing-prompts` | Ram Navami AI photo editing prompts | India/festival cluster | index when ready | Ram Navami cards + safety note |
| `/republic-day-ai-photo-editing-prompts` | Republic Day AI photo editing prompts | India/festival cluster | index when ready | flag/civic safety note + cards |
| `/diwali-ai-photo-editing-prompts` | Diwali AI photo editing prompts | India/festival cluster | index when ready | Diwali cards + safety note |
| `/prompts/[slug]` | `{effect} prompt` | effect detail | index only if unique prompt + visual + FAQ | detail template below |
| `/effects/[slug]` | alias for prompt detail | optional alias | 308 redirect or canonical | avoid duplicate canonical |

Index rule:
- Indexable category pages need at least 3 real prompt cards and unique intro/copy.
- Indexable effect detail pages need unique prompt, variables, before/after or sample preview, FAQ, internal links, and schema.
- Placeholder/detail pages without real assets must be noindex and excluded from sitemap.

### 5.3 Homepage structure

Owner hero correction is mandatory.

Required first screen:
1. H1 stacked above description. No left/right title-description split.
2. Short explanation below H1.
3. Main generator/editor module directly below copy.
4. No generic CTA button group in hero.
5. Only the core Generate/editor action remains prominent in the module.

Homepage recommended section order:
1. Hero task entry: `AI Editor RSP Editing Prompts` + short explanation + editor/generator module.
2. Above-fold / immediate effect grid: 6-9 concrete cards with before/after, Copy Prompt, Open in Editor.
3. RSP-style trend hub: boy, girl, couple, bike, cinematic, double exposure, festival.
4. Provider prompt examples: Gemini, ChatGPT, Nano Banana, Bing.
5. How it works: find effect → copy prompt → apply/open editor → provider state clear.
6. Popular categories: Personal, Social Creator, Ecommerce, Business, Utility, Festival/Trend.
7. Preservation/trust rules.
8. Pricing/credits explanation lower on page, only after value is visible.
9. FAQ.

### 5.4 Prompt library structure

Required controls:
- Search by keyword/effect/provider/use case.
- Filters: Boy, Girl, Couple, Festival, Bike, Cinematic, Double Exposure, 3 Layer, Ghost, IPL, Holi, Eid, Ram Navami, Instagram milestone, Personal, Social Creator, Ecommerce, Business, Utility.
- Provider filters: Gemini, ChatGPT, Nano Banana, Bing, CapCut, Lightroom, Generic AI editor.
- Sort: Trending, New, Festival, Most copied, Provider, Easy copy.

Required card fields:
- before image or sample preview;
- after image or sample preview;
- effect title in user search language;
- category/subcategory;
- provider tags;
- prompt excerpt;
- best for;
- avoid if;
- variables to replace;
- Copy Prompt button;
- Open in Editor / Try in Editor;
- external-use hints;
- safety note.

### 5.5 Effect detail template

Each indexable effect detail page must include:
1. H1: `{Use Case} AI Photo Editing Prompt` or provider-specific equivalent.
2. 40-70 word short answer explaining what this prompt creates.
3. Before/after visual pair or sample preview with honest label.
4. Copy prompt block.
5. Editable variables: subject, outfit, background, lighting, mood, aspect ratio, name/team/festival, preserve identity.
6. Negative constraints: no face identity change, no fake text, no altered logos, no unwanted body reshaping, no copyrighted/celebrity likeness misuse.
7. Best for / Avoid if table.
8. Provider compatibility: Gemini, ChatGPT, Nano Banana, Bing, CapCut/Lightroom where relevant.
9. Step block: upload photo → paste prompt → adjust variables → generate/share.
10. Open in Editor CTA with slug/prompt handoff.
11. External-use hints.
12. Related prompts.
13. FAQ.
14. Updated date and unofficial disclaimer.
15. Schema: BreadcrumbList + FAQPage + HowTo or CreativeWork + ImageObject when assets exist.

## 6. Effect catalog contract

### 6.1 Minimum quantity

Required for this repositioning round:
- At least 60 active effect records in the catalog.
- At least 30 index-ready prompt/effect cards across RSP/social/provider/use-case pages.
- Homepage featured cards: at least 6, all with before/after or sample preview.
- Mature target after this round: 100+ effects.

India-first required coverage inside the 60:
- RSP/social India prompt cards: at least 20.
- Provider cards: at least 12 across Gemini/ChatGPT/Nano Banana/Bing.
- Festival/cultural cards: at least 8, but only index pages when content is real and seasonally relevant.

### 6.2 Category taxonomy

Required top-level categories:
- RSP / India Social Trends
- Personal Photo
- Social Creator
- Ecommerce
- Business
- Utility
- Festival / Culture
- Provider-specific

Required India/RSP subcategories:
- Boy AI photo editing
- Girl AI photo editing
- Couple photo editing
- Bike / car photo editing
- Cinematic portrait
- Double exposure
- 3 layer AI photo
- Ghost girlfriend / trend effects, only if safe and non-exploitative
- Instagram milestone poster
- IPL
- Holi
- Eid
- Ram Navami
- Republic Day
- Diwali

Required broad-use subcategories:
- Professional headshot
- LinkedIn headshot
- Profile picture
- Product photo shadow
- White background product photo
- Product label cleanup
- YouTube thumbnail
- TikTok cover
- Background swap
- HD photo enhance
- Object removal
- Restore lighting
- Change clothes

### 6.3 Effect JSON schema

```json
{
  "slug": "rsp-editing-ai-boy-cinematic-prompt",
  "title": "RSP Editing AI Boy Cinematic Prompt",
  "aliases": ["ai editor rsp editing", "rsp editing ai boy", "cinematic ai photo editing prompt"],
  "category": "RSP / India Social Trends",
  "subcategory": "Boy / Cinematic",
  "primary_keyword": "rsp editing ai boy prompt",
  "region_focus": ["India"],
  "language_variant": "English/Hinglish",
  "summary": "Create a cinematic social portrait from a selfie while keeping face identity, outfit shape, and pose recognizable.",
  "short_answer": "This RSP-style AI boy cinematic prompt turns a selfie into a dramatic social portrait with cinematic lighting, background depth, and realistic face preservation. Copy the prompt, replace the outfit and background variables, then use it in Gemini, ChatGPT, or AI Editor RSP.",
  "before_image": {
    "asset_path": "/effects/rsp-editing-ai-boy-cinematic/before.webp",
    "alt": "Selfie before RSP-style cinematic AI photo editing prompt",
    "status": "real|generated_sample|placeholder_noindex"
  },
  "after_image": {
    "asset_path": "/effects/rsp-editing-ai-boy-cinematic/after.webp",
    "alt": "Cinematic RSP-style AI boy photo edit result",
    "status": "real|generated_sample|placeholder_noindex"
  },
  "copy_prompt": "Edit this photo into a cinematic RSP-style social portrait. Keep the same face identity, expression, hairstyle, body proportions, and pose. Add dramatic golden-hour lighting, a blurred urban background, realistic skin texture, sharp outfit details, and high-quality DSLR depth. Do not add fake text, do not change the face, and do not distort hands.",
  "variables": {
    "subject": ["boy", "girl", "couple", "selfie subject"],
    "outfit": ["casual shirt", "traditional outfit", "jacket", "festival outfit"],
    "background": ["urban street", "bike scene", "festival lights", "stadium", "cinematic rain"],
    "lighting": ["golden hour", "neon", "studio", "festival glow"],
    "festival_or_event": ["Holi", "Eid", "IPL", "Diwali", "none"],
    "aspect_ratio": ["1:1", "4:5", "9:16", "16:9"]
  },
  "negative_prompt_constraints": [
    "do not change face identity",
    "do not reshape body",
    "do not add fake text",
    "do not change logos or product labels",
    "do not imitate celebrities or private persons without consent"
  ],
  "best_for": ["Instagram profile", "Reels thumbnail", "WhatsApp DP", "social post"],
  "avoid_if": ["group photo", "face is hidden", "low-light blurry image", "celebrity/third-party likeness"],
  "provider_tags": ["Gemini", "ChatGPT", "Nano Banana", "Generic AI editor"],
  "provider_notes": {
    "gemini": "Upload the source photo first, paste the prompt, and keep identity preservation explicit.",
    "chatgpt": "Attach the image and request one edit before asking for variations.",
    "nano_banana": "Use the same prompt as an image-edit instruction, not as text-to-image from scratch.",
    "generic": "Use in any AI editor that supports image upload plus text instructions."
  },
  "ctas": {
    "copy_prompt": true,
    "open_editor": "/ai-photo-prompt-editor?effect=rsp-editing-ai-boy-cinematic-prompt",
    "external_provider_hint": true,
    "related_prompts": ["bike-ai-photo-editing-prompt", "double-exposure-ai-photo-prompt", "instagram-milestone-poster-prompt"]
  },
  "index_policy": "index|noindex_until_assets_ready|noindex_draft",
  "schema_types": ["CreativeWork", "HowTo", "FAQPage", "BreadcrumbList"],
  "updated_at": "2026-06-05",
  "unofficial_disclaimer": "AI Editor RSP is an unofficial prompt library and is not affiliated with Google, OpenAI, Instagram, or RSP Editing.",
  "analytics": {
    "impression_event": "effect_card_view",
    "copy_event": "prompt_copy_click",
    "open_editor_event": "prompt_apply_to_editor",
    "external_event": "external_provider_open_click"
  },
  "status": "active|draft|needs_assets|noindex"
}
```

### 6.4 Data rules

Mandatory:
- `copy_prompt` for every active effect.
- `copy_prompt_available=true` for every active effect.
- `open_editor` deep link for every active effect.
- `best_for`, `avoid_if`, `provider_tags`, `provider_notes`, `negative_prompt_constraints` for every active effect.
- `index_policy` for every route and effect.
- `updated_at` on trend/festival pages.
- `unofficial_disclaimer` on provider/RSP/festival pages.

Home-featured effects require:
- before/after or honest sample preview;
- Copy Prompt;
- Open in Editor;
- provider tags;
- mobile-tappable actions.

Noindex required when:
- fewer than 3 real cards on category page;
- effect has duplicate prompt and no unique value;
- missing visual/sample preview;
- placeholder content only;
- unsafe/ambiguous copyright, celebrity, or brand usage.

## 7. Provider and trust contract

### 7.1 Principle

Copy Prompt is always available.
Upload-to-Edit is conditional.
Provider availability must be explicit before user expectation is created.

### 7.2 Runtime provider state contract

```json
{
  "copy_prompt_enabled": true,
  "provider_enabled": false,
  "provider_name": null,
  "generation_mode": "disabled|preview|live",
  "paid_enabled": false,
  "checkout_enabled": false,
  "credits_enabled": true,
  "free_generation_available": false,
  "result_cache_ttl_hours": null,
  "message": "Copy prompts are available. Upload-to-edit generation is currently in preview mode.",
  "last_verified_at": "2026-06-05T00:00:00Z"
}
```

### 7.3 UI behavior by state

`generation_mode=disabled`:
- show Copy Prompt as primary available value;
- editor module can show upload preview, but no live Generate promise;
- Generate button label must be “Preview upload flow” or “Join waitlist”, not “Generate now”;
- no credits charged;
- pricing/checkout CTAs for generation are de-emphasized or disabled with explanation.

`generation_mode=preview`:
- user can upload/select effect if no provider call is made or if preview is safe;
- UI states clearly that final generation is not live or is limited;
- Copy Prompt remains available;
- waitlist or “use externally” CTA can appear.

`generation_mode=live`:
- Generate can be primary inside editor module;
- show credit/quota before generation;
- show loading, success, failure, quota exhausted, provider error, network retry;
- failed provider calls do not consume credits.

`paid_enabled=true` and `checkout_enabled=true`:
- pricing can link to checkout, but only after product value and provider state are clear;
- no “unlimited” wording;
- Stripe Tax/billing compliance remains required if checkout is used.

### 7.4 Allowed and disallowed copy

Allowed:
- “Copy this prompt and use it in Gemini, ChatGPT, Nano Banana, or your preferred AI image editor.”
- “Upload-to-edit generation is in preview. Copy Prompt remains available.”
- “Provider unavailable. No credits were charged.”
- “Unofficial RSP-style prompt library.”

Disallowed:
- “Official RSP editor.”
- “Official Gemini/ChatGPT integration.”
- “Guaranteed same result.”
- “Unlimited edits.”
- “Generate now” when provider is not live.
- “Download RSP templates” if no safe/legal downloadable templates exist.

## 8. SEO-copy freeze contract

Design must not start until these page-level copy contracts are frozen for all indexable pages.

### 8.1 Homepage freeze

Path: `/`
Primary keyword: AI Editor RSP Editing Prompts
Secondary keywords: AI photo editing prompts, RSP editing prompts, Gemini photo editing prompts, ChatGPT photo editing prompts, AI photo prompt editor
Search intent: find viral/social prompt → copy → apply/upload → understand provider state

H1:
AI Editor RSP Editing Prompts

Short answer:
AI Editor RSP helps you find RSP-style AI photo editing prompts seen on Reels and Shorts. Browse viral prompt recipes, copy the text, customize details like outfit or background, then try the edit in your preferred AI photo tool or in the AI Editor RSP editor.

Required H2s:
- Find RSP-style prompts from viral photo trends
- Copy prompts for Gemini, ChatGPT, Nano Banana and more
- Browse by boy, girl, couple, bike, cinematic and festival edits
- Copy a prompt or apply it to your photo
- Use prompts safely with your own photos
- Frequently Asked Questions

Hero layout requirement:
- vertical stack: H1 → short answer → editor/generator module;
- no left/right headline-description split;
- no generic CTA button group;
- main Generate/editor action remains inside the editor module.

FAQ required:
- What is AI Editor RSP editing?
- Does RSP mean an official tool?
- Can I copy these prompts for Gemini or ChatGPT?
- Which RSP prompts are popular in India?
- Can I upload my own photo?
- Is this site affiliated with Google, ChatGPT, Instagram, or RSP Editing?

### 8.2 RSP hub freeze

Path: `/rsp-editing-prompts`
Primary keyword: RSP editing prompts
Search intent: India/social prompt retrieval

H1:
RSP Editing Prompts for AI Photo Edits

Required H2s:
- Trending RSP-style AI photo editing prompts
- Boy, girl, couple and bike prompt ideas
- Festival and IPL AI photo editing prompts
- How to copy and customize an RSP prompt
- Use RSP-style prompts in Gemini or ChatGPT
- Safety and consent notes

Minimum body requirement:
- at least 20 prompt cards total across hub and linked detail pages;
- at least 3 cards visible on the hub before indexation;
- updated date;
- unofficial disclaimer.

### 8.3 Provider cluster freeze

Paths:
- `/gemini-photo-editing-prompts`
- `/chatgpt-photo-editing-prompts`
- `/nano-banana-photo-editing-prompts`
- `/bing-image-creator-prompts`

Each provider page must include:
- provider-specific intro;
- what works best;
- what to avoid;
- prompt cards;
- how to use uploaded photos;
- identity/product preservation caveats;
- no official-affiliation wording;
- FAQ.

### 8.4 Effect detail freeze

Each effect detail page must freeze:
- H1;
- short answer;
- prompt block;
- variables;
- best-for/avoid-if;
- provider notes;
- FAQ;
- related prompt links;
- index policy;
- schema type.

## 9. Schema, AEO, GEO, and technical SEO requirements

Homepage:
- WebSite
- WebApplication only if editor module is real
- Organization
- FAQPage
- BreadcrumbList

Library/hub/category pages:
- CollectionPage
- ItemList
- BreadcrumbList
- FAQPage where FAQ exists

Effect detail pages:
- CreativeWork or HowTo
- FAQPage
- BreadcrumbList
- ImageObject for before/after when assets exist

Editor page:
- WebApplication
- HowTo
- FAQPage

AEO/GEO requirements:
- Each indexable page answers the user job above fold before product architecture.
- Short answer blocks are 40-70 words.
- Tables should map effect → best for → provider → variables → avoid if.
- FAQ must cover face preservation, provider availability, prompt copying, uploaded photo use, and unofficial status.

Technical SEO requirements:
- self-referencing canonical for each indexable route;
- sitemap includes only indexable pages;
- noindex pages excluded from sitemap;
- 308 redirects or canonical aliases for duplicate paths;
- image alt text describes before/after effect and use case;
- mobile render preserves copy/open-editor actions;
- route contract must not silently rename `/privacy`, `/terms`, `/pricing`, `/prompt-library`, `/ai-photo-prompt-editor` without redirects.

## 10. Analytics and validation events

Required events:
- `trend_page_view`
- `effect_card_view`
- `effect_card_click`
- `prompt_copy_click`
- `prompt_apply_to_editor`
- `library_filter_used`
- `provider_filter_click`
- `editor_upload_start`
- `generate_click`
- `generate_success`
- `generate_error`
- `external_provider_open_click`
- `related_prompt_click`
- `no_provider_available_view`
- `waitlist_click`

Required dimensions:
- country / India vs non-India;
- landing page;
- query cluster if available;
- prompt category;
- effect slug;
- provider;
- generation mode;
- organic/social/direct source;
- device type.

Success signals:
- users copy prompts from organic landing pages;
- users open editor from prompt cards;
- provider-unavailable views do not spike exits without prompt copy;
- India/RSP pages generate prompt_copy events;
- mobile users can complete copy/open-editor actions.

## 11. Commercial and pricing boundary

Commercial experience must not dominate first session.

Allowed commercial structure:
- Free: prompt browsing/copying, limited or preview upload flow, limited live generations if provider is enabled.
- Pro: defined monthly generation limit, HD/no-watermark/saved prompts/batch effects if implemented.
- Credit pack: occasional extra generations if checkout and tax are live.
- Business/API: ecommerce/product image batch workflow only if backend supports it.

Rules:
- No “unlimited” generation wording.
- Do not sell generation if provider is disabled.
- Checkout CTAs must reflect real `paid_enabled` and `checkout_enabled` state.
- Stripe Checkout, if used, must preserve existing tax/billing compliance rules.
- Copy Prompt remains free and available regardless of paid state.

## 12. Trust, safety, and compliance

Required safety notes:
- Use your own photos or photos you have permission to edit.
- Do not impersonate celebrities, private people, or official brands.
- Do not use prompts to create deceptive identity, fake official documents, fake screenshots, or false text/logos.
- Product and ecommerce prompts must preserve labels/logos unless the user explicitly asks for safe cleanup.
- Festival/cultural prompts must avoid offensive, political, or misleading claims.

Brand/provider rules:
- Mention Gemini, ChatGPT, Nano Banana, Bing, CapCut, Lightroom only as compatible external tools or provider tags.
- Do not imply endorsement, partnership, or official integration.
- “RSP Editing” references must be handled as search language / unofficial RSP-style prompt context, not ownership or official affiliation.

## 13. NOT-DO

- Do not lead with “Reusable Style Prompt” or force users to learn RSP architecture first.
- Do not keep the homepage as a generic industrial editor console.
- Do not remove SEO baseline routes or India-first cluster pages without a new SEO/Product gate.
- Do not create hundreds of programmatic pages without unique prompt + visual/sample + FAQ + user task value.
- Do not index placeholder or thin category pages.
- Do not hide Copy Prompt behind login, upload, payment, credits, or provider state.
- Do not make pricing/auth/credits dominate the first experience.
- Do not claim generation works if provider is disabled or preview-only.
- Do not imply official affiliation with Google, OpenAI, ChatGPT, Gemini, Instagram, Nano Banana, Bing, CapCut, Lightroom, or RSP Editing.
- Do not host risky downloads/templates/presets unless legal/source status is clear.
- Do not use internal names like `Cyberpunk Console`, `Portrait Cleanroom`, `Catalog Shadow`, `Moody Editorial` as primary SEO titles.
- Do not promise exact same external-provider result.

## 14. Downstream acceptance checklist

### 14.1 For content / effect catalog

Deliverables:
- effect catalog JSON with at least 60 active effects;
- at least 30 index-ready cards;
- at least 20 India/RSP/social cards;
- first 6 homepage featured cards;
- provider clusters for Gemini, ChatGPT, Nano Banana, Bing or documented implementation-safe subset;
- use-case/festival clusters with noindex policy when not ready.

Acceptance:
- Every active effect has copy_prompt, title, category, provider tags, variables, best_for, avoid_if, safety note, open_editor URL.
- Titles use user search language.
- Prompt text is unique enough to justify page/indexation.
- Festival/trend pages include updated date and unofficial disclaimer.
- No placeholder-only public effect is presented as complete.

Recommended first homepage cards:
1. RSP Editing AI Boy Cinematic Prompt
2. Professional Headshot From Selfie Prompt
3. Gemini IPL AI Photo Editing Prompt
4. Couple Photo Editing Prompt
5. Product Photo Shadow Prompt
6. Instagram Flash Filter Prompt
7. Bike AI Photo Editing Prompt
8. Double Exposure AI Photo Prompt
9. Background Swap Without Changing Subject Prompt

### 14.2 For design

Deliverables:
- homepage first screen with vertical H1 → description → editor/generator module;
- no hero CTA button group outside the main editor/generator action;
- library grid with mobile-friendly filters and card actions;
- effect detail page template;
- editor states for copy mode, upload, provider disabled, preview, live generation, loading, result, quota, error;
- provider/trust badges that inform without becoming the lead message.

Acceptance:
- First 5 seconds: user understands they can find/copy/apply AI photo editing prompts.
- First screen is task entry, not marketing split layout.
- Above fold contains real effect value, not abstract protocol explanation.
- Copy/Open actions are visible and tappable on mobile.
- Before/after or sample preview is visually dominant on effect cards/detail pages.

### 14.3 For backend / data

Deliverables:
- effect catalog data source/API or static JSON contract;
- provider state endpoint/config matching this PRD;
- deep link handling for selected effect slug/prompt;
- analytics event plumbing;
- sitemap/index policy data.

Acceptance:
- Copy Prompt path does not depend on provider.
- Upload-to-Edit is gated by provider state.
- Disabled/preview/live states are reliable and consistent across pages.
- Failed provider calls do not deduct credits.
- Indexable/noindex state is machine-readable for frontend sitemap/meta generation.

### 14.4 For frontend

Deliverables:
- route implementation for required IA or documented aliases/redirects;
- homepage vertical hero + editor module;
- effect card component;
- library search/filter/sort;
- effect detail template;
- editor prompt-import state;
- provider state UI;
- schema/canonical/sitemap/noindex implementation;
- analytics events.

Acceptance:
- User can complete: find effect → see before/after → copy prompt → open/apply in editor → provider state clear.
- Copy Prompt works from home cards, library cards, and detail pages.
- Open in Editor carries effect slug/prompt and persists after upload.
- Provider disabled state appears before false generation expectation.
- Mobile flow works at common India/social mobile viewport sizes.
- Code/deploy task must commit + push + deploy from the same SHA.

### 14.5 For SEO recheck

Acceptance:
- Required page matrix exists or has documented noindex/redirect rationale.
- No baseline SEO route was silently dropped.
- Indexable pages have unique title/meta/H1/H2/schema/body/prompt/FAQ.
- Noindex pages are excluded from sitemap.
- RSP/India pages preserve exact search-language aliases.
- Provider pages avoid official-affiliation wording.
- India-first event segmentation is implemented.

### 14.6 For product acceptance / QA

Required real user tasks:
1. Land on homepage and identify value in 5 seconds.
2. Verify hero layout: title above description above editor/generator; no left/right title-description split; no generic CTA button group.
3. Copy a prompt from homepage card.
4. Browse `/prompt-library`, filter by category/provider, copy prompt.
5. Open RSP hub and find a boy/girl/couple/bike/festival prompt.
6. Open provider page and verify provider-specific caveats.
7. Open effect detail and verify before/after, prompt, variables, best_for, avoid_if, provider notes, FAQ, related links.
8. Open effect in editor and verify selected prompt persists.
9. Upload a source image and verify provider mode before generation expectation.
10. If provider disabled/preview, verify Copy Prompt remains available and no fake generation promise appears.
11. If provider live, verify loading/result/error/quota states and no-credit-on-provider-fail behavior.
12. Repeat core path on mobile.

PM verdict JSON expected downstream:

```json
{
  "pm_verdict": "PM_GO | PM_CONDITIONAL_GO | PM_NO_GO",
  "competitive_minimum_verdict": "pass | fail | partial",
  "core_tool_ux_verdict": "pass | fail | partial",
  "conversion_path_verdict": "pass | fail | partial",
  "verified_user_tasks": ["find effect", "view before/after", "copy prompt", "open/apply in editor", "provider state clear"],
  "verified_tool_states": ["empty", "uploaded", "loading", "result", "quota_exhausted", "auth_required", "error", "provider_unavailable"],
  "scope_gaps": [],
  "blocker_count": 0,
  "next_gate": "motest_qa"
}
```

## 15. Handoff summary

For content:
- Build the catalog first. Minimum 60 effects; 30 index-ready; 20 India/RSP/social. Use search-language names. Every effect needs copy prompt, variables, provider compatibility, best_for, avoid_if, safety note, and open-editor CTA.

For design:
- First screen is vertical title → description → editor/generator module. Remove generic CTA group. Show concrete effect cards and before/after proof early. Mobile-first for Indian social-search traffic.

For backend:
- Provide effect catalog contract, provider state contract, index/noindex flags, analytics plumbing, and deep link support. Copy Prompt must not depend on provider or auth.

For frontend:
- Implement SEO-led IA without dropping baseline pages. Copy Prompt and Open in Editor must work across home/library/detail. Provider state must be honest. Schema/canonical/sitemap/noindex must follow page matrix.

For SEO/Product/QA:
- Recheck actual user task chain: find effect → before/after → copy prompt → open/apply in editor → provider state clear. No PM/QA GO if this chain fails.

## 16. Completion criteria for this PRD

This PRD is complete when downstream workers can proceed without inventing product decisions:
- final positioning is defined;
- India-first SEO assumption is explicit;
- IA/page matrix inherits both upstream SEO reports;
- hero correction is product/design/frontend/QA acceptance requirement;
- core user flows are defined;
- effect catalog schema and minimum counts are defined;
- provider trust contract is defined;
- downstream acceptance checklists are defined.