Customize BIGGI
Customize BIGGI at the smallest scope that solves the problem. Project files are reviewable with the codebase; global configuration follows you across repositories.
Choose a customization
| Need | Use |
|---|---|
| Repository-wide conventions | AGENTS.md |
| Additional instruction files | Custom Instructions |
| Reusable behavior for a role | Custom Agents |
| A specialist a primary agent can invoke | Custom Subagents |
| Domain knowledge and a repeatable method | Skills |
| A user-invoked prompt template | Workflows |
| External tools or data | MCP or plugins |
| Durable project facts across sessions | Project Memory |
| Better search in a large repository | Codebase Indexing |
| Tool safety boundaries | Agent Permissions |
Project and global scope
Project customizations usually live under .biggi/ or in the repository root. Commit them when the whole project should use the same behavior.
Global runtime configuration lives under ~/.config/biggi/. Keep personal preferences, private provider setup, and cross-project agents there.
Keep instructions maintainable
- State the desired behavior, not a long history of why it exists.
- Use one source of truth for each rule.
- Prefer links to repository files over copying large reference material.
- Give custom agents narrow responsibilities and permissions.
- Test a workflow in a new session after changing instructions.
- Run BIGGI: Reload Config and Skills after editing configuration files.
The cloud-backed Marketplace is not part of the current release. Install or create local skills, plugins, workflows, and MCP configuration directly.