TypeScript Clean Code

Apply Robert C. Martin's Clean Code principles, adapted for idiomatic TypeScript, when writing, reviewing, or auditing TypeScript codebases.

Rule loading order

1. Read rules/clean-code-naming.md.
2. Read rules/clean-code-functions.md.
3. Read rules/clean-code-types-interfaces.md.
4. Read rules/clean-code-error-handling.md.
5. Read rules/clean-code-modules-organization.md.
6. Read rules/clean-code-testing.md.
7. Read rules/clean-code-comments-docs.md.
8. Read rules/clean-code-smells.md.
9. Use AGENTS.md as a compact summary plus pointer.

Enforcement policy

• Use recommendation-first language for style, naming, and organizational guidance.
• Use strict language (must / must not) only for type safety, error correctness, or runtime failure prevention.
• Prefer the official TypeScript documentation and handbook when resolving conflicts; update these rules when best practices evolve.