nextfriday-naming
Next Friday naming conventions for variables, constants, files, hooks, and services. Use when writing or reviewing code that involves naming identifiers.
Install
npx skillscat add next-friday/nextfriday-skills/nextfriday-naming Install via the SkillsCat registry.
The skill provides naming conventions for variables, constants, files, hooks, and services in code. It resolves ambiguity and inconsistent naming that can hinder readability and maintenance. Developers should apply these rules when writing or reviewing code to ensure clear, consistent identifiers.
Next Friday Naming Conventions
Rules for naming variables, constants, and files.
Variable Naming
Boolean Prefix
Boolean variables must use prefixes: is, has, should, can, did, will
// Bad:
const loading = true;
const visible: boolean = true;
// Good:
const isLoading = true;
const isVisible: boolean = true;Constant Case
Constants with primitive values use SCREAMING_SNAKE_CASE.
// Bad:
const apiUrl = "https://api.example.com";
const maxRetries = 3;
// Good:
const API_URL = "https://api.example.com";
const MAX_RETRIES = 3;Meaningful Names
No lazy identifiers (xxx, asdf) or single characters (except i, j, k, n, _).
// Bad:
const xxx = "value";
items.map((x) => x.id);
// Good:
const userName = "value";
items.map((item) => item.id);Service Functions
Async functions in *.service.ts use fetch prefix.
// Bad: user.service.ts
export async function getUsers() {}
// Good: user.service.ts
export async function fetchUsers() {}File Naming
| File Type | Convention | Example |
|---|---|---|
| .ts / .js | kebab-case | user-service.ts |
| .tsx / .jsx | PascalCase | UserCard.tsx |
| .md | SNAKE_CASE | README.md |
| *.hook.ts | use prefix |
useForm() |
Categories
Install
npx skillscat add next-friday/nextfriday-skills/nextfriday-naming Install via the SkillsCat registry.