Loading…
Write precise TypeScript — generic constraints, conditional types, mapped types, template literal types, branded/nominal types, type narrowing, satisfies operator, and utility type composition. Use when asked about "TypeScript generics", "conditional type", "mapped type", "infer keyword", "branded type", "nominal typing", "template literal type", "satisfies", "utility types", "type narrowing", "discriminated union", "type predicate", "TypeScript strict mode", "keyof typeof", or "TypeScript advanced patterns". Do NOT use for: React-specific TypeScript — see frontend-patterns. Do NOT use for: API type generation — see api-design.
typescript-patterns is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. ## When to Use - Use when: types are too broad (`any`, `as unknown`, `as SomeType` casts) - Use when: building a reusable library or SDK that needs precise gene. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding typescript-patterns to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install yanacuti1121/Yana-AIReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
## When to Use - Use when: types are too broad (`any`, `as unknown`, `as SomeType` casts) - Use when: building a reusable library or SDK that needs precise generics - Use when: nee