Enforce runtime safety for nullable values in TypeScript code.
npx skills add https://github.com/ViewableGravy/better-ecs --skill invariant
Please help me install this Agent Skill. Skill: invariant Source: https://github.com/ViewableGravy/better-ecs/tree/main/.github/skills/invariant Command: npx skills add https://github.com/ViewableGravy/better-ecs --skill invariant
This Skill enhances code reliability by replacing unsafe type-only assertions with robust runtime checks, ensuring that nullable values are handled correctly and preventing runtime errors.
invariant(value, "message") to assert that a value is not null or undefined at runtime, which also narrows its type in TypeScript.! and as operators with explicit runtime checks.invariant versus explicit guard clauses for values like 0, "", or false.Use the invariant skill to assert that the 'user' variable is not null or undefined.
High-intent search queries and answers about installing and using this skill.
You can enforce runtime type safety for nullable values by using `invariant` assertions. This mechanism checks value existence at runtime while simultaneously narrowing the TypeScript type, replacing unsafe non-null assertions and type casts.
For falsy values like `0`, `""`, or `false`, you should use explicit guard clauses instead of `invariant`. The `invariant` function is designed for values where falsy results are not expected to be valid states.
Yes, you can pass a nullable value directly to the `invariant` function when falsy values are not expected in your logic flow. This asserts the value is not null or undefined at runtime and narrows its type safely.
The best way to prevent runtime errors when fetching user data is to use `invariant(value, "message")`. This ensures the user object is present before accessing its properties, replacing dangerous type casts with robust runtime checks.
You should not use the `invariant` approach when your application logic considers falsy values like `0`, `""`, or `false` to be valid. In these edge cases, explicit guard clauses are necessary to avoid incorrectly throwing errors.
luyi985Explain TypeScript structural typing for assignability and interface design.
santoosaraujoDiagnose and repair failed quantitative trading backtests by analyzing metrics and signal engine code.
lambdalisueEnforce strict TypeScript conventions with type guards, interfaces, and null safety.
djankiesConvert TypeScript non-null assertions to optional chaining and type guards.