mcclowes/ai-aware-code-structure
Use when deciding how to organise code in an AI-assisted codebase — whether to split or merge a file, where to draw module boundaries, how big a file should get, whether to separate logic from rendering/styles/data, whether to use barrel/index re-export files, or where types and test files should live. Triggers on "should I split this file", "this file is getting too big", "separate concerns", "where should this code live", "are barrel files worth it", "central types file or co-locate", "colocate tests or a tests folder", reviewing or refactoring file/module organisation, structuring a new component or feature, or any architecture decision where part of the audience is an AI coding agent. Apply this whenever someone is choosing how to lay code out across files and an LLM will be reading or editing it, even if they only say "refactor this" or "clean up the structure" without mentioning AI.
83
87%
Does it follow best practices?
Impact
82%
1.54xAverage score across 9 eval scenarios
Passed
No known issues
criteria.jsonevals/scenario-3/
{
"context": "A tiny feature is split across view/logic/styles/types files. The criteria check whether the answer recognises the over-split smell for an AI-heavy codebase, names the cross-file-context problem, and still preserves genuinely isolatable splits rather than blanket-merging.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Concludes over-split, consolidate coupled pieces",
"description": "Concludes the layout is over-split for an AI-heavy codebase and recommends consolidating the tightly coupled pieces",
"max_score": 8
},
{
"name": "Identifies dumb-view-props smell",
"description": "Identifies the smell that the view's props are shaped by the sibling logic file, so an agent editing the view lacks context it won't fetch",
"max_score": 8
},
{
"name": "Keeps isolatable styles separate",
"description": "Keeps genuinely isolatable styles as a defensible separate file rather than blanket-merging everything",
"max_score": 6
}
]
}