You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The instructions file is loaded and passed to the coder's instruction handling mechanism. Each coder will use these instructions according to its own configuration:
59
+
60
+
-**Claude**: Instructions are written to `CLAUDE.md`
61
+
-**Goose**: Instructions are written to `.goosehints`
62
+
-**Gemini**: Instructions are written to `GEMINI.md`
63
+
-**Other coders**: Check the specific coder documentation
64
+
65
+
Example instructions file:
66
+
67
+
```markdown
68
+
# Custom Instructions
69
+
70
+
You are an expert Python developer following these guidelines:
71
+
1. Use type hints for all functions
72
+
2. Write comprehensive docstrings
73
+
3. Follow PEP 8 style guidelines
74
+
4. Include unit tests for all new functions
75
+
```
76
+
77
+
You can combine instructions with other configuration options:
78
+
79
+
```bash
80
+
metacoder "Refactor this code" \
81
+
--coder claude \
82
+
--instructions style_guide.md \
83
+
--config claude_config.yaml \
84
+
--mcp-collection tools.yaml
85
+
```
86
+
50
87
## Environment Variables
51
88
52
89
Config files support environment variable expansion:
0 commit comments