# CLAUDE.md — BT Web Group Packages Project
Guidance for Claude when building **any** asset in this repo: marketing web pages,
service/bundle/tripwire pages, email templates (eblasts), landing pages, or copy.
---
## 0 — The two rules that override everything
1. **Source of truth is `PACKAGES.md` + `FINALIZATION_QUESTIONS.md`. Read both before
writing or editing any page, email, price, name, or fact.** Never invent a price,
tier name, phone number, address, testimonial, or stat. If a value isn't in those
files, ask — don't guess.
2. **Match the *look and feel* of `packages-html/packages-root.html`. Do NOT copy
its *structure*.** Every new page gets a unique layout/section order/composition,
but the visual language (tokens, type, color, components, spacing rhythm, motion)
must feel like it came from the same brand. `packages-root.html` is the canonical
design reference — open it when in doubt.
---
## 1 — Source-of-truth files
| File | Holds | Use it for |
|---|---|---|
| `PACKAGES.md` | Prices, tier names, market rates, feature bullets, bundle math, CRM context slugs, AI display rules, the list of downstream files to keep in sync | Any number, package name, or feature bullet that appears on a page or in an email |
| `FINALIZATION_QUESTIONS.md` | The owner's finalized decisions: brand/contact facts, testimonials, client logos, case-study numbers, assessment copy, email/UTM rules, AI-page scope, visual direction | Brand facts, proof content, copy decisions, and "is this allowed yet?" scope calls |
**Precedence when they disagree:** `FINALIZATION_QUESTIONS.md` answers are the most
recent human decision and win. When you act on one, reconcile `PACKAGES.md` to match in
the same change, and call out the drift to the user. (Example: `PACKAGES.md` still says
"12 years / since 2014" but the finalized answer is "20+ years / since 2005".)
**When you change a price or name:** update `PACKAGES.md` first, then every downstream
file it lists in §6 (service pages, bundle pages, tripwire pages, AI pages, eblasts).
Keep them in sync in one pass.
---
## 2 — Design system (the look & feel to replicate)
All of the following is lifted from `packages-html/packages-root.html`. Reuse the
tokens and component patterns; invent your own page structure around them.
### 2.1 Scoping & paste-safety (non-negotiable build rule)
- Pages are **Beaver Builder paste-safe**: no ``, ``, or ``. A page is
self-contained — inline `` font tags, one or more `