creative-landing-pageslisted

# Creative Landing Pages Create an authored experience around one clear idea. Preserve the existing stack unless the brief justifies change. Treat motion and 3D as optional delivery mechanisms, not quality by themselves. ## Read the right references - Read [concept-and-art-direction.md](references/concept-and-art-direction.md) before proposing a visual direction or changing a design. - Read [stack-and-motion.md](references/stack-and-motion.md) before adding a dependency, animation system, smooth scrolling, canvas, WebGL, or 3D. - Read [quality-gates.md](references/quality-gates.md) before implementation and again during review. - Read [asset-rights.md](references/asset-rights.md) when sourcing, generating, licensing, or transforming fonts, images, video, audio, models, or code examples. - Read [sources.md](references/sources.md) only when checking provenance or whether a named tool is still suitable. ## Operating workflow ### 1. Ground the brief Inspect the project, content, assets, and existing conventions. Write a compact brief containing: - audience, desired action, and proof needed; - content hierarchy and mandatory sections; - available assets versus missing assets; - device, accessibility, performance, delivery, and maintenance constraints; - implementation stack and what may not change; - observable done criteria. Ask at most one question only when a missing answer changes the product materially. Otherwise state assumptions and proceed. ### 2. Form the concept