d4f5c5b16f
Replace the agent framework codebase with a new monorepo structure for an AI-native Linear-like product where agents are first-class citizens. New architecture: - server/ — Go backend (Chi + gorilla/websocket + sqlc) - API server with REST routes for issues, agents, inbox, workspaces - WebSocket hub for real-time updates - Local daemon entry point for agent runtime connection - PostgreSQL migration with 13 tables (issue, agent, inbox, etc.) - WebSocket protocol types for server<->daemon communication - apps/web/ — Next.js 16 frontend - Dashboard layout with sidebar navigation - Route skeleton: inbox, issues, agents, board, settings - packages/ui/ — Preserved shadcn/ui design system (26+ components) - packages/types/ — Full API contract types (Issue, Agent, Workspace, Inbox, Events) - packages/sdk/ — REST ApiClient + WebSocket WSClient - packages/store/ — Zustand stores (issue, agent, inbox, auth) - packages/hooks/ — React hooks (useIssues, useAgents, useInbox, useRealtime) - packages/utils/ — Shared utilities Removed: apps/cli, apps/desktop, apps/mobile, apps/gateway, packages/core, skills/, and all agent-framework code. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
73 lines
2 KiB
Markdown
73 lines
2 KiB
Markdown
# CLAUDE.md
|
|
|
|
This file gives coding agents high-signal guidance for this repository.
|
|
|
|
## 1. Project Context
|
|
|
|
Multica is an AI-native task management platform — like Linear, but with AI agents as first-class citizens.
|
|
|
|
- Agents can be assigned issues, create issues, comment, and change status
|
|
- Supports local (daemon) and cloud agent runtimes
|
|
- Built for 2-10 person AI-native teams
|
|
|
|
## 2. Architecture
|
|
|
|
**Polyglot monorepo** — Go backend + TypeScript frontend.
|
|
|
|
- `server/` — Go backend (Chi + sqlc + gorilla/websocket)
|
|
- `apps/web/` — Next.js 16 frontend
|
|
- `packages/` — Shared TypeScript packages (ui, types, sdk, store, hooks, utils)
|
|
|
|
## 3. Core Workflow Commands
|
|
|
|
```bash
|
|
# Frontend
|
|
pnpm install
|
|
pnpm dev:web # Next.js dev server
|
|
pnpm build # Build all TS packages
|
|
pnpm typecheck # TypeScript check
|
|
pnpm test # TS tests
|
|
|
|
# Backend (Go)
|
|
make dev # Run Go server with hot-reload
|
|
make daemon # Run local daemon
|
|
make test # Go tests
|
|
make sqlc # Regenerate sqlc code
|
|
make migrate-up # Run database migrations
|
|
make migrate-down # Rollback migrations
|
|
|
|
# Infrastructure
|
|
docker compose up -d # Start PostgreSQL
|
|
```
|
|
|
|
## 4. Coding Rules
|
|
|
|
- TypeScript strict mode is enabled; keep types explicit.
|
|
- Go code follows standard Go conventions (gofmt, go vet).
|
|
- Keep comments in code **English only**.
|
|
- Prefer existing patterns/components over introducing parallel abstractions.
|
|
- Avoid broad refactors unless required by the task.
|
|
|
|
## 5. Testing Rules
|
|
|
|
- **TypeScript**: Vitest. Mock external/third-party dependencies only.
|
|
- **Go**: Standard `go test`. Use testcontainers or test database for DB tests.
|
|
|
|
## 6. Commit Rules
|
|
|
|
- Use atomic commits grouped by logical intent.
|
|
- Conventional format:
|
|
- `feat(scope): ...`
|
|
- `fix(scope): ...`
|
|
- `refactor(scope): ...`
|
|
- `docs: ...`
|
|
- `test(scope): ...`
|
|
- `chore(scope): ...`
|
|
|
|
## 7. Minimum Pre-Push Checks
|
|
|
|
```bash
|
|
pnpm typecheck
|
|
pnpm test
|
|
make test
|
|
```
|