# Landing Book
### Real landing pages. Reviewed patterns. Better decisions.
Landing Book is a lightweight Codex skill built from 74 real landing-page
teardowns. It gives your agent concrete examples for planning, auditing, and
rewriting landing pages instead of falling back on generic advice.
The library covers SaaS, creator products, newsletters, courses, sponsorships,
pricing, social proof, and request-demo flows. It works offline and loads only
the cases relevant to the task.
## What it helps you do
- Turn a product brief into a clear landing-page structure.
- Improve positioning, copy, CTA, proof, pricing, and forms.
- Audit an existing page and prioritize the biggest decision problems.
- Compare patterns across similar products and conversion goals.
- Adapt proven design ideas without copying another brand.
## What your agent gets
- **74 curated landing-page cases**
- **61 reviewed visual teardowns**
- **A practical design and audit playbook**
- **Detailed evidence with source URLs and image hashes**
The published library is text-only. There is no screenshot bundle, crawler
output, or large archive to load into context.
## Install
```bash
git clone https://github.com/hbui290/landing-book.git
mkdir -p "$HOME/.codex/skills"
ln -s "$PWD/landing-book" "$HOME/.codex/skills/landing-book"
```
If the destination already exists, inspect it before replacing it.
## Try it
```text
Design a landing page for my self-serve SaaS. Choose two relevant cases and
explain why their patterns fit the offer.
```
```text
Audit this request-demo page. Prioritize the three biggest problems and ground
each recommendation in a reviewed case.
```
```text
Show me three credible ways to use social proof on a B2B landing page.
```
## How it works
Codex starts with the [playbook](references/playbook.md), searches the
[catalog](references/catalog.md), then opens the smallest useful set of case
notes. Detailed evidence is loaded only when visual grounding matters.
Observations, recommendations, and hypotheses remain separate. Landing Book
does not invent customer proof, conversion lifts, or A/B-test results.
## Add or update cases
Use the [maintenance workflow](MAINTAINING.md) to capture sources, analyze one
asset per chat, run independent visual QA, and publish reviewed text without
adding raw screenshots to the skill.
## Sources and scope
Landing Book is an independent research project and is not affiliated with
Landing Pages Explained or the companies referenced in the cases.
Brand names and source material belong to their respective owners. The
repository excludes original screenshots, links back to the reviewed sources,
and keeps hashes for provenance. Its notes describe visible design choices;
they do not establish conversion performance or unseen page behavior.