js-conventions

Applies JavaScript and TypeScript coding conventions for Node.js 24+ projects.

2|Updated May 16, 2026
One-click install
npx skills add https://github.com/avbel/ai-skills --skill js-conventions-avbel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: js-conventions
Source: https://github.com/avbel/ai-skills/tree/main/skills/js-conventions
Command: npx skills add https://github.com/avbel/ai-skills --skill js-conventions-avbel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? JavaScript and TypeScript projects accumulate inconsistent style, outdated dependencies, and conflicting lint setups. This Skill gives your AI agent a single authoritative rulebook covering package management, module systems, async patterns, type safety, error handling, and lint toolchain detection so generated code matches modern project conventions without repeated explanation. ## Core Features & Use Cases - Lint Toolchain Detection: Detects whether a project uses Biome, XO, or ESLint and follows the existing config exactly, never running a second formatter over the same files. - Modern Code Standards: Enforces ESM with ES2024+, node: prefixed imports, async/await patterns, strict TypeScript typing without any, and structured error handling with cause chaining. - Legacy Package Replacement: Maps deprecated packages like lodash, axios, moment, and request to native Node.js equivalents such as fetch, crypto.randomUUID(), and structuredClone(). - Use Case: When adding a feature to a TypeScript service, the agent detects the project's Biome config, writes ESM code with proper error wrapping, replaces a proposed axios dependency with native fetch, and validates with pnpm biome check and tsc --noEmit. ## Quick Start Ask your AI agent to write or modify JavaScript or TypeScript files in your project and it will automatically apply these conventions, detect your lint setup, and run post-edit validation.

Frequently Asked Questions about js-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent JavaScript code style with AI coding agents?▼

Provide the agent with explicit conventions covering formatting, naming, imports, and error handling. This Skill detects the project's existing Biome, XO, or ESLint config and instructs the agent to follow it exactly rather than introducing new rules.

Biome vs ESLint vs XO for TypeScript projects?▼

Biome is a single Rust binary combining formatting, linting, and import sorting, replacing Prettier plus ESLint. XO is an opinionated ESLint wrapper with TypeScript support. The Skill detects whichever is configured and never runs two tools over the same files.

What npm packages should I replace with native Node.js features?▼

Replace lodash with native Array/Object methods, axios and node-fetch with native fetch, uuid with crypto.randomUUID(), rimraf with fs.rm recursive, dotenv with node --env-file, and moment with Temporal or date-fns. Node 18-24+ includes these natively.

Does Biome replace TypeScript type checking?▼

No, Biome is not a type checker. Keep tsc --noEmit in CI because type-aware rules like no-floating-promises have no Biome equivalent. Run Biome for lint and format, then tsc separately for type validation.

When should I disable a lint rule in Biome or ESLint?▼

Prefer changing the project config over inline disable comments, and ask for user confirmation first. Use narrow single-line suppressions with a documented reason, and never suppress an entire file with eslint-disable or biome-ignore-all.