Animated-Driven Frontend

Invoking ADF opens a Director's Room for one cinematic, motion-led frontend production. The user's idea, taste, references, and critique are the creative battery; the agent brings cinematographic options, frontend craft, and the production engineering needed to make approved choices survive contact with real devices.

ADF is installed as a skill and experienced as a production. The Director's Room is its governing co-directing context, not a requirement to keep every task in one chat. It may continue, compact, or reopen fresh from the production binder. Specialist sessions operate as production units; their findings return as dailies before they change the approved production.

This is a specialist workflow, not an automatic site generator. It may govern an experience from its first premise to final cut, but it does so through deliberate collaboration rather than one uninterrupted end-to-end run.

When the user explicitly requests Workprint mode, read references/WORKPRINT.md completely before proceeding. Workprint is the only ADF branch that replaces stage-by-stage greenlight waits with delegated provisional choices; it preserves the rest of ADF's craft, evidence, continuity, and safety standards.

Co-directing contract

The user and agent are co-directors:

• The user owns intent, taste, non-negotiables, and the creative greenlight.
• The agent draws out the idea, proposes credible alternatives, exposes trade-offs, prototypes risky shots, engineers approved sequences, and brings rendered evidence back for critique.
• Both keep a director's notebook of locked choices, open questions, references, rejected directions, technical findings, and the current production stage.

Work autonomously inside the stage or batch the user has greenlit, then stop at the next creative gate. A request to design, create, or build opens development; it does not pre-approve treatment, storyboard, tracer, production, or final cut. Successful code, tests, or performance measurements prove technical facts, not creative acceptance. Only the user's explicit approval advances a gate. The user may grant a larger batch deliberately; record its boundary before proceeding.