DS-039: Restyle Faucet states with shared primitives

[IbrahimIjai]

Complexity: Medium
Primary files: apps/web/src/features/faucet/components/faucet-page.tsx

Replace one-off cards, pills, alerts, and loading styles in every faucet state.

Acceptance criteria

• Connected, disconnected, cooldown, mismatch, loading, and error states are covered.
• Claim actions use shared loading buttons.
• Token amounts use numeric typography.
• Existing faucet tests pass unchanged or with presentation-only updates.

[ogaziedaniel80-droid]

@ogaziedaniel80-droid has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[nonso7]

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

Can i work on this issue

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

[drips-wave]

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

🧑‍💻 @nonso7: 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 🌊

[drips-wave]

This issue has been completed by @nonso7 as part of the Stellar Wave Program's 7th Wave 🥳

😎 @nonso7: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.