Skip to content

feat(web): establish feature-based architecture and component folder structure#39

Merged
GRACENOBLE merged 3 commits into
mainfrom
34-feat-web-architecture
Jun 23, 2026
Merged

feat(web): establish feature-based architecture and component folder structure#39
GRACENOBLE merged 3 commits into
mainfrom
34-feat-web-architecture

Conversation

@GRACENOBLE

@GRACENOBLE GRACENOBLE commented Jun 23, 2026

Copy link
Copy Markdown
Owner

Summary

  • Creates directory skeleton (components/layout/, common/, home/, ui/, features/, server/, types/) with .gitkeep placeholders
  • Adds App Router route groups app/(auth)/ and app/(dashboard)/
  • Updates web/AGENTS.md to document the new feature-based layout

Test plan

  • pnpm lint — 0 errors (1 pre-existing warning in __mocks__)
  • pnpm build — passes cleanly
  • Existing app/ source files untouched

Closes #34

Summary by CodeRabbit

  • Documentation
    • Updated project structure documentation with comprehensive architectural guidance for developers.

Create directory skeleton for components/, features/, server/, types/,
and app route groups (auth)/(dashboard). Update AGENTS.md to document
the new layout so subsequent features have a clear home.

Closes #34
@github-actions github-actions Bot added the area: web Next.js web app label Jun 23, 2026
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@GRACENOBLE, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 52 minutes and 55 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d0271bc1-5bf9-4afc-ae4f-986abfc8179d

📥 Commits

Reviewing files that changed from the base of the PR and between 1573304 and 9b600b9.

📒 Files selected for processing (10)
  • backend/docs/_index.md
  • backend/docs/database.md
  • backend/docs/email.md
  • backend/docs/error-handling.md
  • backend/docs/migrations.md
  • backend/docs/queue.md
  • backend/docs/routing.md
  • backend/docs/streams.md
  • backend/docs/websocket.md
  • web/AGENTS.md
📝 Walkthrough

Walkthrough

The "Project structure" section in web/AGENTS.md is replaced with a detailed directory scaffold. It documents the Next.js App Router layout under app/, expands components/ into layout/, common/, home/, and ui/ subdirectories, introduces a features/<feature>/ convention with scoped components/, hooks/, and types.ts, and adds explicit server/ and types/ top-level entries.

Changes

Project Structure Documentation

Layer / File(s) Summary
Project structure tree in AGENTS.md
web/AGENTS.md
Lines 27–44: replaces the prior minimal directory list and "create when needed" guidance with a fully annotated scaffold covering app/, components/ subdirectories (layout/, common/, home/, ui/), features/<feature>/ convention, lib/, server/, and types/.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through folders with glee,
features/ and server/ — now plain to see!
No more "create when needed" to guess,
Each directory labeled, no more mess.
🐇✨ The scaffold is planted, the structure is free!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: establishing a feature-based architecture and defining component folder structure for the web layer.
Linked Issues check ✅ Passed The PR satisfies all acceptance criteria from #34: directory skeleton created, web/AGENTS.md updated with new structure, existing app/ files untouched, and lint/build pass.
Out of Scope Changes check ✅ Passed All changes are directly aligned with establishing the feature-based architecture defined in #34; no out-of-scope modifications detected.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 34-feat-web-architecture

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@web/AGENTS.md`:
- Around line 27-30: The project structure documentation in the app/ section of
AGENTS.md is incomplete and does not reflect the route groups created by this
PR. Update the structure tree to include the newly created route groups
app/(auth)/ and app/(dashboard)/ along with their respective key files and
layouts. Ensure the documentation hierarchy clearly shows these route groups as
subdirectories under app/ so that anyone reading the document understands the
full scaffold structure established by this PR.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b78e0be2-2cf8-4cf5-a55f-d2079ad5f1b3

📥 Commits

Reviewing files that changed from the base of the PR and between 6c8a18a and 1573304.

📒 Files selected for processing (10)
  • web/AGENTS.md
  • web/app/(auth)/.gitkeep
  • web/app/(dashboard)/.gitkeep
  • web/components/common/.gitkeep
  • web/components/home/.gitkeep
  • web/components/layout/.gitkeep
  • web/components/ui/.gitkeep
  • web/features/.gitkeep
  • web/server/.gitkeep
  • web/types/.gitkeep

Comment thread web/AGENTS.md
@github-actions github-actions Bot added the area: backend Go REST API label Jun 23, 2026
@GRACENOBLE GRACENOBLE merged commit 47c348f into main Jun 23, 2026
4 checks passed
@GRACENOBLE GRACENOBLE deleted the 34-feat-web-architecture branch June 23, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: backend Go REST API area: web Next.js web app

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(web): establish feature-based architecture and component folder structure

1 participant