Skip to content
Back to skills

Ztx3 Cinematic Motion Audio Reactive

ASecurity

Cinematic Animation Engine focused task: audio reactive. Use when the requested frontend feature or review involves audio reactive.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
developmentreactapifrontend

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztx3-cinematic-motion-audio-reactive --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztx3 Cinematic Motion Audio Reactive?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ztx3 Cinematic Motion Audio Reactive
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztx3-cinematic-motion-audio-reactive/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztx3-cinematic-motion-audio-reactive)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ztx3-cinematic-motion-audio-reactive
description: "Cinematic Animation Engine focused task: audio reactive. Use when the requested frontend feature or review involves audio reactive."
---

# Audio Reactive

## Why and when

Extract FFT bands and smooth values; require opt-in for microphone/audio. Work under the project's actual framework and browser constraints; do not assert this is implemented merely because a recipe exists.

## Implementation procedure

1. Inspect the current component and data flow; record constraints, user journey and existing integration.
2. Describe the mechanism: Extract FFT bands and smooth values; require opt-in for microphone/audio. Choose the smallest API with well-defined ownership.
3. Create real code and testable state transitions; document dependencies, cleanup and errors.
4. Handle mobile and container width changes, reduced motion, RTL/LTR and keyboard where applicable.
5. Record a runnable example or a reproducible browser test in the target project.

## Specific pitfalls

No autoplay audio without user activation. Version-pin relevant APIs and do not silently override old behavior.

## Parent engine acceptance protocol

Define a single progress clock and ownership map; implement intro, sustain, exit and reversible seek; provide disabled-motion final state.

Seek normalized timeline at 0, 0.25, 0.5, 0.75, 1 and backward; assert no duplicate raf loops.

## Definition of done

- [ ] Mechanism present in production code and demonstrable.
- [ ] Test at real narrow viewport and at least one wide viewport.
- [ ] No inaccessible keyboard/pointer-only workflows.
- [ ] Reduced-motion/static fallback as relevant.
- [ ] Source/license provenance included for reused upstream code.
- [ ] Error/empty/unsupported state is visible and usable.
- [ ] Report tests actually run and any unverified claim.

See `$ztx3-cinematic-motion` for full handbook; do not use MCP.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.