# Anime.js mechanical animation engine

> An animation-library website with a neon circular instrument hero, a dark mechanical assembly, and pale technical-diagram views connecting labeled API modules to an exploded cylindrical object.

- Kind: Website
- Live website: https://animejs.com
- Page: https://meetreference.com/v/ref-anime-js-f7ae/
- Ready-to-use agent handoff: https://meetreference.com/v/ref-anime-js-f7ae/agent.txt
- Authorship: Not stated
- Made with: Not stated
- Model: not stated
- Built with: not stated
- Style: 3D sites; technical illustration, mechanical, dark interface, wireframe, neon accents, exploded view, instrumentation
- Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions.
- Shared by Julian Garnier in Website: https://www.awwwards.com/sites/anime-js
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this website

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Use a single detailed object as the organizing metaphor, presenting it first as a dramatic shaded form and then as a fine-line technical diagram. Connect peripheral monospaced labels to distinct components with thin, angled leader lines, while keeping the primary heading in a stable corner. For a new subject, replace the cylindrical mechanism and API labels with a subject-specific assembly and vocabulary; reserve clear space around the copy and strengthen annotation contrast.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the captured walkthrough frames, not by the creator.

Minimal, technical portfolio-style presentation with precise mechanical illustrations and restrained UI.

- Color: Charcoal and near-black sections contrast with pale warm-gray backgrounds, fine gray linework, white text, and small bright accent colors in the circular graphic and controls.
- Type: Clean sans-serif typography; bold, compact headings and small supporting labels and interface text.
- Framing: A dark introductory panel pairs text at the left with a large circular graphic; adjacent dark panels center a dark, detailed mechanical illustration. Lighter panels place a heading and short paragraph near the upper left, with large technical drawings occupying the remaining space.
- Structure: A compact navigation bar sits above the dark hero area. Below it is a grid of light panels featuring variations in the mechanical line drawing, small annotation-like text, and dark rounded control strips near the lower edge.

Storyboard, nine frames spread across the captured walkthrough: https://meetreference.com/media/ref-anime-js-f7ae/storyboard.webp

- Frame 1 at 1.0s: https://meetreference.com/media/ref-anime-js-f7ae/f1.webp
- Frame 2 at 2.9s: https://meetreference.com/media/ref-anime-js-f7ae/f2.webp
- Frame 3 at 4.9s: https://meetreference.com/media/ref-anime-js-f7ae/f3.webp
- Frame 4 at 6.8s: https://meetreference.com/media/ref-anime-js-f7ae/f4.webp
- Frame 5 at 8.7s: https://meetreference.com/media/ref-anime-js-f7ae/f5.webp
- Frame 6 at 10.7s: https://meetreference.com/media/ref-anime-js-f7ae/f6.webp
- Frame 7 at 12.6s: https://meetreference.com/media/ref-anime-js-f7ae/f7.webp
- Frame 8 at 14.6s: https://meetreference.com/media/ref-anime-js-f7ae/f8.webp
- Frame 9 at 16.5s: https://meetreference.com/media/ref-anime-js-f7ae/f9.webp

## Links

- Visit site: https://animejs.com
- Original post: https://www.awwwards.com/sites/anime-js
- Source and design credit: https://www.awwwards.com/sites/anime-js