skills.rest
Rzyfront
RzyfrontCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vendix-naming-conventions

Enforce Vendix naming conventions for code identifiers and file names.

5|Updated Aug 23, 2025
Search Tags:#linting#coding-standards#snake_case#CamelCase#PascalCase#enforce-naming
One-click install
npx skills add https://github.com/Rzyfront/Vendix --skill vendix-naming-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vendix-naming-conventions
Source: https://github.com/Rzyfront/Vendix/tree/main/skills/vendix-naming-conventions
Command: npx skills add https://github.com/Rzyfront/Vendix --skill vendix-naming-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces Vendix naming conventions across codebases to prevent inconsistent naming and related bugs, improving readability and maintainability.

Core Features & Use Cases

  • Enforces snake_case for variables.
  • Enforces CamelCase for functions.
  • Enforces PascalCase for classes and interfaces.
  • Enforces SCREAMING_SNAKE_CASE for constants.
  • Enforces kebab-case for files and folders.
  • Use Case: Standardize naming across new projects and when onboarding new contributors to accelerate collaboration.

Quick Start

Review your codebase and start applying the Vendix naming conventions to new and existing files.

Frequently Asked Questions about vendix-naming-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce naming conventions like snake_case and CamelCase in CI lint checks?▼

You can enforce naming conventions across variables, functions, classes, and files by codifying precise rules for snake_case, CamelCase, PascalCase, SCREAMING_SNAKE_CASE, and kebab-case to enable CI lint checks and prevent inconsistent identifiers during code reviews.

What is the standard naming convention for variables, functions, and classes?▼

Standard naming conventions typically enforce snake_case for variables, CamelCase for functions, PascalCase for classes and interfaces, and SCREAMING_SNAKE_CASE for constants to improve code readability and maintainability.

Can I enforce kebab-case for file and folder names across an existing codebase?▼

Yes, you can enforce kebab-case for files and folders by applying naming rules to new and existing files, standardizing naming across projects and accelerating collaboration when onboarding new contributors.

Does enforcing coding standards and linting rules require any external dependencies?▼

No, enforcing these coding standards and linting rules requires no external dependencies, allowing you to review your codebase and start applying the naming conventions directly into your development workflows.

Why do I need strict naming conventions for enums and interfaces?▼

Strict naming conventions for enums and interfaces prevent inconsistent identifiers that cause bugs and slow code reviews, ensuring team-wide adoption and maintaining codebase readability and maintainability.

Related Skills

Explore More Software Engineering Skills→
jdubrayjdubray
27

coding-standard-javascript

Enforce JavaScript/TypeScript naming conventions for files, variables, functions, classes, and constants.

Community
Intermediate
cq112233cq112233
21

chinese-git-workflow

Standardize Git workflows and configurations for Chinese hosting services.

Community
Intermediate
Jaydpatel01Jaydpatel01

code-quality-and-review

Enforce code correctness, readability, and safety with linters and type checkers.

Community
Advanced
ilamanovilamanov

codebase-conventions

Enforce coding conventions for file organization, naming, and tool usage.

Community
Intermediate