Add docs for how to use the shared utility helpers in new components

[Chucks1093]

Summary

The client has several shared utility helpers (address shortening, price formatting, handle truncation) but no documentation telling contributors they exist or how to use them. New contributors often reimplement the same logic inline instead of reaching for the shared utilities.

Scope

• Add a utilities section to the contributor guide listing each shared helper, what it does, and where it lives
• Include a short example for each helper showing input and output
• Add a note that new formatting logic should go in the utils folder before being added inline to a component

Acceptance Criteria

• All existing shared helpers are listed with descriptions
• Each entry includes an input/output example
• Contributor guide note discourages inline reimplementation

ETA: 12 hours

---

Coordinate on Telegram

[mekeke111]

Hi maintainer I am a full stack developer I can handle this

[Prasiejames]

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

pls i will love to work on this

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

[Yormee-103]

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

Hello maintainer, i would like to work on this issue

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

[covenantalade]

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

Let me work on this issue

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

[grantfox-oss]

🦊 GrantFox — @Yormee-103 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @Yormee-103: 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]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Yormee-103's PR #465 was approved and merged by @Chucks1093.

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

👏 Great work, @Yormee-103! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @Yormee-103 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @Yormee-103: 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.