InstructionMITv1.0.0awesome-copilot

Code Generation Guidelines

Guidelines for writing Node.js and JavaScript code with Vitest testing

At a glance

Kind
Instruction · Ananke prompt
Reference
awesome-copilot/nodejs-javascript-vitest · ananke://prompt/awesome-copilot/nodejs-javascript-vitest@1.0.0
Applies to
**/*.js, **/*.mjs, **/*.cjs
Files
1 · 1.4 KB
How it's used
Instructions apply automatically to files matching their applyTo glob in GitHub Copilot. For Claude Code, reference the file from CLAUDE.md.

Upstream metadata

applyTo**/*.js, **/*.mjs, **/*.cjs

Documentation

View upstream ↗
Contents

Coding standards

  • Use JavaScript with ES2022 features and Node.js (20+) ESM modules
  • Use Node.js built-in modules and avoid external dependencies where possible
  • Ask the user if you require any additional dependencies before adding them
  • Always use async/await for asynchronous code, and use ‘node:util’ promisify function to avoid callbacks
  • Keep the code simple and maintainable
  • Use descriptive variable and function names
  • Do not add comments unless absolutely necessary, the code should be self-explanatory
  • Never use null, always use undefined for optional values
  • Prefer functions over classes

Testing

  • Use Vitest for testing
  • Write tests for all new features and bug fixes
  • Ensure tests cover edge cases and error handling
  • NEVER change the original code to make it easier to test, instead, write tests that cover the original code as it is

Documentation

  • When adding new features or making significant changes, update the README.md file where necessary

User interactions

  • Ask questions if you are unsure about the implementation details, design choices, or need clarification on the requirements
  • Always answer in the same language as the question, but use english for the generated content like code, comments or docs