ref-sp-js-javascriptlisted

# JavaScript ## Purpose Provide portable defaults for maintainable JavaScript when full TypeScript is not the right tool, especially for scripts and browser-side code that still benefit from structure and JSDoc. ## When to use this skill - Writing plain JavaScript for scripts, browser code, or small tools. - Adding or improving JSDoc types. - Refactoring dynamic JavaScript into clearer, more explicit code. - Reviewing whether a JavaScript module should stay JS or move to TypeScript. ## Scope Boundaries - Use this skill for portable JavaScript structure and JSDoc guidance. - Use `ref-sp-js-react` when the main question is about React component structure, hooks, or React-specific dependency choices, whether the file is JavaScript or TypeScript. - Use `ref-sp-js-next` when Next.js framework concerns dominate the design. - Use `ref-sp-js-typescript` when the main question is about strict type-system design rather than JSDoc-backed JavaScript. - Use `ref-sp-dev-coding-patterns` for language-agnostic naming, comments, CLI ergonomics, and testing defaults. - Use `ref-sp-dev-projects-architecture` for portable feature-boundary or shared-utility decisions. - Use `ref-sp-js-userscript` or `ref-sp-js-web-standalone-template` when the JavaScript lives inside a userscript or standalone browser app and those constraints dominate the design. ## Defaults - Prefer modern ESM syntax. - Prefer TypeScript for modern Node and Deno code when the runtime can execute `.ts` or `.mts` directly