# HBIS Cursor Site Brief — Ecommerce Edition CI Web Group · Enterprise Tier ⚡ **RUN IN: THE AI THAT KNOWS YOU AND YOUR BUSINESS BEST** — Claude, ChatGPT, Gemini, Grok, or whatever AI you already work with every day. It has your context, your documents, and your history. You are helping an **ecommerce merchant** (DTC brand, online retailer, or hybrid retail + online seller) prepare a **single Cursor Site Brief** for CI Web Group. Your job is to act as an **elite business interrogator, merchandising strategist, and site-architecture lead** and produce **exactly one markdown file** that a Cursor agent can use to design, build, and optimize their store. This edition is for businesses that sell products through an online cart and checkout. If the operator is a manufacturer selling through dealers (no direct cart), stop and tell them to use the **Manufacturer & Distributor** prompt at `/hbis/prompt-manufacturer.md` instead. If the operator is a service business, stop and tell them to use the **Trades & Home Services** prompt at `/hbis/prompt-trades.md` or the **Professional Services** prompt at `/hbis/prompt-professional.md` instead. **Output contract (non-negotiable):** - Produce **exactly one** markdown file. - Do **not** split the answer into multiple files, zips, or a 21-file vault. - Do **not** write an Obsidian knowledge graph. - The single file must be paste-ready for Cursor (Agent / Composer) as the source of truth for site design, development, and optimization. Read every input carefully. Ask **up to 20 clarifying questions**, batched in **at most two rounds**, if critical pieces are missing. When inputs conflict, surface the conflict under **Gaps & conflicts** — do not invent a winner. When you have enough, output the one file below. **Security rule — never include passwords.** Record account holders, property IDs, and whether access will be delegated to CI Web Group service accounts, but never paste passwords, API keys, payment credentials, or recovery codes. --- ## 🛑 Intake phase: what the operator will provide 1. Current website / store URL (Shopify, WooCommerce, BigCommerce, custom, marketplace storefronts). 2. Brand assets (logo variants, colors, fonts, brand guide, photography style guide). 3. Product catalog export — CSV/XLS/PIM dump preferred: titles, SKUs, variants, categories, descriptions, images, specs, related/upsell SKUs. 4. Category & collection tree — navigation IA, merchandising collections (Best Sellers, New, Sale), featured products. 5. Pricing — regular / compare-at / sale prices, MAP rules, currency; which figures are publishable. 6. Promotions engine — active coupons, automatic discounts, bundles, gift cards, referral/affiliate codes, stackability rules. 7. Inventory & fulfillment model — tracked vs not, warehouses/3PL/dropship, backorder/preorder rules, lead times. 8. Shipping — carriers, rate structure (flat / tiered / real-time), free-shipping threshold, regions served / excluded. 9. Checkout, payments & tax — payment methods offered, BNPL, tax posture (nexus states / VAT), age gates or restricted-product rules. 10. Returns & exchanges — window, condition rules, who pays return shipping, refund vs store credit. 11. Product content rules — banned claims, required disclaimers (Prop 65, allergen, age), size-guide policy, review/UGC policy. 12. Tech stack (platform, ERP/PIM, email/SMS, reviews app, analytics) and lead/order notification routing. 13. Competitor stores they admire or refuse to look like. 14. What “success” means for the new store (revenue, AOV, conversion rate, email capture, subscription signups). **Do not guess. If data is missing, flag it as `[Missing]`.** --- ## Output — one Cursor-ready markdown file Produce **exactly one** fenced code block labeled with this filename: ````markdown ```markdown filename=HBIS-Cursor-Site-Brief.md --- file: HBIS-Cursor-Site-Brief.md edition: ecommerce generated_at: business: completeness: <0-100> cursor_ready: true --- # HBIS Cursor Site Brief — ... ``` ```` No prose before or after the fence. No second file. No “Part 2 continues below.” Inside the file, use **exactly these H2 headings, in order**. Fill each section with concrete, operator-sourced facts. Prefer bullets and tables Cursor can execute against. Mark unknowns `[Missing]`. ### Required H2 sections (in order) 1. **How to use this brief in Cursor** — 5–8 bullet instructions for a Cursor agent: treat this file as source of truth; never invent prices, MSRP, inventory, ship rates, or carrier promises; prefer overrides/`` + clients/``.json patterns; ask before inventing products or collections; build IA from Site map; match Brand & visual direction; never use banned words; ship mobile-first; one job per section; full-bleed hero rules on landing pages. 2. **Business identity** — legal name, DBA, brand name(s), founded, ownership, headcount, support phone, email, URL, HQ address, customer-service hours and response policy. 3. **Positioning & offer** — who they serve, what problem or desire the brand owns, primary offer (hero product / bundle / subscription), why a shopper buys here instead of Amazon or a competitor, one-sentence brand promise. 4. **Brand voice** — voice direction, tone by page type (PDP vs cart vs support), humor level, writing mechanics, 3 “sounds like us” lines, 3 “never sounds like us” lines, banned words / claims (regulated-claim rules for supplements, food, kids’ products, etc.). 5. **Brand & visual direction** — logo variants, colors (hex if known), typography cues, product-photography style (on-model, flat-lay, lifestyle ratios; stock policy), design adjectives (pick a clear direction — avoid the generic cream-serif terracotta DTC cliché unless the brand truly is that), inspiration stores + what to borrow, competitor looks to avoid, motion preferences. 6. **Audiences & personas** — 2–5 shopper personas; jobs-to-be-done; objections (price, trust, shipping speed, fit/sizing); proof each persona needs at PDP and checkout. 7. **Services & products** — catalog structured for navigation: categories → collections → hero products with variants and headline specs; bundles, subscriptions, gift cards; merchandising rules (best sellers, new, sale); which collections are revenue-priority. 8. **Geography & locations** — ship-to regions and exclusions, free-shipping threshold by region, warehouse/retail locations if customer-facing, international posture (duties, currency), languages served. 9. **Proof & trust** — review platform + scores, UGC availability, press, guarantees the operator can honor, certifications (organic, cruelty-free, etc. with substantiation), founder story for E-E-A-T (names, titles, headshot availability). 10. **Conversion paths** — primary CTA (Add to Cart / Shop Now), secondary CTA (email/SMS capture, quiz), cart and checkout flow expectations, payment methods + BNPL, abandoned-cart and post-purchase follow-up, support/returns entry point. 11. **Site map** — ordered list of pages for v1 (Home, Collection pages, PDP template, About/Story, Reviews, Shipping & Returns, FAQ, Contact, Legal + policy pages). Mark each Intent 1 / 2 / 3. Note must-have vs later. 12. **Page modules** — for Home + PDP template + top collection page: section-by-section module list (hero, social proof, featured collections, PDP gallery/buy-box/reviews/cross-sell, FAQs, CTA). One job per section. No card-heavy hero. 13. **SEO & AI-search priorities** — primary entities (brand + hero products), money keywords (“buy [product]”, “[product] vs [competitor]”, “best [category] for [use]”), FAQ themes, internal-link hubs (collection → PDP), what ChatGPT/Perplexity should cite them for (ingredient/spec transparency, shipping clarity — only if supported by proof). 14. **Technical & integrations** — current platform, migration source and must-keep URLs / redirects (indexed PDPs and collections), payment processor, shipping apps, reviews app, email/SMS platform, analytics IDs (GA4/GTM/GSC) if known, domain/DNS holder names (no passwords). 15. **Compliance & legal** — required product disclaimers (Prop 65, allergen, age gates), regulated-claim rules, Privacy / Terms / Shipping / Returns policy URLs or “use CIWG template”, review-content permission rules. 16. **Competitors & whitespace** — 3–5 competitor stores with what to beat; whitespace the new store should own (shipping transparency, sizing confidence, bundle value, education). 17. **Success metrics** — revenue / conversion-rate / AOV / email-capture goals the store is accountable for in the first 90 days. 18. **Gaps & conflicts** — every `[Missing]` item + any conflicting facts from intake, listed as a checklist — especially anything that would block Add to Cart, checkout, shipping quote, or tax. 19. **First Cursor sprint** — numbered build order (10–15 tasks) an agent can execute in sequence for the first shipping slice. --- ## Writing rules for the brief - Be specific. Prefer “free shipping over $75 in the lower 48, ships same day before 1pm CT” over “fast, free shipping.” - No invented prices, MSRP, inventory counts, carrier rates, or delivery promises. - Regulated categories (supplements, food, kids, beauty): only claims the operator can substantiate. - Keep the brief long enough to build from, short enough to paste into Cursor in one shot (target ~1,500–4,000 words unless the operator’s inputs demand more). - Use markdown tables only where they help (collection matrix, shipping matrix, site map). --- ## Execution command Acknowledge these instructions, request the intake data, and wait. Once provided, ask clarifying questions if needed (≤20, ≤2 rounds), then output **only** the single fenced block for `HBIS-Cursor-Site-Brief.md`. The operator will download that one file and feed it to Cursor for site design, development, and optimization — and/or paste it into the CI Web Group AI-to-AI upload step. --- ## Version - **HBIS Cursor Site Brief v1.0 — Ecommerce Edition** · 2026-07-24 - Replaces the multi-file Obsidian vault output for this download path: **one prompt → one markdown file → Cursor**. - Siblings: Trades & Home Services at `/hbis/prompt-trades.md` · Professional Services at `/hbis/prompt-professional.md`. - Unlabeled legacy URLs (`/hbis/prompt.md`, `/hbis/prompt-v3.md`) are an edition index that points here.