Skip to content
BoldCreate

Project context and instruction files

Teach the BoldCreate CLI agent about your project and working preferences with Markdown instruction files.

You can give the assistant standing instructions, such as coding style or how to run tests, in plain Markdown files. BoldCreate reads applicable instruction files at the start of every message.

Which files are loaded

BoldCreate looks in several locations and loads instructions in this order. When files disagree, instructions loaded later take precedence.

OrderWhereFiles
1Your personal files~/.boldcreate/AGENTS.md, then ~/.claude/CLAUDE.md
2Each folder above your workspace, up to the Git root (root first)AGENTS.md, CLAUDE.md, .claude/CLAUDE.md
3Your workspace folderAGENTS.md, CLAUDE.md, .claude/CLAUDE.md
4Your workspace’s project instructions.github/copilot-instructions.md, .boldcreate/boldcreate-instructions.md
5Your workspace’s rule files.github/instructions/*.instructions.md, .cursor/rules/*.mdc

The parent-folder search matters in a monorepo. If you start BoldCreate in packages/api, the repository root’s AGENTS.md is loaded before the package’s own file.

AGENTS.md and CLAUDE.md files deeper inside your workspace (for example, src/db/AGENTS.md) aren’t loaded in full. BoldCreate is told they exist, with their first line, and reads them when it works in that folder.

Rule files that apply everywhere are loaded in full. A .github/instructions file with applyTo: "**" (or no applyTo) applies everywhere. A .cursor/rules file with alwaysApply: true also applies everywhere. Scoped rule files are listed with when they apply and read for matching files.

Empty files are skipped, and duplicate text is loaded only once. Files you already use with Claude Code, GitHub Copilot, or Cursor can work as they are.

Size limits

Instruction files are sent with every message, so each file is capped at about 24,000 characters and all instruction files together at about 64,000 characters. If the total limit is exceeded, BoldCreate mentions the path; the agent can still read that file when needed. Keep instructions short and focused.

Import other files

A line containing only @path/to/file.md is replaced with that file’s text, relative to the file containing the import. Imports work one level deep, up to 10 per file.

For example:

# Project guide
@docs/conventions.md
@docs/testing.md

See what was loaded

At session startup, the header lists the instruction files BoldCreate found. Press Ctrl+O to expand the header and see their full paths.

Write useful instructions

An AGENTS.md should give a new teammate the project information they need:

# AGENTS.md

## Project
TypeScript monorepo. API in packages/api, web app in apps/web.

## Commands
- Install: npm ci
- Test the API: npm test -w @acme/api

## Conventions
- Use TypeScript for new files.
- Add a test for each new endpoint.

## Don't
- Don't edit generated files in src/gen/.

Use exact commands and short, direct rules. Keep personal preferences in ~/.boldcreate/AGENTS.md and project facts in the repository’s AGENTS.md so your team can share them. For one session only, use --append-system-prompt.