ts-dev

Name: ts-dev
Availability: InStock
Author: mdproctor

Enforce TypeScript best practices for type safety, async patterns, and testing.

1|5|Updated Mar 29, 2026

Search Tags:#typescript #testing #async #code-quality #type-safety #best-practices

Ready to run

npx skills add https://github.com/mdproctor/cc-praxis --skill ts-dev-mdproctor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ts-dev
Source: https://github.com/mdproctor/cc-praxis/tree/main/ts-dev
Command: npx skills add https://github.com/mdproctor/cc-praxis --skill ts-dev-mdproctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides comprehensive guidance to enforce TypeScript development best practices, reducing defects and enabling safer, more maintainable codebases.

Core Features & Use Cases

Strong type safety discipline: enforce strict TypeScript configurations, avoid any, and use type guards and discriminated unions.
Async patterns and error handling: promote proper awaiting, promise handling, and robust error paths.
Testing & quality: encourage realistic tests, type-level checks, and meaningful test strategies.
Code hygiene: promote readability, const-first style, and safe object shapes.

Quick Start

Run ts-dev in your project to start applying TypeScript development guidelines across new code, fixes, and refactors.

Frequently Asked Questions about ts-dev

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

FAQPage Schema

What are the best practices for safe async patterns and error handling in TypeScript?▼

TypeScript best practices for async patterns require proper promise awaiting and robust error handling paths to ensure reliability. This involves enforcing strict type configurations and discouraging unsafe runtime assumptions during async operations.

How do I enforce strict type safety and avoid using any in TypeScript?▼

To enforce strict type safety in TypeScript, use strict compiler configurations and replace any with unknown coupled with type guards. This approach prevents unsafe type coercions and improves overall code maintainability.

Why should I avoid non-null assertions when writing TypeScript code?▼

Avoiding non-null assertions in TypeScript code prevents runtime errors by forcing explicit null checks. Using unknown with type guards offers a safer alternative for maintaining type safety and robust code hygiene.

How do I write meaningful tests and type-level checks for TypeScript projects?▼

Writing meaningful TypeScript tests involves implementing realistic test strategies and type-level checks to validate code quality. This ensures your testing approach covers both runtime behavior and compile-time type safety constraints.

Can I apply TypeScript code quality rules during refactoring and bug fixes?▼

Yes, applying TypeScript code quality rules during refactoring and bug fixes enforces const-first style, safe object shapes, and discriminated unions. This maintains readability and reliability when modifying existing codebases.