// JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.
Code design patterns: pure functions, immutability, composition, and async. Use when designing code or functions.
System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.
CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.
Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.
Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.
Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.
| name | javascript-practices |
| description | JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code. |
Conventions for JS/TS syntax, modules, types, and runtime behavior.
import * as path from "@std/path"; // namespace import
import { utils } from "./utils.ts"; // explicit extension
export function buildConfig() {} // direct named export
const port = config.port ?? 8000; // nullish coalescing
Modules: Direct named exports, namespace imports, explicit .ts extensions
Syntax: const over let, always semicolons, === strict equality, ??
over ||
Types: Number() over +, instanceof over typeof, prefer null over
undefined
Runtime: import.meta.dirname, globalThis over window, optional
projectRoot params
Async: Use return await consistently for better stack traces and correct
error handling
Avoid: eval, prototype mutation, truthy/falsy checks on non-booleans
See rules.md for complete guidelines with examples.