State Management Cleanup

[RUKAYAT-CODER]

Description

Overview
Multiple state management solutions exist (Zustand stores) without clear separation of concerns.

Background
State is spread across searchStore, quizStore, notificationStore without clear domain separation.

Specifications

• Consolidate related state
• Add proper TypeScript types

Tasks:

• Audit existing stores
• Remove duplicate state
• Add selectors

Impacted Files:

• src/app/store/*.ts
• src/store/*.ts

Labels: frontend, state-management, priority-medium

Acceptance Criteria
Clean state architecture

🙆Contribution Guidelines:
Assignment required before PR submission
Timeframe: 48-72 hours
PR description must include: Close #issue no
Star the repo⭐

[Samacode]

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

as a reactjs specialist i can tackle and solve this issue

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

[drips-wave]

Congratulations, @Samacode! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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