skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
poteto/noodle185 installs

ts-best-practices

TypeScript type safety guidelines for writing maximally type-safe code. Apply these patterns when writing or reviewing any TypeScript: discriminated unions, type narrowing, type guards, exhaustiveness checks, avoiding `as` casts, preferring `unknown` over `any`, and making impossible states unrepresentable. Use this skill whenever writing TypeScript code, reviewing TypeScript for type safety issues, or when the user mentions type safety, type narrowing, discriminated unions, or asks to make types stricter/more explicit.

How do I install this agent skill?

npx skills add https://github.com/poteto/noodle --skill ts-best-practices
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides standard TypeScript type safety guidelines and code examples. No security issues were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

What does this agent skill do?

Type Safety

This project's TypeScript policy. Apply when writing or reviewing TypeScript.

RuleSummary
No as castsEvery as is a potential runtime crash. Validate at boundaries, then cast only if earned. Prefer Zod/Valibot over manual validation.
unknown over anyany disables type checking for everything it touches. External data is always unknown.
Discriminated unionsModel variants with a shared literal discriminant. No optional-field bags.
Narrowing hierarchyPrefer: discriminated union switch > in operator > typeof/instanceof > type guard > as
Type guardsMust actually verify the claim. Name them isX or hasX. Prefer discriminant narrowing when possible.
Exhaustiveness checksAlways add default: never arm to switches over discriminated unions. Use an absurd() helper to reduce boilerplate.
satisfies over asWhen verifying a value matches a type without widening, use satisfies to preserve literal types.
Impossible statesIf a bug requires asking "can this combination happen?" the type is too loose. Tighten it.

Read references/patterns.md for code examples of each rule.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/poteto/noodle/ts-best-practices">View ts-best-practices on skillZs</a>