TypeScript Coding Standards

TypeScript coding standards for frontend React projects enforce explicit parameter and return types, structured imports, type guards, and JSDoc documentation. They mandate PascalCase for components and camelCase for utility files to improve maintainability.

Enforce type safety without external tooling by codifying strict tsconfig settings and explicit API definitions. This skill provides guidelines for using type guards and explicit types to catch errors early without requiring additional linting installations.

Structure imports and naming conventions in a TypeScript frontend project by applying structured import ordering, using PascalCase for component files and camelCase for utilities. This skill codifies these patterns to ensure readability and consistency.

No, you do not need external linting tools to apply these TypeScript coding standards. The guidelines enforce best-practice patterns, naming conventions, and JSDoc documentation independently, relying on your project's existing TypeScript checks.

Document TypeScript components and hooks for better onboarding by adding file headers and inline JSDoc documentation. This skill enforces consistent documentation practices alongside explicit types and structured imports to improve collaboration.