auteur

Install

npx skillfoxx add skills/auteur

npx skills add agiwhitelist/auteur --skill auteur -a claude-code -y

npx skills add agiwhitelist/auteur --skill auteur -a cursor -y

npx skills add agiwhitelist/auteur --skill auteur -a github-copilot -y

npx skills add agiwhitelist/auteur --skill auteur -a codex -y

npx skills add agiwhitelist/auteur --skill auteur -a gemini-cli -y

npx skills add agiwhitelist/auteur --skill auteur -a cline -y

npx skills add agiwhitelist/auteur --skill auteur -a roo -y

npx skills add agiwhitelist/auteur --skill auteur -a opencode -y

npx skills add agiwhitelist/auteur

This is third-party code. Review the repository files before installing.

What it does

The skill walks the agent through a web build the way a director makes a film: art direction is committed in writing first, then assets, then markup, then the cut. It has three registers: build for an excellent conventional site, direct for a cinematic scroll-directed site, and system for a multi-screen product in one design system. It generates and sources assets with local CLIs, including images, video frames, depth maps and 3D, recording licenses. Nothing ships until the build passes the executable slopscan anti-slop linter, the motionqa animation check and the systemscan cross-route check. A reference recon phase reads external pages; it can be skipped to work offline.

Who it is for. For developers and designers who need a landing page, promo or multi-screen product that does not look templated.

Example request

Build me a cinematic landing page with scroll animation for our product using auteur.

Limitations

The skill installs without keys or a build step, but some phases depend on external tools. Asset generation relies on local CLIs for images, video and 3D that may not be present. The reference recon phase reaches external sites, so it must be skipped without access to them. The slopscan, motionqa and systemscan checks require Node and Playwright.

How to disable. Remove the auteur folder from the agent's skills directory, for example from ~/.claude/skills/. If installed as a Claude Code plugin, remove it with /plugin.

Security check

• Runs local build and check scripts: Node, Playwright, ffmpeg
• The reference recon phase makes outbound requests to external sites

README in short

The README presents auteur as an Agent Skill: a SKILL.md, reference recipes and a few runnable scripts, about 1MB, with no dependencies or keys. The skill builds sites the film way: art direction is committed before markup, assets come from local CLIs, and every build passes an executable anti-slop linter and a motion check. It installs with one npx skills add command, as a Claude Code plugin, via OpenClaw or by cloning into the skills directory. The gallery shows ten live sites built by the skill, each passing its own linter with no errors. MIT licensed.

SKILL.md

---
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.

Related