Skip to main content
Charlie reads instructions from AGENTS.md. For most teams, the best setup is a single root-level AGENTS.md that defines your default operating rules for planning, coding, reviews, and communication.

​
Instructions template

Use this compact template and keep rules stable over time: 
# <Section Title>

## Scope
- Paths, packages, or contexts this section applies to.

## Context
- Team- or domain-specific background Charlie should know.

## Rules
- [R1] <Clear imperative rule>
- [R2] <Clear imperative rule>
- [R3] <Clear imperative rule>

## Examples

### Good
- [R1]
```ts
// minimal example
```

### Bad
- [R2]
```ts
// anti-pattern
```

​
Instructions vs. skills

  • Instructions (AGENTS.md) define persistent policy and defaults.
  • Skills (.agents/skills/*/SKILL.md) define reusable task-shaped playbooks you invoke with $<skill-name>.
Use instructions for durable rules. Use skills for repeatable workflows.

​
Common mistakes to avoid

  • Putting task-by-task checklists in AGENTS.md (that belongs in skills).
  • Duplicating the same rule across multiple files.
  • Writing vague guidance without a default action.