[Frontend] Three divergent skeleton implementations; shared ui/Skeleton.StreamListSkeleton is dead code

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

Skeleton placeholders are implemented three inconsistent ways: ui/Skeleton.tsx uses animate-pulse bg-gray-200, the dashboard reimplements its own SkeletonCard with bg-white/5 + shimmer, and the wallet button uses a CSS .wallet-btn-skeleton. The exported StreamListSkeleton (ui/Skeleton.tsx:11) is never imported anywhere.

Acceptance criteria

• Standardize on one Skeleton primitive and have dashboard/wallet/incoming reuse it
• Remove or wire up the unused StreamListSkeleton
• Verify loading states look visually consistent across /dashboard, /incoming and the wallet button

Files to touch

• frontend/src/components/ui/Skeleton.tsx
• frontend/src/components/dashboard/dashboard-view.tsx
• frontend/src/components/wallet/WalletButton.tsx

Out of scope

• Changing when skeletons are shown

[Michvista]

@Michvista has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please assign this issue to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Michvista to this issue.

[Emelie-Dev]

@Emelie-Dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emelie-Dev to this issue.

[TheEmmaIhezie]

@TheEmmaIhezie has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I am interested in working on this issue because consistent and maintainable code is an important part of building reliable applications. Having multiple implementations of the same UI component can create unnecessary complexity, make future updates harder, and increase the chance of inconsistent behavior across different parts of the application. Creating a shared Skeleton component improves code quality and ensures a better user experience.

My relevant experience comes from my cybersecurity background, where I have developed an interest in secure and structured software development practices. I understand the importance of reducing technical debt, maintaining clean codebases, and creating systems that are easier to test, maintain, and improve over time.

I am also interested in strengthening my frontend development skills and gaining more experience contributing to real-world projects. This task aligns with my goal of improving software reliability through better organization, reusable components, and consistent development practices.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheEmmaIhezie to this issue.

[Ajibose]

@Ajibose has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ajibose to this issue.

[razeprasine]

@razeprasine has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer, I’d like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @razeprasine to this issue.

[drips-wave]

Congratulations, @razeprasine! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @razeprasine: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @razeprasine has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #876)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@razeprasine's PR #931 was approved and merged by @ogazboiz.

🏆 @razeprasine: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (468 total points). Track your full progress on GrantFox.

👏 Great work, @razeprasine! Keep contributing to LabsCrypt.