lang-js

Standardize JavaScript code to Google JS Style with ESM-only conventions.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-js
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lang-js
Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/lang-js
Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-js

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives teams a shared JavaScript standard so code stays consistent, readable, and easy to maintain across new features, refactors, and reviews.

Core Features & Use Cases

  • Style Guidance: Follows Google JS Style, prefers const by default, and avoids deprecated patterns like var.
  • Modern Runtime Practices: Encourages ESM-only modules, async and await, destructuring, spread syntax, and Node 22+ compatibility.
  • Quality Tooling: Aligns code with Prettier, ESLint, Vitest, Jest, and JSDoc expectations for production-ready work.
  • Use Case: Use this Skill when writing a new module, reviewing a pull request, or cleaning up legacy JavaScript to match repository conventions.

Quick Start

Ask for JavaScript code or a review that follows lang-js standards, uses ESM, and applies Google JS Style consistently.

Frequently Asked Questions about lang-js

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

FAQPage Schema
How do I standardize JavaScript code to match Google JS Style and ESM conventions?

Configure ESLint and Prettier to enforce Google JS Style and ESM-only conventions. This standardization ensures consistent use of const, async/await, and JSDoc across Node 22+ projects for readable, maintainable code.

What is the best way to write modern JavaScript modules for Node 22+ projects?

Write modern JavaScript modules for Node 22+ by adopting ESM-only conventions, async/await, and destructuring. Integrating JSDoc for public APIs ensures your code aligns with Google JS Style and remains readable.

Does this JavaScript standardization approach work with Vitest and Jest testing frameworks?

Yes, the standardization approach supports Vitest and Jest testing frameworks. It aligns test writing across application and library code with modern tooling expectations, ensuring production-ready quality and consistent style.

How do I use ESLint and Prettier to enforce modern JavaScript style guidelines during code review?

Use ESLint and Prettier to enforce modern JavaScript style guidelines during code review. This combination standardizes formatting, enforces const by default, and flags deprecated patterns like var for consistent, readable code.

Can I use this standard for refactoring legacy JavaScript to match modern repository conventions?

Yes, use this standard to refactor legacy JavaScript to match modern repository conventions. It guides transitions to ESM-only modules, async/await, and JSDoc, ensuring clean, production-ready code for new features and reviews.