New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Transitions Dev

by vvedantb in vvedantb/eva

Production-ready CSS transitions for web apps. An agent skill from vvedantb/eva.

MITAuto-check passedDocuments & Office

Install Transitions Dev

skills CLI
$ npx skills add vvedantb/eva --skill transitions-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vvedantb/eva transitions-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vvedantb/eva.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/transitions-dev .claude/skills/transitions-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
transitions-dev
GitHub stars
101
Token cost
~3.9k tokens
SKILL.md length
1,655 words
Files
20
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Production-ready CSS transitions for web apps. An agent skill from vvedantb/eva.

  • Works in 4 steps: Search the workspace for indicators:… → For each hit, match against the decision… → Output a numbered list grouped by file → …
  • Implementing notification badges
  • SKILL.md covers Quick reference, Decision rules, Commands and Universal install, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Transitions Dev is an agent skill from vvedantb/eva. Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, error state shakes, search/input clear, skeleton loaders, shimmer text, sliding tabs, tooltips, or staggered text reveals. Triggers on "add a transition", "animate the dropdown", "make the modal open smoothly", "swap icon", "page slide", "stagger animation", "open / close transition"…

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files (for example `01-card-resize.md`, `02-number-pop-in.md` and `03-notification-badge.md`).

It sits in Documents & Office, covering Slides and decks. The repository describes itself as: Orchestrate sandboxed agents that run in the cloud while you work. The licence is MIT.

When your agent uses it

  • Implementing notification badges
  • Page transitions
  • Avatar group hovers
  • Error state shakes

Example prompts

  • “add a transition”
  • “animate the dropdown”
  • “make the modal open smoothly”
  • “/transitions-dev”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Search the workspace for indicators: transition: declarations, @keyframes, hardcoded ms / s durations in style files, components matching…
  2. For each hit, match against the decision rules and pick the single best-fit transition.
  3. Output a numbered list grouped by file
  4. Do not edit anything. End with: "Run transitions apply on any line to install the suggested transition."

What it can do on your machine

Read from SKILL.md and the folder at commit 166d464. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • transitions.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Transitions Dev loads about 3.9k tokens when it runs. Until then it costs about 215 tokens; SKILL.md has 1,655 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~215
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vvedantb/eva at commit 166d464, republished under its MIT licence (© vvedantb). 1,655 words, ~3,898 tokens.

