Skip to content
Back to skills

Ztc Product Storytelling Image Sequence Vs Video

ASecurity

Focused implementation and verification of image sequence vs video in Apple-Style Product Storytelling.

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

Works with

  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztc-product-storytelling-image-sequence-vs-video --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztc Product Storytelling Image Sequence Vs Video?

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

Security grade badge for Ztc Product Storytelling Image Sequence Vs Video
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztc-product-storytelling-image-sequence-vs-video/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztc-product-storytelling-image-sequence-vs-video)

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: ztc-product-storytelling-image-sequence-vs-video
description: "Focused implementation and verification of image sequence vs video in Apple-Style Product Storytelling."
---
# Image Sequence Vs Video

Parent: `ztc-product-storytelling` — read its acceptance gate and `../../src/product-story.mjs` before editing.

## Required implementation
Choose AVIF/WebP frames, video seek or GLB camera animation based on file budget, responsiveness, alpha support and decoded memory.

### 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:** 120-frame storyboard maps exact first/mid/last frames, supports reverse scroll, bounds cache, renders a static poster on 404.
- **Limitations:** The package contains a procedural frame demo, not licensed Apple product assets or a finished 120-frame photo sequence.
- **Evidence:** file paths, screenshot artifact paths, browser/driver, commands, actual test results, and unresolved TODOs.

## References
- https://gsap.com/docs/v3/Plugins/ScrollTrigger/
- https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/decode

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.