Installs into .claude/skills of the current project.
Are you the author of Ztc Creative Preloader Intro Choreography?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/realjustawall-ztc-creative-preloader-intro-choreography)
---
name: ztc-creative-preloader-intro-choreography
description: "Focused implementation and verification of intro choreography in Creative Preloader & Intro Engine."
---
# Intro Choreography
Parent: `ztc-creative-preloader` — read its acceptance gate and `../../src/preloader.mjs` before editing.
## Required implementation
Coordinate logo, type and scene handoff using a single controllable sequence; intro should not replay on every back nav.
### Exact workflow
1. Inspect current code ownership and versions; write down the affected components, selectors, assets and timeline owners.
2. Reproduce baseline at 320px/390px/768px/1440px, with pointer/touch, navigation, RTL if applicable, and reduced-motion.
3. Integrate the smallest change confined to this responsibility. Use typed/validated props and explicit lifecycle cleanup. Ensure failed assets, missing browser APIs and aborted interactions degrade gracefully.
4. Instrument observable state (progress, time, active selection, DOMRect, material parameters or frame index). Avoid non-deterministic quality claims.
5. Verify start, mid, end and reverse progress; resize after loading fonts/images; test one failure path and repeated navigation; inspect browser console and screenshots.
6. Compare user-facing behavior and performance to baseline. If a regression is observed, roll back just this change and record the cause.
## Contract
- **Input:** authenticated/validated application state, viewport, user preference, and dependencies explicitly available in target project.
- **Output:** meaningful accessible DOM and stable optional visual enhancement; no hidden input-only navigation.
- **Acceptance:** All-ready, required-failure, optional-failure, abort and reduced-motion paths are tested; no bogus percentage and no inaccessible overlay.
- **Limitations:** Readiness weight reports task completion only; it is NOT a byte-accurate network loading meter.
- **Evidence:** file paths, screenshot artifact paths, browser/driver, commands, actual test results, and unresolved TODOs.
## References
- https://developer.mozilla.org/en-US/docs/Web/API/Document/fonts
- https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion
