---
id: daily-everything-claude-code-conventions
name: "everything-claude-code-conventions"
url: https://skills.yangsir.net/skill/daily-everything-claude-code-conventions
author: affaan-m
domain: ai-code-generation-quality
tags: ["everything", "claude", "code", "conventions", "ai"]
install_count: 5500
rating: 4.40 (20 reviews)
github: https://github.com/affaan-m/everything-claude-code
---

# everything-claude-code-conventions

> 提供 Claude Code 编码规范和最佳实践，帮助开发者编写高质量、可维护的代码

**Stats**: 5,500 installs · 4.4/5 (20 reviews)

## Before / After 对比

### 规范化提交信息

**Before**:

在没有 `everything-claude-code-conventions` Skill 的情况下，开发者需要手动记忆并严格遵循项目定义的 Conventional Commits 规范，包括使用 `fix`、`feat` 等特定前缀，保持第一行简洁并使用祈使句，以及控制消息长度。这通常需要查阅文档，并在每次提交时进行自我检查或通过代码审查来纠正不规范的提交信息。这个过程耗时且容易出错，导致提交历史不一致，增加了维护和理解项目的难度。

**After**:

启用 `everything-claude-code-conventions` Skill 后，Claude 在生成代码或建议提交时，会自动遵循项目定义的 Conventional Commits 规范。它会确保提交信息包含正确的前缀、简洁的描述，并以祈使句形式表达。开发者无需手动记忆或查阅规范，Claude 会直接输出符合要求的提交信息，或在不符合时提供即时反馈和修正建议。这显著提高了提交信息的质量和一致性，加速了开发流程，并降低了代码审查中关于提交规范的沟通成本。

| Metric | Before | After | Change |
|---|---|---|---|
| 提交信息规范符合率 | 70% | 95% | +35.71% |
| 提交信息审查与修正时间 | 5小时/月 | 1小时/月 | -80% |

### 统一代码架构与风格

**Before**:

在没有 `everything-claude-code-conventions` Skill 的情况下，开发者在编写新功能或修改现有代码时，需要手动学习并遵循项目特定的架构模式，例如混合模块组织和单一包结构，以及 JavaScript 语言的编码风格。这要求开发者投入时间阅读现有代码库、查阅内部文档，并依赖经验来确保代码与项目整体风格保持一致。尤其对于大型项目或新加入的团队成员，理解和应用这些隐性或显性规范是一个耗时且容易引入不一致性的过程。

**After**:

启用 `everything-claude-code-conventions` Skill 后，Claude 在生成或修改 JavaScript 代码时，能够自动理解并遵循项目定义的混合模块组织架构、单一包结构以及其他编码风格指南。这意味着 Claude 生成的代码将自然地融入现有项目，符合既定的文件组织、模块导入导出方式和命名约定。开发者可以专注于业务逻辑，而无需担心代码风格或架构一致性问题，因为 Claude 会确保输出的代码与项目规范高度匹配，显著减少了代码审查中关于风格和结构问题的讨论，提升了开发效率和代码质量。

| Metric | Before | After | Change |
|---|---|---|---|
| 代码风格与架构一致性 | 80% | 98% | +22.5% |
| 代码风格与架构重构时间 | 8小时/月 | 2小时/月 | -75% |

## Readme

# everything-claude-code-conventions

# Everything Claude Code Conventions

Generated from [affaan-m/everything-claude-code](https://github.com/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 related skills

**Files typically involved**:

- `rules/*/coding-style.md`

- `rules/*/hooks.md`

- `rules/*/patterns.md`

- `rules/*/security.md`

- `rules/*/testing.md`

**Example commit sequence**:

```
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 related skills

```

### Add New Skill

Adds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts.

**Frequency**: ~4 times per month

**Steps**:

- Create a new directory under skills/{skill-name}/

- Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)

- Optionally add scripts or supporting files under skills/{skill-name}/scripts/

- Address review feedback and iterate on documentation

**Files typically involved**:

- `skills/*/SKILL.md`

- `skills/*/scripts/*.sh`

- `skills/*/scripts/*.js`

**Example commit sequence**:

```
Create a new directory under skills/{skill-name}/
Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)
Optionally add scripts or supporting files under skills/{skill-name}/scripts/
Address review feedback and iterate on documentation

```

### Add New Agent

Adds a new agent to the system for code review, build resolution, or other automated tasks.

**Frequency**: ~2 times per month

**Steps**:

- Create a new agent markdown file under agents/{agent-name}.md

- Register the agent in AGENTS.md

- Optionally update README.md and docs/COMMAND-AGENT-MAP.md

**Files typically involved**:

- `agents/*.md`

- `AGENTS.md`

- `README.md`

- `docs/COMMAND-AGENT-MAP.md`

**Example commit sequence**:

```
Create a new agent markdown file under agents/{agent-name}.md
Register the agent in AGENTS.md
Optionally update README.md and docs/COMMAND-AGENT-MAP.md

```

### Add New Command

Adds a new command to the system, often paired with a backing skill.

**Frequency**: ~1 times per month

**Steps**:

- Create a new markdown file under commands/{command-name}.md

- Optionally add or update a backing skill under skills/{skill-name}/SKILL.md

**Files typically involved**:

- `commands/*.md`

- `skills/*/SKILL.md`

**Example commit sequence**:

```
Create a new markdown file under commands/{command-name}.md
Optionally add or update a backing skill under skills/{skill-name}/SKILL.md

```

### Sync Catalog Counts

Synchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state.

**Frequency**: ~3 times per month

**Steps**:

- Update agent, skill, and command counts in AGENTS.md

- Update the same counts in README.md (quick-start, comparison table, etc.)

- Optionally update other documentation files

**Files typically involved**:

- `AGENTS.md`

- `README.md`

**Example commit sequence**:

```
Update agent, skill, and command counts in AGENTS.md
Update the same counts in README.md (quick-start, comparison table, etc.)
Optionally update other documentation files

```

### Add Cross Harness Skill Copies

Adds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms.

**Frequency**: ~2 times per month

**Steps**:

- Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md

- Optionally add harness-specific openai.yaml or config files

- Address review feedback to align with CONTRIBUTING template

**Files typically involved**:

- `.agents/skills/*/SKILL.md`

- `.cursor/skills/*/SKILL.md`

- `.agents/skills/*/agents/openai.yaml`

**Example commit sequence**:

```
Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md
Optionally add harness-specific openai.yaml or config files
Address review feedback to align with CONTRIBUTING template

```

### Add Or Update Hook

Adds or updates git or bash hooks to enforce workflow, quality, or security policies.

**Frequency**: ~1 times per month

**Steps**:

- Add or update hook scripts in hooks/ or scripts/hooks/

- Register the hook in hooks/hooks.json or similar config

- Optionally add or update tests in tests/hooks/

**Files typically involved**:

- `hooks/*.hook`

- `hooks/hooks.json`

- `scripts/hooks/*.js`

- `tests/hooks/*.test.js`

- `.cursor/hooks.json`

**Example commit sequence**:

```
Add or update hook scripts in hooks/ or scripts/hooks/
Register the hook in hooks/hooks.json or similar config
Optionally add or update tests in tests/hooks/

```

### Address Review Feedback

Addresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment.

**Frequency**: ~4 times per month

**Steps**:

- Edit SKILL.md, agent, or command files to address reviewer comments

- Update examples, headings, or configuration as requested

- Iterate until all review feedback is resolved

**Files typically involved**:

- `skills/*/SKILL.md`

- `agents/*.md`

- `commands/*.md`

- `.agents/skills/*/SKILL.md`

- `.cursor/skills/*/SKILL.md`

**Example commit sequence**:

```
Edit SKILL.md, agent, or command files to address reviewer comments
Update examples, headings, or configuration as requested
Iterate until all review feedback is resolved

```

## Best Practices

Based on analysis of the codebase, follow these practices:

### Do

- Use conventional commit format (feat:, fix:, etc.)

- Follow *.test.js naming pattern

- Use camelCase for file names

- Prefer mixed exports

### Don't

- Don't write vague commit messages

- Don't skip tests for new features

- Don't deviate from established patterns without discussion

*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*
Weekly Installs305Repository[affaan-m/everyt…ude-code](https://github.com/affaan-m/everything-claude-code)GitHub Stars105.0KFirst Seen5 days agoSecurity Audits[Gen Agent Trust HubPass](/affaan-m/everything-claude-code/everything-claude-code-conventions/security/agent-trust-hub)[SocketPass](/affaan-m/everything-claude-code/everything-claude-code-conventions/security/socket)[SnykPass](/affaan-m/everything-claude-code/everything-claude-code-conventions/security/snyk)Installed oncodex297cursor272gemini-cli270amp270cline270github-copilot270

---
*Source: https://skills.yangsir.net/skill/daily-everything-claude-code-conventions*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-everything-claude-code-conventions/markdown*