feat: Setup Zustand counter store

[JeanMeijer]

Description

Sets up Zustand for state management in the Next.js app router. Adds zustand package, creates counter-store.ts and counter-store-provider.tsx, and integrates the provider.

Screenshots / Recordings

Type of Change

• Bug fix
• New feature
• Breaking change
• UI/UX update
• Docs update
• Refactor / Cleanup

Related Areas

• Authentication
• Calendar UI
• Data/API
• Docs

Testing

• Manual testing performed
• Cross-browser testing (if UI changes)
• Mobile responsiveness verified (if UI changes)

Checklist

• I’ve read the CONTRIBUTING guide
• My code works and is understandable and follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in complex areas
• I have updated the documentation
• Any dependent changes are merged and published

Notes

By submitting, I confirm I understand and stand behind this code. If AI was used, I’ve reviewed and verified everything myself.

Want me to make any changes? Add a review or comment with @tembo and i'll get back to work!

---

Summary by cubic

Set up Zustand state management with a global counter store and integrated its provider into the Next.js app router.

• New Features
  • Added zustand dependency.
  • Implemented a vanilla counter store (count, incrementCount, decrementCount).
  • Added CounterStoreProvider and useCounterStore hook, and wrapped app providers to expose the store app-wide.

^{Written for commit dc377a2. Summary will update automatically on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
analog	Ready	Preview	Comment	Nov 25, 2025 10:16pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 5 files