Team Style Guide
A minimal but complete set of code-style atoms for a TypeScript team. Encodes the rules, patterns, anti-patterns, principle, and one key trade-off that define how this team writes and reviews code.
$ aoe install @team/collection-team-style-guideProjection
Always in _index.xml · the agent never has to ask for this.
Team Style Guide [collection] v1.0.0
A minimal but complete set of code-style atoms for a TypeScript team. Encodes the rules, patterns, anti-patterns, principle, and one key trade-off that define how this team writes and reviews code.
Loaded when retrieval picks the atom as adjacent / supporting.
Team Style Guide [collection] v1.0.0
A minimal but complete set of code-style atoms for a TypeScript team. Encodes the rules, patterns, anti-patterns, principle, and one key trade-off that define how this team writes and reviews code.
Includes
- @team/rule-no-default-export
- @team/rule-explicit-return-types
- @team/rule-no-magic-numbers
- @team/rule-test-each-public-fn
- @team/pattern-result-type-over-throw
- @team/pattern-builder-over-options-bag
- @team/pattern-named-arguments
- @team/anti-pattern-god-class
- @team/anti-pattern-comment-explaining-bad-code
- @team/principle-readability-over-cleverness
- @team/tradeoff-strict-types-vs-iteration-speed
Target
claude-code
Entry Point
Start with @team/principle-readability-over-cleverness — it is the root
heuristic that all other atoms follow from.
The 4 rules are enforced by ESLint + CI; violations block merge.
The 3 patterns are the preferred solutions when their problem applies.
The 2 anti-patterns are actively detected in code review.
The tradeoff is surfaced explicitly so engineers don't have to rediscover it.
Loaded when retrieval picks the atom as a focal / direct hit.
Team Style Guide [collection] v1.0.0
A minimal but complete set of code-style atoms for a TypeScript team. Encodes the rules, patterns, anti-patterns, principle, and one key trade-off that define how this team writes and reviews code.
Includes
- @team/rule-no-default-export
- @team/rule-explicit-return-types
- @team/rule-no-magic-numbers
- @team/rule-test-each-public-fn
- @team/pattern-result-type-over-throw
- @team/pattern-builder-over-options-bag
- @team/pattern-named-arguments
- @team/anti-pattern-god-class
- @team/anti-pattern-comment-explaining-bad-code
- @team/principle-readability-over-cleverness
- @team/tradeoff-strict-types-vs-iteration-speed
Target
claude-code
Entry Point
Start with @team/principle-readability-over-cleverness — it is the root
heuristic that all other atoms follow from.
The 4 rules are enforced by ESLint + CI; violations block merge.
The 3 patterns are the preferred solutions when their problem applies.
The 2 anti-patterns are actively detected in code review.
The tradeoff is surfaced explicitly so engineers don't have to rediscover it.
Relations
related: [@team/principle-readability-over-cleverness, @team/tradeoff-strict-types-vs-iteration-speed] includes: [@team/rule-no-default-export, @team/rule-explicit-return-types, @team/rule-no-magic-numbers, @team/rule-test-each-public-fn, @team/pattern-result-type-over-throw, @team/pattern-builder-over-options-bag, @team/pattern-named-arguments, @team/anti-pattern-god-class, @team/anti-pattern-comment-explaining-bad-code, @team/principle-readability-over-cleverness, @team/tradeoff-strict-types-vs-iteration-speed]
Source
aoe-engine/examples/coding-style/primes/compiled/@team/collection-team-style-guide/atom.yaml