typescript

Inspect TypeScript files (.ts/.tsx) in pull requests for Manos typing pattern violations.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/brianmontero18/astral --skill typescript-brianmontero18
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/brianmontero18/astral/tree/main/.claude/skills/typescript
Command: npx skills add https://github.com/brianmontero18/astral --skill typescript-brianmontero18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure TypeScript code adheres to the Manos project's typing patterns, improving reliability and consistency across codebases.

Core Features & Use Cases

  • Enforces no use of any and promotes explicit typing with proper null handling.
  • Encourages interface-based props typing for components instead of inline props.
  • Guides correct placement of type definitions and reusable type patterns.

Quick Start

Review TypeScript files in the PR and verify adherence to Manos typing patterns.

Frequently Asked Questions about typescript

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

FAQPage Schema
How do I enforce type safety and ban the use of 'any' in TypeScript pull requests?

To enforce type safety in pull requests, scan .ts and .tsx files to identify TypeScript code using 'any' and report violations. This ensures explicit typing and proper null handling across your codebase.

What is the best way to type component props in TypeScript?

The best way to type component props is using interface-based props typing instead of inline props. This enforces proper props typing and consistent type-definition placement in your .ts and .tsx files.

How do I check for consistent type definition placement in TypeScript projects?

To check for consistent type definition placement, review TypeScript files in pull requests to verify adherence to standardized typing patterns. This guides correct placement of type definitions and reusable type patterns.

Does this static analysis tool work with both .ts and .tsx files?

Yes, this static analysis tool works with both .ts and .tsx files in pull requests. It focuses on type definitions, props typing, and null handling to ensure consistent typing patterns across your project.

Can I use this to enforce null handling patterns in TypeScript code?

Yes, you can use this to enforce null handling patterns in TypeScript code. It identifies TypeScript code that deviates from proper null handling and reports violations to improve reliability and consistency.

Why should I avoid inline props typing in favor of interface-based typing?

You should avoid inline props typing because interface-based typing for components enforces proper props typing and consistent type-definition placement. This improves reliability and consistency across the codebase.