lime-start

As a frontend developer, implement the CalculatorHero section for the Calculator page. This section features an animated hero with a continuous 2D motion loop where numbers and symbols dynamically arrange themselves into a calculator layout. It uses motion/react for responsive animations. Acceptance criteria: The CalculatorHero component must render exactly once on the Calculator page. It should display animated numbers and symbols that form a calculator layout, with animations triggered on scroll or page load. The design must match the provided CSS, ensuring responsive scaling and animation clarity. The section should be accessible to all users, with no restricted access. Page access: shared by all personas (User). This is verification context and does not request role-specific implementation.

As a frontend developer, implement the CalculatorCore section for the Calculator page. This section is the main calculator interface, managing all calculator state and interaction logic. It includes a display area, a 12-key number pad, operation buttons, a clear button, and an equals button. Buttons feature dynamic ripple effect animations using motion/react. Acceptance criteria: The CalculatorCore component must render exactly once on the Calculator page. It should manage calculator state transitions and update the display in real-time as users input numbers and operations. The design must match the provided CSS, ensuring responsive layout and button animations. The section should be accessible to all users, with no restricted access. Page access: shared by all personas (User). This is verification context and does not request role-specific implementation.

As a frontend developer, implement the Footer section for the Calculator page. This section provides a shared footer shell across the project, including brand information and legal content. Acceptance criteria: The Footer component must render exactly once on the Calculator page. It should include brand elements and project legal content, matching the provided CSS design. The section should be accessible to all users, with no restricted access. Page access: shared by all personas (User). This is verification context and does not request role-specific implementation.