Download SKILL.mdSave it as .claude/skills/transitions-dev/SKILL.md (or your agent's skills folder). This skill also uses 19 other files; get the full folder from GitHub.
name
transitions-dev
description
Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, error state shakes, search/input clear, skeleton loaders, shimmer text, sliding tabs, tooltips, or staggered text reveals. Triggers on "add a transition", "animate the dropdown", "make the modal open smoothly", "swap icon", "page slide", "stagger animation", "open / close transition", "make it animate", "fade between", "success animation", "form error", "shake on invalid", "hover lift", "avatar stack hover", "clear the search", "skeleton loader", "loading shimmer", "shimmer text", "sliding tabs", "segmented control", "tooltip", "reveal text". Also transitions reveal, transitions review, transitions apply.

Transitions.dev

Eighteen 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

TransitionWhen to useReference
Card resizeTween a container's width or height when its layout state changes.01-card-resize.md
Number pop-inRe-enter each digit with a blurred slide when a number updates.02-number-pop-in.md
Notification badgeSlide a small badge onto a trigger and pop the dot.03-notification-badge.md
Text states swapSwap text in place with a blurred up-and-down transition.04-text-states-swap.md
Menu dropdownOpen an origin-aware dropdown that grows from its trigger.05-menu-dropdown.md
Modal open / closeScale-up modal dialog with a softer scale-down on close.06-modal.md
Panel revealSlide a panel into a region with a cross-blur.07-panel-reveal.md
Page side-by-sideSlide between two side-by-side pages (list ↔ detail, step 1 ↔ step 2).08-page-side-by-side.md
Icon swapCross-fade two icons in the same slot with blur and scale.09-icon-swap.md
Success checkCompose fade + rotate + Y-bob + path stroke-draw to celebrate a completed action.10-success-check.md
Avatar group hoverDistance-falloff lift on a row of items with a bouncy spring on return.11-avatar-group-hover.md
Error state shakePer-segment cubic-bezier shake with auto-reverting border + message.12-error-state-shake.md
Input clear with dissolveFly-out + per-word streak when a text field is cleared.13-input-clear-dissolve.md
Skeleton loader and revealPulse a placeholder, then cross-fade + cross-blur to the loaded content.14-skeleton-reveal.md
Shimmer textSweep a highlight band across muted text on a loop (pure CSS).15-shimmer-text.md
Tabs slidingSlide the active pill between tabs in a segmented control.16-tabs-sliding.md
Tooltip open/closeDelayed fade+scale in, instant out (pure CSS).17-tooltip.md
Texts revealStaggered blurred rise for stacked text lines, quiet fade out.18-texts-reveal.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.
  • Clearing a text field (search box × button, filter reset) → input clear with dissolve.
  • Placeholder that loads then swaps to real content (list row, card, profile header) → skeleton loader and reveal.
  • In-progress / "thinking" text that should feel alive (loading label, streaming status) → shimmer text.
  • Small horizontal set of mutually-exclusive options with a moving highlight (view switcher, segmented control, filter tabs) → tabs sliding.
  • Hover/focus hint that appears over a trigger (icon tooltip, info bubble) → tooltip open / close.
  • Stacked headline + supporting line entering with rhythm (hero copy, empty state, onboarding step) → texts reveal.
  • No clear match → fall back to transitions reveal and let the user pick. Don't guess.

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.

Commands

The skill exposes three namespaced verbs the agent should recognise in addition to direct transition requests. Every command starts with transitions so the invocation never collides with verbs from other skills installed in the same project.

transitions reveal — list every transition

Trigger phrases: transitions reveal, "reveal the transitions", "list all transitions", "what transitions are in this skill", "show the transitions catalog".

Behaviour: print the eighteen transitions as a numbered plain-text list — name, one-line summary, and the matching reference filename. Reuse the rows in ## Quick reference above; do not invent new copy. No project access.

transitions review — audit the project for fit

Trigger phrases: transitions review, "review my project", "audit my animations", "where would transitions.dev help", "find places to use this skill".

Behaviour:

  1. Search the workspace for indicators: transition: declarations, @keyframes, hardcoded ms / s durations in style files, components matching the decision-rule patterns (modals, dropdowns, badges, search inputs, skeletons, tabs, tooltips, …).
  2. For each hit, match against the decision rules and pick the single best-fit transition.
  3. Output a numbered list grouped by file:
    • path/to/Component.tsx:L42 — looks like a dropdown opening, suggest menu-dropdown (05-menu-dropdown.md).
    • Skip ad-hoc transitions that already use a t-* class.
  4. Do not edit anything. End with: "Run transitions apply on any line to install the suggested transition."
transitions apply — install the best-fit transition

Trigger phrases: transitions apply, "apply a transition here", "add the right transition", "install transitions-dev here", "fix the animation on this element".

Behaviour:

  1. Read context: the currently-open file, the element nearest the cursor, surrounding CSS / JSX. If the user named a transition explicitly (e.g. transitions apply menu-dropdown), use it.
  2. Run the decision rules from ## Decision rules on that context and pick one transition. If two could fit, prefer the lower-overhead one (same tie-breaker the existing rules use).
  3. Surface a one-line proposal: "I'd apply menu-dropdown here because the element opens from a trigger and is anchored. Confirm to install?".
  4. On confirmation, follow the existing five-step procedure in ## Output format verbatim (root block, snippet, hooks, reduced-motion guard, JS orchestration if needed).
  5. If the agent can't pick a single transition with confidence, fall back to transitions reveal and ask the user to choose.
Show full SKILL.md (712 more words)Show less

Universal install

Copy _root.css into your project once and import it (or paste its :root block into your global stylesheet). It defines the semantic tunable variables for all eighteen transitions. Every snippet reads from these names — --resize-*, --badge-*, --dropdown-*, --clear-*, --shimmer-*, --tabs-*, --tt-*, --stagger-*, and the rest.

Each reference file also restates just the variables that snippet needs, so you can install a single transition without pulling the whole block. Don't duplicate the block — if _root.css is already imported, skip re-pasting any per-snippet :root.

The --pX-* source tokens used by the live demo at transitions.dev are intentionally not exported. Tunable values are renamed to semantic names so the user owns the design vocabulary. A few transitions (input clear, shimmer text, tabs, tooltip) carry color tokens that differ by theme — each reference file documents the html[data-theme="dark"] overrides.

Output format

When inserting a transition into the user's project:

  1. Install the variables from _root.css into the user's global stylesheet, but only if they aren't already there — or just the per-snippet :root block from the reference file if installing a single transition. If the universal block is already imported, 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-clear, .t-skel, .t-shimmer, .t-tabs, .t-tt, .t-stagger, …) and state attributes (data-open, data-state, data-page, aria-selected, .is-open, .is-closing, .is-error, .is-shaking, .has-value, .is-clearing, .is-pulsing, .is-revealed, .is-shown, .is-hiding).
  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, input clear, skeleton reveal, tabs sliding, texts reveal), 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. Shimmer text and tooltip are pure CSS — no JS needed.

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 setTimeout that 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 (or offsetHeight) 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: … with transition: 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 ships 20 as a placeholder. Replace it with path.getTotalLength() rounded up by 1 for your path, otherwise the stroke pre-reveals or over-draws.
  • Setting transition-timing-function in CSS for the avatar group hover — it has to be set inline in JS before the --shift / --scale-active writes so the bouncy ease-out only applies on mouseleave.
  • Mixing .is-error and .is-shaking into 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.
  • Leaving the input clear glow on mix-blend-mode: multiply in dark mode — flip to screen, bump --glow-opacity to ~0.85, and paint white gradients in JS.
  • Forgetting to write the tabs pill's first position without a transition — on first paint and resize, set transform + width with transition: none (then reflow + restore) or the pill animates in from translateX(0) / width: 0.

