BU

build-free-types

Enables type safety in vanilla JavaScript using JSDoc, eliminating the need for a separate build or compilation step.

Install

mkdir -p .claude/skills/build-free-types && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2302" && unzip -o skill.zip -d .claude/skills/build-free-types && rm skill.zip

Installs to .claude/skills/build-free-types

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when the user asks to "set up types without a build step", "use vanilla JS with types", "configure erasable syntax", or mentions "JSDoc type checking". It provides instructions for modern type safety using JSDoc in browsers and native TypeScript execution in Node.js.
271 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Configure JSDoc type checking for browser code
  • →Enable native TypeScript execution in Node.js
  • →Enforce erasable syntax for build-free projects
  • →Manage type checking via a single root tsconfig.json

How it works

It configures the TypeScript compiler to check JavaScript files using JSDoc and enables native execution of TypeScript files in Node.js by enforcing erasable syntax.

Inputs & outputs

You give it
Vanilla JavaScript or TypeScript source files
You get back
Type-safe code execution without a compilation step

When to use build-free-types

  • →Set up types without a build step
  • →Enable JSDoc type checking in VS Code
  • →Configure vanilla JS for type safety

About build-free-types

Provides instructions and configuration for implementing JSDoc-based type checking. It helps developers maintain modern type safety in projects that use erasable syntax or raw JS.

This skill should be used when the user asks to "set up types without a build step", "use vanilla JS with types", "configure erasable syntax", or mentions "JSDoc type checking". It provides instructions for modern type safety using JSDoc in browsers and native TypeScript execution in Node.js.

When not to use it

  • →Projects requiring non-erasable features like enums or namespaces
  • →Projects where explicit include fields are strictly required for directory isolation

Prerequisites

Node.js v24.11.0 or higherTypeScript 5.5+ for modern JSDoc imports

Limitations

  • →Cannot use non-erasable TypeScript features like enums
  • →Requires strict adherence to file extension rules in imports

How it compares

Unlike traditional setups that require a build step like tsc, this approach uses native runtime execution and IDE-based type checking.

Compared to similar skills

build-free-types side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
build-free-types (this skill)97moNo flagsIntermediate
nia-docs110moReviewBeginner
zustand1135moNo flagsIntermediate
turborepo615moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry