# RoofHero Visual System — Current Working Master

Last consolidated: 2026-05-28

## Current editable masters

This MD + HTML pair is the current working source of truth for RoofHero brand-system iteration. Keep referencing and iterating on these files rather than creating new one-off working files:

- `ROOFHERO_VISUAL_SYSTEM_CURRENT.md`
- `ROOFHERO_VISUAL_SYSTEM_CURRENT.html`

Use these files for current RoofHero visual-system work:

- `ROOFHERO_VISUAL_SYSTEM_CURRENT.html` — visual companion dashboard for this MD.
- `roofhero-brand-visual-system-v3.html` — broad brand visual system.
- `roofhero-roof-trace-component-v1.html` — selected base graphic component.
- `roofhero-ad-templates-v1.html` — early V1 paid ad templates.
- `roofhero-anchor-graphics-v1.html` — early exploratory graphics board.
- `roofhero-icons-images-graphics-reference-v1.md` — graphics and image rules.
- `roofhero-animation-reference-v1.md` — motion direction.

## Roover relationship

Roover is the engine/blueprint system. RoofHero is the homeowner-facing proof and conversion system.

Use `../Roover Brand/roover-brand-visual-system-v2.html` as the structural reference for how to build and document component families:

- surfaces
- primitives
- trace system
- build map
- icons
- explainers
- ads/social
- shipped foundations
- motion and usage standards

Do not copy Roover visually without translating it. Roover can feel more technical and engine-like. RoofHero should feel more trust-led, practical, homeowner-friendly, and ad-ready.

## Locked / emerging decisions

- The selected RoofHero cornerstone graphic is the **grid + roof trace component**.
- Base formula: `pampas technical grid + soft roof plane + blaze perimeter trace + dark ridge lines + one or two proof chips`.
- The roof trace should feel like evidence, not decoration.
- Proof chips should use evidence language: `Same scope`, `Roof Review`, `Local pricing path`, `No sales-call pile-on`.
- Keep the old dark-green/orange RoofHero visual punch, but retire old lead-gen claims.

## Current focus when work resumes

Work one component family at a time, then lock it before generating variants.

Recommended next order:

1. Roof trace component: refine and lock base template.
2. Generate roof trace variants: square ad, story/reel, website hero, email header, dark campaign, real roof photo overlay.
3. Roof Review packet graphic.
4. Address → Roof Review → clearer scope → local pricing path explainer.
5. Trust chips / badges.
6. Icon set.
7. Paid ad templates.
8. Website section/component templates.
9. Motion and usage standards.

## Guardrails

Never use:

- `Compare 3 quotes`
- `Get roof quotes in hours`
- fake speed claims
- fake savings claims
- fake roofer availability
- guaranteed pricing language
- top-rated/best-roofer claims

Preferred language:

- `Start with a clearer roof scope.`
- `Roof Review first.`
- `Clearer scope before roof quotes.`
- `RoofHero reviews your roof first, then shows the right local pricing path.`

## Pickup prompt

Continue RoofHero visual system work from:

`/Users/mikebullot/Library/CloudStorage/GoogleDrive-mike@roofhero.com.au/My Drive/RoofHero HQ Drive/12 Brand & Messaging/RoofHero Brand/ROOFHERO_VISUAL_SYSTEM_CURRENT.md`

Focus on one component family only. Current component: grid + roof trace component in `roofhero-roof-trace-component-v1.html`.