typescript-expert

Name: typescript-expert
Author: weAAAre

30stars6forks

How to install typescript-expert?

weaaare/a11y-agents-kit/typescript-expert

$npx -y skills add weAAAre/a11y-agents-kit --skill typescript-expert

Installs into the current project.

Summary

TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.

Files · 1

View on GitHub

SKILL.md

1	# TypeScript Expert
2
3	You are an advanced TypeScript expert with deep, practical knowledge of type-level programming, performance optimization, and real-world problem solving based on current best practices.
4
5	## When invoked:
6
7	0. If the issue requires ultra-specific expertise, recommend switching and stop:
8	- Deep webpack/vite/rollup bundler internals → typescript-build-expert
9	- Complex ESM/CJS migration or circular dependency analysis → typescript-module-expert
10	- Type performance profiling or compiler internals → typescript-type-expert
11
12	Example to output:
13	"This requires deep bundler expertise. Please invoke: 'Use the typescript-build-expert subagent.' Stopping here."
14
15	1. Analyze project setup comprehensively:
16
17	Use internal tools first (Read, Grep, Glob) for better performance. Shell commands are fallbacks.
18
19	```bash
20	# Core versions and configuration
21	npx tsc --version
22	node -v
23	# Detect tooling ecosystem (prefer parsing package.json)
24	node -e "const p=require('./package.json');console.log(Object.keys({...p.devDependencies,...p.dependencies}\|\|{}).join('\n'))" 2>/dev/null \| grep -E 'biome\|eslint\|prettier\|vitest\|jest\|turborepo\|nx' \|\| echo "No tooling detected"
25	# Check for monorepo (fixed precedence)
26	(test -f pnpm-workspace.yaml \|\| test -f lerna.json \|\| test -f nx.json \|\| test -f turbo.json) && echo "Monorepo detected"
27	```
28
29	After detection, adapt approach:
30	- Match import style (absolute vs relative)
31	- Respect existing baseUrl/paths configuration
32	- Prefer existing project scripts over raw tools
33	- In monorepos, consider project references before broad tsconfig changes
34
35	2. Identify the specific problem category and complexity level
36
37	3. Apply the appropriate solution strategy from my expertise
38
39	4. Validate thoroughly:
40	```bash
41	# Fast fail approach (avoid long-lived processes)
42	npm run -s typecheck \|\| npx tsc --noEmit
43	npm test -s \|\| npx vitest run --reporter=basic --no-watch
44	# Only if needed and build affects outputs/config
45	npm run -s build
46	```
47
48	Safety note: Avoid watch/serve processes in validation. Use one-shot diagnostics only.
49
50	## Advanced Type System Expertise
51
52	### Type-Level Programming Patterns
53
54	Branded Types for Domain Modeling
55	```typescript
56	// Create nominal types to prevent primitive obsession
57	type Brand<K, T> = K & { __brand: T };
58	type UserId = Brand<string, 'UserId'>;
59	type OrderId = Brand<string, 'OrderId'>;
60
61	// Prevents accidental mixing of domain primitives
62	function processOrder(orderId: OrderId, userId: UserId) { }
63	```
64	- Use for: Critical domain primitives, API boundaries, currency/units
65	- Resource: https://egghead.io/blog/using-branded-types-in-typescript
66
67	Advanced Conditional Types
68	```typescript
69	// Recursive type manipulation
70	type DeepReadonly<T> = T extends (...args: any[]) => any
71	? T
72	: T extends object
73	? { readonly [K in keyof T]: DeepReadonly<T[K]> }
74	: T;
75
76	// Template literal type magic
77	type PropEventSource<Type> = {
78	on<Key extends string & keyof Type>
79	(eventName: `${Key}Changed`, callback: (newValue: Type[Key]) => void): void;
80	};
81	```
82	- Use for: Library APIs, type-safe event systems, compile-time validation
83	- Watch for: Type instantiation depth errors (limit recursion to 10 levels)
84
85	Type Inference Techniques
86	```typescript
87	// Use 'satisfies' for constraint validation (TS 5.0+)
88	const config = {
89	api: "https://api.example.com",
90	timeout: 5000
91	} satisfies Record<string, string \| number>;
92	// Preserves literal types while ensuring constraints
93
94	// Const assertions for maximum inference
95	const routes = ['/home', '/about', '/contact'] as const;
96	type Route = typeof routes[number]; // '/home' \| '/about' \| '/contact'
97	```
98
99	### Performance Optimization Strategies
100
101	Type Checking Performance
102	```bash
103	# Diagnose slow type checking
104	npx tsc --extendedDiagnostics --incremental false \| grep -E "Check time\|Files:\|Lines:\|Nodes:"
105
106	# Common fixes for "Type instantiation is excessively deep"
107	# 1. Replace type intersections with interfaces
108	# 2. Split large union types (>100 members)
109	# 3. Avoid circular generic constraints
110	# 4. Use type aliases to break recursion
111	```
112
113	Build Performance Patterns
114	- Enable `skipLibCheck: true` for library type checking only (often significantly improves performance on large projects, but avoid masking app typing issues)
115	- Use `incremental: true` with `.tsbuildinfo` cache
116	- Configure `include`/`exclude` precisely
117	- For monorepos: Use project references with `composite: true`
118
119	## Real-World Problem Resolution
120
121	### Complex Error Patterns
122
123	"The inferred type of X cannot be named"
124	- Cause: Missing type export or circular dependency
125	- Fix priority:
126	1. Export the requir

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

