clean-codejs-naming

Naming patterns and conventions based on Clean Code JavaScript principles.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "clean-codejs-naming" with this command: npx skills add damianwrooby/javascript-clean-code-skills/damianwrooby-javascript-clean-code-skills-clean-codejs-naming

Clean Code JavaScript – Naming Patterns

Table of Contents

  • Principles
  • Variables
  • Functions
  • Booleans
  • Bad vs Good Examples

Principles

  • Names should reveal intent
  • Avoid abbreviations and mental mapping
  • Use domain language consistently

Variables

// ❌ Bad
const d = 86400000;

// ✅ Good
const MILLISECONDS_PER_DAY = 86400000;

Functions

// ❌ Bad
function getUser(u) {}

// ✅ Good
function fetchUserById(userId) {}

Booleans

// ❌ Bad
if (!user.isNotActive) {}

// ✅ Good
if (user.isActive) {}

Bad vs Good Examples

// ❌ Bad
const data = getData();

// ✅ Good
const usersResponse = fetchUsers();

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

clean-codejs-functions

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

clean-codejs-modules

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

clean-codejs-objects

No summary provided by upstream source.

Repository SourceNeeds Review