Establish a component style guide or Storybook setup for shared frontend components

[phertyameen]

Location

frontend/.storybook/ (new), frontend/src/components/

Problem

As the number of shared components (transaction status, error boundaries, theme-aware elements) grows per the earlier-proposed feature issues, no confirmed isolated development/documentation environment exists for building and reviewing these components outside the full app context, slowing both development and design review.

Acceptance Criteria

• Storybook (or an equivalent lightweight alternative) set up and covering at least the highest-reuse shared components
• Documented in CONTRIBUTING.md as the expected place to add stories for new shared components going forward
• Does not become a maintenance burden disconnected from real usage, stories are kept minimal and tied to actual component props

[Tobi-8]

please maintainer , assign me to this issue. I have looked through your description, and i have had experience in this type of issue.
kindly assign

[RaymondAbiola]

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

Please can I work on this

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