migrate-js-to-modern-typescript

Migrating a JavaScript codebase to TypeScript — converting .js files to .ts, adding types to existing JS, or tightening a loosely-typed TS project toward strict mode. Covers tsconfig and allowJs strategy, incremental strict-flag ratcheting (noImplicitAny, strictNullChecks, noUncheckedIndexedAccess), typing public surfaces, replacing `any` and unsafe casts with `unknown` and narrowing, validating runtime boundaries (JSON, env, API responses), converting CommonJS to ESM and prototypes to classes, and the build/CI changes a migration needs. Trigger even when the user only says "add types", "turn on strict mode", or "convert this file to TypeScript", and especially on a mixed JS/TS repo. Distinct from general TypeScript refactoring — this is the migration act itself, performed file by file while keeping the build green.

跳到安装

仓库: pproenca/dot-skills
最近来源活动: 2026年7月5日 07:23
检测到的 SKILL.md 语言: 英语
星标: 194
分支: 17

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/pproenca/dot-skills --skill migrate-js-to-modern-typescript

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

47 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

drizzle-nextjs-postgres

Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.

2026-07-24

relational-data-modeling

Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.

2026-07-23

relational-database-design

Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.

2026-07-23

查看这个仓库的全部 Skills

JavaScript to TypeScript Migration Best Practices

Guide for taking a JavaScript codebase to strict, modern TypeScript without a big-bang rewrite. Contains 42 rules across 7 categories, prioritized by impact to drive an incremental, file-by-file migration that keeps the build compiling at every step.

When to Apply

Reference these guidelines when:

Converting a .js codebase to .ts (whole project or one module at a time)

Adding types to existing JavaScript via JSDoc or annotations

Choosing a tsconfig and allowJs strategy for a mixed JS/TS repo

Turning on strict mode or individual strict flags on a large codebase

Replacing any, as casts, and ! assertions left over from a quick conversion

Validating external data (JSON, env, API responses) so the types you wrote are true at runtime

Converting CommonJS to ESM, prototypes to classes, and other JS idioms to TS

Updating the build, runner, and CI to type-check and publish TypeScript

name

migrate-js-to-modern-typescript

description

JavaScript to TypeScript Migration Best Practices

When to Apply

Reference these guidelines when:

Converting a .js codebase to .ts (whole project or one module at a time)
Adding types to existing JavaScript via JSDoc or annotations
Choosing a tsconfig and allowJs strategy for a mixed JS/TS repo
Turning on strict mode or individual strict flags on a large codebase
Replacing any, as casts, and ! assertions left over from a quick conversion
Validating external data (JSON, env, API responses) so the types you wrote are true at runtime
Converting CommonJS to ESM, prototypes to classes, and other JS idioms to TS
Updating the build, runner, and CI to type-check and publish TypeScript

Priority	Category	Impact	Prefix
1	Migration Setup & tsconfig	CRITICAL	`setup-`
2	Strictness Ratcheting	CRITICAL	`strict-`
3	Typing Public Surfaces	HIGH	`surface-`
4	Replacing `any` & Unsafe Casts	HIGH	`unsafe-`
5	Runtime Data Validation	MEDIUM-HIGH	`runtime-`
6	JS-to-TS Idiom Conversion	MEDIUM	`idiom-`
7	Tooling & Build Migration	LOW-MEDIUM	`tooling-`

File	Description
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

migrate-js-to-modern-typescript

安装方式

检查来源文件

JavaScript to TypeScript Migration Best Practices

When to Apply

JavaScript to TypeScript Migration Best Practices

When to Apply

How the Migration Flows

Rule Categories by Priority

Quick Reference

1. Migration Setup & tsconfig (CRITICAL)

2. Strictness Ratcheting (CRITICAL)

3. Typing Public Surfaces (HIGH)

4. Replacing any & Unsafe Casts (HIGH)

5. Runtime Data Validation (MEDIUM-HIGH)

6. JS-to-TS Idiom Conversion (MEDIUM)

7. Tooling & Build Migration (LOW-MEDIUM)

How to Use

Related Skills

Reference Files

migrate-js-to-modern-typescript

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

JavaScript to TypeScript Migration Best Practices

When to Apply

JavaScript to TypeScript Migration Best Practices

When to Apply

How the Migration Flows

Rule Categories by Priority

Quick Reference

1. Migration Setup & tsconfig (CRITICAL)

2. Strictness Ratcheting (CRITICAL)

3. Typing Public Surfaces (HIGH)

4. Replacing any & Unsafe Casts (HIGH)

5. Runtime Data Validation (MEDIUM-HIGH)

6. JS-to-TS Idiom Conversion (MEDIUM)

7. Tooling & Build Migration (LOW-MEDIUM)

How to Use

Related Skills

Reference Files