Project settings

Per-project configuration. Opened from the sidebar by clicking the gear icon next to the project name, or by right-clicking the project.

Core fields

Field	Editable after creation	Notes
Name	✓	Human label. Changing it doesn't rename the folder
Folder path	✗	Fixed at creation; to change, create a new project and import
ID prefix	✓	Short identifier (e.g., `KAN`). Changing it affects new cards; existing cards keep their old prefix on their display ID
Color	✓	The coloured strip on every card
Next task number	✓	Counter for auto-incrementing task IDs. Usually auto-managed; edit if you need to jump (e.g., skip 13 for superstitious reasons)

Document paths

Ideafy auto-discovers markdown files in docs/ and the CLAUDE.md at the project root. You can override this with custom document paths — a list of relative paths the agent should be aware of as context.

When a document is registered here, you can mention it with @document in card chat, and Ideafy loads it into the agent's context.

Narrative

Narrative file path — defaults to docs/product-narrative.md. Points at the project's Product Narrative file, the living document the agent reads as context for every evaluate run.

Narrative mode — how the narrative was set up:

Create — Ideafy generated it through the interview
Existing — points at a file you wrote
Skip — no narrative; evaluate runs without project context
Skill — configured to be generated interactively via the product-narrative skill

You can change the mode later. Switching to Create re-runs the interview and overwrites the file. Switching to Existing lets you repoint at a different file.

Git worktrees

Use worktrees — toggle. Default on. When on, Ideafy creates a .worktrees/kanban/[PRJ-N-...] worktree for each card that goes into implementation. When off, all work happens on the project's main branch.

Turn off only if:

Your project setup breaks with worktrees (very rare)
You prefer the simpler single-branch flow and accept losing per-card isolation

Team assignment (Team edition)

Team — dropdown of teams you're a member of, plus a None option. Linking the project to a team enables pool sync — every card mutation fires a sync-card call to Supabase. See Team overview.

Unlinking (setting the dropdown back to None) keeps all local data, but stops pool sync for new mutations. Existing pool cards remain in the pool but won't update from your edits anymore.

MCP & Skills installation

A separate section for the one-click install operations:

Install Ideafy MCP — Writes the MCP server entry to .claude/settings.json in the project root (or platform equivalent). Hits POST /api/projects/[id]/mcp
Install Ideafy Skills — Copies ideafy.md, human-test.md, product-narrative.md into .claude/skills/. Hits POST /api/projects/[id]/skills
Install Hook — Adds the UserPromptSubmit hook to .claude/settings.json. Hits POST /api/projects/[id]/hook

Each has an Uninstall counterpart that reverses the operation. Uninstalling removes Ideafy's entries from the config files but leaves any other MCP servers, skills, or hooks you have.

Where settings live

Per-project settings are stored in rows of the SQLite projects table. Backed up along with the rest of the local database.

Prev: General settings Next: Team settings Up: User guide index