Priority: P1 (HIGH). Assuming an existing JavaScript project: - No formatting wars: use Prettier consistently; run it on save and commit. - No untested code: use TDD or add post-code tests with Jest/Vitest, co-located and targeting >80% coverage. - No dirty commits: run ESLint and formatting checks before push. - Avoid unsynchronized Pkg Manager versions across `npm`, `yarn`, or `pnpm`. - Avoid mixing build tools unnecessarily: use Vite for apps and Rollup for libraries. - Avoid disabling lin...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill javascript-tooling --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Javascript Tooling?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-javascript-tooling-1ff50461)More formats (shields.io, HTML) on the badges page.
Priority: P1 (HIGH). Assuming an existing JavaScript project:
- No formatting wars: use Prettier consistently; run it on save and commit.
- No untested code: use TDD or add post-code tests with Jest/Vitest, co-located and targeting >80% coverage.
- No dirty commits: run ESLint and formatting checks before push.
- Avoid unsynchronized Pkg Manager versions across `npm`, `yarn`, or `pnpm`.
- Avoid mixing build tools unnecessarily: use Vite for apps and Rollup for libraries.
- Avoid disabling lint rules broadly; configure ESLint with recommended rules and Prettier integration.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
