Problem
AGENTS.md, CLAUDE.md, and .github/copilot-instructions.md are approximately 95% identical (68 lines each). The only differences are the first paragraph and minor spec-reference phrasing specific to each target platform:
| File |
Target platform |
AGENTS.md |
Codex / generic agents |
CLAUDE.md |
Claude Code |
.github/copilot-instructions.md |
GitHub Copilot |
The shared body (Critical Rules, Development Commands, Package Structure, Go Conventions, Workflow) is fully generic to any rhiza-go project.
This means every fix to the shared body must be applied to three files, and downstream repos accumulate drift.
Suggestion
Template all three files from a single source with parameters for project name, description, and spec file path. The rhiza sync could generate/update these files, with the project-specific header injected from a config value (e.g. in .rhiza/.cfg.toml or template.yml).
Problem
AGENTS.md,CLAUDE.md, and.github/copilot-instructions.mdare approximately 95% identical (68 lines each). The only differences are the first paragraph and minor spec-reference phrasing specific to each target platform:AGENTS.mdCLAUDE.md.github/copilot-instructions.mdThe shared body (Critical Rules, Development Commands, Package Structure, Go Conventions, Workflow) is fully generic to any rhiza-go project.
This means every fix to the shared body must be applied to three files, and downstream repos accumulate drift.
Suggestion
Template all three files from a single source with parameters for project name, description, and spec file path. The rhiza sync could generate/update these files, with the project-specific header injected from a config value (e.g. in
.rhiza/.cfg.tomlortemplate.yml).