Exodia Project Workflow

A comprehensive development workflow for building Exodia, a modern AI-powered tool for designing and automating call-for-projects responses with RAG (Retrieval-Augmented Generation) capabilities.

Project Overview

Exodia transforms call-for-projects management into a seamless, fast, and collaborative process with:

**Tech Stack**: Next.js, Supabase (PostgreSQL + Auth), TypeScript, pnpm, Tailwind CSS, shadcn/ui

Development Workflow

Phase 1: Planning (REQUIRED Before Coding)

1. **Enter Plan Mode** - Always start in plan mode to create a detailed implementation plan

2. **Write the Plan** - Save to `.claude/tasks/TASK_NAME.md` using checkboxes and headings

3. **Include in Plan**:

- Detailed implementation steps

- Reasoning behind architectural decisions

- Tasks broken down into small units

- Research on required packages/external knowledge (use Task tool)

- Think MVP - don't over-plan

4. **Request Review** - Ask for approval before implementing. Do NOT continue until approved

5. **Update Plan During Work** - Append detailed descriptions of changes for handover to other engineers

Phase 2: Test-Driven Development (TDD)

**Three Laws of TDD** (STRICTLY ENFORCED):

1. You shall not write code until you have written a failing test

2. You shall only write one new failing unit test at a time

3. You shall not write more code than is necessary to make the failing test pass

**TDD Cycle**:

1. Write a test that fails (code doesn't exist yet)

2. Write just enough code to make the test pass

3. Optimize the code without altering behavior

4. Repeat

**Testing Commands**:

```bash

pnpm test:coverage # Run tests with coverage report

pnpm test:ui # Run tests with UI

```

Phase 3: Implementation

**Before Committing**:

```bash

pnpm lint # Check linting

pnpm typecheck # Run TypeScript checks

```

**Documentation Requirements**:

Core Features by Epic

1. Project Management

2. Document Automation & RAG

3. Collaboration & Access Control

4. Notifications & Tracking

5. Security & Compliance

Architecture & Key Files

**Environment Management**:

**UI Design System**:

**Database**:

**Deployment**:

Contributing Workflow

1. Create feature branch from `main`

2. Write failing tests first (TDD)

3. Implement minimum code to pass tests

4. Run `pnpm lint` and `pnpm typecheck` before commits

5. Add/update documentation (max 250 lines per file in `.claude/docs/`)

6. Update `CLAUDE.md` in English if workflow changes

Important Constraints

Key Documentation Files

All documentation lives in `.claude/docs/`: