Implementation

Step 1: Audit the App

Before writing any code, scan the codebase thoroughly. Search for:

• Every <Link> and router.push — these are your navigation triggers. Open every file that contains one.
• Every <Suspense> boundary — each one is a candidate for a reveal animation. Check what its fallback renders.
• Every page/route component — list them all. Each page needs a VT placement decision.
• Persistent elements — headers, navbars, sidebars, sticky controls that stay on screen across navigations. These need viewTransitionName isolation.
• Shared visual elements — images, cards, or avatars that appear on both a source and target view (e.g., a thumbnail in a list and the same image on a detail page).
• Skeleton-to-content control pairs — if a Suspense fallback renders a control (search input, tab bar) that also exists in the real content, both need a matching viewTransitionName.

Then classify every navigation and produce a navigation map:

For each shared element (name prop), note every navigation where a pair forms and where it doesn’t — this determines whether you need enter/exit as a fallback alongside share.

Step 2: Add CSS Recipes

Choose the animation pattern from the audit and this skill’s guidance, then copy only the applicable sections from css-recipes.md. Always include reduced motion. Add live-root, persistent-element, backdrop, or floating-element rules only when the audit found those surfaces.

Customize timing after the structure works. Keep ordinary crossfades opacity-only; scope blur to a specific shared morph when it is intentional.

Step 3: Isolate Persistent Elements

For every persistent element identified in Step 1, add a viewTransitionName style to pull it out of the page content’s transition snapshot:

Then add the Persistent Element Isolation CSS (prevents the element from animating during page transitions). If the element uses backdrop-blur or backdrop-filter, use the Backdrop-Blur Workaround instead.

If a Suspense fallback mirrors a persistent control (e.g., a skeleton search input), give both the real control and the skeleton the same viewTransitionName so they morph in place.

Step 4: Add Directional Page Transitions

For hierarchical navigations identified in Step 1, tag the navigation direction using addTransitionType inside startTransition:

Then wrap each page component (not layout) in a type-keyed <ViewTransition>:

The nav-forward and nav-back CSS classes from Directional Navigation produce horizontal slides. For simpler apps where directional motion isn’t needed, a bare <ViewTransition default="none"> wrapper with enter="fade-in" / exit="fade-out" works too.

Extract this into a reusable component so every page doesn’t repeat the verbose type map:

This also becomes the single place to adjust if you add new transition types later.

Rules:

• Always pair enter with exit — without an exit animation, the old page disappears instantly while the new one animates in.
• Always include default: "none" in type map objects and default="none" on the component — otherwise it fires on every transition.
• Place the directional <ViewTransition> in each page component, not in a layout. Layouts persist across navigations and never trigger enter/exit.
• Only use directional slides for hierarchical navigation or ordered sequences (prev/next). Lateral/sibling navigation (tab-to-tab) should use a bare <ViewTransition> (cross-fade) or default="none".

Step 5: Add Suspense Reveals

For every <Suspense> boundary identified in Step 1, wrap the fallback and content in separate <ViewTransition>s:

This example uses slide-down / slide-up for directional vertical motion. For a simpler reveal, a bare <ViewTransition> around the <Suspense> gives a cross-fade with zero configuration. Choose based on the spatial meaning described in the main skill.

Rules:

• Always use default="none" on the content <ViewTransition> to prevent re-animation on revalidation or unrelated transitions.
• Use simple string props (not type maps) on Suspense <ViewTransition>s — Suspense resolves fire as separate transitions with no type, so type-keyed props won’t match.
• A fallback/content share pair morphs between snapshots. Use it only when that interpolation is desired and does not distort layout or geometry.
• If the same element appears in both the fallback and the content (a title, a heading), it flickers on reveal — an opacity dip. Render it outside the <Suspense> boundary (or pin it), so it isn’t in both. See Suspense reveal flicker.

Step 6: Add Shared Element Transitions

For every shared visual element identified in Step 1, add matching named <ViewTransition> wrappers on both the source and target views:

The share="morph" class uses the Shared Element Morph recipe (controlled duration + motion blur). For a simpler cross-fade, use share="auto" (browser default).

When list items contain shared elements, compose both patterns with two nested <ViewTransition> layers — an outer keyed VT for list identity and an inner named VT for the cross-route pair. See Composing Shared Elements with List Identity.

Rules:

• Names must be globally unique — use prefixes like photo-${id}.
• Add default="none" on list-side shared elements to prevent per-item cross-fades on filter/search updates.
• The target must be in the DOM at navigation time for the pair to form. If it’s behind a Suspense fallback (not rendered yet), no pair forms and it won’t morph. It works when the target is present at the snapshot — render it above the data boundary, or have its data cached/prefetched so it resolves in time.

Step 7: Verify Each Navigation Path

Walk through every row in the navigation map from Step 1 and confirm:

• Does the VT mount/unmount on this navigation, or does it stay mounted (same-route)?
• For named VTs: does a shared pair form? If not, does enter/exit provide a fallback?
• Does default="none" block an animation you actually want?
• Do persistent elements stay static (not sliding with page content)?
• Do Suspense reveals animate independently from directional navigations?

If any path produces no animation or competing animations, use the symptom-driven troubleshooting guide.

For Next.js-specific implementation steps (transitionTypes on <Link>, prefetch behavior, and same-route dynamic segments), see nextjs.md.