Author here, 'the shape of a repository' refers to the structure/organization of files/directories, file naming conventions, unicode conventions (do not allow invisible Unicode for example), making sure build artifacts aren't committed, max file size, etc. Requiring files like LICENSE, README.md, etc exist. Anything about the structure/conventions of a repo that isn't actual code (a language specific linter should be used for the actual code).
Would be interested to hear what other kinds of conventions/rules you guys find useful to enforce for a repo, and how you currently do that.
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
2 comments of 3
[ 3.5 ms ] story [ 9.6 ms ] threadWould be interested to hear what other kinds of conventions/rules you guys find useful to enforce for a repo, and how you currently do that.
I hope that helps.