Web モーション
スクロール連動のセクション表示
サービス紹介を読みやすく段階的に表示する
入力する内容
要求する出力
既存リポジトリに組み込んだ再利用可能なコンポーネントと設定、必要なスタイルまたはシェーダー、実行可能なデモ、変更ファイル一覧、検証結果と既知の制約
原本のモデル方針 · 実行したモデルではありません
model-agnostic coding agent
原本の利用メモ
- 画像ではなく、既存コードベースで実装を行う開発エージェント向けプロンプト。
入力を反映したプロンプト
初期値を反映しています。このプロンプトは実行していません。
再利用する原文プロンプト
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.要求する確認事項 · 未実施
- 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.
実行記録
テンプレート記録を保存 ↓出典と原本の保存
Kumyu Academy creative templates