Code Generation Guidelines
Guidelines for writing Node.js and JavaScript code with Vitest testing
MCP get_skill({ skillId: "code-generation-guidelines-4600a6e8" })Use this skill with your agent
Create a free account and connect via MCP
# Code Generation Guidelines ## 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
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Agents Playwright Tester
Testing mode for Playwright tests
Act Informed: First understand together with the human, then do
Interactive, input-tool powered, task refinement workflow: interrogates scope, deliverables, constraints before carrying out the task; Requires the Joyride extension.
Agent Skills File Guidelines
Guidelines for creating high-quality Agent Skills for GitHub Copilot