Skip to content
Skills Library
Programming · Building & coding

devs:typescript-core

/devs:typescript-core

Use when writing, debugging, reviewing, or configuring TypeScript — type errors, tsconfig and strictness setup, ESLint findings, testing with vitest, Node backend or library development, package selection, or monorepo configuration. Contains type-check-verified references, verified strict tsconfig templates, and a curated package stack. For React component/UI work, use devs:react-core alongside this.

Licence
MIT
Last repository change
16.08.2026

Assessment and security

80/ 100Class: good
Format15 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
17
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when writing, debugging, reviewing, or configuring TypeScript — type errors, tsconfig and strictness setup, ESLint findings, testing with vitest, Node backend or library development, package selection, or monorepo configuration. Contains type-check-verified references, verified strict tsconfig templates, and a curated package stack. For React component/UI work, use devs:react-core alongside this.

Original author description

Use when writing, debugging, reviewing, or configuring TypeScript — type errors, tsconfig and strictness setup, ESLint findings, testing with vitest, Node backend or library development, package selection, or monorepo configuration. Contains type-check-verified references, verified strict tsconfig templates, and a curated package stack. For React component/UI work, use devs:react-core alongside this.

How it works

  1. Reference routing
  2. Decision guides
  3. tsconfig templates (${CLAUDESKILLDIR}/assets/tsconfig-templates/)
Original SKILL.md headings · 50 lines, 435 words
SKILL.md preview
---
name: devs:typescript-core
description: "Use when writing, debugging, reviewing, or configuring TypeScript — type errors, tsconfig and strictness setup, ESLint findings, testing with vitest, Node backend or library development, package selection, or monorepo configuration. Contains type-check-verified references, verified strict tsconfig templates, and a curated package stack. For React component/UI work, use devs:react-core alongside this."
---

# TypeScript Core Development

Reference hub for TypeScript work. Verify versions, compiler options, and APIs against npm (`npm view <pkg> version`) and the installed toolchain — never from trained knowledge.

## Reference routing

Load references on demand — not all at once.

| Reference | Use when |
|---|---|
| [strict-configuration.md](references/strict-configuration.md) | tsconfig strictness anatomy, compiler defaults, ESLint flat config |
| [common-errors.md](references/common-errors.md) | The genuinely confusing compiler errors (TS2742, TS1484, TS1479, ...) |
| [error-handling.md](references/error-handling.md) | Result types (True Myth), Effect error channel, boundary strategy |
| [patterns.md](references/patterns.md) | ts-pattern, builder/newtype idioms, satisfies / const type params / NoInfer / using |
| [testing.md](references/testing.md) | vitest config, mocking, testing-library setup, MSW, coverage |
| [principles.md](references/principles.md) | Type-safety posture: unknown at boundaries, parse-don't-validate, exhaustiveness |
| [project-structure.md](references/project-structure.md) | exports/imports maps, #-subpath imports, project references, run-TS-directly |
| [dependencies.md](references/dependencies.md) | Version policy, updates, knip/publint/arethetypeswrong, audit, provenance |
| [packages-always-use.md](references/packages-always-use.md) | The curated default stack (zod, Effect, True Myth, LogTape, ...) |
| [packages-utilities.md](references/packages-utilities.md) | type-fest (Tagged), es-toolkit, ts-pattern, TypeID |
| [packages-cli.md](references/packages-cli.md) | CLI framework decision table, @inquirer/prompts, Ink 7, ora, listr2 |

For code-review checklists use the `devs:code-review` skill; React UI work belongs to `devs:react-core` / the react-dev agent.

## Decision guides

**Package manager:** detect from the lockfile in existing projects and conform (`pnpm-lock.yaml`/`bun.lock`/`yarn.lock`/`package-lock.json`); prefer pnpm otherwise. Wrap network-touching commands in Socket Firewall when available: `sfw pnpm add …`, `sfw npm install`.

**Test runner:** vitest by default; `node:test` when zero-dependency matters. Details: [testing.md](references/testing.md).

**Error strategy:** exceptions at the edges, typed Results (True Myth) or Effect in the core — the decision table is in [error-handling.md](references/error-handling.md).

**Package selection:** the curated stack in [packages-always-use.md](references/packages-always-use.md) (with do-not-use lists). Prefer the platform (`fetch`, `node:test`, Temporal) when it covers the need.

**Invoking tsc:** through the project's scripts or `./node_modules/.bin/tsc` — bare `npx tsc` resolves to a squatter package, not TypeScript.

## tsconfig templates (`${CLAUDE_SKILL_DIR}/assets/tsconfig-templates/`)

TS-7-verified. `strict-base.json` is the shared baseline (strict + the valuable non-implied flags + `verbatimModuleSyntax`); variants extend it — copy the base plus one variant:

- `strict-node.json` — Node service: nodenext, `types: ["node"]`, `erasableSyntaxOnly` (sources run directly under Node's type stripping).
- `library.json` — published library: nodenext resolution, declarations + `isolatedDeclarations`.
- `strict-react.json` — React app: bundler resolution, `jsx: react-jsx`, `noEmit`.
- `monorepo-base.json` — workspace base: composite + declarations; packages add include/rootDir/outDir and project references.

All nodenext variants require `"type": "module"` in package.json (TS1287 otherwise — the comment in each file says so).

This skill deliberately ships no scaffolding scripts: framework CLIs (`npm create vite`, `pnpm create ...`) own scaffolding in this ecosystem; these templates and the greenfield spec in the typescript-dev agent cover the TypeScript layer.
Files in this package (17)
  • SKILL.md 4 KB
  • assets/tsconfig-templates/library.json 1 KB
  • assets/tsconfig-templates/monorepo-base.json 1 KB
  • assets/tsconfig-templates/strict-base.json 1 KB
  • assets/tsconfig-templates/strict-node.json 1 KB
  • assets/tsconfig-templates/strict-react.json 1 KB
  • references/common-errors.md 6 KB
  • references/dependencies.md 4 KB
  • references/error-handling.md 4 KB
  • references/packages-always-use.md 5 KB
  • references/packages-cli.md 4 KB
  • references/packages-utilities.md 4 KB
  • references/patterns.md 3 KB
  • references/principles.md 2 KB
  • references/project-structure.md 4 KB
  • references/strict-configuration.md 4 KB
  • references/testing.md 5 KB

Versions

The database has no other skills named devs:typescript-core.

Database snapshot: 13.11.2026 · package version 3811f7906fef (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 80devs:react-core
    Use when building or debugging React applications — component and hook idioms, rendering and re-render performance, state architecture, data fetching, application security, project architecture, or choosing React-ecosystem packages. Contains runtime-verified references, a…
  • 100typescript-tooling
    Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.
  • 100javascript
    Guides JavaScript and TypeScript development with modern tooling and patterns. ALWAYS trigger on "typescript", "javascript", "tsconfig", "eslint", "prettier", "vitest", "jest", "react", "node.js", "express", "npm", "package.json", "type error", "ts error", "js project setup",…
  • 100typescript
    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.
  • 100typescript
    JavaScript/TypeScript language engineering — the strictest-profile type system (discriminated unions, branded types, satisfies), parse-don't-validate boundaries with Zod, ESM and the Node runtime, typescript-eslint discipline (no floating promises), and Vitest/MSW/fast-check…
  • 80devs:react-components
    Use when creating or reviewing React components to the house style — container/presenter structure, the four-canonical-states contract, Tailwind styling and the cn() utility, headless component patterns, form implementation, component accessibility, Storybook stories, or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.