Replace Basic Loader with Proper Skeleton UI

[deepanshu-prajapati01]

Hi team 👋

I’ve noticed that our app currently uses a basic spinner/loader in several key pages and components (like home, ideas, etc.) during data fetching — especially visible on slower internet connections.

While functional, this loader doesn't provide any contextual feedback about what kind of data is being fetched. It also lacks polish from a modern UX perspective.

---

🔴 Current Problem:

• Users only see a generic spinner, which feels disconnected from the content they’re about to see.
• There’s no indication of the layout or structure of incoming content.
• This creates a jarring loading experience, especially when transitioning between routes or reloading content-heavy pages.

---

✅ Proposed Solution:

• Replace the spinner with a skeleton loader for major components
• Skeletons will give users a visual preview of the data layout, making loading feel more intentional and polished.
• Ensure skeleton components are lightweight, responsive, and theme-aware (support both light and dark modes).

---

🏷 Labels Requested:

• gssoc2025
• level 3
• enhancement

---

👉 Please assign this issue to me — I’ll handle the refactor and ensure we have a smooth, modern, and context-aware loading experience throughout the app.

Thanks! 🙌

[rahulkhandait-sde]

@deepanshu-prajapati01 go for it