本文へ移動
cccskills
無料GitHub で公開

typescript

Enforces modern TypeScript best practices for type-safe code, strict configuration, runtime validation, and clear type contracts. Use when writing or reviewing TypeScript/JavaScript code, configuring tsconfig.json, or when the user asks for TypeScript style guidance.

インストール方法を見る

含まれるファイル(8)

  • SKILL.md6.8 KB
  • typescript.mdc8.8 KB
  • typescript/references/advanced-patterns.md6.7 KB
  • typescript/references/architecture.md9.2 KB
  • typescript/references/biome.md10.2 KB
  • typescript/references/performance.md6.7 KB
  • typescript/references/testing.md8.7 KB
  • typescript/SKILL.md14.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

TypeScript Best Practices

Quick Start

Apply these rules by default when touching TypeScript/JavaScript:

  1. Enable strict: true in tsconfig.json (most impactful change)
  2. Define clear type contracts with interfaces/type aliases
  3. Use unknown instead of any; narrow with type guards
  4. Implement runtime validation for external data (APIs, user input)
  5. Prefer string literal unions over numeric enums
  6. Use named exports, avoid default exports

Workflow (use this order)

  1. Clarify scope: new code, refactor, or review.
  2. Enforce strictness in tsconfig.json (or confirm it is already strict).
  3. Define explicit type contracts for inputs/outputs (interfaces/type aliases).
  4. Replace any with unknown + narrowing/guards.
  5. Add runtime validation for external data boundaries.
  6. Normalize exports/imports and tighten API surfaces.
  7. Add or update tests for changed behavior.

Review Checklist

  • Strict mode enabled and no any leaks.
  • Public types are explicit and documented.
  • Runtime validation exists for untrusted inputs.
  • Literal unions used instead of numeric enums.
  • Named exports only; imports are organized.
  • Tests cover edge cases and error paths.

Local Resources

Use the always-applied rule file in this folder:

  • typescript.mdc (authoritative TypeScript/JSX guidance; read when you need the full rule text)

Configuration

Essential tsconfig.json settings:

{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictPropertyInitialization": true,
    "allowJs": true,
    "checkJs": true
  }
}

Type Definitions

Interfaces for Object Shapes

Use interfaces for object shapes and class contracts. Define in .d.ts or .ts files, reference via JSDoc in .js files.

interface UserProfile {
  id: string;
  name: string;
  email: string;
  age?: number;
}

Type Aliases for Unions & Complex Types

Use type aliases for unions, intersections, and tuples.

type ID = string | number;
type UserRole = "admin" | "user" | "guest";
type Coords = [number, number];

Type Safety

Avoid any, Use unknown

any bypasses all type checks. unknown forces narrowing before use.

❌ Bad:

function processData(data: any) {
  console.log(data.foo.bar); // No type safety
}

✅ Good:

function processData(data: unknown) {
  if (typeof data === 'object' && data !== null && 'foo' in data) {
    const typed = data as { foo: { bar: string } };
    console.log(typed.foo.bar);
  }
}

Runtime Validation

TypeScript's checks are compile-time only. For external data (APIs, user input), implement runtime validation with type guards.

Type Guards for Primitives

function isString(value: unknown): value is string {
  return typeof value === 'string';
}

function isNumber(value: unknown): value is number {
  return typeof value === 'number' && !isNaN(value);
}

Type Guards for Complex Objects

interface Product {
  id: string;
  name: string;
  price: number;
}

function isProduct(obj: unknown): obj is Product {
  return (
    typeof obj === 'object' && obj !== null &&
    'id' in obj && typeof obj.id === 'string' &&
    'name' in obj && typeof obj.name === 'string' &&
    'price' in obj && typeof obj.price === 'number'
  );
}

Enums and Unions

Prefer string literal unions over numeric enums for better type safety and simpler runtime representation.

❌ Bad:

enum UserStatus {
  Active,    // 0
  Inactive,  // 1
  Pending    // 2
}

✅ Good:

type UserStatus = 'active' | 'inactive' | 'pending';

// If enum is necessary, use const string enum:
const enum UserRole {
  Admin = "admin",
  User = "user",
  Guest = "guest"
}

Generics

Use generics for reusable, type-safe functions and components.

function identity<T>(arg: T): T {
  return arg;
}

const num = identity(123);  // number
const str = identity("hello"); // string

Code Organization

Named Exports (No Default Exports)

Named exports promote explicit imports and easier refactoring.

❌ Bad:

export default class UserService { }

✅ Good:

export class UserService { }
export const DEFAULT_USER = { };

Organized Imports

Group imports: libraries → absolute paths → relative paths. Sort alphabetically.

import React from 'react';
import { useSelector } from 'react-redux';

import { API_URL } from 'config/constants';
import { selectUser } from 'store/selectors';

import { Button } from './components/Button';
import { formatCurrency } from '../utils/formatters';

Examples

Example 1: Type guard for API response

Input: "Validate and process API response" Output:

interface ApiUser {
  id: string;
  name: string;
  email: string;
}

function isApiUser(obj: unknown): obj is ApiUser {
  return (
    typeof obj === 'object' && obj !== null &&
    'id' in obj && typeof obj.id === 'string' &&
    'name' in obj && typeof obj.name === 'string' &&
    'email' in obj && typeof obj.email === 'string'
  );
}

async function fetchUser(id: string): Promise<ApiUser | null> {
  const response = await fetch(`/api/users/${id}`);
  const data: unknown = await response.json();
  
  if (isApiUser(data)) {
    return data;
  }
  return null;
}

Example 2: String literal union type

Input: "Status type with specific values" Output:

type OrderStatus = 'pending' | 'processing' | 'shipped' | 'delivered';

function updateOrderStatus(orderId: string, status: OrderStatus) {
  // TypeScript ensures only valid status values
  console.log(`Order ${orderId} -> ${status}`);
}

updateOrderStatus('123', 'shipped'); // ✅ OK
// updateOrderStatus('123', 'invalid'); // ❌ Type error

Example 3: Generic utility function

Input: "Reusable function that works with any array type" Output:

function getFirst<T>(items: T[]): T | undefined {
  return items[0];
}

const firstNum = getFirst([1, 2, 3]); // number | undefined
const firstStr = getFirst(['a', 'b']); // string | undefined

Example 4: JSDoc types for JavaScript files

Input: "Type-check JavaScript file with JSDoc" Output:

// types.d.ts
export interface UserProfile {
  id: string;
  name: string;
  email: string;
}

// user-service.js
/**
 * @typedef {import('./types').UserProfile} UserProfile
 */

/**
 * @param {UserProfile} user
 * @returns {string}
 */
export function greetUser(user) {
  return `Hello, ${user.name}!`;
}

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.

日本語の概要は準備中です。原文の説明を表示しています。

heyAyushh/stacc32026年9月21日 更新

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

日本語の概要は準備中です。原文の説明を表示しています。

heyAyushh/stacc32026年9月21日 更新

Add Agentation visual feedback toolbar to a Next.js project

日本語の概要は準備中です。原文の説明を表示しています。

heyAyushh/stacc32026年9月21日 更新

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

日本語の概要は準備中です。原文の説明を表示しています。

heyAyushh/stacc32026年9月21日 更新

Derive and implement first-principles audio-coupled haptic and kinetic UI feedback. Use when designing, reviewing, or coding haptics/audio for mobile apps, native iOS/Android, React Native/Expo, SwiftUI, games, detent pickers, toggles, sliders, page curls, scroll gestures, wallet/signature flows, Solana transactions, backend/realtime state changes, confirmations, settlements, and semantic UI events where feedback should follow signal math instead of ad hoc vibration calls.

日本語の概要は準備中です。原文の説明を表示しています。

heyAyushh/stacc32026年9月21日 更新

Babysit a GitHub pull request during a user-approved monitoring window by polling review comments, CI checks/workflow runs, and mergeability state. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and report fresh review feedback. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

日本語の概要は準備中です。原文の説明を表示しています。

heyAyushh/stacc32026年9月21日 更新

heyAyushh のスキルをすべて見る

このスキルの問題を報告する