everything-claude-code-conventions

Name: everything-claude-code-conventions
Availability: InStock
Author: cescrafli

Enforce JavaScript development conventions and conventional commit patterns.

Updated Mar 26, 2026

Search Tags:#architecture #javascript #conventions #coding-standards #project-structure #commit-messages

Ready to run

npx skills add https://github.com/cescrafli/compyrasion --skill everything-claude-code-conventions-cescrafli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: everything-claude-code-conventions
Source: https://github.com/cescrafli/compyrasion/tree/main/.claude/skills/everything-claude-code
Command: npx skills add https://github.com/cescrafli/compyrasion --skill everything-claude-code-conventions-cescrafli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes JavaScript development practices and conventional commit patterns for everything-claude-code to ensure consistency, quality, and maintainability across the project.

Core Features & Use Cases

Establishes file naming, project structure, and coding standards aligned with the repository.
Provides guidelines for architecture, testing patterns, and commit messages to improve collaboration.
Use Case: When implementing changes, apply the conventions to produce clean diffs and predictable behavior across teammates.

Quick Start

Apply the conventions when making a change to the codebase.

Frequently Asked Questions about everything-claude-code-conventions

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

FAQPage Schema

What are conventional commit messages and why use them for JavaScript projects?▼

Conventional commit messages standardize commit history by enforcing a consistent format for JavaScript development. This structured approach improves collaboration and ensures predictable behavior across team workflows.

How do I enforce coding standards and project structure conventions in a JavaScript codebase?▼

You enforce coding standards by applying predefined rules for file naming, project structure, and architecture. This standardizes development practices to ensure consistency, quality, and maintainability across the repository.

What's the best way to standardize JavaScript architecture and file naming conventions across a team?▼

The best way to standardize JavaScript architecture is to establish shared guidelines for file naming and project structure. Applying these conventions during codebase maintenance produces clean diffs and predictable behavior.

Does this coding conventions skill require specific JavaScript frameworks or dependencies to work?▼

No specific JavaScript frameworks or dependencies are required. The coding conventions apply broadly to codebase maintenance, feature development, and collaboration workflows without external component dependencies.

When do I need conventional commit patterns and coding standards for codebase maintenance?▼

You need conventional commit patterns and coding standards when making changes to a codebase to ensure consistent style. They are required during feature development and collaboration to maintain architecture clarity and quality.