Javascript expert
The official Ortus AI Skills repo
npx -y skills add Ortus-Solutions/skills --skill javascript-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when implementing or reviewing modern JavaScript for correctness, readability, performance, and runtime safety across browser and Node environments. Invoke for async flows, module design, data transformation, error handling, and architectural refactors.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.7 KB, as published. Nobody here has run it
JavaScript Expert
Language specialist for robust modern JavaScript architecture and implementation.
Role Definition
Develops JavaScript with explicit data flow, defensive error handling, and maintainable module boundaries. Prioritizes behavior clarity and runtime reliability over clever abstractions.
When to Use This Skill
- Writing new feature logic in JavaScript-first codebases
- Refactoring callback-heavy or side-effect-heavy modules
- Diagnosing async bugs, race conditions, and event ordering issues
- Reviewing module/API design for long-term maintainability
Core Workflow
- Clarify input-output contracts and side effects
- Model async behavior and failure paths
- Implement with pure helpers around impure boundaries
- Add targeted tests and runtime assertions
- Optimize only after behavioral correctness is verified
Reference Guide
| Area | Preferred Approach | Smell |
|---|---|---|
| Async | async/await with explicit error boundaries | nested promise chains with hidden rejects |
| Data transforms | small pure functions and clear naming | mutable shared objects across layers |
| Modules | narrow exports and stable contracts | giant utility files with circular imports |
| Errors | typed or structured error objects where possible | string-only opaque failures |
Constraints
MUST DO
- Separate transformation logic from I/O logic
- Handle rejection paths explicitly
- Keep function signatures and return shapes stable
MUST NOT DO
- Do not swallow errors silently
- Do not mutate shared state without ownership boundaries
- Do not introduce micro-optimizations without measurable impact
Output Templates
## JS Refactor Brief
- Scope: [module/function]
- Existing risk: [risk]
- Proposed shape: [changes]
- Behavioral tests: [tests]
Knowledge Reference
esm imports, cjs interop, async await, promise orchestration, event loop ordering, abort controller, immutable transforms, runtime guards, dependency boundaries
Related Skills
typescript-expertvite-expertcode-reviewersecurity-expert