Not sure if this is in relation to traditional/manual codebases or if we are talking about one where AI agents contribute heavily.
In my own agentic flow I prioritize:
- Directories:
- /plan - it contains every implementation plan and test scenarios for every new major feature.
- /test - with Unit and BDD tests files and scripts
-/Docs - ofcourse all documentation
- Agent or Claude.md + Plan.md that serves as roadmap - NON NEGOTIABLE
- Others: Zod, Monorepo, git etc and other engineering/architecture good practices
- CI/CD
This is for both manual/human and agentic codebases. Many/most repos already have conventions/rules which are somewhat implicit and only enforced manually via code reviews. In repos that heavily use agents/AI I feel that having some sort of strict and deterministic enforcement is even more useful - AGENTS.md works pretty well, but it is not deterministic or actually enforced in any way - agents can ignore or forget about what AGENTS.md says, and this becomes more and more apparent as a repo grows - the conventions are slowly and incrementally violated, incorrectly placed/named/structured files compound and confuse the agent more and more - the mess keeps growing. alint does integrate and play well with AGENTS.md - it can export the ruleset it defines into AGENTS.md in a agent-friendly/readable way. It can also explain a deterministic rule to an agent and help it figure out how to fix a violation.
Comments
Not sure if this is in relation to traditional/manual codebases or if we are talking about one where AI agents contribute heavily. In my own agentic flow I prioritize: - Directories: - /plan - it contains every implementation plan and test scenarios for every new major feature. - /test - with Unit and BDD tests files and scripts -/Docs - ofcourse all documentation - Agent or Claude.md + Plan.md that serves as roadmap - NON NEGOTIABLE - Others: Zod, Monorepo, git etc and other engineering/architecture good practices - CI/CD
I hope that helps.
This is for both manual/human and agentic codebases. Many/most repos already have conventions/rules which are somewhat implicit and only enforced manually via code reviews. In repos that heavily use agents/AI I feel that having some sort of strict and deterministic enforcement is even more useful - AGENTS.md works pretty well, but it is not deterministic or actually enforced in any way - agents can ignore or forget about what AGENTS.md says, and this becomes more and more apparent as a repo grows - the conventions are slowly and incrementally violated, incorrectly placed/named/structured files compound and confuse the agent more and more - the mess keeps growing. alint does integrate and play well with AGENTS.md - it can export the ruleset it defines into AGENTS.md in a agent-friendly/readable way. It can also explain a deterministic rule to an agent and help it figure out how to fix a violation.