Trello

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me kanban boards that replace Trello: lists of cards you drag across, simple enough to use for anything.

STACK
- Node 20+ with Fastify, server-rendered HTML with vanilla JS for the dragging
- SQLite through better-sqlite3, WAL mode, with FTS5
- WebSockets for live updates
- A PWA, because a good share of card-shuffling happens on a phone
- Caddy in front

THE DATA MODEL
- boards: id, workspace_id, name, description, background_json, is_closed, visibility, created_at
- lists: id, board_id, name, position, is_archived
- cards: id, list_id, title, description_md, position, due_at, due_reminder_minutes, start_at, is_complete, cover_json, is_archived, created_at, updated_at
- labels: id, board_id, name, colour; card_labels
- members, card_members, checklists, checklist_items
- comments: id, card_id, author_id, body_md, created_at, edited_at
- attachments: id, card_id, kind, path_or_url, sha256, bytes, mime, thumb_path
- activity: id, board_id, card_id, actor_id, action, payload_json, at — append-only, and what makes a card's history readable
- automations: id, board_id, trigger_json, conditions_json, actions_json, is_active
- automation_runs: id, automation_id, card_id, status, error, at

POSITION, WHICH IS THE UNGLAMOROUS HEART OF IT
- Ordering by a float between neighbours is the obvious approach and it fails: after enough drags the gaps run out of precision and cards start swapping places by themselves
- Use fractional indexing over strings, or integers with a rebalance when the gap closes. Either way, decide now and test it by dragging one card between two others five hundred times
- Moving a card is one write, not a renumbering of the list. That is what makes it feel instant on a phone with a poor connection

DRAGGING
- Pointer events, so mouse and touch are one code path
- Optimistic: the card moves immediately and the server confirms. A rejected move animates back with a reason
- Auto-scroll when dragging near an edge, and a drop indicator that shows exactly where it will land
- Fully operable without dragging: keyboard shortcuts and a move dialogue. Drag-and-drop with no alternative excludes anybody who cannot use a pointer precisely, which is a lot of people

LIVE UPDATES
- WebSocket per board, broadcasting after the write commits, never before
- Each change carries a client identifier so your own optimistic move is reconciled rather than duplicated
- On reconnect, ask for everything since the last known change and apply it in order
- Presence: who else is looking at this board, which is enough. Cursors on a kanban board are noise

THE CARD
- Title, description in Markdown, labels, members, due date with a reminder, checklists, attachments, comments
- The activity feed and the comments interleaved in one readable history
- A checklist item can be converted into its own card, which is the most-used small feature in this category
- Attachments stored by hash with the type from content, images thumbnailed, EXIF stripped

VIEWS
- The board, and a list view for people who want a table
- A calendar view over due dates
- Filters by label, member, due state and text, with the filter in the URL so it can be shared
- Search across cards with FTS5, respecting permissions inside the query
- Archive rather than delete, with a restore

AUTOMATION
- Triggers: a card moved into a list, a due date arriving, a label added, a checklist completed, or a schedule
- Actions: move, assign, add a label, set a due date, post a comment, call a webhook
- Conditions to narrow it
- Every run recorded with its result. An automation that silently does nothing is worse than none
- Keep it small. Three triggers people understand beat twenty they do not

PERMISSIONS
- Workspace members, board members, and observers who can read and comment
- Public boards by link, read-only, which is genuinely useful for a roadmap
- Checked on the server for every read and write, including in search

NOTIFICATIONS
- Mentions and assignments immediately, everything else batched into a digest
- Due-date reminders at the configured offset, recorded so nobody is reminded twice
- Email always, push where the platform allows

OPERATIONS
- .env: DATABASE_PATH, STORAGE_PATH, BASE_URL, SESSION_SECRET, SMTP_URL, VAPID keys
- Migrations on boot, each once
- The WebSocket layer in its own process
- Nightly backup off the machine, restore script
- Health endpoint

WHAT MATTERS MOST
Ordering and the mobile drag. Get fractional positions right and make dragging work properly with a thumb on a phone, then use it for a real project for a fortnight. The whole appeal of this product is that it is simple and it feels good to use, and both of those live entirely in those two things.

Give me the repository, the PWA, migrations, .env.example, a seed board, and a README with deploy steps behind Caddy.