creative-web-pages
/creative-web-pages
Planuje długie strony produktowe: 13 typów stron, 25 układów sekcji i listę treści opartą na faktach, bez zmyślonych liczb.
- Autor
- AfkanOzdemir ↗
- Repozytorium
- creative-web-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Planuje długie strony produktowe: 13 typów stron, 25 układów sekcji i listę treści opartą na faktach, bez zmyślonych liczb.
Oryginalny opis (EN)
Plans long, content-rich product pages — 13 page archetypes (landing, features, how-it-works, privacy, security, pricing without invented numbers, FAQ, changelog, manifesto, auth split-screen, docs index, 404, contact), 25 section layouts, rhythm rules and a facts-only content checklist. Use when the user wants a new marketing page, a longer page with more content, a page outline, or says every page has the same structure. Do NOT use for visual tokens (use creative-web-worlds) or for writing individual animations (use creative-web-motion).
Jak działa
- Critical
- Rhythm rules
- Length
- Facts-only content checklist
- Workflow
- Index
- Examples
- Troubleshooting
Podgląd SKILL.md
---
name: creative-web-pages
description: Plans long, content-rich product pages — 13 page archetypes (landing, features, how-it-works, privacy, security, pricing without invented numbers, FAQ, changelog, manifesto, auth split-screen, docs index, 404, contact), 25 section layouts, rhythm rules and a facts-only content checklist. Use when the user wants a new marketing page, a longer page with more content, a page outline, or says every page has the same structure. Do NOT use for visual tokens (use creative-web-worlds) or for writing individual animations (use creative-web-motion).
license: MIT
compatibility: Works in Claude Code, Codex, Cursor, OpenCode and claude.ai. Section skeletons assume React or Next.js with Tailwind CSS v4.
metadata:
author: afkanozdemir
version: 1.0.1
suite: creative-web
tags: [frontend, design, motion]
---
# Page blueprints
A long page is not many sections — it is **one argument told in beats**. Each section makes exactly
one point, and the sequence alternates *showing* (a scene or widget) with *saying* (a statement).
## Critical
- Cut any section you cannot fill with true content; never pad with invented claims.
- One idea per section; never two pinned sections back-to-back; at most 2–3 pins per page.
- Each page gets its own visual metaphor — do not reuse another page's hero scene.
- The draw from `creative-web/scripts/deal.mjs draw` names the sections and two reflexes to leave out; start from it.
## Rhythm rules
1. **One idea per section.** Section title = the idea in ≤ 6 words ("Forget means forgotten.", "Only the sources it used.").
2. **Alternate surfaces** the way the dealt world allows (its `## Surfaces` section): bg ↔ bg-2,
or dark ↔ light bands where the world has both. Never two pinned sections back-to-back.
3. **Pinned showpieces: max 2–3 per page**, desktop only. Pins are expensive attention; spend them on
the hero and the one or two moments that *are* the product.
4. **Vary section layouts.** No layout more than twice in a row. Rotate: split ↔ full-bleed ↔ grid ↔
track ↔ statement.
5. **Index labels** (`01 / 09`) only when the page is an inventory (features, principles), set in the
world's label face, untracked, sentence case. Otherwise no label above a section title.
6. **Vary 3D/scene metaphors.** If one page uses a particle cloud, the next uses cards, type, lines or
a lattice. The scene should *be* the section's metaphor (a question falling into an archive; a record
dissolving when forgotten), not ambient stars.
7. **Finale + CTA.** End with a statement or marquee, then the ask (CTA band or ask pill).
## Length
| Page | Desktop screens | Sections |
|---|---|---|
| Landing | 14–20 | 9–13 |
| Features / Privacy / Security | 14–20 | 10–13 |
| How it works | 8–12 | 5–7 |
| FAQ / Pricing / Contact | 4–8 | 3–6 |
Pinned sections count as `1 + pin length` screens (`end: '+=150%'` ≈ 2.5 screens).
## Facts-only content checklist
Source real copy from, in order: the product's own UI strings, settings labels, help/FAQ, legal
pages (privacy policy, terms), the PRODUCT/brief file, release notes, and the code (what the feature
actually does). Write it down in a facts file before designing.
Never invent:
- metrics, user/customer counts, uptime, speedups, benchmarks
- customer logos, testimonials, quotes, case studies
- prices or plan limits that aren't published
- certifications (SOC 2, ISO, GDPR "compliant") unless documented
- features that are "coming soon" presented as shipped
- vendor names for infrastructure the client hasn't disclosed
Sample content inside widgets (names, cities, headlines) is allowed when visibly labelled `Sample`.
## Workflow
1. Write the facts file (what is true, what is not offered).
2. Pick an archetype from `references/blueprints.md`; adjust section count to the facts you have —
**cut sections you can't fill truthfully**.
3. For each section choose a layout (`references/section-patterns.md`) and a widget
(`creative-web-widgets` skill) or scene (`creative-web-webgl` skill). Check rhythm rules 2–6.
4. Put all strings in i18n messages. Build. Screenshot every section at 1440×900 and 390×844.
5. Run axe with motion on and with `prefers-reduced-motion: reduce`.
## Index
- [references/blueprints.md](references/blueprints.md) — 13 page archetypes with section lists
- [references/section-patterns.md](references/section-patterns.md) — 25 section layouts
## Examples
**User says:** "Make the features page bigger and longer, with more widgets."
**Actions:** facts file → features archetype → hero scene + index grid + numbered scenes alternating light/dark + finale → widget per capability → QA.
**Result:** a 15–20 screen page where each section proves one capability.
**User says:** "We need a privacy page people actually read."
**Actions:** privacy archetype → principles track, keep/drop columns, data-flow diagram, sensitive-data locks, forget scene, sessions, export/delete timeline, FAQ — only facts from the product's settings and legal text.
**Result:** a trust page built entirely from verifiable behaviour.
## Troubleshooting
**Error:** the page feels repetitive.
**Cause:** the same layout three times in a row. **Solution:** rotate split → full-bleed → grid → track → statement.
**Error:** not enough facts to fill the archetype.
**Cause:** the product doesn't have those capabilities. **Solution:** remove sections; a shorter honest page beats a padded one.
Pliki w paczce (3)
- SKILL.md 5 KB
- references/blueprints.md 6 KB
- references/section-patterns.md 7 KB
Wersje
W bazie nie ma innych skilli o nazwie creative-web-pages.
Migawka bazy z 13.11.2026 · wersja paczki 0373609cfff0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100content-brief
Buduje brief nowej strony na podstawie zapytań z Search Console i cytowalności konkurencji, z planem treści i pomiarem, bez zmyślonych liczb wyszukań. - 90saas-landing-pages
Tworzy kompletne szkice stron docelowych SaaS na siedmiu szablonach: strony główne, produktowe, cenowe, porównawcze i integracji. - 100writing-landing-page-copy
Pisze teksty na landing page w ustrukturyzowanym wywiadzie i sekcja po sekcji, nastawione na konwersję. - 100landing-page
Pisze teksty landing page sekcja po sekcji, od hero po końcowe wezwanie do działania, z FAQ i metadanymi SEO. - 100seo-content-brief
Generuje briefy treści SEO oparte na konkurencji, z liczbą słów dla sekcji, oceną konkurentów, wskazówkami gęstości słów kluczowych i szablonami typów stron, dla nowych i istniejących stron. - 90pb-landing-page
Buduje i uruchamia landing page: potwierdzone teksty bez zmyślonych twierdzeń, strona w tokenach marki, przegląd UI i SEO, wdrożenie po GO oraz kontrola na żywym adresie.