Skip to content
Back to skills

Typescript Strict Types Typescript Strict Types Strict Mode

ASecurity

Reviews TypeScript strict typing in repos that already use strict compiler settings, focusing on unknown narrowing, safe DTO contracts, and eliminating unsafe any usage under strict mode.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
developmenttypescriptrustgoapi

Works with

  • api

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill typescript--strict-types--typescript-strict-types-strict-mode --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Typescript Strict Types Typescript Strict Types Strict Mode?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Typescript  Strict Types  Typescript Strict Types Strict Mode
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-typescript-strict-types-typescript-strict-types-st/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-typescript-strict-types-typescript-strict-types-st)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: typescript.strict-types.typescript-strict-types-strict-mode
name: TypeScript Strict Types Strict Mode
description: >
  Reviews TypeScript strict typing in repos that already use strict compiler settings, focusing on unknown narrowing, safe DTO contracts, and eliminating unsafe any usage under strict mode.
stack:
  - TypeScript
category: strict-types
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - strict mode typescript
  - strict true
  - strict typing strict mode
  - typescript strict compiler
  - strict null checks
compatibility:
  compiler:
    strict: true
---

# TypeScript Strict Types Strict Mode

## Purpose

Use this skill for TypeScript repositories that already use strict compiler settings.

This variant gives stricter guidance for repos where the compiler already enforces type safety and the main work is removing unsafe assumptions, narrowing unknown values, and keeping boundary contracts precise.

## When to Use

Use this skill when:

- `strict: true` is enabled
- the repo is ready for stricter type guidance
- unsafe `any` needs to be removed under strict settings
- DTO and boundary contracts need tightening

## Do

Prefer `unknown` plus narrowing at trust boundaries.

Use explicit DTOs and type guards for untrusted input.

Preserve narrow, testable contracts.

## Do Not

Avoid recommending non-strict fallbacks when the repo is already strict.

Avoid broad type assertions that bypass compiler value.

## Review Checklist

- [ ] `strict: true` is enabled.
- [ ] Unknown values are narrowed safely.
- [ ] Unsafe `any` is not leaking through public APIs.
- [ ] Boundary contracts are explicit.

## Expected Output

1. Confirm strict compiler mode.
2. Recommend strict-safe narrowing patterns.
3. Flag broad assertions and unsafe `any`.
4. Keep contracts explicit at boundaries.
5. Produce strict-mode-specific guidance.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…