Merge pull request #72 from techdiary-dev/main

merge from prod(main)

Author: kingRayhan

.dev.vars

@@ -0,0 +1,75 @@
+name: Claude Code Review
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+    # Optional: Only run on specific file changes
+    # paths:
+    #   - "src/**/*.ts"
+    #   - "src/**/*.tsx"
+    #   - "src/**/*.js"
+    #   - "src/**/*.jsx"
+
+jobs:
+  claude-review:
+    # Optional: Filter by PR author
+    # if: |
+    #   github.event.pull_request.user.login == 'external-contributor' ||
+    #   github.event.pull_request.user.login == 'new-developer' ||
+    #   github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
+    
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code Review
+        id: claude-review
+        uses: anthropics/claude-code-action@beta
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          
+          # Optional: Specify model (defaults to Claude Sonnet 4, uncomment for Claude Opus 4)
+          # model: "claude-opus-4-20250514"
+          
+          # Direct prompt for automated review (no @claude mention needed)
+          direct_prompt: |
+            Please review this pull request and provide feedback on:
+            - Code quality and best practices
+            - Potential bugs or issues
+            - Performance considerations
+            - Security concerns
+            - Test coverage
+            
+            Be constructive and helpful in your feedback.
+          
+          # Optional: Customize review based on file types
+          # direct_prompt: |
+          #   Review this PR focusing on:
+          #   - For TypeScript files: Type safety and proper interface usage
+          #   - For API endpoints: Security, input validation, and error handling
+          #   - For React components: Performance, accessibility, and best practices
+          #   - For tests: Coverage, edge cases, and test quality
+          
+          # Optional: Different prompts for different authors
+          # direct_prompt: |
+          #   ${{ github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR' && 
+          #   'Welcome! Please review this PR from a first-time contributor. Be encouraging and provide detailed explanations for any suggestions.' ||
+          #   'Please provide a thorough code review focusing on our coding standards and best practices.' }}
+          
+          # Optional: Add specific tools for running tests or linting
+          # allowed_tools: "Bash(npm run test),Bash(npm run lint),Bash(npm run typecheck)"
+          
+          # Optional: Skip review for certain conditions
+          # if: |
+          #   !contains(github.event.pull_request.title, '[skip-review]') &&
+          #   !contains(github.event.pull_request.title, '[WIP]')
+

.github/persistence-context.md

@@ -0,0 +1,59 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@beta
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          
+          # Optional: Specify model (defaults to Claude Sonnet 4, uncomment for Claude Opus 4)
+          # model: "claude-opus-4-20250514"
+          
+          # Optional: Customize the trigger phrase (default: @claude)
+          # trigger_phrase: "/claude"
+          
+          # Optional: Trigger when specific user is assigned to an issue
+          # assignee_trigger: "claude-bot"
+          
+          # Optional: Allow Claude to run specific commands
+          # allowed_tools: "Bash(npm install),Bash(npm run build),Bash(npm run test:*),Bash(npm run lint:*)"
+          
+          # Optional: Add custom instructions for Claude to customize its behavior for your project
+          # custom_instructions: |
+          #   Follow our coding standards
+          #   Ensure all new code has tests
+          #   Use TypeScript for new files
+          
+          # Optional: Custom environment variables for Claude
+          # claude_env: |
+          #   NODE_ENV: test
+

.github/workflows/claude-code-review.yml

@@ -10,6 +10,7 @@ pnpm-lock.yaml
 bun.lockb
 bun.lock
 .yarn/install-state.gz
+package-lock.json
 
 # testing
 /coverage
@@ -32,10 +33,15 @@ yarn-error.log*
 
 # local env files
 .env*.local
+.env
+.dev.vars
 
 # vercel
 .vercel
 
 # typescript
 *.tsbuildinfo
 next-env.d.ts
+.vscode/mcp.json
+# Sentry Config File
+.env.sentry-build-plugin

.github/workflows/claude.yml

