executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
view-transitionsUse when adding page transition animations, image expand/contract effects, shared-element transitions, or improving navigation UX in a single-page or multi-page application.
Independent GitHub snapshot · Automated classification · Original documentation governs
Jarring instant page changes are one of the most noticeable perceived- performance problems in web applications. Smooth transitions help users maintain context during navigation — they understand where they came from and where they are going. Previously, achieving this required complex JavaScript animation libraries; the View Transitions API delivers it natively at a fraction of the code cost.
Check whether the site uses the View Transitions API or a JavaScript animation library for page and component transitions.
Implement view transitions using document.startViewTransition() for SPA route changes or @view-transition for MPA cross-document navigation.
Explain how the View Transitions API captures before/after snapshots and animates between them, and how view-transition-name enables shared-element transitions.
Review transition implementation for missing prefers-reduced-motion guards, duplicate view-transition-name values (must be unique per snapshot), and transitions that may cause layout thrash in the old/new state.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/css/view-transitions