Everything Claude Code Conventions

Generated from

affaan-m/everything-claude-code

on 2026-03-20

Overview

This skill teaches Claude the development patterns and conventions used in everything-claude-code.

Tech Stack

Primary Language

JavaScript

Architecture

hybrid module organization

Test Location

separate

When to Use This Skill

Activate this skill when:

Making changes to this repository

Adding new features following established patterns

Writing tests that match project conventions

Creating commits with proper message format

Commit Conventions

Follow these commit message conventions based on 500 analyzed commits.

Commit Style: Conventional Commits

Prefixes Used

fix

test

feat

docs

Message Guidelines

Average message length: ~65 characters

Keep first line concise and descriptive

Use imperative mood ("Add feature" not "Added feature")

Commit message example

feat(rules): add C# language support

Commit message example

chore(deps-dev): bump flatted (#675)

Commit message example

fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691)

Commit message example

docs: add Antigravity setup and usage guide (#552)

Commit message example

merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer

Commit message example

Revert "Add Kiro IDE support (.kiro/) (#548)"

Commit message example

Add Kiro IDE support (.kiro/) (#548)

Commit message example

feat: add block-no-verify hook for Claude Code and Cursor (#649)

Architecture

Project Structure: Single Package

This project uses

hybrid

module organization.

Configuration Files

.github/workflows/ci.yml

.github/workflows/maintenance.yml

.github/workflows/monthly-metrics.yml

.github/workflows/release.yml

.github/workflows/reusable-release.yml

.github/workflows/reusable-test.yml

.github/workflows/reusable-validate.yml

.opencode/package.json

.opencode/tsconfig.json

.prettierrc

eslint.config.js

package.json

Guidelines

This project uses a hybrid organization

Follow existing patterns when adding new code

Code Style

Language: JavaScript

Naming Conventions

Element

Convention

Files

camelCase

Functions

camelCase

Classes

PascalCase

Constants

SCREAMING_SNAKE_CASE

Import Style: Relative Imports

Export Style: Mixed Style

Preferred import style

// Use relative imports

import

{

Button

}

from

'../components/Button'

import

{

useAuth

}

from

'./hooks/useAuth'

Testing

Test Framework

No specific test framework detected — use the repository's existing test patterns.

File Pattern:

*.test.js

Test Types

Unit tests

Test individual functions and components in isolation

Integration tests

Test interactions between multiple components/services

Coverage

This project has coverage reporting configured. Aim for 80%+ coverage.

Error Handling

Error Handling Style: Try-Catch Blocks

Standard error handling pattern

try

{

const

result

=

await

riskyOperation

(

)

return

result

}

catch

(

error

)

{

console

.

error

(

'Operation failed:'

,

error

)

throw

new

Error

(

'User-friendly message'

)

}

Common Workflows

These workflows were detected from analyzing commit patterns.

Database Migration

Database schema changes with migration files

Frequency

~2 times per month

Steps

:

Create migration file

Update schema definitions

Generate/update types

Files typically involved

:

*/schema.

migrations/*

Example commit sequence

:

feat: implement --with/--without selective install flags (#679)

fix: sync catalog counts with filesystem (27 agents, 113 skills, 58 commands) (#693)

feat(rules): add Rust language rules (rebased #660) (#686)

Feature Development

Standard feature implementation workflow

Frequency

~22 times per month

Steps

:

Add feature implementation

Add tests for feature

Update documentation

Files typically involved

:

manifests/*

schemas/*

/.test.

/api/

Example commit sequence

:

feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer

docs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex/Cursor) skill copies

fix: address PR review — skill template (When to use, How it works, Examples), bun.lock, next build note, rust-reviewer CI note, doc-lookup privacy/uncertainty

Add Language Rules

Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines.

Frequency

~2 times per month Steps : Create a new directory under rules/{language}/ Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content Optionally reference or link to