everything-claude-code-conventions

Apply everything-claude-code development patterns to JavaScript code and commits.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/thangvawn/agent_financial --skill everything-claude-code-conventions-thangvawn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: everything-claude-code-conventions
Source: https://github.com/thangvawn/agent_financial/tree/main/.cursor/.agents/skills/everything-claude-code
Command: npx skills add https://github.com/thangvawn/agent_financial --skill everything-claude-code-conventions-thangvawn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires none, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures that Claude adheres to the established development patterns and conventions for everything-claude-code, promoting consistency and best practices in the project.

Core Features & Use Cases

  • Conventional Commits: Follows a standardized commit message format to improve readability and ease of integration.
  • Code Style Guidelines: Provides clear naming conventions and import styles for JavaScript projects.
  • Architecture: Guides Claude in understanding the hybrid module organization and configuration files.
  • Testing: Assists in creating unit and integration tests that follow the project's file patterns.
  • Error Handling: Implements try-catch blocks for robust error handling and user-friendly messages.

Quick Start

Use the everything-claude-code-conventions skill to format your next commit message using the correct prefix and message structure.

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 format JavaScript commit messages for consistency?

JavaScript code style guidelines provide clear naming conventions and import styles for the project. Adhering to these rules ensures consistency across hybrid module organizations and configuration files.

How do I handle errors in JavaScript development?

Testing in JavaScript requires creating unit and integration tests that follow the project's file patterns. This ensures modules function correctly and maintain expected behavior across the hybrid architecture.

Can I use these conventions for non-JavaScript projects?

Conventional commits distinguish themselves from standard commit messages by enforcing a structured prefix and format. This approach improves readability and eases integration, unlike ad-hoc commit styles.

Why does my JavaScript code style fail project checks?

To start formatting conventional commits, apply the correct prefix and message structure for your next change. This ensures your commit history aligns with the project's standardized format.