implementing staggered sequences in css

[ameerf-wix]

Description

Related Issue

Checklist

• I have read the Contributing Guide
• I have added/updated tests for my changes (if applicable)
• I have updated documentation/rules/skills (if applicable)

Screenshots / Demos

Additional Notes

[github-actions]

Generated llms.txt preview

llms.txt

# @wix/interact

> Declarative, configuration-driven interaction library — web-native, AI-ready, and framework-agnostic.

- Install: `npm install @wix/interact @wix/motion-presets`
- Three entry points: vanilla JS (`@wix/interact`), React (`@wix/interact/react`), Web Components (`@wix/interact/web`)
- Five trigger types: hover, click, viewEnter, viewProgress, pointerMove
- Effects via named presets (`@wix/motion-presets`), keyframes, CSS transitions, or custom JS callbacks
- Configs are JSON-serializable -- designed for LLM generation

## Docs

- [Full Reference](https://wix.github.io/interact/rules/full-lean.md): Declarative configuration-driven interaction library. Binds animations to triggers via JSON config. (779 lines)
- [Integration Guide](https://wix.github.io/interact/rules/integration.md): Rules for integrating `@wix/interact` into a webpage — binding animations and effects to user-driven triggers via declarative configuration. (364 lines)
- [Validation Guide](https://wix.github.io/interact/rules/validate.md): Rules for using `@wix/interact-validate` — validate an `InteractConfig` before it reaches the runtime. (315 lines)

## Optional

- [Click Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/click.md): This document contains rules for generating click-triggered interactions in `@wix/interact`. (197 lines)
- [Hover Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/hover.md): This document contains rules for generating hover-triggered interactions in `@wix/interact`. (199 lines)
- [PointerMove Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/pointermove.md): These rules help generate pointer-driven interactions using `@wix/interact`. (279 lines)
- [ViewEnter Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/viewenter.md): This document contains rules for generating interactions that respond to elements entering the viewport using the `@wix/interact`. (232 lines)
- [ViewProgress Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/viewprogress.md): These rules help generate scroll-driven interactions using `@wix/interact`. (233 lines)
- [@wix/interact Plugin Rules](https://wix.github.io/interact/rules/plugins.md): Rules for extending `@wix/interact` with external plugins via `Interact.use()` and `$`-prefixed config fields. (122 lines)
- [All rules in one file](https://wix.github.io/interact/llms-full.txt): Complete concatenation (2720 lines)

llms-full.txt header

# @wix/interact v2.5.6 -- AI Rules Reference
# https://wix.github.io/interact/llms.txt
# 9 files, 2720 lines

Download full files from workflow artifacts, or run node scripts/generate-llms.mjs locally.

[ydaniv]

Why do we have pointers to the code in the rules? All of these should just be removed

[ydaniv]

Is there a case where we still use generateId()?

[ydaniv]

Did we decide to stop supporting these? If so there is still a place where you check for typeof === 'function', so we need to remove that completely.

Also, what about customEffects? We probably still need JS support for these, right?