$npx -y skills add affaan-m/ECC --skill everything-claude-codeDevelopment conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
| 1 | # Everything Claude Code Conventions |
| 2 | |
| 3 | > Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-03-20 |
| 4 | |
| 5 | ## Overview |
| 6 | |
| 7 | This skill teaches Claude the development patterns and conventions used in everything-claude-code. |
| 8 | |
| 9 | ## Tech Stack |
| 10 | |
| 11 | - **Primary Language**: JavaScript |
| 12 | - **Architecture**: hybrid module organization |
| 13 | - **Test Location**: separate |
| 14 | |
| 15 | ## When to Use This Skill |
| 16 | |
| 17 | Activate this skill when: |
| 18 | - Making changes to this repository |
| 19 | - Adding new features following established patterns |
| 20 | - Writing tests that match project conventions |
| 21 | - Creating commits with proper message format |
| 22 | |
| 23 | ## Commit Conventions |
| 24 | |
| 25 | Follow these commit message conventions based on 500 analyzed commits. |
| 26 | |
| 27 | ### Commit Style: Conventional Commits |
| 28 | |
| 29 | ### Prefixes Used |
| 30 | |
| 31 | - `fix` |
| 32 | - `test` |
| 33 | - `feat` |
| 34 | - `docs` |
| 35 | |
| 36 | ### Message Guidelines |
| 37 | |
| 38 | - Average message length: ~65 characters |
| 39 | - Keep first line concise and descriptive |
| 40 | - Use imperative mood ("Add feature" not "Added feature") |
| 41 | |
| 42 | |
| 43 | *Commit message example* |
| 44 | |
| 45 | ```text |
| 46 | feat(rules): add C# language support |
| 47 | ``` |
| 48 | |
| 49 | *Commit message example* |
| 50 | |
| 51 | ```text |
| 52 | chore(deps-dev): bump flatted (#675) |
| 53 | ``` |
| 54 | |
| 55 | *Commit message example* |
| 56 | |
| 57 | ```text |
| 58 | fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691) |
| 59 | ``` |
| 60 | |
| 61 | *Commit message example* |
| 62 | |
| 63 | ```text |
| 64 | docs: add Antigravity setup and usage guide (#552) |
| 65 | ``` |
| 66 | |
| 67 | *Commit message example* |
| 68 | |
| 69 | ```text |
| 70 | merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer |
| 71 | ``` |
| 72 | |
| 73 | *Commit message example* |
| 74 | |
| 75 | ```text |
| 76 | Revert "Add Kiro IDE support (.kiro/) (#548)" |
| 77 | ``` |
| 78 | |
| 79 | *Commit message example* |
| 80 | |
| 81 | ```text |
| 82 | Add Kiro IDE support (.kiro/) (#548) |
| 83 | ``` |
| 84 | |
| 85 | *Commit message example* |
| 86 | |
| 87 | ```text |
| 88 | feat: add block-no-verify hook for Claude Code and Cursor (#649) |
| 89 | ``` |
| 90 | |
| 91 | ## Architecture |
| 92 | |
| 93 | ### Project Structure: Single Package |
| 94 | |
| 95 | This project uses **hybrid** module organization. |
| 96 | |
| 97 | ### Configuration Files |
| 98 | |
| 99 | - `.github/workflows/ci.yml` |
| 100 | - `.github/workflows/maintenance.yml` |
| 101 | - `.github/workflows/monthly-metrics.yml` |
| 102 | - `.github/workflows/release.yml` |
| 103 | - `.github/workflows/reusable-release.yml` |
| 104 | - `.github/workflows/reusable-test.yml` |
| 105 | - `.github/workflows/reusable-validate.yml` |
| 106 | - `.opencode/package.json` |
| 107 | - `.opencode/tsconfig.json` |
| 108 | - `.prettierrc` |
| 109 | - `eslint.config.js` |
| 110 | - `package.json` |
| 111 | |
| 112 | ### Guidelines |
| 113 | |
| 114 | - This project uses a hybrid organization |
| 115 | - Follow existing patterns when adding new code |
| 116 | |
| 117 | ## Code Style |
| 118 | |
| 119 | ### Language: JavaScript |
| 120 | |
| 121 | ### Naming Conventions |
| 122 | |
| 123 | | Element | Convention | |
| 124 | |---------|------------| |
| 125 | | Files | camelCase | |
| 126 | | Functions | camelCase | |
| 127 | | Classes | PascalCase | |
| 128 | | Constants | SCREAMING_SNAKE_CASE | |
| 129 | |
| 130 | ### Import Style: Relative Imports |
| 131 | |
| 132 | ### Export Style: Mixed Style |
| 133 | |
| 134 | |
| 135 | *Preferred import style* |
| 136 | |
| 137 | ```typescript |
| 138 | // Use relative imports |
| 139 | import { Button } from '../components/Button' |
| 140 | import { useAuth } from './hooks/useAuth' |
| 141 | ``` |
| 142 | |
| 143 | ## Testing |
| 144 | |
| 145 | ### Test Framework |
| 146 | |
| 147 | No specific test framework detected — use the repository's existing test patterns. |
| 148 | |
| 149 | ### File Pattern: `*.test.js` |
| 150 | |
| 151 | ### Test Types |
| 152 | |
| 153 | - **Unit tests**: Test individual functions and components in isolation |
| 154 | - **Integration tests**: Test interactions between multiple components/services |
| 155 | |
| 156 | ### Coverage |
| 157 | |
| 158 | This project has coverage reporting configured. Aim for 80%+ coverage. |
| 159 | |
| 160 | |
| 161 | ## Error Handling |
| 162 | |
| 163 | ### Error Handling Style: Try-Catch Blocks |
| 164 | |
| 165 | |
| 166 | *Standard error handling pattern* |
| 167 | |
| 168 | ```typescript |
| 169 | try { |
| 170 | const result = await riskyOperation() |
| 171 | return result |
| 172 | } catch (error) { |
| 173 | console.error('Operation failed:', error) |
| 174 | throw new Error('User-friendly message') |
| 175 | } |
| 176 | ``` |
| 177 | |
| 178 | ## Common Workflows |
| 179 | |
| 180 | These workflows were detected from analyzing commit patterns. |
| 181 | |
| 182 | ### Database Migration |
| 183 | |
| 184 | Database schema changes with migration files |
| 185 | |
| 186 | **Frequency**: ~2 times per month |
| 187 | |
| 188 | **Steps**: |
| 189 | 1. Create migration file |
| 190 | 2. Update schema definitions |
| 191 | 3. Generate/update types |
| 192 | |
| 193 | **Files typically involved**: |
| 194 | - `**/schema.*` |
| 195 | - `migrations/*` |
| 196 | |
| 197 | **Example commit sequence**: |
| 198 | ``` |
| 199 | feat: implement --with/--without selective install flags (#679) |
| 200 | fix: sync catalog counts with filesystem (27 agents, 113 skills, 58 commands) (#693) |
| 201 | feat(rules): add Rust language rules (rebased #660) (#686) |
| 202 | ``` |
| 203 | |
| 204 | ### Feature Development |
| 205 | |
| 206 | Standard feature implementation workflow |
| 207 | |
| 208 | **Frequency**: ~22 times per month |
| 209 | |
| 210 | **Steps**: |
| 211 | 1. Add feature implementation |
| 212 | 2. Add tests for feature |
| 213 | 3. Update documentation |
| 214 | |
| 215 | **Files typically involved**: |
| 216 | - `manifests/*` |
| 217 | - `schemas/*` |
| 218 | - `**/*.test.*` |
| 219 | - `**/api/**` |
| 220 | |
| 221 | **Example commit sequence**: |
| 222 | ``` |
| 223 | feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer |
| 224 | docs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex/Cursor) skill copies |
| 225 | 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 |
| 226 | ``` |
| 227 | |
| 228 | # |