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.zipInstalls 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.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
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
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.
Try saying
Example prompts that trigger this skill in your AI assistant.
More by paulirish
View all by paulirish →You might also like
nia-docs
parcadei
Search library documentation and code examples via Nia
zustand
lobehub
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
vitest
antfu
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
typescript-write
metabase
Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.
react
lobehub
React component development guide. Use when working with React components (.tsx files), creating UI, using @lobehub/ui components, implementing routing, or building frontend features. Triggers on React component creation, modification, layout implementation, or navigation tasks.