homaroma/ORIGINAL_REQUEST.md

Original User Request x

Initial Request — 2026-06-28T19:40:16-04:00

Develop the update_category_image feature to allow updating the image URL of a category. This requires changes in both apps/backend (for the API and database update) and apps/mcp-server (for the MCP tool definition and handler).

Working directory: /home/ti/git/homaroma Integrity mode: development

Requirements

R1. Backend Implementation

• Implement the logic in apps/backend to update a category's imageUrl field.
• Expose an endpoint, service method, or procedure that the MCP server can call to perform this update.

R2. MCP Tool Implementation

• Create a new tool named update_category_image in apps/mcp-server.
• Define the schema to accept id (Category ID as a number) and imageUrl (as a string).
• Implement the handler to call the backend logic and return a clear success or error message.

Acceptance Criteria

Verification (Programmatic)

• The code must compile successfully without TypeScript errors in both apps/backend and apps/mcp-server.
• The update_category_image tool must be successfully registered in the MCP server.
• (Optional if possible) A script or test confirms that calling the backend logic correctly updates the imageUrl field of a category.

Follow-up — 2026-06-29T01:16:39Z

Teamwork Project Prompt — Draft

Status: Launched Goal: Teamwork system is currently executing the project.

Implement a Premium Mega Menu featuring 3 distinct 1:1 image placements (Root Image on far left, Column Image next to column title, Link Hover Image on far right) across all four HomAroma applications (apps/spa, apps/admin, apps/backend, apps/website).

Working directory: /home/ti/git/homaroma Integrity mode: development

Requirements

R1. Database and Backend Updates (apps/backend)

Update the Prisma schema (or corresponding data models) to include three new image fields (e.g., rootImage, columnImage, hoverImage). Ensure the backend APIs and MCP server tools correctly process and return these fields in the MegaMenuPayload.

R2. Admin Panels Implementation (apps/admin & apps/spa)

Update the Mega Menu UI in the admin applications to reflect the 3-image layout. Ensure there is a way to configure or pass these new image fields. The layout should match the recent mockup (Root image left, Column images inside the center grid, Hover image far right).

R3. Storefront UI Implementation (apps/website)

Implement the 3-image layout in the Next.js storefront. Images must maintain a 1:1 aspect ratio. The UI should use next/image for performance optimization, lazy loading, and smooth micro-animations (fade-ins) to gracefully handle the visual complexity.

Acceptance Criteria

Data & Architecture

• Prisma schema is migrated successfully without data loss.
• The MegaMenuPayload type definitions across all apps include the 3 new image fields.

Storefront & Admin UI Verification

• Root image renders correctly on the far left of the dropdown panel.
• Column image renders correctly next to or above the column title.
• Hovering a link correctly displays its specific 1:1 image on the far right without causing layout shifts.
• apps/website uses lazy loading for the hover images to protect Core Web Vitals.
• The mobile drawer menu does not break and gracefully hides complex image layouts if necessary.