Reference files

© vvedantb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 19 other files in .claude/skills/transitions-dev of vvedantb/eva.

  • SKILL.md
  • 01-card-resize.md
  • 02-number-pop-in.md
  • 03-notification-badge.md
  • 04-text-states-swap.md
  • 05-menu-dropdown.md
  • 06-modal.md
  • 07-panel-reveal.md
  • 08-page-side-by-side.md
  • 09-icon-swap.md
  • 10-success-check.md
  • 11-avatar-group-hover.md
  • 12-error-state-shake.md
  • 13-input-clear-dissolve.md
  • 14-skeleton-reveal.md
  • 15-shimmer-text.md
  • 16-tabs-sliding.md
  • 17-tooltip.md
  • 18-texts-reveal.md
  • _root.css

Open the folder on GitHubat commit 166d464

Compare with similar skills

Transitions Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Transitions Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Transitions Dev this skillvvedantb/eva101—~3.9kAutomated safety check: PassMIT
Image To Editable Pptningzimu/image-to-editable-ppt-skill2.8k—~4.3kAutomated safety check: PassMIT
Slidesfcakyon/claude-codex-settings1.2k1 repos~1.1kAutomated safety check: PassMIT
Ppt Image FirstNyxTides/ppt-image-first1.2k—~1.6kAutomated safety check: PassApache-2.0
Vibe to Agentic Engineering Frameworkshanraisshan/claude-code-best-practice67k—~3.3kAutomated safety check: PassMIT
Gpt Image2 PptJuneYaooo/gpt-image2-ppt-skills1.3k—~8.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Image To Editable Ppt

    ningzimu/image-to-editable-ppt-skill

    Rebuild slide images, scanned or image-based PPT/PPTX files, and PDF decks into object-level editable PowerPoint (.pptx), preserving speaker notes when supplied.

    2.8k GitHub stars~4.3k tokensUpdated 21 days ago
    Documents & OfficeAuto-check passed

  • Slides

    fcakyon/claude-codex-settings

    Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities.

    1.2k GitHub starsUsed in 1 repo~1.1k tokens
    Documents & OfficeAuto-check passed

  • Ppt Image First

    NyxTides/ppt-image-first

    Build presentation plans for PPT / slides / decks through a conversation-first workflow, then propose multiple visual directions with preview images before writing deck specs.

    1.2k GitHub stars~1.6k tokensUpdated 5 mo ago
    Documents & OfficeAuto-check passed

  • Vibe to Agentic Engineering Framework

    shanraisshan/claude-code-best-practice

    Explains the conceptual model behind a presentation on moving from unstructured vibe coding to fully configured agentic engineering, including its 4-level scoring system and slide conventions.

    67k GitHub stars~3.3k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Gpt Image2 Ppt

    JuneYaooo/gpt-image2-ppt-skills

    Generate visually striking PPT slides via OpenAI's gpt-image-2 -- use any style in styles/<collection/STYLEID.md or mimic a user-supplied .pptx template; outputs high-res slide PNGs and a 16:9 .pptx.

    1.3k GitHub stars~8.9k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check: notes

  • Compiledeck

    scunning1975/MixtapeTools

    Create and compile beautiful Beamer presentations following the Rhetoric of Decks philosophy.

    469 GitHub starsUsed in 2 repos~3.1k tokens
    Documents & OfficeAuto-check passed

