waapi

Create deterministic DOM animations using native WAAPI within HyperFrames playback contexts.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/automatedigital/spark --skill waapi-automatedigital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: waapi
Source: https://github.com/automatedigital/spark/tree/main/skills/creative/waapi
Command: npx skills add https://github.com/automatedigital/spark --skill waapi-automatedigital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need for external animation libraries like GSAP when building DOM motion for HyperFrames, ensuring animations render deterministically and synchronize perfectly with HyperFrames' playback timing without unnecessary dependencies.

Core Features & Use Cases

  • Native WAAPI Integration: Use standard element.animate() with keyframes, easing, and timing options directly in HyperFrames compositions.
  • Deterministic Playback Control: Adapter-managed currentTime seeking ensures animations stay in sync with HyperFrames' timeline, with fill: "both" preserving seeked states.
  • Common Use Cases: Lightweight DOM motion, data-driven generated animations, and simple keyframe timelines where CSS keyframes are too rigid and GSAP is unnecessary.

Quick Start

Use the waapi skill to create a paused orb animation with 3 second duration, 2 second delay, and fill mode "both" for a HyperFrames clip using element.animate().

Frequently Asked Questions about waapi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create native DOM animations in HyperFrames without external libraries?

To create native DOM animations in HyperFrames without external libraries, use the standard WAAPI element.animate() method with keyframes. This approach ensures deterministic rendering and timeline synchronization without GSAP dependencies.

Why do my Web Animations API keyframes fall out of sync during timeline seeking?

Web Animations API keyframes fall out of sync during seeking if animation states are not paused or lack fill mode both. The WAAPI adapter requires finite duration and paused states to manage currentTime seeking for deterministic HyperFrames playback.

Can I use element.animate() with HyperFrames playback contexts?

Yes, you can use element.animate() within HyperFrames playback contexts by adhering to WAAPI adapter contracts. Animations require finite duration, finite iterations, fill mode both, and a paused state to synchronize with the timeline.

Do I need GSAP for simple keyframe timeline generation?

You do not need GSAP for simple keyframe timeline generation. Native WAAPI integration supports standard element.animate() with keyframes and easing, providing a lightweight alternative for DOM motion where CSS keyframes are too rigid.

What are the limitations of using WAAPI for HyperFrames DOM motion?

Limitations of using WAAPI for HyperFrames DOM motion include strict adapter contract requirements. Animations must have finite durations, use fill mode both, and remain paused, meaning infinite iterations or non-paused states will break deterministic timeline synchronization.