CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

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.

84

2.86x
Quality

88%

Does it follow best practices?

Impact

83%

2.86x

Average score across 9 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted, opinionated decision-guide: every heuristic is concrete and AI-specific rather than restating general refactoring wisdom, and the quick-reference table plus 'Applying this skill' section make it easy to act on. Weaknesses are mild — some narrative prose could be tightened, the heuristics are restated three times, and a worked example would raise actionability further.

Suggestions

Trim the narrative framing (e.g. the two-reader-to-three-reader setup and 'like pulling teeth' metaphor) and drop one of the three restatements of the heuristics — the prose section, the table, or 'Applying this skill' — to tighten conciseness.

Add a short worked example walking one real split decision through the 'understood in isolation?' test to push actionability toward fully executable guidance.

Consider moving the 'Three placement calls' detail (barrels, types, tests) into a reference file, which would shrink SKILL.md below the ~50-line threshold and enable top progressive-disclosure marks.

DimensionReasoningScore

Conciseness

Largely efficient, skill-specific guidance with no padding about basics Claude knows, but the narrative framing ('like pulling teeth', the two-reader-to-three-reader setup) and a third restatement of the heuristics in 'Applying this skill' are minor over-explanation that could be trimmed. Fits 'efficient; minor instances of over-explanation', not the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Concrete, specific guidance throughout: the isolation test, a ~300-line threshold, exact import forms ('@/components/Card'), the 'Foo.tsx next to Foo.test.tsx' convention, and a situation→action table. As an instruction-only skill this is actionable without code, but it stops short of fully copy-paste-ready examples, matching 'mostly executable guidance... with minor gaps'.

4 / 5

Workflow Clarity

'Applying this skill' gives clear per-scenario sequences (deciding, reviewing, structuring new) with the isolation test acting as an explicit checkpoint, and the quick-reference table serves as a checklist. No validation/error-recovery loops are present, so it does not reach the 5 anchor.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers, a summary table, and no external references — none are needed at this size. The rubric reserves 5 for sub-50-line skills or well-signaled one-level-deep references; at ~90 body lines this fits 'good structure; most content is appropriately placed' with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: comprehensive capability list, verbatim natural trigger phrases, and explicit what/when guidance in third-person voice. The only weakness is that a few catch-all triggers ('refactor this', 'any architecture decision') are broad enough to overlap with general refactoring skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — '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' — comprehensively covering the skill's scope.

5 / 5

Completeness

Explicitly answers both what ('how to organise code in an AI-assisted codebase' with enumerated decisions) and when ('Use when deciding how to organise code...', 'Apply this whenever someone is choosing how to lay code out across files and an LLM will be reading or editing it') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes natural phrases users would actually say ('should I split this file', 'this file is getting too big', 'separate concerns', 'where should this code live', 'are barrel files worth it', 'colocate tests or a tests folder') plus broader variants ('refactor this', 'clean up the structure'), giving comprehensive coverage with synonyms.

5 / 5

Distinctiveness Conflict Risk

The niche (code organisation where an AI agent is a reader) is clearly distinct, but broad triggers like 'refactor this', 'clean up the structure', and 'any architecture decision where part of the audience is an AI coding agent' create minor overlap risk with general refactoring and code-review skills. Fits 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict anchor at 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page