- name
- landing-book
- description
- Use when designing, auditing, rewriting, or comparing SaaS, creator, course, newsletter, sponsorship, pricing, social-proof, or request-demo landing pages and trustworthy offline examples are useful.
# Landing Book
Use this private offline evidence library. Its 74 cases comprise:
- 61 with independently verified still images.
- 10 source-text-only cases without a verified still.
- 3 inventory-only records without usable prose or still evidence.
Portraits, logos, decoration, and recommendation cards are excluded.
## Retrieve
1. For end-to-end design or audits, open `references/playbook.md`. For a narrow
comparison, skip directly to the catalog.
2. Search `references/catalog.md` by goal or exact hyphenated pattern.
```bash
rg -i 'social-proof' references/catalog.md | rg -i 'breakcold|shipfast'
rg -i 'newsletter' references/catalog.md | rg -i 'creator'
rg -i 'request.*demo' references/catalog.md | rg -i 'chargebee|sleeknote|hubspot'
```
3. Open the smallest relevant set in `references/cases/`: usually one file for
a narrow question or two to three files for an end-to-end plan.
4. Open the linked evidence Markdown only when detailed visual grounding matters.
The published evidence is text-only; cite the source URL or image SHA-256.
5. Raw images and machine records are upstream audit material, excluded from
the installed skill.
## Evidence contract
- Original images are primary. OCR/Gemini are supporting layers.
- Keep observations grounded; label inferences as hypotheses with their limits.
- Never claim conversion causality or invented A/B-test results.
- A crop covers only its available pixels, not unseen page content.
- Source-only cases may use archived prose but must not inherit visual claims.
- Inventory-only records confirm existence; do not use them as design evidence.
- Do not browse unless Boss requests current/live information.
- Adapt patterns to the brief; never copy a page verbatim.
Auf GitHub ansehen