agentleFS
DojoCodingLabsDojoCodingLabs/code-sensei/skills/javascript/SKILL.md

javascript

Skill14 starsChanged 8 months agoMITView on GitHub

JavaScript essentials for vibecoders. Activated when Claude works with .js/.mjs/.jsx/.ts files. Covers the language concepts most commonly encountered during vibecoding.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use java.

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.
  • testdino-hqSkill

    java

    Google's official Java style guide. Covers 2-space indentation, 100-char line limit, naming conventions, braces, imports, Javadoc, exception handling, lambdas, and streams. Enforces @Override annotations and specific imports.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Analogy: If HTML is the skeleton and CSS is the skin, JavaScript is the brain and muscles.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 8 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 — CodeSensei Teaching Module

What is JavaScript?

  • Analogy: If HTML is the skeleton and CSS is the skin, JavaScript is the brain and muscles. It makes things HAPPEN — clicks, animations, data loading, form validation.
  • Key insight: JavaScript runs in the browser (frontend) AND on the server (backend with Node.js). Same language, two different environments.

Core Concepts to Teach (in order of frequency during vibecoding)

const / let / var

  • const = a constant, can't be reassigned (use this most of the time)
  • let = a variable that can change
  • var = the old way, avoid it (mention only if Claude uses it)
  • Quiz: "Why did Claude use const instead of let here?"

Arrow Functions () => {}

  • Analogy: A shorthand recipe card. Instead of writing "Function: do this thing," you write "=> do this thing"
  • This is the #1 syntax that confuses beginners. Normalize it early.

Objects {}

  • Analogy: A filing cabinet with labeled drawers. Each drawer (property) has a name and contains something.
  • { name: "Juan", age: 25 } — the object has two "drawers"

Arrays []

  • Analogy: A numbered list. Items have positions (starting from 0, not 1!)
  • .map(), .filter(), .forEach() — the "assembly line" methods

Async/Await

  • Analogy: Ordering food at a restaurant. You place the order (await) and the kitchen works on it while you chat. When it's ready, it arrives. You don't stand at the kitchen door waiting.
  • Key insight: Some things take time (loading data, saving to database). await means "wait for this to finish before moving on."

Import/Export

  • Analogy: Sharing tools between workshops. export puts a tool in the shared toolbox. import grabs it from there.
  • Key insight: This is how code is organized into separate files that work together.

Template Literals `Hello ${name}`

  • Analogy: Mad Libs — the backtick string has blanks (${}) that get filled in with real values.

Common Patterns in Vibecoded Projects

  • fetch() — asking another server for data (like calling a restaurant for delivery)
  • .then() / .catch() — what to do when the data arrives / if something goes wrong
  • JSON.parse() / JSON.stringify() — translating between text and data objects
  • console.log() — leaving yourself a note to see what's happening (debugging)

What NOT to Teach Early

  • Prototypes, closures, this keyword, generators, symbols, proxies
  • These are advanced topics that vibecoders rarely encounter directly

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.