
Enforcing Typescript Standards
This is the kind of skill you want running on every TypeScript file you touch. It enforces explicit return types, keeps imports organized by source type, orders class members consistently, and pushes you toward type guards instead of type assertions. The opinionated parts are good: it prefers `??` over `||`, bans nested functions, wants immutability over mutation, and tells you to stop mocking everything in tests. It also has strong opinions on comments, basically saying delete anything that just restates what the code already shows. If you're working on a team or just want to stop bikeshedding style decisions, this codifies a solid set of conventions that lean toward safety and readability without being dogmatic.
- skills.sh installs
- 168
- GitHub stars
- 1
- last updated
- Jun 3, 2026
Install
$ npx -y skills add jgeurts/eslint-config-decent --skill enforcing-typescript-standards --agent claude-codeInstalls into .claude/skills of the current project.
Files
Enforcing TypeScript Standards
Enforces the project's core TypeScript standards including explicit typing, import organization, class member ordering, and code safety rules.
Triggers
Activate this skill when the user says or implies any of these:
- "write", "create", "implement", "add", "build" (new TypeScript code)
- "fix", "update", "change", "modify", "refactor" (existing TypeScript code)
- "review", "check", "improve", "clean up" (code quality)
- Any request involving
.tsor.tsxfiles
Specific triggers:
- Creating a new
.tsor.tsxfile - Modifying existing TypeScript code
- Reviewing TypeScript code for compliance
Core Standards
Type Safety
Sponsors
Details
- Repository
- github.com/jgeurts/eslint-config-decent
- First seen
- Jun 3, 2026