← ClaudeAtlas

page-builderlisted

Plan the structure, section order, and conversion architecture of a web page or site before any visual design happens. Use when the user asks to "build a landing page", "what sections should this page have", "structure a homepage", "plan a marketing site", "lay out a product page", or when starting any new page and the information architecture is not yet decided ("תבנה דף נחיתה", "מה צריך להיות בדף"). Produces a section-by-section blueprint, hero pattern, trust-signal placement, and CTA hierarchy — category-aware and i18n/RTL-aware. Pairs with the frontend-design skill (which handles aesthetics) and web-design-guidelines (which audits the result). It decides structure and content architecture; it does NOT do the visual design (frontend-design) or the accessibility audit (web-design-guidelines).
yybd/app-factory · ★ 5 · Web & Frontend · score 77
Install: claude install-skill yybd/app-factory
# Page Builder This skill decides **what goes on the page and in what order** — the skeleton — before the `frontend-design` skill decides how it looks. Structure first, aesthetics second, audit last. Do not jump to writing markup. First produce a blueprint the user can react to, then build. **Before starting, read `PRODUCT.md`** (audience, voice, the single goal, and which proof the audience needs) — it is the contract this skill builds against. (`DESIGN.md` is read later, when handing off to `frontend-design`.) ## Prerequisites - **Tools:** none beyond Claude Code. - **Credentials:** none. - **Hub (`$APP_HUB`):** not used; reads the site repo's own `PRODUCT.md` (and `DESIGN.md` at hand-off). - **Other tracks:** `frontend-design` (design-track) takes the blueprint; `copy-edit` (shared-track) edits the claims the page carries; `content-site-structure` (web-track) scaffolds a multilingual content tree — on request only, and this skill never needs it to plan a page. ## When this skill runs - A new page or site is being created and the section structure is not yet agreed. - The user describes a goal ("get signups", "explain the rules", "sell the course") but not a layout. - An existing page converts poorly or feels unstructured and needs re-architecting. If the page structure is already fixed and the request is purely visual, skip to `frontend-design`. ## The blueprint process 1. **Identify the page archetype.** Landing page, homepage, product/marketing page, co