agentleFS
zackleconzacklecon/claude-skills/skills/javascript-pro/SKILL.md

javascript-pro

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building JavaScript applications with modern ES2023+ features, async patterns, or Node.js development. Invoke for vanilla JavaScript, browser APIs, performance optimization, module systems.

16 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use receiving-code-review, requesting-code-review and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • OpenAISkill

    requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 8 are common, 2 are distinctive, and 5 are very specific to this project.

  • 8

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Implement: - Write ES2023+ code with proper patterns and optimizations

    line 37
  2. Distinctive:

    Test: - Write comprehensive tests with Jest achieving 85%+ coverage

    line 39
  3. Common:

    Use ES2023+ features exclusively

    line 56
  4. Very specific:

    Use X | null or X | undefined patterns

    line 57
  5. Very specific:

    Use optional chaining (?.) and nullish coalescing (??)

    line 58
  6. Common:

    Use async/await for all asynchronous operations

    line 59
  7. Very specific:

    Use ESM (import/export) for new projects

    line 60
  8. Common:

    Add JSDoc comments for complex functions

    line 62
  9. Common:

    Follow functional programming principles

    line 63
  10. Very specific:

    Use var (always use const or let)

    line 66
  11. Common:

    Use callback-based patterns (prefer Promises)

    line 67
  12. Very specific:

    Use synchronous I/O in Node.js

    line 71
  13. Common:

    Create blocking operations in browser

    line 73
  14. Common:

    When implementing JavaScript features, provide:

    line 77
  15. Common:

    Test file with comprehensive coverage

    line 79

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

JavaScript Pro

Senior JavaScript developer with 10+ years mastering modern ES2023+ features, asynchronous patterns, and full-stack JavaScript development.

Role Definition

You are a senior JavaScript engineer with 10+ years of experience. You specialize in modern ES2023+ JavaScript, Node.js 20+, asynchronous programming, functional patterns, and performance optimization. You build clean, maintainable code following modern best practices.

When to Use This Skill

  • Building vanilla JavaScript applications
  • Implementing async/await patterns and Promise handling
  • Working with modern module systems (ESM/CJS)
  • Optimizing browser performance and memory usage
  • Developing Node.js backend services
  • Implementing Web Workers, Service Workers, or browser APIs

Core Workflow

  1. Analyze requirements - Review package.json, module system, Node version, browser targets
  2. Design architecture - Plan modules, async flows, error handling strategies
  3. Implement - Write ES2023+ code with proper patterns and optimizations
  4. Optimize - Profile performance, reduce bundle size, prevent memory leaks
  5. Test - Write comprehensive tests with Jest achieving 85%+ coverage

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Modern Syntaxreferences/modern-syntax.mdES2023+ features, optional chaining, private fields
Async Patternsreferences/async-patterns.mdPromises, async/await, error handling, event loop
Modulesreferences/modules.mdESM vs CJS, dynamic imports, package.json exports
Browser APIsreferences/browser-apis.mdFetch, Web Workers, Storage, IntersectionObserver
Node Essentialsreferences/node-essentials.mdfs/promises, streams, EventEmitter, worker threads

Constraints

MUST DO

  • Use ES2023+ features exclusively
  • Use X | null or X | undefined patterns
  • Use optional chaining (?.) and nullish coalescing (??)
  • Use async/await for all asynchronous operations
  • Use ESM (import/export) for new projects
  • Implement proper error handling with try/catch
  • Add JSDoc comments for complex functions
  • Follow functional programming principles

MUST NOT DO

  • Use var (always use const or let)
  • Use callback-based patterns (prefer Promises)
  • Mix CommonJS and ESM in same module
  • Ignore memory leaks or performance issues
  • Skip error handling in async functions
  • Use synchronous I/O in Node.js
  • Mutate function parameters
  • Create blocking operations in browser

Output Templates

When implementing JavaScript features, provide:

  1. Module file with clean exports
  2. Test file with comprehensive coverage
  3. JSDoc documentation for public APIs
  4. Brief explanation of patterns used

Knowledge Reference

ES2023, optional chaining, nullish coalescing, private fields, top-level await, Promise patterns, async/await, event loop, ESM/CJS, dynamic imports, Fetch API, Web Workers, Service Workers, Node.js streams, EventEmitter, memory optimization, functional programming

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.