transitions-dev
Jakubantalik/transitions-dev · Agent Skill
Modelli CSS di transizione pronti all'uso per applicazioni web, con frammenti di codice già pronti per card, finestre modali, menu a discesa, pannelli e transizioni tra pagine.
Vai all'installazione ↓Panoramica
| Autore | |
|---|---|
| Repository | Jakubantalik/transitions-dev ↗ |
| Cartella dello skill | transitions-dev |
| Stelle | 46 |
| Fork | 6 |
| File inclusi | 14 |
| Licenza | MIT |
| Aggiornato | 20 maggio 2026 |
| Link | Sorgente dello skill ↗ · Repository ↗ |
Verifica Mozgi
Cosa abbiamo trovato nei file dello skill. I dettagli con l’abbonamento.
Installazione
Uno skill è una cartella con un file SKILL.md. Scegli il tuo agente ed esegui i comandi in un terminale (macOS, Linux o Git Bash su Windows) dalla radice del progetto.
Incolla il prompt in Claude, Codex o un altro assistente: controllerà lo skill e lo installerà.
Install the “transitions-dev” skill from mozgi.io (https://mozgi.io/skills/jakubantalik-transitions-dev/) for me. 1. Download the archive: https://mozgi.io/skills/jakubantalik-transitions-dev/download If it fails, take the skill folder from the source: https://github.com/Jakubantalik/transitions-dev/tree/main/skills/transitions-dev 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “transitions-dev” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/transitions-dev/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/Jakubantalik/transitions-dev.git /tmp/transitions-dev mkdir -p .claude/skills cp -r /tmp/transitions-dev/skills/transitions-dev .claude/skills/transitions-dev
Riavvia Claude Code: lo skill compare nell'elenco; per richiamarlo a mano usa /transitions-dev. Per tutti i progetti: ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/Jakubantalik/transitions-dev.git /tmp/transitions-dev mkdir -p .agents/skills cp -r /tmp/transitions-dev/skills/transitions-dev .agents/skills/transitions-dev
Codex cerca gli skill in .agents/skills dalla cartella corrente fino alla radice del repo; richiamalo con /skills o $transitions-dev. Per tutti i progetti: ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/Jakubantalik/transitions-dev.git /tmp/transitions-dev mkdir -p .cursor/skills cp -r /tmp/transitions-dev/skills/transitions-dev .cursor/skills/transitions-dev
Cursor carica lo skill all'avvio; richiamalo con “/” nella chat Agent. Cursor legge anche .claude/skills e .agents/skills. Per tutti i progetti: ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/Jakubantalik/transitions-dev.git /tmp/transitions-dev mkdir -p .gemini/skills cp -r /tmp/transitions-dev/skills/transitions-dev .gemini/skills/transitions-dev
Gemini CLI propone di attivare lo skill quando il compito corrisponde: tu confermi. Per tutti i progetti: ~/.gemini/skills.
Leggi SKILL.md e i file correlati prima di installare. Clicca un file per l'anteprima.
Contenuto di SKILL.md
Testo originale dell'autore · sola letturaTransitions.dev
Twelve portable CSS transitions, each namespaced under t-* selectors with semantic CSS custom properties. Drop-in: paste the snippet, wire the documented HTML hooks, done. No framework dependencies, no demo-specific markup, and every snippet ships a prefers-reduced-motion guard.
Quick reference
| Transition | When to use | Reference |
| --- | --- | --- |
| Card resize | Tween a container's width or height when its layout state changes. | 01-card-resize.md ↗ |
| Number pop-in | Re-enter each digit with a blurred slide when a number updates. | 02-number-pop-in.md ↗ |
| Notification badge | Slide a small badge onto a trigger and pop the dot. | 03-notification-badge.md ↗ |
| Text states swap | Swap text in place with a blurred up-and-down transition. | 04-text-states-swap.md ↗ |
| Menu dropdown | Open an origin-aware dropdown that grows from its trigger. | 05-menu-dropdown.md ↗ |
| Modal open / close | Scale-up modal dialog with a softer scale-down on close. | 06-modal.md ↗ |
| Panel reveal | Slide a panel into a region with a cross-blur. | 07-panel-reveal.md ↗ |
| Page side-by-side | Slide between two side-by-side pages (list ↔ detail, step 1 ↔ step 2). | 08-page-side-by-side.md ↗ |
| Icon swap | Cross-fade two icons in the same slot with blur and scale. | 09-icon-swap.md ↗ |
| Success check | Compose fade + rotate + Y-bob + path stroke-draw to celebrate a completed action. | 10-success-check.md ↗ |
| Avatar group hover | Distance-falloff lift on a row of items with a bouncy spring on return. | 11-avatar-group-hover.md ↗ |
| Error state shake | Per-segment cubic-bezier shake with auto-reverting border + message. | 12-error-state-shake.md ↗ |
Decision rules
When the user asks for a transition, match against the visible UI element first, then the verb:
- Trigger + small dot floating on top → notification badge.
- Trigger + surface that grows from it → dropdown (anchored, origin-aware) or modal (centered, no anchor).
- Surface that slides into a region of the page → panel reveal.
- Two screens, list ↔ detail or step 1 ↔ step 2 → page side-by-side.
- Element changes width or height → card resize.
- Element's text content changes in place → text states swap.
- Two icons in the same slot → icon swap.
- A number updates → number pop-in.
- Confirmation / success / "done" moment (checkmark, payment processed, file uploaded) → success check.
- Hovering an item in a horizontal stack (avatars, chips, segmented buttons, tag pills) → avatar group hover.
- Form validation error / "this is wrong" feedback (invalid field, wrong PIN, duplicate name) → error state shake.
If two transitions could fit, prefer the lower-overhead one (card resize over panel reveal, dropdown over modal, success check over a full modal celebration) unless the design clearly calls for the heavier surface. The success check is animation-only — if you also need to swap from a spinner to the check, pair it with icon swap.
Universal install
Drop this :root block into your project once. Every transition snippet reads from these semantic names — there are no per-component values to chase down later.
/* transitions-dev — copy this :root block into your project once.
Every transition snippet reads from these semantic names. */
:root {
/* Card resize */
--resize-dur: 300ms;
--resize-ease: cubic-bezier(0.22, 1, 0.36, 1);
/* Number pop-in */
--digit-dur: 500ms;
--digit-distance: 8px;
--digit-stagger: 70ms;
--digit-blur: 2px;
--digit-ease: cubic-bezier(0.34, 1.45, 0.64, 1);
--digit-dir-x: 0;
--digit-dir-y: 1;
/* Notification badge */
--badge-slide-dur: 260ms;
--badge-pop-dur: 500ms;
--badge-pop-close-dur: 180ms;
--badge-fade-dur: 400ms;
--badge-fade-close-dur: 180ms;
--badge-blur: 2px;
--badge-offset-x: -8.2px;
--badge-offset-y: 12.4px;
--badge-slide-ease: cubic-bezier(0.22, 1, 0.36, 1);
--badge-pop-ease: cubic-bezier(0.34, 1.36, 0.64, 1);
--badge-close-ease: cubic-bezier(0.4, 0, 0.2, 1);
/* Text states swap */
--text-swap-dur: 200ms;
--text-swap-translate-y: 8px;
--text-swap-blur: 2px;
--text-swap-ease: ease-out;
/* Menu dropdown */
--dropdown-open-dur: 250ms;
--dropdown-close-dur: 150ms;
--dropdown-pre-scale: 0.97;
--dropdown-closing-scale: 0.99;
--dropdown-ease: cubic-bezier(0.22, 1, 0.36, 1);
/* Modal open / close */
--modal-open-dur: 250ms;
--modal-close-dur: 150ms;
--modal-scale: 0.96;
--modal-scale-close: 0.96;
--modal-ease: cubic-bezier(0.22, 1, 0.36, 1);
/* Panel reveal */
--panel-open-dur: 400ms;
--panel-close-dur: 350ms;
--panel-translate-y: 100px;
--panel-blur: 2px;
--panel-ease: cubic-bezier(0.22, 1, 0.36, 1);
/* Page side-by-side */
--page-slide-dur: 200ms;
--page-fade-dur: 200ms;
--page-slide-distance: 8px;
--page-blur: 3px;
--page-stagger: 0ms;
--page-exit-enabled: 1;
--page-slide-ease: cubic-bezier(0.22, 1, 0.36, 1);
--page-fade-ease: cubic-bezier(0.22, 1, 0.36, 1);
/* Icon swap */
--icon-swap-dur: 200ms;
--icon-swap-blur: 2px;
--icon-swap-start-scale: 0.25;
--icon-swap-ease: ease-in-out;
/* Success check */
--check-opacity-dur: 550ms;
--check-rotate-dur: 550ms;
--check-rotate-from: 80deg;
--check-bob-dur: 450ms;
--check-y-amount: 40px;
--check-blur-dur: 500ms;
--check-blur-from: 10px;
--check-path-dur: 550ms;
--check-path-delay: 80ms;
--check-ease-out: cubic-bezier(0.22, 1, 0.36, 1);
--check-ease-opacity: cubic-bezier(0.22, 1, 0.36, 1);
--check-ease-rotate: cubic-bezier(0.22, 1, 0.36, 1);
--check-ease-bob: cubic-bezier(0.34, 1.35, 0.64, 1);
--check-ease-path: cubic-bezier(0.22, 1, 0.36, 1);
/* Avatar group hover */
--avatar-lift: -4px;
--avatar-dur: 320ms;
--avatar-scale: 1.05;
--avatar-falloff: 0.45;
--avatar-ease-in: cubic-bezier(0.22, 1, 0.36, 1);
--avatar-ease-out: cubic-bezier(0.34, 3.85, 0.64, 1);
/* Error state shake */
--shake-distance: 6px;
--shake-overshoot: 4px;
--shake-dur-a: 80ms;
--shake-dur-b: 60ms;
--shake-ease: cubic-bezier(0.22, 1, 0.36, 1);
--revert-hold: 3000ms;
--revert-dur: 280ms;
}
The --pX-* source tokens used by the live demo at transitions.dev ↗ are intentionally not exported here. Tunable values are renamed to semantic names (--badge-*, --dropdown-*, --modal-*, …) so the user owns the design vocabulary.
Output format
When inserting a transition into the user's project:
1. Add the :root block above to the user's global stylesheet, but only if it isn't already there. If the user already imported the universal install block once, do not duplicate it.
2. Paste the chosen transition's CSS verbatim from the relevant reference file. Do not rewrite selectors, do not collapse the transition into shorthand, do not strip will-change. The snippets are tuned and tested.
3. Wire the documented HTML hooks — class names (.t-dropdown, .t-modal, .t-success-check, .t-avatar, .t-input, …) and state attributes (data-open, data-state, data-page, .is-open, .is-closing, .is-exit, .is-enter-start, .is-animating, .is-error, .is-shaking).
4. Preserve the @media (prefers-reduced-motion: reduce) block. Every snippet ships one. Removing it makes the component fail accessibility audits.
5. For transitions that need JS (dropdown, modal, text swap, number pop-in, page slide, success check, avatar group hover, error state shake), copy the small orchestration snippet from the reference file and adapt the selectors to the user's DOM. Keep the timing reads (getComputedStyle(...)getPropertyValue("--…")) so durations stay in sync with the :root values.
Keep the diff small: only edit the files needed to introduce the transition. Don't rename the user's existing variables, don't reformat unrelated CSS, don't pull in a motion library.
Common mistakes to avoid
- Stripping the close-state class cleanup on dropdown/modal — without the
setTimeoutthat removes.is-closing, the next open jumps from the closing scale instead of the resting pre-open scale. - Forgetting the reflow in the text swap, number pop-in, success check replay, and error state shake —
void el.offsetWidth(oroffsetHeight) between class/attribute removal and re-addition is what guarantees the animation replays. - Animating a single container instead of the inner pieces — for the badge, animate the dot, not the trigger; for page slide, animate the page sections, not the container.
- Replacing
transition: …withtransition: all— every snippet enumerates exact properties on purpose so unrelated style changes don't ride in for free. - Hardcoding the success check's
stroke-dasharray— the snippet ships20as a placeholder. Replace it withpath.getTotalLength()rounded up by 1 for *your* path, otherwise the stroke pre-reveals or over-draws. - Setting
transition-timing-functionin CSS for the avatar group hover — it has to be set inline in JS *before* the--shift/--scale-activewrites so the bouncy ease-out only applies onmouseleave. - Mixing
.is-errorand.is-shakinginto one class for the error state shake — keeping them orthogonal is what allows the shake to replay (remove → reflow → re-add) without flickering the whole error treatment.
Reference files
- 01-card-resize.md ↗ — Card resize
- 02-number-pop-in.md ↗ — Number pop-in
- 03-notification-badge.md ↗ — Notification badge
- 04-text-states-swap.md ↗ — Text states swap
- 05-menu-dropdown.md ↗ — Menu dropdown
- 06-modal.md ↗ — Modal open / close
- 07-panel-reveal.md ↗ — Panel reveal
- 08-page-side-by-side.md ↗ — Page side-by-side
- 09-icon-swap.md ↗ — Icon swap
- 10-success-check.md ↗ — Success check
- 11-avatar-group-hover.md ↗ — Avatar group hover
- 12-error-state-shake.md ↗ — Error state shake
- _root.css ↗ — the universal install block on its own, ready to import directly.
Domande frequenti
Che cosa fa lo skill transitions-dev?
Modelli CSS di transizione pronti all'uso per applicazioni web, con frammenti di codice già pronti per card, finestre modali, menu a discesa, pannelli e transizioni tra pagine.
Come si installa transitions-dev?
Apri il blocco “Installazione” in questa pagina e scegli il tuo agente — Claude Code, Codex, Cursor o Gemini CLI — per i comandi pronti che copiano la cartella dello skill nel posto giusto. Oppure copia il prompt dalla scheda “Con l'assistente” e lascia che sia l'assistente a controllare e installare lo skill.
Con quali modelli AI funziona transitions-dev?
Gli skill sono semplici istruzioni in Markdown (formato Agent Skills), quindi transitions-dev funziona con qualsiasi agente che legge SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode e altri. Il modello carica le istruzioni solo quando il compito corrisponde alla descrizione dello skill.
transitions-dev è gratuito?
Lo skill è pubblicato apertamente da Jakubantalik con licenza MIT. Lo skill in sé non costa nulla: paghi solo il tuo fornitore AI per i token usati.
È sicuro installare gli skill?
Uno skill è un insieme di istruzioni che il tuo agente seguirà: leggi SKILL.md e i file correlati prima di installarlo. Gli script nella cartella dello skill vengono eseguiti solo se li esegue l'agente: controlla cosa fa e non concedere permessi superflui.
In cosa differisce uno skill da un server MCP o da un plugin?
Un server MCP o un plugin danno al modello nuovi strumenti: codice che viene eseguito e restituisce un risultato. Uno skill fornisce conoscenza e metodo: come affrontare il compito, quali passi seguire e com'è un buon risultato. Non servono server né chiavi API.