home / skills / prowler-cloud / prowler / typescript
This skill enforces TypeScript strict patterns and best practices, promoting consts, flat interfaces, unknowns, and robust typings for safer refactoring.
npx playbooks add skill prowler-cloud/prowler --skill typescriptReview the files below or copy the command above to add this skill to your agents.
---
name: typescript
description: >
TypeScript strict patterns and best practices.
Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).
license: Apache-2.0
metadata:
author: prowler-cloud
version: "1.0"
scope: [root, ui]
auto_invoke: "Writing TypeScript types/interfaces"
allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
---
## Const Types Pattern (REQUIRED)
```typescript
// ✅ ALWAYS: Create const object first, then extract type
const STATUS = {
ACTIVE: "active",
INACTIVE: "inactive",
PENDING: "pending",
} as const;
type Status = (typeof STATUS)[keyof typeof STATUS];
// ❌ NEVER: Direct union types
type Status = "active" | "inactive" | "pending";
```
**Why?** Single source of truth, runtime values, autocomplete, easier refactoring.
## Flat Interfaces (REQUIRED)
```typescript
// ✅ ALWAYS: One level depth, nested objects → dedicated interface
interface UserAddress {
street: string;
city: string;
}
interface User {
id: string;
name: string;
address: UserAddress; // Reference, not inline
}
interface Admin extends User {
permissions: string[];
}
// ❌ NEVER: Inline nested objects
interface User {
address: { street: string; city: string }; // NO!
}
```
## Never Use `any`
```typescript
// ✅ Use unknown for truly unknown types
function parse(input: unknown): User {
if (isUser(input)) return input;
throw new Error("Invalid input");
}
// ✅ Use generics for flexible types
function first<T>(arr: T[]): T | undefined {
return arr[0];
}
// ❌ NEVER
function parse(input: any): any { }
```
## Utility Types
```typescript
Pick<User, "id" | "name"> // Select fields
Omit<User, "id"> // Exclude fields
Partial<User> // All optional
Required<User> // All required
Readonly<User> // All readonly
Record<string, User> // Object type
Extract<Union, "a" | "b"> // Extract from union
Exclude<Union, "a"> // Exclude from union
NonNullable<T | null> // Remove null/undefined
ReturnType<typeof fn> // Function return type
Parameters<typeof fn> // Function params tuple
```
## Type Guards
```typescript
function isUser(value: unknown): value is User {
return (
typeof value === "object" &&
value !== null &&
"id" in value &&
"name" in value
);
}
```
## Import Types
```typescript
import type { User } from "./types";
import { createUser, type Config } from "./utils";
```
This skill enforces TypeScript strict patterns and best practices for .ts/.tsx code, focusing on types, interfaces, generics, const maps, type guards, and eliminating any. It helps maintain a single source of truth for runtime values, keeps interfaces flat, and encourages safer alternatives like unknown, generics, and utility types. The goal is clearer code, better autocomplete, and safer refactors.
The skill inspects TypeScript source to detect anti-patterns such as inline nested interfaces, direct union string types, and uses of any. It recommends replacing direct unions with const maps and derived types, flattening nested object types into referenced interfaces, and adding type guards and typed imports. It also suggests utility type usage and safer alternatives to any like unknown and generics.
Why derive unions from consts instead of writing unions directly?
Deriving unions from const objects creates a single source of truth that preserves runtime values, improves autocomplete, and makes refactors safer.
When should I use unknown vs generics?
Use unknown when input truly could be anything and you need runtime checks; use generics to express flexible, type-safe APIs where the caller supplies the concrete type.