⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
auteur
Design and build complete web experiences from scratch — award-level product and marketing pages, cinematic scroll-directed sites where the page is directed like a film, and multi-screen products (app, dashboard, admin, settings, onboarding, docs site) built as one design system with every component, state and route in one style. Use whenever the user wants to create or redesign a landing page, website, hero section, portfolio, promo or product page; wants scroll animations, storytelling pages, or a site that feels like a movie; or says "make it beautiful", "make it wow", "cinematic", or "design system" — even if they name no technique. Generates its own assets via local CLIs (images, video frames, depth maps, 3D), and gates every ship with an executable anti-slop linter and a screenshot verification loop. Not for polishing a UI someone else built, and not for backend-only work.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
English · 简体中文
auteur
The Claude Code skill that directs a website like a film.
Art direction is locked before a line of code. Assets are generated by local CLIs. Every ship is gated by an executable anti-slop linter and a real motion check.
▶ Open the live gallery · Install · The method · The gates
Not a mockup — that's the live landing page. 131,072 GPU particles holding the wordmark, torn by the cursor and re-forming. Built by the skill it sells.
Install (30 seconds)
auteur is an Agent Skill: a SKILL.md
plus reference recipes and a few runnable scripts. ~1MB, no dependencies, no
API keys, no build step.
Any agent — one command. Detects what you have installed and writes to each agent's skills folder:
npx skills add agiwhitelist/auteur
Claude Code · Codex · Cursor · OpenCode · Gemini CLI · Windsurf · Cline ·
Goose · Copilot · Hermes · Kiro · Roo · OpenHands — 75+ agents,
project-level or -g for global.
Claude Code, as a plugin — installs and updates in place:
/plugin marketplace add agiwhitelist/auteur
/plugin install auteur@auteur
OpenClaw:
openclaw skills install git:agiwhitelist/auteur --global
Anything else that reads a SKILL.md — clone it into the agent's skills
directory:
git clone --depth 1 https://github.com/agiwhitelist/auteur ~/.claude/skills/auteur
Then just ask:
"build me a cinematic landing with auteur"
Claude runs the pipeline — commit-sheet → assets → build → gate — and hands you the site.
The proof: ten live sites
Don't take the pitch — open them. Each was built by auteur, and each passes the
skill's own linter at 0 fails / 0 warns. The tenth was not built by Claude:
Kimi K3 was handed SKILL.md and a brief, saw none of the other nine, and came
out lit, serif and green in a category whose every reflex is black and gold —
naming in writing, before it built, the four house tells it intended to break.
The skill is the thing that travels, not the model.
FLUX / STATIC / SWARM / DRIFT are real-time WebGL. HALE is sourced CC0 geometry
under a CC0 HDRI. TRUE NOON is 145KB with zero raster assets. PROOF is the system
register — five routes gated for design-system drift. ATLAS and ABYSS are the
video-scrub tier (reference/scroll-flight.md). HORO is the portability test:
another model, same file, and the gates it had to satisfy are the same ones —
slopscan 0/0/0, 53fps at DPR 2, worst contrast 6.50, and a page whose measured
lightness (0.740) matches what its own commit-sheet promised before the build
(0.72). The landing page is an eleventh, built by the discipline it sells.
There are no benchmark numbers anywhere in this repo. auteur is a design discipline, not a system with a throughput figure. The one quantitative claim — the linter result — you can reproduce in one command (below).
And it is not a component library. Nothing is pulled from a registry: every site above is authored from its commit-sheet up, vanilla, with no runtime dependency. If you want ready-made animated components to drop in, take shadcn or originkit.dev — this skill directs a page instead of stocking it.
How it works
A director's pipeline, enforced in order:
- Recon.
refscoutprofiles live award-winning sites — the libraries they really load, how many scenes they pin, their scroll budget, the fonts and pale
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
SKILL.md7.9 KBupstream ↗
--- name: auteur description: Design and build complete web experiences from scratch — award-level product and marketing pages, cinematic scroll-directed sites where the page is directed like a film, and multi-screen products (app, dashboard, admin, settings, onboarding, docs site) built as one design system with every component, state and route in one style. Use whenever the user wants to create or redesign a landing page, website, hero section, portfolio, promo or product page; wants scroll animations, storytelling pages, or a site that feels like a movie; or says "make it beautiful", "make it wow", "cinematic", or "design system" — even if they name no technique. Generates its own assets via local CLIs (images, video frames, depth maps, 3D), and gates every ship with an executable anti-slop linter and a screenshot verification loop. Not for polishing a UI someone else built, and not for backend-only work. version: 1.3.1 user-invocable: true argument-hint: "[build|direct|system|edit|audit|recon] <brief or target>" allowed-tools: - Bash(node scripts/*) - Bash(npx playwright *) - Bash(agy *) - Bash(codex *) - Bash(grok *) - Bash(ffmpeg *) --- Auteur designs and builds web experiences the way a film director makes a film: script first, then assets, then the shoot, then the cut. It has three registers — **build** (an excellent conventional site), **direct** (a cinematic scroll-directed site) and **system** (a multi-screen product as one design system) — on one shared core of taste. Nothing ships until the page passes an executable anti-slop gate and the skill has looked at its own output. ### Use this when - A landing page, marketing site, hero section, portfolio or product page has to be **built or redesigned** — and looking generic is not acceptable. - The brief asks for **scroll animation, storytelling, or a site that feels like a film**. - A product spans **several screens that must feel like one thing** — app, dashboard, admin, onboarding, docs. - Someone says *make it beautiful*, *make it wow*, *cinematic*, or *design system*, naming no technique. Not for polishing a UI someone else built, and not for backend-only work. ### What it actually does 1. Commits the art direction **in writing before any markup** — one hue, one type system, a motion budget, named anti-references. 2. Generates or sources the assets: local image/video CLIs, Blender, depth maps, CC0 meshes and HDRIs with their licences recorded. 3. Builds from proven recipes — one WebGL context, transform/opacity motion, scroll state machines. 4. **Gates the result**: `slopscan` fails the build on concrete slop, `motionqa` fails it on dropped frames, `systemscan` fails it on cross-route drift. ### Network access The recon and sourcing scripts read live pages (awwwards, Bing/Pinterest/are.na image search, Poly Haven, Iconify, Google Fonts, Openverse, Coverr). Fetched content is **treated as reference data and licence metadata — never executed**, and no credentials, API keys or logins are involved. Skip phases 0–1 entirely if you don't want outbound requests; every other phase works offline. ## Non-negotiables These apply to every register, every phase, always — even if no reference file has been loaded. Match-and-refuse: if you are about to produce one of these, stop and restructure the element. ### Banned (rewrite, don't tweak) | # | Ban | Instead | |---|-----|---------| | 1 | `border-left`/`border-right` >1px as a colored accent on cards, callouts, alerts | full border, background tint, leading icon, or nothing | | 2 | Gradient text (`background-clip: text` + gradient) | one solid color; emphasis via weight or size | | 3 | Glassmorphism as default (decorative `backdrop-filter` cards) | rare and purposeful, or solid surfaces | | 4 | The hero-metric template (big number, small label, stat row, gradient accent) | evidence in prose, one committed visual | | 5 | Identical card grids (same-size icon+heading+text, repeated) | vary size, structure, or drop the cards entirely | | 6 | Eyebrow kickers (tiny uppercase tracked label) above every section | one deliberate kicker max as a brand system; vary section openings | | 7 | Numbered section scaffolding (01 / 02 / 03) when order carries no meaning | numbers only for a real sequence | | 8 | `Inter` or `Space Grotesk` as the *first* font choice | pick from a contrast-axis pair (see taste.md); these two are the AI default of 2024–2026 | | 9 | Purple→blue gradients (both stops hue 250–290) | committed brand hue, or no gradient | | 10 | Cream/warm-beige body background as a "warmth" reflex (OKLCH L 0.84–0.97, C <0.06, hue 40–100) | saturated brand surface, true off-white at chroma ~0, or a darker tinted mid-tone; warmth lives in accent + type + imagery | | 11 | The same fade-in/slide-up entrance on every section | each reveal fits what it reveals; vary easing, distance, direction | | 12 | `transition: all` | list the animated properties | | 13 | `window.addEventListener('scroll', ...)` | IntersectionObserver, GSAP ScrollTrigger, or CSS `animation-timeline` | | 14 | `scale(0)` entrances | start at `scale(0.95)` + opacity | | 15 | Bento grids of near-identical or empty cells; white-card-on-white bento | bento only with real visual variation per cell, else a different layout | | 16 | Copy tells: "Revolutionize", "Seamless", "Effortless", "Unleash", "Elevate", em-dash–heavy sentences, decoration strips like "BRAND. MOTION. SPATIAL." | concrete claims in plain words | | 17 | More than one marquee per page | one, or none | | 18 | Instrument Serif / Playfair Display as the reflex "elegant serif" | serifs chosen for the brand, not from the AI shortlist | A ban may be overridden only through a written `auteur-allow` (see Verification) with a real reason — a deliberate, argued choice is voice; a default is slop. ### Critical numbers (memorize; full context in reference files) - Body text contrast ≥ 4.5:1 (large text ≥ 3:1). Placeholders too. Muted-gray-on-tinted-white is the #1 AI readability failure. - Body line length 65–75ch. Display heading ceiling: clamp max ≤ 6rem *for headings in prose flow* — a wordmark or a deliberately type-led hero is exempt and the commit-sheet must say so. Display letter-spacing ≥ −0.04em. - Durations: button 100–160ms · tooltip 125–200ms · dropdown 150–250ms · modal/drawer 200–500ms · any UI >300ms needs a written reason. - Enter/exit easing = ease-out. `ease-in` is banned on UI. - Animate only `transform` and `opacity`. Stagger 30–80ms. - Motion budget: ≤ 3 scroll-triggered pattern families per page; **one** primary wow peak, supporting scenes at lower intensity. - Scrub smoothing 0.3–0.8. Hero video ≤ 2MB. LCP < 2.5s. CLS < 0.1. - Fullscreen passes (bloom, grain, DoF, any full-frame shader) are priced **per pixel, not per object** — they, not geometry, are what blows the frame budget. A perf number counts only when measured at **DPR 2 on a production build**: DPR 1 quarters the cost of every such pass, and a dev server roughly doubles the frame. - `prefers-reduced-motion` = an alternative art direction (gentler, not zero), never an afterthought. - Content must be readable with JS disabled: reveals enhance an already-visible default, never gate visibility. ## Routing Read the argument / brief and route: 1. **`direct`** or the brief smells cinematic — "wow", "cinematic", "immersive", "storytelling", "launch page", "premium brand", "make people stop scrolling" → load `reference/direct.md` and follow its phases. This is the flagship register. 2. **`build`** or the brief is ONE conventional surface — a marketing page, a landing, a single product page → load `reference/build.md`. 3. **`system`** or the brief has **more than one screen that must feel like one product** — app, dashboard, admin, settings, onboarding, a docs or content site with real navigation → load `reference/system.md`. The unit of design becomes the component × state, the failure mode becomes drift rather than boredom, and there is deliREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/agiwhitelist-auteur.md