How to use the TypeScript Pro agent skill (typescript-pro)

What the TypeScript Pro skill makes the agent do

Once installed, the agent follows a TypeScript-focused workflow: it reviews your tsconfig and type coverage, designs type-first APIs with branded types and generics, implements type guards and discriminated unions, and then runs tsc --noEmit to catch type errors before moving on. It can also configure project references and incremental compilation for monorepos.

For full-stack work, the skill covers wiring up tRPC so client and server share types end to end. When a topic needs more detail, the agent loads one of the skill's reference notes on advanced types, type guards, utility types, configuration or patterns.

• Type design: generics, conditional types, mapped types, template literal types
• Runtime narrowing: custom type guards, assertion functions, exhaustive switches
• Project setup: strict tsconfig.json, project references, declaration files
• Full-stack: tRPC for shared client and server types

Install the TypeScript Pro skill

Download the typescript-pro ZIP from the skill page on this site. Then choose one of two install locations depending on how you want to use it. A personal install applies to all your projects; a project install applies only to that repository and can be shared with teammates through version control.

In the Claude apps, you can instead upload the ZIP under Settings, then Capabilities, then Skills.

• Personal: unzip the folder into ~/.claude/skills/
• Project only: unzip the folder into .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills → upload the ZIP

Check the skill folder layout

After unzipping, the skill folder should contain SKILL.md at its top level, plus a references folder. SKILL.md holds the instructions and the agent reads the reference files only when a task needs them. If SKILL.md is missing from the folder the agent sees, the skill will not load, so check the folder structure first when troubleshooting.

• SKILL.md (main instructions)
• references/advanced-types.md
• references/configuration.md
• references/patterns.md
• references/type-guards.md
• references/utility-types.md

Trigger the skill with natural requests

You do not need a special command. Describe the TypeScript work you want in ordinary language and mention the topic. The skill is tuned for requests about generics, conditional or mapped types, type guards, discriminated unions, tsconfig, monorepo setup and tRPC.

Be specific about the goal. A request that names the constraint or the file usually produces a more useful result than a vague one.

• "Write a type guard for this API response that narrows to the success case."
• "Model these loading, success and error states as a discriminated union."
• "Set up a strict tsconfig with project references for our three packages."
• "Add a branded type so user IDs and order IDs can't be mixed up."
• "Wire up tRPC so the React client gets the router's types automatically."

Check the type checker output yourself

The skill tells the agent to run tsc --noEmit as it works. You can run the same check in your own terminal to confirm the result. The skill also suggests a coverage tool such as type-coverage for checking that public APIs are typed, which is optional and must be installed separately.

Treat the agent's claims about correctness as a starting point. Run your build and tests before merging.

• Run tsc --noEmit in your project to confirm zero errors
• Optionally run type-coverage if you use it
• Review any use of as assertions or any types the agent introduces