Skip to content
cccskills
FreePublished on GitHubEnglish overview

typescript-patterns

Apply practical patterns for writing and reviewing TypeScript or JavaScript, from strict compiler settings and safe input narrowing to generics, async errors, and module boundaries. The guidance helps keep public APIs explicit and data handling type-safe.

OriginalShow the original description

TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.

affaan-m/ECC293,783 stars(GitHub 293,783 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Setting up strict TypeScript compiler options
  • Replacing unsafe any values with validated types
  • Designing generics and discriminated unions
  • Reviewing async error handling and module exports

Overview

What it does

This skill provides guidance for type design and code structure when writing, reviewing, or refactoring TypeScript and JavaScript. It covers strict compiler settings, using unknown and narrowing instead of any, and giving exported functions explicit types. It also explains how to model states and caller-dependent types with discriminated unions and generics. Other topics include runtime validation of external input, async operations and errors, dependency direction, public exports, type tests, and compiler configuration.

When it helps

Use it to configure a new TypeScript project, address type errors, or review changes involving .ts and .tsx files. It can also guide efforts to reduce loose typing or design types, generics, and module boundaries for a feature. The patterns are also relevant when reviewing JavaScript or deciding how to validate runtime data.

Example requests

  • “Review this tsconfig.json for stricter type checking.”
  • “Replace this any with safe input validation and type narrowing.”
  • “Review this async flow and the module’s public exports.”

Notes

To run type tests or checks, the relevant tools, such as tsc, Vitest, or ESLint, must be installed in the project. Zod is given as an example input validation library, but using a particular library is not required.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt provides type design guidance and describes no external sending or deletion operations.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingChecks require tools such as `tsc`, Vitest, or ESLint; setup steps are absent.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 30, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md23.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummary

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC293.8KUpdated Oct 30, 2026

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC293.8KUpdated Oct 30, 2026

agent-eval

FreeSummary

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC293.8KUpdated Oct 30, 2026

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC293.8KUpdated Oct 30, 2026

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC293.8KUpdated Oct 30, 2026

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC293.8KUpdated Oct 5, 2026

See all skills by affaan-m

Report a problem with this skill