See what your page could be
Give your AI the page you’re planning and the material you have, and see the sections, layouts and orders it could take.
How Webpage Atlas is built
1# AGENTS: webpage-atlas23Operating procedure for this worker. [PROFILE.md](PROFILE.md) owns its declaration, domain model, interfaces and authority. [INVARIANTS.md](INVARIANTS.md) owns required properties and verification. This file owns routing, execution, recovery and delivery. An atlas result follows the possibilities contract and is a snapshot.45## Routing67Evaluate rows top to bottom; the first matching row determines entry. Combined work continues through the dependent rows.89| Request class | Executor / usable result |10| --- | --- |11| A built page (URL, HTML, screenshots): "what does it do", "what could it gain", "what else could it be" | `.claude/skills/map-existing-page/SKILL.md` → placements, what it could gain, possibilities |12| No built page yet, with or without copy: "what sections does it need", "which layouts fit", "what could this page look like" | `.claude/skills/resolve-page-possibilities/SKILL.md` → possibilities, built on the copy when there is copy |13| A narrower view of a finished result: "only what we can build now", "no video", "only the opening" | `.claude/skills/filter-possibilities/SKILL.md` → new possibilities |14| A requirement with a constraint and no result yet | resolve or map first, without the constraint; then filter |15| "What is a bento grid", "which purposes does a pricing page hold" | `python3 tools/space.py search` / `show`, or `view/index.html`; answer without a result |16| Choose a layout, write the page, its headings or copy, design or build it | Deliver the possibilities; the answer names the person using the result, a copywriter or a designer for the choice and the wording |17| One bounded account dashboard, including its settings and views | Resolve or map the page; exhibit named view routes and their obligations without claiming executable view or state behavior |1# PROFILE: webpage-atlas23## Identity45| Field | Value |6| --- | --- |7| Id | `webpage-atlas` |8| Name | Webpage Atlas |9| Type | declarative |1011## Responsibility, purpose1213**Page requirement or existing page × the Webpage Atlas space → possibilities: the section purposes the page holds for its reader, every layout that can carry each purpose with its fit from the material that exists and its empty slots, every permitted link between sections, and example skeletons checked link by link. It chooses none.**1415Given a page requirement and its context, show every construction the Webpage Atlas space holds for it, checked against the space's rules and connected to what can follow it. Choose none. AI reads the requirement into space values, observes the material that exists, places the sections of an existing page and composes example skeletons; programs derive which purposes the page holds or needs, which layouts carry each purpose, each construction's fit, every permitted link, every check on a skeleton or placement, and apply filters exactly.1617The result serves whoever plans, writes, designs or builds a marketing, content, utility or dashboard page: a founder who asks what a pricing page needs, a designer who wants every layout a proof section can take with the material at hand, a builder checking an existing page or a bounded account dashboard. It shows the skeleton of the page, the layouts open to each section, what each layout's slots hold and which material would open more. The space is one page: the whole is the page; an action that leaves it is recorded by its intent. A dashboard can include account settings and named views; its example routes describe section order, not an executable application.181---2name: resolve-page-possibilities3description: Show everything the Webpage Atlas space holds for a page that is not built yet, with or without copy already written - the section purposes the page holds or its reader and offer need, every layout that can carry each purpose with its fit from the material that exists and its empty slots, every permitted link between sections, and example skeletons checked link by link. Chooses nothing. Use when someone asks what sections a page needs, which layouts fit, or what a page could look like, including when they already have copy for it.4---56# Resolve page possibilities78Page requirement × the space → possibilities: `possibilities.json` (canonical), `possibilities.md` and `possibilities.html` in `artifacts/<name>/`, under [contracts/possibilities.md](../../../contracts/possibilities.md). Run from the atlas root (the folder holding `PROFILE.md`).910## Inputs1112The requester's words: what the page is for, who arrives and what they know, what is offered, what material exists (images, numbers, quotes, demos, steps, terms), and any copy already written for the page. Nothing else is required; what the words leave open stays open.1# Possibilities23The result of an atlas request: everything the atlas's space holds for one requirement, checked and connected, with nothing chosen. A person reads it to see the options before deciding; a producer reads it as the input to its own choice.45## Files67A request writes one folder: the destination the request names, otherwise `atlases/{atlas}/artifacts/{request-id}/`.89| File | Holds | Written by |10| --- | --- | --- |11| `request.json` | The interpreted request: requirement in the requester's words, anchors, existing material, the filter criterion when there is one | the atlas's skill |12| `possibilities.json` | The result. Canonical: consumers read it by field name | program, with the atlas's judgments recorded in it |13| `possibilities.html` | Fully contained reader: page orders, section/layout possibilities, material conditions, findings and embedded native data | product-local renderer |14| `possibilities.md` | The same result for people, rendered from `possibilities.json` | renderer |1516A filter writes a new folder whose `request.json` cites the result it narrowed. A result is never edited after it is written; a changed request makes a new result.17| Skill | Transformation |
|---|---|
filter-possibilities | Possibilities × criterion → narrower possibilities |
map-existing-page | Existing page × the space → placements, coverage and possibilities |
resolve-page-possibilities | Page requirement × the space → possibilities |
Example
The LeanOS Content Atlas page, resolved with Webpage Atlas.
Show me the possibilities for the Content Atlas product page at leanos.tech/atlas/content/. Visitors are business owners and practitioners looking for meaningful choices for their content; they know the problem and are judging this way of solving it. The atlas is free under MIT, and the main action opens the public repository. We have the copy, a real coverage map and the public docs on GitHub.Possibilities
artifacts/leanos-content-atlas/possibilities.json
- AnchorsProduct page · Problem recognised · Low consideration · Free download
- Purposes22Orientation · Customer testimony · Problem · Solution introduction · Approach contrast
- Patterns34Split with overlapping image · Split with bento grid · Centered heading with image row
- Constructions11058 fit · 52 conditional
- Routes3Orientation → Problem → Approach contrast → Solution introduction → Mechanism → Capabilities → Product view → Outcomes → Inclusions → Requirements → Terms → Call to action → After the action → Support → Further reading
| What you get | You’ll need |
|---|---|
| 70 section types, each with the question it answers for your reader. | A GitHub account |
| 41 layouts, each listing the material it needs from you. | An agent that reads skills, such as Claude Code or Codex |
| Order rules, with a program that checks each order. | Python 3.10 or later, Git and Make |
| 3 skills: plan a page, map a live page, narrow a result. |
One page at a time. It writes no copy and builds nothing; you take your choices to your writer, designer or AI.
Get it
Opening Stripe…
We couldn’t open Stripe. Try again, or contact Support.
This product isn’t available to buy. See Available or contact Support.
The offer has changed. Review the current price and terms before continuing.
We can’t confirm your payment yet. Check your receipt or contact Support before paying again.
Payment cancelled. You’re back at Webpage Atlas.
Payment didn’t go through. Check your details and try again.
- Licence
- $19 USD once for one person, on your ventures and client work. Share your results, not the repository or model. Each further person needs a licence.
- Access
- After payment, a private GitHub invitation to the username you enter in Stripe.
- Payment
- Pay through Stripe. Enter your email and GitHub username there.
- Updates
- Updates while maintained; received versions stay usable. A successor under a new name is a separate purchase.
- Refunds
- Digital purchases are non-refundable.
- Help
- Email bella@leanos.tech for help getting it working. Reply to your purchase email for access recovery.