메뉴
JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| 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.
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.
Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.