Hide Unsafe Type Assertions in Well-Typed Functions

Overview

Keep type signatures clean; hide assertions in implementations.

If a function needs a type assertion or any internally, that's OK - as long as the public signature is correct. Users see a well-typed API; the unsafe code is contained.

When to Use This Skill

• Function implementations need type assertions
• TypeScript can't follow your logic
• Wrapping libraries with poor types
• Internal complexity, clean external API

The Iron Rule