everything-claude-code-conventions

Enforce JavaScript development conventions and conventional commit patterns for everything-claude-code.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/DrinkBoooz/PyTrade --skill everything-claude-code-conventions-drinkboooz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: everything-claude-code-conventions
Source: https://github.com/DrinkBoooz/PyTrade/tree/main/.opencode/skills/trading-creation-tool/ecc/skills/everything-claude-code
Command: npx skills add https://github.com/DrinkBoooz/PyTrade --skill everything-claude-code-conventions-drinkboooz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude-style development conventions and patterns for everything-claude-code need to be consistently applied across JavaScript projects to ensure maintainability and readability.

Core Features & Use Cases

  • Provides a standardized set of conventions for file naming, architecture layout, commit messages, and testing practices.
  • Guides teams on applying conventional commits, code style, and testing patterns during feature work, bug fixes, and documentation updates.
  • Example use: when starting a new feature branch, Claude should apply the project’s commit-lint rules and scaffolding patterns.

Quick Start

Instruct Claude to apply the project’s JavaScript conventions and conventional commit patterns to all changes.

Frequently Asked Questions about everything-claude-code-conventions

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

FAQPage Schema
How do I enforce conventional commits and JavaScript coding standards in my project?

You can enforce conventional commits and JavaScript coding standards by applying automated conventions for file naming, architecture layout, and commit-message formats to ensure maintainability across your codebase.

What's the best way to standardize file naming and module structure for JavaScript features?

Standardize file naming and module structure by adopting a hybrid module organization layout that guides how files are named, structured, and documented during feature and maintenance tasks.

Does this convention system work with hybrid module organization in JavaScript codebases?

Yes, this convention system is designed for JavaScript codebases that use a hybrid module organization, applying standardized import/export styles and frontmatter-driven metadata to guide development.

How do I apply frontmatter-driven metadata and commit-lint rules when starting a new feature branch?

Apply frontmatter-driven metadata and commit-lint rules by instructing Claude to scaffold new features using the project's standardized patterns, ensuring code style and commit formats are met.

Why does my team need standardized conventions for bug fixes and documentation updates?

Standardized conventions for bug fixes and documentation updates ensure consistent readability and maintainability across the project by enforcing unified code style, testing patterns, and collaboration workflows.

Can I use these coding standards for both feature work and maintenance tasks?

Yes, these coding standards apply to both feature work and maintenance tasks, providing a standardized set of conventions for file naming, architecture layout, and testing practices throughout the development lifecycle.