typescript

Enforce Google's official TypeScript style guide for consistent code.

9|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/testdino-hq/google-styleguides-skills --skill typescript-testdino-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/testdino-hq/google-styleguides-skills/tree/main/typescript
Command: npx skills add https://github.com/testdino-hq/google-styleguides-skills --skill typescript-testdino-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces Google's official TypeScript coding standards, ensuring consistency, maintainability, and best practices across your projects.

Core Features & Use Cases

  • Strict Mode Enforcement: Guides you to enable and adhere to TypeScript's strict compiler options.
  • Type System Best Practices: Recommends interfaces over type aliases, discourages any, and promotes explicit typing.
  • Naming Conventions: Provides clear rules for naming classes, functions, variables, and files.
  • Use Case: When writing new TypeScript code or refactoring existing code, consult this Skill to ensure your code aligns with Google's high standards for clarity and robustness.

Quick Start

Follow the naming conventions for functions and variables as outlined in the guide.

Frequently Asked Questions about typescript

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

FAQPage Schema
What are Google's TypeScript coding standards for interfaces vs type aliases?

Google's TypeScript style guide recommends using interfaces over type aliases for object shapes and enforces explicit typing to ensure consistency and maintainability across your projects.

How do I enforce strict mode and type safety in TypeScript?

To enforce strict mode and type safety in TypeScript, enable the strict compiler options, avoid using the any type, and require explicit return types and readonly properties as outlined in the style guide.

What naming conventions should I follow for TypeScript functions and variables?

TypeScript naming conventions for functions and variables require clear and consistent rules to ensure code clarity, guiding you to align class, function, variable, and file names with Google's standards.

Why should I avoid non-null assertions and any types in TypeScript?

Avoiding non-null assertions and any types in TypeScript prevents common mistakes and enforces type safety, ensuring your code adheres to Google's official standards for robust and maintainable code.

Does Google's TypeScript style guide require explicit return types on all functions?

Google's TypeScript style guide enforces explicit return types on functions to maintain strict type safety, alongside requiring readonly properties and proper null handling to prevent common coding mistakes.