smith-typescript

Enforce TypeScript development standards across frontend and backend projects.

1|Updated Nov 25, 2025

Search Tags:#typescript #vitest #testing #jest #type-checking #tsconfig #alias-config

Ready to run

npx skills add https://github.com/tianjianjiang/smith --skill smith-typescript

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smith-typescript
Source: https://github.com/tianjianjiang/smith/tree/main/smith-typescript
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript development standards help teams align on configuration, testing, and type checking practices across frontend and backend projects.

Core Features & Use Cases

Standardize path alias configuration in Vite/Jest/Vitest for consistent module resolution.
Provide guidelines for TypeScript type checking, CI alignment, and test organization.
Support phased adoption with prerequisites referencing core smith principles and standards.

Quick Start

Apply these standards to your TypeScript projects to standardize aliases, tests, and type checks.

Frequently Asked Questions about smith-typescript

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

FAQPage Schema

How do I standardize path alias configuration for TypeScript in Vite and Vitest?▼

To standardize path alias configuration for TypeScript, align module resolution settings across Vite, Vitest, and tsconfig. This ensures consistent imports and prevents module resolution errors during local development and automated testing.

What are the prerequisites for enforcing TypeScript development standards across projects?▼

Prerequisites for enforcing TypeScript development standards include configuring path aliases, setting up CI type checks, and placing tests near source files. You must also align configurations with core smith principles and standards for phased adoption.

How does CI type checking work with TypeScript and Jest?▼

CI type checking with TypeScript and Jest involves running automated type checks in your pipeline to catch errors before deployment. It requires proper tsconfig setup and alignment with testing frameworks to validate types across the codebase.

Does this TypeScript standard support both frontend and backend projects?▼

Yes, these TypeScript standards support both frontend and backend projects. They provide unified guidelines for type checking, test organization, and configuration across diverse project types using Vite or Vitest.

What is the best way to organize TypeScript tests with Vitest?▼

The recommended way to organize TypeScript tests with Vitest is by placing test files near the source code they validate. This nearby test placement strategy improves maintainability and aligns with standard CI type checking practices.

Why does TypeScript path alias resolution fail in Jest?▼

TypeScript path alias resolution fails in Jest when configurations are not standardized across tsconfig and testing tools. Aligning module resolution settings prevents inconsistent imports and fixes failing tests.