From 747a9499e0f43cf160cab7cab78bf47173799349 Mon Sep 17 00:00:00 2001 From: "ecc-tools[bot]" <257055122+ecc-tools[bot]@users.noreply.github.com> Date: Fri, 3 Apr 2026 12:33:31 +0000 Subject: [PATCH] feat: add everything-claude-code-conventions ECC bundle (.agents/skills/everything-claude-code/SKILL.md) --- .../skills/everything-claude-code/SKILL.md | 322 ++---------------- 1 file changed, 37 insertions(+), 285 deletions(-) diff --git a/.agents/skills/everything-claude-code/SKILL.md b/.agents/skills/everything-claude-code/SKILL.md index 173826a8..bda24423 100644 --- a/.agents/skills/everything-claude-code/SKILL.md +++ b/.agents/skills/everything-claude-code/SKILL.md @@ -1,11 +1,11 @@ --- name: everything-claude-code-conventions -description: Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits. +description: Development conventions and patterns for everything-claude-code. TypeScript project with conventional commits. --- # Everything Claude Code Conventions -> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-03-20 +> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-03 ## Overview @@ -13,7 +13,7 @@ This skill teaches Claude the development patterns and conventions used in every ## Tech Stack -- **Primary Language**: JavaScript +- **Primary Language**: TypeScript - **Architecture**: hybrid module organization - **Test Location**: separate @@ -27,20 +27,17 @@ Activate this skill when: ## Commit Conventions -Follow these commit message conventions based on 500 analyzed commits. +Follow these commit message conventions based on 10 analyzed commits. ### Commit Style: Conventional Commits ### Prefixes Used -- `fix` -- `test` - `feat` -- `docs` ### Message Guidelines -- Average message length: ~65 characters +- Average message length: ~94 characters - Keep first line concise and descriptive - Use imperative mood ("Add feature" not "Added feature") @@ -48,49 +45,37 @@ Follow these commit message conventions based on 500 analyzed commits. *Commit message example* ```text -feat(rules): add C# language support +feat: add everything-claude-code-conventions ECC bundle (.claude/ecc-tools.json) ``` *Commit message example* ```text -chore(deps-dev): bump flatted (#675) +feat: add everything-claude-code-conventions ECC bundle (.claude/identity.json) ``` *Commit message example* ```text -fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691) +feat: add everything-claude-code-conventions ECC bundle (.codex/agents/explorer.toml) ``` *Commit message example* ```text -docs: add Antigravity setup and usage guide (#552) +feat: add everything-claude-code-conventions ECC bundle (.codex/agents/reviewer.toml) ``` *Commit message example* ```text -merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer +feat: add everything-claude-code-conventions ECC bundle (.codex/agents/docs-researcher.toml) ``` *Commit message example* ```text -Revert "Add Kiro IDE support (.kiro/) (#548)" -``` - -*Commit message example* - -```text -Add Kiro IDE support (.kiro/) (#548) -``` - -*Commit message example* - -```text -feat: add block-no-verify hook for Claude Code and Cursor (#649) +feat: add everything-claude-code-conventions ECC bundle (.claude/commands/feature-development.md) ``` ## Architecture @@ -99,21 +84,6 @@ feat: add block-no-verify hook for Claude Code and Cursor (#649) 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 @@ -121,7 +91,7 @@ This project uses **hybrid** module organization. ## Code Style -### Language: JavaScript +### Language: TypeScript ### Naming Conventions @@ -134,7 +104,7 @@ This project uses **hybrid** module organization. ### Import Style: Relative Imports -### Export Style: Mixed Style +### Export Style: Named Exports *Preferred import style* @@ -145,72 +115,24 @@ 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* +*Preferred export style* ```typescript -try { - const result = await riskyOperation() - return result -} catch (error) { - console.error('Operation failed:', error) - throw new Error('User-friendly message') -} +// Use named exports +export function calculateTotal() { ... } +export const TAX_RATE = 0.1 +export interface Order { ... } ``` ## Common Workflows These workflows were detected from analyzing commit patterns. -### Database Migration - -Database schema changes with migration files - -**Frequency**: ~2 times per month - -**Steps**: -1. Create migration file -2. Update schema definitions -3. 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 +**Frequency**: ~30 times per month **Steps**: 1. Add feature implementation @@ -218,205 +140,37 @@ Standard feature implementation workflow 3. Update documentation **Files typically involved**: -- `manifests/*` -- `schemas/*` -- `**/*.test.*` -- `**/api/**` +- `.claude/commands/*` **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 +feat: add everything-claude-code-conventions ECC bundle (.claude/ecc-tools.json) +feat: add everything-claude-code-conventions ECC bundle (.claude/skills/everything-claude-code/SKILL.md) +feat: add everything-claude-code-conventions ECC bundle (.agents/skills/everything-claude-code/SKILL.md) ``` -### Add Language Rules +### Add Ecc Bundle Component -Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines. +Adds a new component to the everything-claude-code-conventions ECC bundle, such as a tool definition, skill file, identity, or command documentation. -**Frequency**: ~2 times per month +**Frequency**: ~5 times per month **Steps**: -1. Create a new directory under rules/{language}/ -2. Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content -3. Optionally reference or link to related skills +1. Create or update a file under a relevant ECC bundle directory (e.g., .claude/ecc-tools.json, .claude/skills/everything-claude-code/SKILL.md, .agents/skills/everything-claude-code/SKILL.md, .claude/identity.json, .claude/commands/*.md) +2. Commit the file with a message indicating addition to the ECC bundle **Files typically involved**: -- `rules/*/coding-style.md` -- `rules/*/hooks.md` -- `rules/*/patterns.md` -- `rules/*/security.md` -- `rules/*/testing.md` +- `.claude/ecc-tools.json` +- `.claude/skills/everything-claude-code/SKILL.md` +- `.agents/skills/everything-claude-code/SKILL.md` +- `.claude/identity.json` +- `.claude/commands/feature-development.md` +- `.claude/commands/add-ecc-bundle-component.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**: -1. Create a new directory under skills/{skill-name}/ -2. Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.) -3. Optionally add scripts or supporting files under skills/{skill-name}/scripts/ -4. 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**: -1. Create a new agent markdown file under agents/{agent-name}.md -2. Register the agent in AGENTS.md -3. 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 Workflow Surface - -Adds or updates a workflow entrypoint. Default to skills-first; only add a command shim when legacy slash compatibility is still required. - -**Frequency**: ~1 times per month - -**Steps**: -1. Create or update the canonical workflow under skills/{skill-name}/SKILL.md -2. Only if needed, add or update commands/{command-name}.md as a compatibility shim - -**Files typically involved**: -- `skills/*/SKILL.md` -- `commands/*.md` (only when a legacy shim is intentionally retained) - -**Example commit sequence**: -``` -Create or update the canonical skill under skills/{skill-name}/SKILL.md -Only if needed, add or update commands/{command-name}.md as a compatibility shim -``` - -### 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**: -1. Update agent, skill, and command counts in AGENTS.md -2. Update the same counts in README.md (quick-start, comparison table, etc.) -3. 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**: -1. Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md -2. Optionally add harness-specific openai.yaml or config files -3. 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**: -1. Add or update hook scripts in hooks/ or scripts/hooks/ -2. Register the hook in hooks/hooks.json or similar config -3. 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**: -1. Edit SKILL.md, agent, or command files to address reviewer comments -2. Update examples, headings, or configuration as requested -3. 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 +Create or update a file under a relevant ECC bundle directory (e.g., .claude/ecc-tools.json, .claude/skills/everything-claude-code/SKILL.md, .agents/skills/everything-claude-code/SKILL.md, .claude/identity.json, .claude/commands/*.md) +Commit the file with a message indicating addition to the ECC bundle ``` @@ -427,14 +181,12 @@ 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 +- Prefer named exports ### Don't - Don't write vague commit messages -- Don't skip tests for new features - Don't deviate from established patterns without discussion ---