typescript-project-setup

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈2

  Distinctive · estimate

  This author's own choices. Worth a look.

• 7

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Run npx tsc --init to create a tsconfig.json file

   line 11
2. Very specific:

   Read the tsconfig.json it generates and make the edits suggested in that file:

   line 12
3. Very specific:

   If running server-side or local scripts, add node to types and npm install --save-dev @types/node

   line 13
4. Very specific:

   If using vite, esbuild, or similar bundlers, set moduleResolution to bundler

   line 15
5. Distinctive:

   If you have more specific info from the bundler info, defer to it instead

   line 16
6. Very specific:

   Create a src directory and add your TypeScript files there

   line 17
7. Very specific:

   Add a build script to your package.json that runs tsc

   line 18
8. Distinctive:

   If using a bundler, add the appropriate build script for it as well

   line 19
9. Very specific:

   If you're running TypeScript code on the commandline, tsx is no longer necessary or recommended if node 22.18.0 or later is installed.

   line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.