rbin-task-flow 1.7.0 → 1.9.0

package/.cursor/rules/coding_standards.mdc

@@ -91,6 +91,31 @@ In **front web** (Next.js, React) or **mobile** (Expo, React Native) projects, e
 
 The `app/` directory contains ONLY route definitions. Each file is a thin wrapper that imports and renders the feature page/screen.
 
+### Next.js App Router — Route groups in app/
+
+In **Next.js App Router** projects, organize `app/` with route groups:
+
+- **`(public)/`** — Public routes (login, signup, landing, etc.)
+- **`(private)/`** — Private routes (dashboard, profile, etc.; protect via layout or middleware)
+- **`(server)/`** — API / server routes (Route Handlers, e.g. `route.ts`)
+
+Example structure:
+
+```
+app/
+├── (public)/
+│   ├── login/page.tsx
+│   └── signup/page.tsx
+├── (private)/
+│   ├── dashboard/page.tsx
+│   └── admin/question/page.tsx
+├── (server)/
+│   └── api/
+│       └── .../route.ts
+├── layout.tsx
+└── ...
+```
+
 **Front-end (Next.js App Router or React):**
 ```typescript
 // src/app/(private)/dashboard/page.tsx
@@ -133,7 +158,7 @@ export class CreateSessionController {
 **Rules:**
 - **Front-end/Mobile**: `page.tsx` / route files NEVER contain logic, state, or imports beyond the feature component
 - **Backend**: `app/` contains controllers and validators only — no business logic
-- Group routes with `(public)` and `(private)` folders (front/mobile)
+- **Next.js App Router**: Use `(public)/` for public routes, `(private)/` for private routes, `(server)/` for API/Route Handlers. Other React front-ends and mobile may use only `(public)` and `(private)` as needed.
 - `layout.tsx` files may contain auth guards and providers
 - All business logic lives in `features/`
 
@@ -279,36 +304,78 @@ export function DashboardPage() {
 }
 ```
 
-### Components — Single Responsibility
+### Page-specific component naming (Front web & Mobile)
 
-Each component has a single responsibility. Components:
-- Receive data via props (no direct service calls unless truly necessary)
-- Are named after the feature: `[feature]-[description].tsx`
-- Stay small and focused
+When a component is specific to a page (lives under `features/[feature]/components/`), it must use the **page prefix** in the file name and in the function name.
+
+**File names (kebab-case):**
+- Page: `[page-name].page.tsx` → e.g. `admin-question.page.tsx`
+- Page-specific components: prefix = page name (no `.page`) → `admin-question-card.tsx`, `admin-question-card-item.tsx`
+- A **child component** of another component stays in the same `components/` folder (same level as parent) and **inherits the parent prefix**: `admin-question-card-item.tsx` (child of `admin-question-card.tsx`). No subfolders.
+
+**Function/component names (PascalCase):**
+- Route in `app/`: one word from route + page name → `AdminQuestion` (export default)
+- Page in features: page name + `Page` → `AdminQuestionPage`
+- Components: PascalCase of the file name → `AdminQuestionCard`, `AdminQuestionCardItem`
+
+| Location | File | Export name |
+|----------|------|-------------|
+| `app/(private)/admin/question/page.tsx` | (route file) | `AdminQuestion` (default) |
+| `features/admin/question/pages/admin-question.page.tsx` | `admin-question.page.tsx` | `AdminQuestionPage` |
+| `features/admin/question/components/admin-question-card.tsx` | `admin-question-card.tsx` | `AdminQuestionCard` |
+| `features/admin/question/components/admin-question-card-item.tsx` | `admin-question-card-item.tsx` | `AdminQuestionCardItem` |
 
 ```typescript
-// src/features/dashboard/components/dashboard-active-card.tsx
-import { Card } from '@/shared/components/card'
-import { Skeleton } from '@/shared/components/skeleton'
+// src/app/(private)/admin/question/page.tsx
+import { AdminQuestionPage } from '@/features/admin/question/pages/admin-question.page'
 
-type DashboardActiveCardProps = {
-  data?: { count: number; trials: number }
-  isLoading: boolean
-  isError: boolean
+export default function AdminQuestion() {
+  return <AdminQuestionPage />
 }
+```
 
-export function DashboardActiveCard({ data, isLoading, isError }: DashboardActiveCardProps) {
-  if (isLoading) return <Skeleton className="h-[200px]" />
-  if (isError) return <ErrorState />
+```typescript
+// src/features/admin/question/pages/admin-question.page.tsx
+'use client'
+
+import { AdminQuestionCard } from '@/features/admin/question/components/admin-question-card'
+
+export function AdminQuestionPage() {
+  return (
+    <section>
+      <AdminQuestionCard />
+    </section>
+  )
+}
+```
+
+```typescript
+// src/features/admin/question/components/admin-question-card.tsx
+import { AdminQuestionCardItem } from '@/features/admin/question/components/admin-question-card-item'
 
+export function AdminQuestionCard() {
   return (
-    <Card title="Active Members">
-      <p className="text-2xl font-bold">{data?.count}</p>
-    </Card>
+    <ul>
+      <AdminQuestionCardItem />
+    </ul>
   )
 }
 ```
 
+```typescript
+// src/features/admin/question/components/admin-question-card-item.tsx
+export function AdminQuestionCardItem() {
+  return <li>...</li>
+}
+```
+
+### Components — Single Responsibility
+
+Each component has a single responsibility. Components:
+- Receive data via props (no direct service calls unless truly necessary)
+- Follow the **page prefix** naming above when they are page-specific (inside a feature)
+- Stay small and focused; child components stay in the same `components/` folder with the inherited prefix in the name
+
 ---
 
 ## shared/ — Global Reusable Code
@@ -751,3 +818,4 @@ export const useAuth = () => useContext(AuthContext)
 9. **Shared is truly shared**: Only put in `shared/` what is used by 2+ features.
 10. **Naming reflects role**: File name + suffix must make the file's purpose immediately obvious.
 11. **No barrel files for re-exports**: Do not use `index.ts` (or `index.tsx`) only to re-export other modules. Import directly from the source file (e.g. `from '@/shared/components/button'` not `from '@/shared/components'`). An `index.ts` is only allowed when it contains real logic or composition, not mere re-exports.
+12. **Page-specific components use page prefix**: In features, the page file is `[page-name].page.tsx`; components specific to that page use the same prefix in file and function name (e.g. `admin-question-card.tsx` → `AdminQuestionCard`). Child components stay in the same `components/` folder and inherit the parent prefix (e.g. `admin-question-card-item.tsx` → `AdminQuestionCardItem`). App route exports `AdminQuestion`, feature page exports `AdminQuestionPage`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rbin-task-flow",
-  "version": "1.7.0",
+  "version": "1.9.0",
   "description": "AI-powered task management for Claude and Cursor",
   "main": "index.js",
   "bin": {