Skip to main content
skill CX Codex

ts-google — Claude Code skill: what it does, how to install

Google TypeScript style guide containing 45 prioritized rules for AI agents. Guides code generation and refactoring according to strict typing standards.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pproenca/dot-skills --skill ts-google -a claude-code
Open on GitHub

What ts-google does

This skill injects Google's TypeScript conventions directly into the agent prompt. The guide covers eight categories. Critical priorities belong to module organization and type safety.

The rules enforce strict typing. They ban the any type and deprecate namespaces. Interfaces take precedence over type aliases for objects. Classes rely on parameter properties, while catch blocks mandate unknown.

Legacy CommonJS projects will break under these constraints.

What it helps with

  • Eliminate any types from generated TypeScript code
  • Convert default exports to explicit named exports
  • Refactor class definitions using parameter properties
  • Format error handling blocks with unknown catch variables

Example prompts for the agent

  • Review src/api.ts against ts-google rules and fix type issues
  • Refactor storage.ts to use named exports and remove namespaces
  • Write a UserService class following Google TypeScript guidelines

How to install ts-google

1Skills CLI (Vercel)

npx skills add pproenca/dot-skills --skill ts-google -a claude-code

2Manually: put the files in place

~/.claude/skills/ts-google/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ts-google/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ts-google

How to install ts-google in Claude Code?

Run npx skills add pproenca/dot-skills --skill ts-google -a claude-code in your terminal. The skill file is placed in ~/.claude/skills/ts-google/SKILL.md.

What does ts-google do?

It provides AI assistants with 45 rules based on Google's TypeScript style guide. The agent applies these standards when writing and refactoring TypeScript code.

Which rules carry the highest priority?

Module Organization (module-) and Type Safety (types-) carry the critical designation. They govern import mechanics, ban namespaces, and strictly forbid any.

Source text

SKILL.md · MIT
---
name: ts-google
description: Google TypeScript style guide for writing clean, consistent, type-safe code. This skill should be used when writing, reviewing, or refactoring TypeScript code. Triggers on TypeScript files, type annotations, module imports, class design, and code style decisions.
---

# Google TypeScript Best Practices

Comprehensive TypeScript style guide based on Google's internal standards, designed for AI agents and LLMs. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

## When to Apply

Reference these guidelines when:
- Writing new TypeScript code
- Organizing modules and imports
- Designing type annotations and interfaces
- Creating classes and functions
- Reviewing code for style consistency
- Refactoring existing TypeScript code

## Rule Categories by Priority

| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | Module Organization | CRITICAL | `module-` |
| 2 | Type Safety | CRITICAL | `types-` |
| 3 | Class Design | HIGH | `class-` |
| 4 | Function Patterns | HIGH | `func-` |
| 5 | Control Flow | MEDIUM-HIGH | `control-` |
| 6 | Error Handling | MEDIUM | `error-` |
| 7 | Naming & Style | MEDIUM | `naming-` |
| 8 | Literals & Coercion | LOW-MEDIUM | `literal-` |

## Quick Reference

### 1. Module Organization (CRITICAL)

- [`module-named-exports`](references/module-named-exports.md) - Use named exports over default exports
- [`module-no-mutable-exports`](references/module-no-mutable-exports.md) - Avoid mutable exports
- [`module-es6-modules`](references/module-es6-modules.md) - Use ES6 modules exclusively
- [`module-no-namespaces`](references/module-no-namespaces.md) - Avoid TypeScript namespaces
- [`module-import-paths`](references/module-import-paths.md) - Use relative paths for project imports
- [`module-import-type`](references/module-import-type.md) - Use import type for type-only imports
- [`module-export-api-surface`](references/module-export-api-surface.md) - Minimize exported API surface

### 2. Type Safety (CRITICAL)

- [`types-no-any`](references/types-no-any.md) - Never use the any type
- [`types-prefer-interfaces`](references/types-prefer-interfaces.md) - Prefer interfaces over type aliases for objects
- [`types-explicit-structural`](references/types-explicit-structural.md) - Explicitly annotate structural types
- [`types-nullable-patterns`](references/types-nullable-patterns.md) - Handle nullable types correctly
- [`types-array-syntax`](references/types-array-syntax.md) - Use consistent array type syntax
- [`types-no-wrapper-types`](references/types-no-wrapper-types.md) - Never use wrapper object types
- [`types-prefer-map-set`](references/types-prefer-map-set.md) - Prefer Map and Set over index signatures
- [`types-no-empty-object`](references/types-no-empty-object.md) - Avoid empty object type

### 3. Class Design (HIGH)

- [`class-parameter-properties`](references/class-parameter-properties.md) - Use parameter properties for constructor assignment
- [`class-readonly-properties`](references/class-readonly-properties.md) - Mark properties readonly when never reassigned
- [`class-no-private-fields`](references/class-no-private-fields.md) - Use TypeScript private over private fields
- [`class-no-static-containers`](references/class-no-static-containers.md) - Avoid container classes with only static members
- [`class-constructor-parens`](references/class-constructor-parens.md) - Always use parentheses in constructor calls
- [`class-no-prototype-manipulation`](references/class-no-prototype-manipulation.md) - Never manipulate prototypes directly

