TechnicalCollectible prompt
Add dynamic animations and visual effects to a website.
## Instructions
# Goal
Enhance the existing site with refined, high-end micro-interactions and transitions to make the UI feel responsive, tactile, and dynamic rather than static, while maintaining its clean corporate aesthetic.
# Scope & Technical Requirements
1. **Page & Section Transitions**:
- Implement smooth, performant route/page transitions (subtle opacity and transform shifts).
- Add staggered entrance animations for key viewport elements (hero headlines, cards, feature sections) as they scroll into view.
2. **Interactive States & Micro-interactions**:
- Add tactile feedback to interactive components (buttons, links, form inputs, cards): scale, subtle elevation, border-color transitions, and active press states.
- Ensure all animations use GPU-accelerated CSS properties (`transform`, `opacity`) to maintain 60fps and prevent layout reflows.
- Keep timing curves smooth and understated (e.g., cubic-bezier easing, durations between 150ms–350ms).
3. **Accessibility**:
- Wrap all animations in `@media (prefers-reduced-motion: reduce)` queries to provide instant or reduced fallbacks.
# Context & Execution
- Read `AGENTS.md` first if present, and execute the listed setup, lint, and build commands verbatim.
- Inspect the codebase to identify the existing routing and styling framework (e.g., Tailwind CSS, CSS Modules, Framer Motion) and implement animations using the project's native stack. Do not introduce heavy new animation dependencies unless existing tooling cannot support the requirement.
- Do not stop to ask clarifying questions. If ambiguous, choose standard, production-ready defaults and proceed autonomously.
# Constraints
- Touch only files required to implement the animations and transitions.
- Do not alter layout geometry, brand colors, typography, or existing business logic.
# Done When
- Entrance animations, micro-interactions, and route transitions are fully implemented and functional.
- The project passes all linting, type-checking, and build commands without errors or warnings.
- The final response lists all modified files and explicitly documents any assumptions made.
Technicalnvoka.com/library/add-dynamic-animations-and-visual-effects-to-a-website-b1c57a75Scan to open
Technical
Add dynamic animations and visual effects to a website.
Enhance the existing site with refined, high-end micro-interactions and transitions to make the UI feel responsive, tactile, and dynamic rather than static, while maintaining its clean corporate aesthetic.
Added by Ryan Hertel
Prompt Strategist
Base44LovableCodexClaude Code
Make it yours
Change any word. Only your copy changes, never the card.
Your prompt
## Instructions
# Goal
Enhance the existing site with refined, high-end micro-interactions and transitions to make the UI feel responsive, tactile, and dynamic rather than static, while maintaining its clean corporate aesthetic.
# Scope & Technical Requirements
1. **Page & Section Transitions**:
- Implement smooth, performant route/page transitions (subtle opacity and transform shifts).
- Add staggered entrance animations for key viewport elements (hero headlines, cards, feature sections) as they scroll into view.
2. **Interactive States & Micro-interactions**:
- Add tactile feedback to interactive components (buttons, links, form inputs, cards): scale, subtle elevation, border-color transitions, and active press states.
- Ensure all animations use GPU-accelerated CSS properties (`transform`, `opacity`) to maintain 60fps and prevent layout reflows.
- Keep timing curves smooth and understated (e.g., cubic-bezier easing, durations between 150ms–350ms).
3. **Accessibility**:
- Wrap all animations in `@media (prefers-reduced-motion: reduce)` queries to provide instant or reduced fallbacks.
# Context & Execution
- Read `AGENTS.md` first if present, and execute the listed setup, lint, and build commands verbatim.
- Inspect the codebase to identify the existing routing and styling framework (e.g., Tailwind CSS, CSS Modules, Framer Motion) and implement animations using the project's native stack. Do not introduce heavy new animation dependencies unless existing tooling cannot support the requirement.
- Do not stop to ask clarifying questions. If ambiguous, choose standard, production-ready defaults and proceed autonomously.
# Constraints
- Touch only files required to implement the animations and transitions.
- Do not alter layout geometry, brand colors, typography, or existing business logic.
# Done When
- Entrance animations, micro-interactions, and route transitions are fully implemented and functional.
- The project passes all linting, type-checking, and build commands without errors or warnings.
- The final response lists all modified files and explicitly documents any assumptions made.
