| name | typescript |
| description | TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
|
| license | Apache-2.0 |
| metadata | {"author":"gentleman-programming","version":"1.0"} |
Const Types Pattern (REQUIRED)
const STATUS = {
ACTIVE: "active",
INACTIVE: "inactive",
PENDING: "pending",
} as const;
type Status = (typeof STATUS)[keyof typeof STATUS];
type Status = "active" | "inactive" | "pending";
Why? Single source of truth, runtime values, autocomplete, easier refactoring.
Flat Interfaces (REQUIRED)
interface UserAddress {
street: string;
city: string;
}
interface User {
id: string;
name: string;
address: UserAddress;
}
interface Admin extends User {
permissions: string[];
}
interface User {
address: { street: string; city: string };
}
Never Use any
function parse(input: unknown): User {
if (isUser(input)) return input;
throw new Error("Invalid input");
}
function first<T>(arr: T[]): T | undefined {
return arr[0];
}
function parse(input: any): any { }
Utility Types
Pick<User, "id" | "name">
Omit<User, "id">
Partial<User>
Required<User>
Readonly<User>
Record<string, User>
Extract<Union, "a" | "b">
Exclude<Union, "a">
NonNullable<T | null>
ReturnType<typeof fn>
Parameters<typeof fn>
Type Guards
function isUser(value: unknown): value is User {
return (
typeof value === "object" &&
value !== null &&
"id" in value &&
"name" in value
);
}
Import Types
import type { User } from "./types";
import { createUser, type Config } from "./utils";
Keywords
typescript, ts, types, interfaces, generics, strict mode, utility types