Configuration

Project Structure

After fp init, your project contains:

your-project/
├── FP_CLAUDE.md              # Agent workflow instructions
└── .fp/
    ├── config.toml           # Project config
    └── integrations.json     # Integration state

config.toml

The project configuration file. Key settings:

prefix = "FP"    # Issue ID prefix (e.g., FP-abcd)

integrations.json

Tracks the state of managed integrations (Claude, etc.):

• Install metadata and timestamps
• Managed resource hashes (for drift detection)
• Scope (project vs. user)
• Migration outcomes (e.g., legacy plugin removal)

Claude Integration Files

After fp setup claude, additional files are managed:

your-project/
├── .claude/
│   ├── skills/
│   │   ├── fp-plan/SKILL.md       # Planning skill
│   │   ├── fp-implement/SKILL.md  # Implementation skill
│   │   └── fp-review/SKILL.md     # Review skill
│   └── settings.local.json        # PostToolUse hook config
├── FP_CLAUDE.md                    # Workflow instructions
└── CLAUDE.md                       # Updated with @FP_CLAUDE.md ref

Multi-Agent Support

fp is designed to support multiple agent integrations. Current and planned:

Integration	Status	Managed Files
Claude Code	✅ Implemented	.claude/skills/*, .claude/settings.local.json
pi	🔜 Planned	.pi/extensions/
Codex	🔜 Planned	AGENTS.md
Cursor	🔜 Planned	.cursor/rules/*.mdc

What to Commit

Always commit:

• .fp/config.toml
• .fp/integrations.json
• FP_CLAUDE.md

Typically commit:

• .claude/skills/ (shared across team)
• .claude/settings.local.json (if project-scoped)

Never commit (stored globally):

• ~/.fiberplane/ (local issue data)