Description
Area: Frontend
Summary: Align loading states with the new bento/glass visual system
This issue comes from the additional audit report and should be handled as a tracked remediation item.
The current implementation either blocks production readiness, weakens maintainability, or leaves the product experience below the required standard.
The fix should be scoped, reviewed against existing project patterns, and verified with the relevant local commands.
Avoid unrelated refactors unless they are necessary to complete the acceptance criteria.
Requirements
- Update skeleton components
- Preserve stable dimensions
- Respect reduced motion
Acceptance Criteria
- No layout shift between skeleton and content
- Skeletons match dark theme
- Build passes
AI Implementation Prompt
AI code engineer prompt:
You are working in the dxmakers/smasage Next.js TypeScript frontend. Implement this issue: Align loading states with the new bento/glass visual system. Preserve existing behavior unless explicitly changed, use strict types, and follow the audit frontend revamp direction. Use Tailwind CSS and Framer Motion where UI interaction is required. Include or update tests where practical, run lint/build, and summarize any follow-up risks.
Description
Area: Frontend
Summary: Align loading states with the new bento/glass visual system
This issue comes from the additional audit report and should be handled as a tracked remediation item.
The current implementation either blocks production readiness, weakens maintainability, or leaves the product experience below the required standard.
The fix should be scoped, reviewed against existing project patterns, and verified with the relevant local commands.
Avoid unrelated refactors unless they are necessary to complete the acceptance criteria.
Requirements
Acceptance Criteria
AI Implementation Prompt
AI code engineer prompt:
You are working in the dxmakers/smasage Next.js TypeScript frontend. Implement this issue: Align loading states with the new bento/glass visual system. Preserve existing behavior unless explicitly changed, use strict types, and follow the audit frontend revamp direction. Use Tailwind CSS and Framer Motion where UI interaction is required. Include or update tests where practical, run lint/build, and summarize any follow-up risks.