← ClaudeAtlas

cinematic-web-directorlisted

Design, build, critique, or polish cinematic websites with a product-specific visual world, semantic tokens, purposeful motion, responsive behavior, and real browser verification. Use for landing pages, product stories, resource libraries, galleries, decks, scroll scenes, video scrub pages, Spline pages, and other frontend work that must feel authored rather than generated.
wrg32786/aigent-design-system · ★ 4 · Web & Frontend · score 77
Install: claude install-skill wrg32786/aigent-design-system
# Cinematic Web Director Build a distinct page, not a reskinned template. ## 1. Load the truth Before editing: 1. Read `PRODUCT.md` and `DESIGN.md` when present. 2. Inspect the target page end to end. 3. Inspect one representative source of visual authority: a live page, token file, shared component, stylesheet, or approved asset. 4. Trace existing motion and media behavior before replacing it. A missing `DESIGN.md` does not make an established product greenfield. Preserve a coherent identity already present in production unless the user asked for a redesign. ## 2. Name the surface mode Choose the mode from this surface: - **Persuade** — the visitor decides and acts. - **Operate** — the visitor completes a task. - **Read** — the visitor understands material. - **Experience** — the visitor enters the work itself. Write the mode down before choosing the composition. A tool's landing page is Persuade; its dashboard is Operate; its guide is Read. ## 3. Set the direction Resolve the smallest useful brief: - user and desired outcome - primary action - real proof or assets - concrete visual world - category default to avoid - anti-references - color strategy - type character - material and composition - one signature interaction Do not ask for arbitrary CSS values. Ask what would change the direction. When the project has no context files, create the compact versions from `docs/project-context.md` if the task includes establishing or replacing the visual system. A narr