Introduce explicit TypeScript inference sites via currying and builder patterns.
npx skills add https://github.com/luyi985/lyi-bash --skill currying-inference
Please help me install this Agent Skill. Skill: currying-inference Source: https://github.com/luyi985/lyi-bash/tree/main/ai/skills/currying-inference Command: npx skills add https://github.com/luyi985/lyi-bash --skill currying-inference
Use when generic types aren't inferred. Use when builder patterns need better types. Use when creating new inference sites.
Define a curried or builder-based API to introduce inference points and then instantiate with a concrete type and endpoint.
High-intent search queries and answers about installing and using this skill.
TypeScript generic inference fails in chained API calls when there are insufficient inference sites for the compiler to bind types. Introducing currying or builder patterns creates explicit inference points, allowing the type checker to correctly propagate type information.
To fix generic type inference gaps using currying, define a curried helper that accepts a concrete type in the first parameter, creating an explicit inference site. This allows the returned function to yield correctly typed results with strong type safety.
The best way to propagate type information in a builder pattern API is to implement builder methods that expose specific inference points. This ensures strong type safety and maintainable inference progress throughout the chained construction process.
Yes, you can use factory helpers to improve TypeScript type safety in existing APIs. By providing factory functions that introduce new inference sites, you can ensure correct type binding where standard generic inference previously failed.
No, currying for TypeScript inference requires no external dependencies or components. It relies entirely on TypeScript's native generics system, using curried helpers and builder classes to manually establish the required inference sites.
You should not use currying to resolve TypeScript inference issues if your APIs cannot expose inference points via parameters or return curried functions. Without these explicit inference sites, the technique cannot ensure strong type safety.
StevenWXYEnforce TypeScript strict mode best practices for type-safe APIs and generics.
SufficientDaikonGenerate chainable, type-safe TypeScript builder APIs with reverse parsing.
ollieb89Implement advanced TypeScript type logic with generics and conditional types.
luyi985Identify and remove TypeScript type parameters that appear only once.
