javascript-code
Skill5 starsChanged 5 months agoMITView on GitHub
JavaScript/TypeScript development, paradigms, and runtime environments
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When writing or maintaining JS/TS applications.
- Distinctive: line 12
When dealing with asynchronous programming (Promises, async/await).
- Distinctive: line 13
When configuring module systems (ESM vs CommonJS).
- Distinctive: line 16
Prefer TypeScript over vanilla JavaScript for large projects to leverage static typing.
- Very specific: line 17
Always use strict equality (===) and avoid loose equality (==).
- Very specific: line 18
Avoid mutating state when possible.
- Very specific: line 19
Use const by default, let when necessary, and never use var.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
JavaScript/TypeScript Code Skill
This skill manages JavaScript and TypeScript specific development practices across Node.js, browsers, and edge runtimes.
When to use this skill
- When writing or maintaining JS/TS applications.
- When dealing with asynchronous programming (Promises, async/await).
- When configuring module systems (ESM vs CommonJS).
Guidelines
- Prefer TypeScript over vanilla JavaScript for large projects to leverage static typing.
- Always use strict equality (
===) and avoid loose equality (==). - Avoid mutating state when possible; prefer functional approaches like
map,filter, andreduce. - Use
constby default,letwhen necessary, and never usevar.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- fastapiSkill
- rustSkill
- backend-codeSkill
- frontend-codeSkill
- java-codeSkill
- python-codeSkill
- codeSkill
- crash-analysisSkill
- memory-debugSkill
- network-debugSkill
- performance-debugSkill
- debugSkill
- argo-cdSkill
- dockerSkill
- github-actionsSkill
- gitlab-ciSkill
- jenkinsSkill
- kubernetesSkill
- devopsSkill
- terraformSkill
- nextjsSkill
- react-nativeSkill
- api-design-planSkill
- architecture-planSkill
- database-planSkill
- security-planSkill
- planSkill
- e2e-testSkill
- integration-testSkill
- testSkill
- tddSkill
- unit-testSkill
- smart-contractsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

