typescript-best-practices
Idiomatic TypeScript patterns for clean, maintainable code.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
TypeScript Best Practices
Priority: P1 (OPERATIONAL)
Implementation Guidelines
-
Naming: Classes/Types=
PascalCase, vars/funcs=camelCase, consts=UPPER_SNAKE. PrefixIonly if needed. - Functions: Arrows for callbacks; regular for exports. Always type public API returns.
- Modules: Named exports only. Import order: external → internal → relative.
-
Async: Use
async/await, not raw Promises.Promise.all()for parallel. -
Classes: Explicit access modifiers. Favor composition. Use
readonly. -
Types: Use
neverfor exhaustiveness,assertsfor runtime checks. -
Optional: Use
?:, not| undefined. -
Imports: Use
import typefor tree-shaking.
Anti-Patterns
- No Default Exports: Use named exports.
- No Implicit Returns: Specify return types.
-
No Unused Variables: Enable
noUnusedLocals. -
No
require: Use ES6import. -
No Empty Interfaces: Use
typeor non-empty interface. -
Use any: Never use
any, useunknownonly when necessary.
Reference & Examples
See references/examples.md for code samples including:
- Immutable Interfaces
- Exhaustiveness Checking
- Assertion Functions
- Dependency Injection Patterns
- Import Organization
Related Topics
language | tooling | security
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-01-20
- 索引更新时间
- 2026-01-26
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!