coding-standard-javascript
JavaScript/TypeScript Coding Standards
When reviewing or generating JavaScript/TypeScript code, follow these rules:
File Naming
- Source files: Use kebab-case (e.g.,
user-service.js,api-client.ts) - Component files: Use kebab-case (e.g.,
user-profile.js,data-table.tsx) - Test files: Use
.test.jsor.spec.jssuffix (e.g.,user-service.test.js) - Type definition files: Use
.d.tssuffix (e.g.,api-types.d.ts)
Variable Naming
- Variables: camelCase (e.g.,
userName,isActive,totalCount) - Constants: UPPER_SNAKE_CASE for true constants (e.g.,
MAX_RETRIES,API_BASE_URL) - Boolean variables: Prefix with
is,has,can,should(e.g.,isLoading,hasError)
More from jdubray/puffin
coding-standard-cpp
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.
26coding-standard-java
Enforce Java coding standards including camelCase variables, PascalCase classes, and PascalCase filenames matching class names.
23coding-standard-python
Enforce Python PEP 8 coding standards including snake_case variables, PascalCase classes, and snake_case filenames.
20modularity-patterns
Recommends modularity, composition, and decoupling patterns for design challenges. Use when designing plugin architectures, reducing coupling, improving testability, or separating cross-cutting concerns.
17coding-standard-c
Enforce C coding standards including snake_case variables and functions, UPPER_SNAKE_CASE macros, and snake_case filenames.
16rlm
Run a Recursive Language Model-style loop for long-context tasks. Uses a persistent local Python REPL and an rlm-subcall subagent as the sub-LLM (llm_query).
1