### 4. Function Patterns (HIGH)

- [`func-declarations-over-expressions`](references/func-declarations-over-expressions.md) - Prefer function declarations over expressions
- [`func-arrow-concise-bodies`](references/func-arrow-concise-bodies.md) - Use concise arrow function bodies appropriately
- [`func-avoid-this-rebinding`](references/func-avoid-this-rebinding.md) - Avoid rebinding this
- [`func-rest-parameters`](references/func-rest-parameters.md) - Use rest parameters over arguments
- [`func-generator-syntax`](references/func-generator-syntax.md) - Use correct generator function syntax
- [`func-default-parameters`](references/func-default-parameters.md) - Use default parameters sparingly

### 5. Control Flow (MEDIUM-HIGH)

- [`control-always-use-braces`](references/control-always-use-braces.md) - Always use braces for control structures
- [`control-triple-equals`](references/control-triple-equals.md) - Always use triple equals
- [`control-for-of-iteration`](references/control-for-of-iteration.md) - Prefer for-of over for-in for arrays
- [`control-switch-default`](references/control-switch-default.md) - Always include default case in switch
- [`control-no-assignment-in-condition`](references/control-no-assignment-in-condition.md) - Avoid assignment in conditional expressions

### 6. Error Handling (MEDIUM)

- [`error-throw-errors`](references/error-throw-errors.md) - Always throw Error instances
- [`error-catch-unknown`](references/error-catch-unknown.md) - Type catch clause variables as unknown
- [`error-empty-catch-comments`](references/error-empty-catch-comments.md) - Document empty catch blocks
- [`error-avoid-assertions`](references/error-avoid-assertions.md) - Avoid type and non-null assertions

### 7. Naming & Style (MEDIUM)

- [`naming-identifier-styles`](references/naming-identifier-styles.md) - Use correct identifier naming styles
- [`naming-descriptive-names`](references/naming-descriptive-names.md) - Use descriptive names
- [`naming-no-decorative-underscores`](references/naming-no-decorative-underscores.md) - Avoid decorative underscores
- [`naming-no-interface-prefix`](references/naming-no-interface-prefix.md) - No I prefix for interfaces
- [`naming-constants`](references/naming-constants.md) - Use CONSTANT_CASE for true constants

### 8. Literals & Coercion (LOW-MEDIUM)

- [`literal-single-quotes`](references/literal-single-quotes.md) - Use single quotes for strings
- [`literal-number-formats`](references/literal-number-formats.md) - Use correct number literal formats
- [`literal-explicit-coercion`](references/literal-explicit-coercion.md) - Use explicit type coercion
- [`literal-array-constructor`](references/literal-array-constructor.md) - Avoid Array constructor

## How to Use

Read individual reference files for detailed explanations and code examples:

- [Section definitions](references/_sections.md) - Category structure and impact levels
- [Rule template](assets/templates/_template.md) - Template for adding new rules

## Reference Files

| File | Description |
|------|-------------|
| [AGENTS.md](AGENTS.md) | Complete compiled guide with all rules |
| [references/_sections.md](references/_sections.md) | Category definitions and ordering |
| [assets/templates/_template.md](assets/templates/_template.md) | Template for new rules |
| [metadata.json](metadata.json) | Version and reference information |

© pproenca · MIT · pproenca/dot-skills

Similar skills

All skills for Code review and refactoring →

From the same set55

react-testing-library A skill with 43 React Testing Library rules. It steers the agent toward tests that check behaviour instead of component internals. CX Codex +1 402installs react-optimise A skill that walks through React app performance: React Compiler, bundle size, rendering, data fetching, Core Web Vitals. Useful when your app feels slow. CX Codex +1 396installs knip-deadcode A set of 43 rules for configuring Knip in JavaScript and TypeScript projects. It helps spot dead code, trim unused dependencies, and wire checks into CI. CX Codex +1 378installs rails-hotwire A skill with Hotwire rules for Rails: Turbo Drive, Frames, Streams, Turbo 8 morphing and Stimulus controllers. Useful when writing or refactoring interactive pages. CX Codex +1 370installs vite A performance optimization guide with 42 Vite rules. Helps your AI agent audit configs, optimize bundles, and fix slow dev servers. CX Codex +1 358installs nginx-c-module-design A skill for anyone writing nginx C modules: it helps you decide what to expose as directives, how to name them and where they belong. Most useful while the module's config interface is still being shaped. CX Codex +1 352installs nginx-c-modules A skill that feeds your agent 49 rules for nginx C module work: pool memory, request lifecycle, config merging. Useful when you write or refactor a handler, filter or upstream. CX Codex +1 349installs dockerfile-optimise A skill with 48 rules from official Docker docs: layer caching, multi-stage builds, security. Useful when writing or refactoring Dockerfiles. CX Codex +1 344installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor