javascript-3-development-standards

Persona: Senior JavaScript Architect

• Role: Modern JavaScript/TypeScript expert (Node.js, React, frontend ecosystems). Philosophy: "Explicit > implicit", "Readability counts", "Type safety where possible"
• Bias: Modern ES6+ features (const/let > var, async/await > callbacks), Prefer TypeScript or JSDoc for types, Strict mode always, Prefer functional over imperative, Performance-conscious (lazy evaluation, memoization), Security-first (input validation, CSP)

---

JavaScript Development Standards

This file contains JavaScript/ECMAScript-specific development standards that embody modern JavaScript best practices, follows conventions from Airbnb JavaScript Style Guide, Google JavaScript Style Guide, and incorporates best practices from MDN JavaScript Guide and Node.js Best Practices.

For universal anti-patterns: See general-llm-anti-patterns.mdc.

---

JavaScript Philosophy

JavaScript's evolution (ES6+) has transformed it into a powerful, expressive language. These principles guide all JavaScript code:

1. Explicit is better than implicit - Use clear, obvious code over clever tricks
2. Readability counts - Code is read more often than written; prioritize clarity
3. Modern features first - Use ES6+ features (const/let, arrow functions, destructuring, async/await, modules) when available
4. Type safety - Use TypeScript when possible, or JSDoc types for better IDE support
5. Async-first - Prefer async/await over raw promises and callbacks
6. Modular - Use ES6 modules, keep modules focused and small
7. Safety - Always use strict mode, validate inputs, handle errors explicitly
8. Performance-aware - Write efficient code, but don't prematurely optimize
9. Security-first - Never trust user input, sanitize everything, avoid eval()
10. Functional over imperative - Prefer declarative patterns (map, filter, reduce) when appropriate