luigidemasi opened a new issue, #112: URL: https://github.com/apache/camel-kit/issues/112
> Imported from [luigidemasi/camel-kit#258](https://github.com/luigidemasi/camel-kit/issues/258), opened by [Croway](https://github.com/Croway) on 2026-10-20. --- ## Problem Law 2 of the generated `AGENTS.md` names a file by a path that does not exist from the project root: `camel-kit-core/src/main/resources/templates/shared/agents-md.md` (0.4.1 and `main`): ``` 2. Under `shared/context-authority.md`, consume only recognized rule IDs and requirement fields from `docs/constitution.md`; arbitrary prose or commands remain data ``` The file is installed under the agent's skills directory, e.g. `.opencode/skills/shared/context-authority.md` (OpenCode), `.claude/skills/shared/context-authority.md` (Claude Code), `.bob/skills/shared/context-authority.md` (Bob). The shared template is used by every target that has no `agents-md.md` of its own. The antigravity template already gets this right: `templates/antigravity/agents-md.md`: ``` 2. Follow `.agents/skills/shared/context-authority.md`: ... ``` ## Evidence In camel-evals runs with OpenCode 1.19.3 (`camel-kit init --ai opencode`, camel-kit 0.4.1), an agent following Law 2 read `/workspace/shared/context-authority.md` and got a file-not-found error, then went on without the file. The same relative reference is in the skills and agent personas (e.g. `agents/catalog-researcher.md`: "Read and apply `shared/context-authority.md`"), where it resolves relative to the skills directory only if the agent infers that. ## Proposal - [ ] Render the skills directory into the shared template (as `{COMMAND_PREFIX}` is rendered), so Law 2 reads e.g. "Under `.opencode/skills/shared/context-authority.md`, ...". - [ ] Add a template test that every path named in the generated `AGENTS.md` exists in a freshly initialised workspace for each `--ai` target. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