@@ -0,0 +1,142 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Development Commands
+
+### Development Server
+- `bun run dev` - Start development server with Turbo
+- Open http://localhost:3000 to view the application
+
+### Database Operations
+- `bun run db:generate` - Generate database migrations from schema changes
+- `bun run db:push` - Push schema changes to database
+- `bun run db:studio` - Open Drizzle Studio (database GUI)
+
+### Build & Deployment
+- `bun run build` - Build for production
+- `bun run start` - Start production server
+- `bun run lint` - Run ESLint checks
+
+### Backend Development
+- `bun run play` - Run backend playground script (`src/backend/play.ts`)
+
+## Architecture Overview
+
+### Technology Stack
+- **Frontend**: Next.js 15 (App Router), React 19, TypeScript
+- **Styling**: Tailwind CSS, shadcn/ui components
+- **Backend**: Next.js API routes, Drizzle ORM
+- **Database**: PostgreSQL
+- **Authentication**: GitHub OAuth
+- **Search**: MeilSearch
+- **File Storage**: Cloudinary
+- **State Management**: Jotai, React Hook Form with Zod validation
+
+### Backend & Database
+- **[SQLKit](https://github.com/sqlkit-dev/sqlkit)** - Very light sql query builder, we are using most of the sql query using this.
+- **[Drizzle ORM](https://orm.drizzle.team/)** - Awesome sql tool but we are only using for migration
+- **[PostgreSQL](https://www.postgresql.org/)** - Primary database
+- **[Next.js API Routes](https://nextjs.org/docs/api-routes/introduction)** - Backend API
+
+### Core Directory Structure
+
+#### Frontend (`/src/app/`)
+- Route groups using Next.js App Router:
+  - `(home)` - Main homepage and article feed
+  - `(dashboard-editor)` - Protected dashboard routes
+  - `[username]` - User profile pages
+  - `[username]/[articleHandle]` - Individual article pages
+- API routes in `/api/` for OAuth and development
+
+#### Backend (`/src/backend/`)
+- **Domain Models** (`/domain/`) - Core business logic entities
+- **Persistence** (`/persistence/`) - Database schemas and repositories
+- **Services** (`/services/`) - Business logic actions
+- **Input Validation** - Zod schemas for type-safe inputs
+
+#### Component Architecture (`/src/components/`)
+- **UI Components** - shadcn/ui based design system
+- **Feature Components** - Domain-specific (Editor, Navbar, etc.)
+- **Layout Components** - Page layouts and providers
+
+### Database Schema Architecture
+
+Key entities and their relationships:
+- **Users** - User profiles with social authentication
+- **Articles** - Blog posts with markdown content and metadata
+- **Series** - Article collections/sequences
+- **Comments** - Nested commenting system with resource association
+- **Tags** - Article categorization
+- **Bookmarks** - User content saving
+- **Reactions** - Emoji-based reactions (LOVE, FIRE, WOW, etc.)
+- **User Sessions** - Session management
+- **User Socials** - OAuth provider connections
+
+### Content Management
+- **Rich Text**: Markdoc for markdown parsing and rendering
+- **File Uploads**: Cloudinary integration for images/media
+- **Search**: MeilSearch for full-text search capabilities
+- **Internationalization**: Custom i18n implementation (Bengali/English)
+
+### State Management Patterns
+- **Server State**: Drizzle ORM with PostgreSQL
+- **Client State**: Jotai for global state management
+- **Form State**: React Hook Form with Zod validation
+- **Environment**: Type-safe environment variables with @t3-oss/env-nextjs
+
+## Required Environment Variables
+
+Server-side:
+- `DATABASE_URL` - PostgreSQL connection string
+- `GITHUB_CLIENT_ID` - GitHub OAuth client ID
+- `GITHUB_CLIENT_SECRET` - GitHub OAuth client secret
+- `GITHUB_CALLBACK_URL` - OAuth callback URL
+- `CLOUDINARY_URL` - Cloudinary configuration
+- `MEILISEARCH_ADMIN_API_KEY` - MeilSearch admin API key
+
+Client-side:
+- `NEXT_PUBLIC_MEILISEARCH_API_HOST` - MeilSearch API host URL
+- `NEXT_PUBLIC_MEILISEARCH_SEARCH_API_KEY` - MeilSearch search API key
+
+## Key Features Implementation
+
+### Authentication Flow
+- GitHub OAuth integration via `/api/auth/github`
+- User sessions managed in `userSessionsTable`
+- Social provider connections in `userSocialsTable`
+
+### Content Creation
+- Rich markdown editor with drag-and-drop support
+- Image upload and optimization via Cloudinary
+- Article series management for content organization
+- Tag-based categorization system
+
+### Search Implementation
+- MeilSearch for full-text search across articles
+- Search configuration and indexing handled in backend services
+- Client-side search interface with real-time results
+
+### Community Features
+- Nested commenting system with resource association
+- Emoji-based reactions (LOVE, FIRE, WOW, etc.)
+- User following and bookmarking functionality
+- Social sharing and user profiles
+
+## Development Workflow
+
+1. Database changes require running `bun run db:generate` followed by `bun run db:push`
+2. Backend logic testing can be done via `bun run play` playground script
+3. Type safety is enforced through Zod schemas for all inputs
+4. UI components follow shadcn/ui patterns and conventions
+5. All forms use React Hook Form with Zod validation schemas
+6. When querying data in component always use Tanstack Query.
+7. When interacting with DB, create a action in `src/backend/services` and use sqlkit package (https://github.com/sqlkit-dev/sqlkit)
+8. For Database schema reference look here for drizzle schema `src/backend/persistence/schemas.ts`
+
+## Special Considerations
+
+- **Bengali Language Support**: Custom font loading (Kohinoor Bangla) and i18n
+- **SEO Optimization**: Dynamic sitemaps, Open Graph tags, and schema markup
+- **Performance**: Next.js Image optimization, bundle splitting, and caching
+- **Security**: Input validation via Zod, secure OAuth flow, environment variable validation