Web motion
Section reveals on scroll
Reveal a service introduction in readable stages.
Your inputs
Requested output
A reusable component and configuration integrated into the existing repository, required styles or shaders, a runnable demo, a list of changed files, validation results and known limitations.
Original model policy · no model was executed
model-agnostic coding agent
Original usage notes
- A prompt for a development agent implementing changes in an existing codebase; the requested output is code.
Prompt with your inputs
The default values are filled in. This prompt has not been executed.
Original reusable prompt
Implement restrained scroll-reveal animations for {{target}} in the existing site. Desired motion: {{effect}}. Use a reusable component or utility with configurable duration, distance and stagger. Trigger when a section enters the viewport; use a one-time reveal by default. Content must remain readable if JavaScript fails, hydration is delayed or observers are unavailable. Avoid scroll hijacking and do not change native scrolling speed. For this UI task, prefer CSS and the Web Animations API or an animation library already installed. Do not introduce Three.js or a new animation dependency unless this specific effect requires it. Animate transform and opacity where possible, avoid layout thrashing, and preserve existing semantic HTML, focus order and interaction behavior.
Implementation constraints:
First inspect the existing repository and installed versions. Reuse its routing, styling, build tools and dependency conventions. Use React Three Fiber only if the project already uses it or the integration is clearly justified; otherwise use the existing Three.js integration or a minimal isolated component. Do not assume version-specific APIs: check the installed package documentation and types. Do not change unrelated pages or silently replace the application architecture. Explain any required new dependency before adding it. Dispose GPU resources, remove event listeners and stop rendering when the component is not visible. Respect prefers-reduced-motion and provide a readable non-WebGL fallback. Keep links and controls in accessible HTML above the canvas. Return the changed files, configuration knobs, tests performed and known limitations.
Acceptance criteria:
- Reduced-motion users see the final visible state immediately.
- Content is never left at opacity zero after navigation, interrupted animation or failed initialization.
- Keyboard navigation and anchor links continue to work.
- The implementation avoids per-frame getBoundingClientRect loops and unnecessary React state updates.
- Verify desktop, touch viewport, back navigation and repeated route entry.Requested checks · not performed
- Reduced-motion users see the final visible state immediately.
- Content is never left at opacity zero after navigation, interrupted animation or failed initialization.
- Keyboard navigation and anchor links continue to work.
- The implementation avoids per-frame getBoundingClientRect loops and unnecessary React state updates.
- Verify desktop, touch viewport, back navigation and repeated route entry.
Execution record
Download template record ↓Source & preservation
Kumyu Academy creative templates