---
description: How to create client preview sites — features, monetization, gallery, pricing
alwaysApply: true
---

# Preview Sites workflow

When creating or expanding client previews in this repo, follow **[`RULE.md`](RULE.md)** and the feature/pricing catalog **[`features.md`](features.md)**.

## Quick mandates

- Static HTML/CSS/JS only; relative paths; concept banner on public pages.
- No secrets or real customer PII.
- Product features, screen lists, build/monthly prices, and deps → **only** from `features.md`.
- UTM tracking is **base** (every portal), not an add-on.
- Payments requires Email & SMS; AI social requires Social consolidation.
- Every client proposal needs: `proposal/NOTES.md`, `proposal/SCOPE.md`, `mockup/ux-gallery.html`, `mockup/pricing.html`.
- Reuse patterns from existing proposals under `proposals/*/mockup/` (gallery, pricing, `ux-planned.html`, `ux-hub.css`).
- Kebab-case: `proposals/<client-name>/`. Keep `templates/` client-free.
- Every page footer must credit: Made by [AI ML Operations, LLC](https://aimloperations.com) (link the company name).
- Public marketing SEO on first shot: unique titles, meta descriptions, descriptive link text (no bare “Learn more”), OG/Twitter + LocalBusiness JSON-LD on homepage; target Lighthouse SEO 100. Details in `RULE.md` → SEO.
- Add each live preview to the Active previews table in `README.md` (business, phone, email, URL).

Do not invent features or prices. If `features.md` and a mock disagree, update the mock to match the catalog.