More from vvedantb/eva

All 23 skills in this repo

  • Eva Feature Demo

    vvedantb/eva

    Record a real agent-browser screencast of one eva feature being used end to end, convert it to an X-ready mp4, and write a tweet for it.

    101 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Animate

    vvedantb/eva

    Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and…

    101 GitHub starsUsed in 6 repos~2.9k tokens
    Auto-check passed

  • Convex Create Component

    vvedantb/eva

    Design and build Convex components with clear boundaries, isolated state, and app-facing wrappers.

    101 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Eva Feature Screenshot

    vvedantb/eva

    Grab a single clean HD screenshot of a new eva feature from the real running app (Playwright at deviceScaleFactor 2, 1280 layout captured crisp at 2560×1440, dev overlays hidden) and write a tweet…

    101 GitHub stars~3.2k tokensUpdated today
    Auto-check: notes

  • Code Structure

    vvedantb/eva

    A skill your agent uses when multiple workflows duplicate the same operational logic, when deciding what belongs in actions vs shared services, or when refactoring repeated operational blocks across…

    101 GitHub starsUsed in 2 repos~1.1k tokens
    Auto-check passed

  • Eva Launch Video

    vvedantb/eva

    Produce polished, mobile-friendly product demo videos of the eva app with Remotion — 1280×720, snappy beat-synced hard cuts, lo-fi music that swells on every cut, and footage captured from the REAL…

    101 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Transitions Dev

What does Transitions Dev do?

Production-ready CSS transitions for web apps. An agent skill from vvedantb/eva. Transitions Dev is an agent skill from vvedantb/eva. Production-ready CSS transitions for web apps.

When should I use Transitions Dev?

Transitions Dev fits situations like: implementing notification badges; page transitions; avatar group hovers; error state shakes.

How do I install Transitions Dev in Claude Code?

Run `npx skills add vvedantb/eva --skill transitions-dev -a claude-code`. Or copy the skill folder (.claude/skills/transitions-dev in vvedantb/eva) into .claude/skills/transitions-dev in your project. Claude Code loads it when a task matches its description.

How do I install Transitions Dev in Codex?

Run `npx skills add vvedantb/eva --skill transitions-dev -a codex`. Or copy the skill folder (.claude/skills/transitions-dev in vvedantb/eva) into .agents/skills/transitions-dev in your project. Codex loads it when a task matches its description.

Can I use Transitions Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vvedantb/eva --skill transitions-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/transitions-dev, .gemini/skills/transitions-dev, .github/skills/transitions-dev and .opencode/skills/transitions-dev in your project.

What does Transitions Dev need to run?

SKILL.md names no scripts, command-line tools or credentials: Transitions Dev is instructions for the agent only.

Does Transitions Dev access the network?

SKILL.md names 1 domain. As links in the text: transitions.dev. This is read from the text; nothing was executed.

Is Transitions Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Transitions Dev use?

Transitions Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Transitions Dev use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Transitions Dev?

Skills that share tags, products or a category with Transitions Dev: Image To Editable Ppt (ningzimu/image-to-editable-ppt-skill, 2.8k stars), Slides (fcakyon/claude-codex-settings, 1.2k stars), Ppt Image First (NyxTides/ppt-image-first, 1.2k stars) and Vibe to Agentic Engineering Framework (shanraisshan/claude-code-best-practice, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Transitions Dev?

vvedantb (a GitHub user) maintains it in vvedantb/eva, which has 101 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 6, 2026.

Source: vvedantb/eva on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.