type-hunter-ts

Audit TypeScript type definitions for design debt and duplicated shapes.

5|Updated Jan 14, 2026

Search Tags:#typescript #types #code-maintainability #design-debt #type-derivation

Ready to run

npx skills add https://github.com/skyosev/agent-skills --skill type-hunter-ts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: type-hunter-ts
Source: https://github.com/skyosev/agent-skills/tree/main/hunter-party-ts/type-hunter-ts
Command: npx skills add https://github.com/skyosev/agent-skills --skill type-hunter-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit TypeScript type definitions for design debt — duplicated shapes, missing derivations, over-engineered generics, under-constrained type parameters, reinvented utility types, and disorganized type architecture. Type structure and maintainability, not type enforcement.

Core Features & Use Cases

Derivation-first type design: promote deriving related types with Pick, Omit, Partial, and intersection types instead of duplicating shapes.
Detect over-engineering and drift: surface overly complex generics, redundant utilities, and scattered type architecture.
Growth-aware maintainability: provide actionable guidance after rapid development to reorganize scattered type architecture.

Quick Start

Audit your TypeScript project to surface duplicated shapes, under-constrained generics, and disorganized type architecture, and propose canonical derivations.

Frequently Asked Questions about type-hunter-ts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit TypeScript types for design debt and duplicated shapes?▼

TypeScript design debt includes duplicated shapes, missing type derivations, over-engineered generics, and reinvented utility types. It occurs when type definitions drift during rapid development, leading to scattered architecture and duplicated structures instead of using standard derivations like Pick, Omit, and Partial.

How do I reduce over-engineered generics and consolidate TypeScript types in a monorepo?▼

To reduce over-engineered generics in a TypeScript monorepo, surface under-constrained type parameters and redundant utilities, then consolidate type logic. Focus on a derivation-first design approach to minimize hand-rolled utilities and reorganize scattered type architecture for better maintainability.

What is the best way to derive related TypeScript types instead of duplicating shapes?▼

The best way to derive related TypeScript types is applying standard utilities like Pick, Omit, Partial, and intersection types. This derivation-first approach prevents shape duplication, reduces design debt, and ensures related structures stay synchronized without hand-rolling redundant definitions.

Can I audit type architecture and enforce tight generics constraints in complex modules?▼

Yes, you can audit type architecture in complex modules to enforce tight generics constraints and minimize hand-rolled type utilities. The process surfaces under-constrained type parameters and disorganized structures, providing actionable guidance to consolidate and simplify type logic.

When should I not use derivation-first type design for TypeScript maintainability?▼

Derivation-first type design may not suit simple modules with minimal type logic where standard utilities like Pick and Omit add unnecessary indirection. If the type architecture lacks complex generics or duplicated shapes, forcing derivations can over-engineer straightforward definitions.