Add ESLint rules for consistent component patterns

[Akatenvictor]

What

Configure additional ESLint rules that enforce consistent patterns: prop-types ordering, hook dependency arrays, and import organization.

Why

Inconsistent code patterns increase cognitive load during reviews and make the codebase harder to navigate. Linting automates style enforcement.

Scope

In: Import ordering rules, hook dependency checks, prop ordering, consistent return types
Out: Custom ESLint rules, formatting rules (handled by Prettier)

Acceptance Criteria

• Import sorting enforced (next, react, third-party, local)
• exhaustive-deps rule enabled for useEffect
• react/hook-use-state rule for consistent useState returns
• No new lint errors after configuration
• Lint passes in CI pipeline
• Autofix available for most rules

Technical Context

• Update .eslintrc.json with additional rules
• Add eslint-plugin-import for import ordering
• Run eslint --fix for existing code

[sudo-robi]

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

Hi maintainer I'm a full stack developer and smart contract developer and auditor let me help you resolve this issue and I assure you it will be thoroughly done neatly as I have seen my way to solve the issue.

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

[sudo-robi]

Hi @Akatenvictor Please allow me to take this issue off your plate by assigning me.

[sudo-robi]

Hi @Akatenvictor Please allow me to take this issue off your plate by assigning me.
@Akatenvictor i will do it well.

[bbkenny]

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

Hi maintainer, I'm a frontend developer who focuses heavily on code quality and standardizing team workflows. I saw the need to add ESLint rules for consistent component patterns. I have extensive experience configuring custom ESLint rules and plugins to enforce best practices and clean architecture across large React codebases. My approach will be to set up the appropriate ESLint plugins and rules to ensure uniformity in component structures. Ready to dive in once assigned!

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

[drips-wave]

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

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