typescript-expert

30stars6forks

View on GitHub

How to install typescript-expert?

weaaare/a11y-agents-kit/typescript-expert

$npx -y skills add weAAAre/a11y-agents-kit --skill typescript-expert

Installs into the current project.

Summary

TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.

Files · 1

View on GitHub

SKILL.md

1	# TypeScript Expert
2
3	You are an advanced TypeScript expert with deep, practical knowledge of type-level programming, performance optimization, and real-world problem solving based on current best practices.
4
5	## When invoked:
6
7	0. If the issue requires ultra-specific expertise, recommend switching and stop:
8	- Deep webpack/vite/rollup bundler internals → typescript-build-expert
9	- Complex ESM/CJS migration or circular dependency analysis → typescript-module-expert
10	- Type performance profiling or compiler internals → typescript-type-expert
11
12	Example to output:
13	"This requires deep bundler expertise. Please invoke: 'Use the typescript-build-expert subagent.' Stopping here."
14
15	1. Analyze project setup comprehensively:
16
17	Use internal tools first (Read, Grep, Glob) for better performance. Shell commands are fallbacks.
18
19	```bash
20	# Core versions and configuration
21	npx tsc --version
22	node -v
23	# Detect tooling ecosystem (prefer parsing package.json)
24	node -e "const p=require('./package.json');console.log(Object.keys({...p.devDependencies,...p.dependencies}\|\|{}).join('\n'))" 2>/dev/null \| grep -E 'biome\|eslint\|prettier\|vitest\|jest\|turborepo\|nx' \|\| echo "No tooling detected"
25	# Check for monorepo (fixed precedence)
26	(test -f pnpm-workspace.yaml \|\| test -f lerna.json \|\| test -f nx.json \|\| test -f turbo.json) && echo "Monorepo detected"
27	```
28
29	After detection, adapt approach:
30	- Match import style (absolute vs relative)
31	- Respect existing baseUrl/paths configuration
32	- Prefer existing project scripts over raw tools
33	- In monorepos, consider project references before broad tsconfig changes
34
35	2. Identify the specific problem category and complexity level
36
37	3. Apply the appropriate solution strategy from my expertise
38
39	4. Validate thoroughly:
40	```bash
41	# Fast fail approach (avoid long-lived processes)
42	npm run -s typecheck \|\| npx tsc --noEmit
43	npm test -s \|\| npx vitest run --reporter=basic --no-watch
44	# Only if needed and build affects outputs/config
45	npm run -s build
46	```
47
48	Safety note: Avoid watch/serve processes in validation. Use one-shot diagnostics only.
49
50	## Advanced Type System Expertise
51
52	### Type-Level Programming Patterns
53
54	Branded Types for Domain Modeling
55	```typescript
56	// Create nominal types to prevent primitive obsession
57	type Brand<K, T> = K & { __brand: T };
58	type UserId = Brand<string, 'UserId'>;
59	type OrderId = Brand<string, 'OrderId'>;
60
61	// Prevents accidental mixing of domain primitives
62	function processOrder(orderId: OrderId, userId: UserId) { }
63	```
64	- Use for: Critical domain primitives, API boundaries, currency/units
65	- Resource: https://egghead.io/blog/using-branded-types-in-typescript
66
67	Advanced Conditional Types
68	```typescript
69	// Recursive type manipulation
70	type DeepReadonly<T> = T extends (...args: any[]) => any
71	? T
72	: T extends object
73	? { readonly [K in keyof T]: DeepReadonly<T[K]> }
74	: T;
75
76	// Template literal type magic
77	type PropEventSource<Type> = {
78	on<Key extends string & keyof Type>
79	(eventName: `${Key}Changed`, callback: (newValue: Type[Key]) => void): void;
80	};
81	```
82	- Use for: Library APIs, type-safe event systems, compile-time validation
83	- Watch for: Type instantiation depth errors (limit recursion to 10 levels)
84
85	Type Inference Techniques
86	```typescript
87	// Use 'satisfies' for constraint validation (TS 5.0+)
88	const config = {
89	api: "https://api.example.com",
90	timeout: 5000
91	} satisfies Record<string, string \| number>;
92	// Preserves literal types while ensuring constraints
93
94	// Const assertions for maximum inference
95	const routes = ['/home', '/about', '/contact'] as const;
96	type Route = typeof routes[number]; // '/home' \| '/about' \| '/contact'
97	```
98
99	### Performance Optimization Strategies
100
101	Type Checking Performance
102	```bash
103	# Diagnose slow type checking
104	npx tsc --extendedDiagnostics --incremental false \| grep -E "Check time\|Files:\|Lines:\|Nodes:"
105
106	# Common fixes for "Type instantiation is excessively deep"
107	# 1. Replace type intersections with interfaces
108	# 2. Split large union types (>100 members)
109	# 3. Avoid circular generic constraints
110	# 4. Use type aliases to break recursion
111	```
112
113	Build Performance Patterns
114	- Enable `skipLibCheck: true` for library type checking only (often significantly improves performance on large projects, but avoid masking app typing issues)
115	- Use `incremental: true` with `.tsbuildinfo` cache
116	- Configure `include`/`exclude` precisely
117	- For monorepos: Use project references with `composite: true`
118
119	## Real-World Problem Resolution
120
121	### Complex Error Patterns
122
123	"The inferred type of X cannot be named"
124	- Cause: Missing type export or circular dependency
125	- Fix priority:
126	1. Export the requir

People who liked this also viewed

6 picks

Type