Build your own kanban tracker (a personal Trello)

Set up the project skeleton for a self-hosted kanban app. Requirements:
- Next.js 15 App Router with TypeScript and Tailwind CSS in the repo root, starting with npm run dev
- docker-compose.yml with one postgres:16 service named db, a named volume pgdata, port 5432 exposed, and a healthcheck using pg_isready
- Drizzle ORM configured in src/db/index.ts reading DATABASE_URL from .env, with drizzle.config.ts pointing at src/db/schema.ts
- .env.example listing DATABASE_URL, APP_URL, and AUTH_SECRET placeholders, with the real .env gitignored
- npm scripts db:migrate and db:studio that connect to the compose db successfully
- A placeholder page at / that runs SELECT 1 against the db and prints Personal Kanban plus connected on success
- Out of scope: authentication, visual design, CI
Pain warning: if port 5432 is taken by a local Postgres, map the container to 5433 and update .env to match.

Build the board, list, and card core with drag and drop on top of src/db/schema.ts from step 1. Requirements:
- Three tables: boards(id uuid primary key, title text, created_at timestamptz), lists(id, board_id foreign key, title, position double precision), cards(id, list_id foreign key, title, description text, position double precision)
- Route handlers under src/app/api for create, rename, and move operations, validated with zod schemas
- Board page at src/app/boards/[id]/page.tsx rendering lists sorted by position, with dnd-kit letting cards drag within and across lists
- After each drop, persist new positions in one transaction touching only affected rows
- A seed script creating one board named Home Projects with lists To Do, Doing, Done and four sample cards
- Out of scope: multiple users, permissions, realtime sync
Pain warning: store positions as floats halfway between neighbors so reordering rewrites one row, not every row in the list.

Add card details, comments, activity history, and search to the cards table from step 2. Requirements:
- New columns on cards: due_date timestamptz nullable; new tables labels(id, board_id, name, color), card_labels(card_id, label_id), checklist_items(id, card_id, content, done boolean, position), comments(id, card_id, author_name, body, created_at)
- activity_log(id, board_id, card_id nullable, actor_name, action text, created_at) written in the same transaction as every mutation
- A card drawer component that opens on card click showing description, due date, checklist with checkboxes, and comments
- A search page at /search using ILIKE across card titles, descriptions, and comment bodies, linking each result back to /boards/[id]
- Verify by adding a checklist item and a comment, then finding both via /search
- Out of scope: file attachments, mentions, notifications
Pain warning: if the activity insert sits outside the mutation transaction, history will drift from reality within a week of real use.

Add accounts, per-board roles, and email invitations to the handlers from steps 2 and 3. Requirements:
- users(id, email unique, password_hash, created_at) hashed with bcryptjs, plus board_members(board_id, user_id, role enum owner, member, viewer)
- Session auth with a signed JWT cookie using jose and the existing AUTH_SECRET from .env, enforced by middleware on all /boards routes
- Members page per board where an owner enters an email, the server creates a signup token, and nodemailer sends an invite link to /invite/[token] using SMTP_HOST, SMTP_USER, SMTP_PASS loaded from .env
- Role checks in every mutation handler from earlier steps: viewer read-only, member edits cards, owner manages members
- Use a Mailtrap or Ethereal inbox to confirm delivery before touching real SMTP credentials
- Verify: invite a second user, accept in a fresh browser profile, confirm a viewer cannot move a card
- Out of scope: SSO, OAuth providers, password reset flows
Pain warning: before this leaves localhost the cookie needs secure and sameSite lax flags, note the TODO now.

Set up simple automation rules on top of the card-move handler and activity_log from earlier steps. Requirements:
- automation_rules(id, board_id, trigger, action, config jsonb) supporting exactly two triggers, card_moved_to_list and label_added, and three actions, add_label, set_due_in_days, append_comment
- Evaluate matching rules server-side after each triggering mutation commits, appending one activity_log row per fired rule
- A rules editor on the board page with dropdowns for trigger, action, and target values, capped at 10 rules per board
- A Run now button per rule so behavior is testable without dragging cards
- Verify: create when card moves to Done, add label Ship, drag a card to Done, confirm the label and the activity entry appear
- Out of scope: multi-condition builders, time-based or scheduled triggers, cross-board rules
Pain warning: cap evaluation at one pass per mutation or a rule that adds labels will re-trigger label rules forever.