feat: add everything-claude-code-conventions ECC bundle (.claude/commands/add-ecc-bundle-component.md)

.agents/skills/everything-claude-code/SKILL.md

@@ -1,103 +1,207 @@
-```markdown
-# everything-claude-code Development Patterns
+---
+name: everything-claude-code-conventions
+description: Development conventions and patterns for everything-claude-code. TypeScript project with conventional commits.
+---
 
-> Auto-generated skill from repository analysis
+# Everything Claude Code Conventions
+
+> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-05
 
 ## Overview
 
-This skill documents the core development patterns, coding conventions, and workflows for the `everything-claude-code` repository. The codebase is written in TypeScript and focuses on modular, convention-driven development without a specific framework. It emphasizes clarity, maintainability, and extensibility, particularly around the ECC (everything-claude-code-conventions) bundle.
+This skill teaches Claude the development patterns and conventions used in everything-claude-code.
 
-## Coding Conventions
+## Tech Stack
 
-### File Naming
+- **Primary Language**: TypeScript
+- **Architecture**: hybrid module organization
+- **Test Location**: separate
 
-- Use **camelCase** for file names.
-  - Example: `myComponent.ts`, `userProfile.test.ts`
+## When to Use This Skill
 
-### Import Style
+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
 
-- Use **relative imports** for all modules.
-  - Example:
-    ```typescript
-    import { myFunction } from './utils';
-    ```
+## Commit Conventions
 
-### Export Style
+Follow these commit message conventions based on 10 analyzed commits.
 
-- Use **named exports** rather than default exports.
-  - Example:
-    ```typescript
-    // utils.ts
-    export function myFunction() { /* ... */ }
+### Commit Style: Conventional Commits
 
-    // usage
-    import { myFunction } from './utils';
-    ```
+### Prefixes Used
 
-### Commit Messages
+- `feat`
 
-- Follow **conventional commit** patterns.
-- Use the `feat` prefix for new features.
-  - Example:  
-    ```
-    feat: add user authentication to ECC bundle (94 chars avg)
-    ```
+### Message Guidelines
 
-## Workflows
+- Average message length: ~82 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
 
-### add-ecc-bundle-component
 
-**Trigger:** When you want to extend the ECC bundle with a new capability, convention, or agent skill.
+*Commit message example*
 
-**Command:** `/add-ecc-bundle-component`
+```text
+feat: add everything-claude-code ECC bundle (.claude/ecc-tools.json)
+```
 
-1. **Create or update** a file in the relevant ECC bundle directory. Common locations include:
-    - `.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`
-    - `.codex/agents/explorer.toml`
-    - `.codex/agents/reviewer.toml`
-    - `.codex/agents/docs-researcher.toml`
-2. **Commit** your changes with a message referencing the ECC bundle, following the conventional commit style.
-    - Example:  
-      ```
-      feat: add new agent config to ECC bundle
-      ```
-3. **Push** your changes and open a pull request if required.
+*Commit message example*
 
-#### Example: Adding a New Tool
+```text
+feat: add everything-claude-code ECC bundle (.claude/skills/everything-claude-code/SKILL.md)
+```
 
-1. Edit `.claude/ecc-tools.json` to include your new tool.
-2. Commit:
-    ```
-    feat: add 'dataCleaner' tool to ECC bundle
-    ```
-3. Push and submit for review.
+*Commit message example*
 
-## Testing Patterns
+```text
+feat: add everything-claude-code ECC bundle (.agents/skills/everything-claude-code/SKILL.md)
+```
 
-- **Test File Naming:** All test files follow the `*.test.*` pattern.
-  - Example: `userService.test.ts`
-- **Testing Framework:** Not explicitly detected; check project documentation or existing test files for specifics.
-- **Test Example:**
-    ```typescript
-    // userService.test.ts
-    import { getUser } from './userService';
+*Commit message example*
 
-    describe('getUser', () => {
-      it('returns user data', () => {
-        // test implementation
-      });
-    });
-    ```
+```text
+feat: add everything-claude-code ECC bundle (.claude/identity.json)
+```
 
-## Commands
+*Commit message example*
 
-| Command                   | Purpose                                                         |
-|---------------------------|-----------------------------------------------------------------|
-| /add-ecc-bundle-component | Add a new component or skill to the ECC bundle                  |
+```text
+feat: add everything-claude-code ECC bundle (.codex/agents/explorer.toml)
+```
 
-```
+*Commit message example*
+
+```text
+feat: add everything-claude-code ECC bundle (.codex/agents/reviewer.toml)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code ECC bundle (.codex/agents/docs-researcher.toml)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
+```
+
+## Architecture
+
+### Project Structure: Single Package
+
+This project uses **hybrid** module organization.
+
+### Guidelines
+
+- This project uses a hybrid organization
+- Follow existing patterns when adding new code
+
+## Code Style
+
+### Language: TypeScript
+
+### Naming Conventions
+
+| Element | Convention |
+|---------|------------|
+| Files | camelCase |
+| Functions | camelCase |
+| Classes | PascalCase |
+| Constants | SCREAMING_SNAKE_CASE |
+
+### Import Style: Relative Imports
+
+### Export Style: Named Exports
+
+
+*Preferred import style*
+
+```typescript
+// Use relative imports
+import { Button } from '../components/Button'
+import { useAuth } from './hooks/useAuth'
+```
+
+*Preferred export style*
+
+```typescript
+// 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.
+
+### Feature Development
+
+Standard feature implementation workflow
+
+**Frequency**: ~30 times per month
+
+**Steps**:
+1. Add feature implementation
+2. Add tests for feature
+3. Update documentation
+
+**Files typically involved**:
+- `.claude/commands/*`
+
+**Example commit sequence**:
+```
+feat: add everything-claude-code ECC bundle (.claude/ecc-tools.json)
+feat: add everything-claude-code ECC bundle (.claude/skills/everything-claude-code/SKILL.md)
+feat: add everything-claude-code ECC bundle (.agents/skills/everything-claude-code/SKILL.md)
+```
+
+### Add Ecc Bundle Component
+
+Adds a new component to the everything-claude-code ECC bundle, such as skills, identity, agent configs, or commands.
+
+**Frequency**: ~5 times per month
+
+**Steps**:
+1. Create or update a file under .claude/skills/everything-claude-code/ or .agents/skills/everything-claude-code/ or .claude/commands/ or .claude/identity.json or .claude/ecc-tools.json or .codex/agents/
+2. Commit the file with a message indicating addition to ECC bundle
+
+**Files typically involved**:
+- `.claude/skills/everything-claude-code/SKILL.md`
+- `.agents/skills/everything-claude-code/SKILL.md`
+- `.claude/commands/*.md`
+- `.claude/identity.json`
+- `.claude/ecc-tools.json`
+- `.codex/agents/*.toml`
+- `.agents/skills/everything-claude-code/agents/*.yaml`
+
+**Example commit sequence**:
+```
+Create or update a file under .claude/skills/everything-claude-code/ or .agents/skills/everything-claude-code/ or .claude/commands/ or .claude/identity.json or .claude/ecc-tools.json or .codex/agents/
+Commit the file with a message indicating addition to ECC bundle
+```
+
+
+## Best Practices
+
+Based on analysis of the codebase, follow these practices:
+
+### Do
+
+- Use conventional commit format (feat:, fix:, etc.)
+- Use camelCase for file names
+- Prefer named exports
+
+### Don't
+
+- Don't write vague commit messages
+- 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.*

.claude/commands/add-ecc-bundle-component.md

@@ -10,16 +10,16 @@ Use this workflow when working on **add-ecc-bundle-component** in `everything-cl
 
 ## Goal
 
-Adds a new component to the everything-claude-code-conventions ECC bundle, such as tools, skills, identity, agent configs, or commands.
+Adds a new component to the everything-claude-code ECC bundle, such as skills, identity, agent configs, or commands.
 
 ## Common Files
 
-- `.claude/ecc-tools.json`
 - `.claude/skills/everything-claude-code/SKILL.md`
 - `.agents/skills/everything-claude-code/SKILL.md`
+- `.claude/commands/*.md`
 - `.claude/identity.json`
-- `.claude/commands/feature-development.md`
-- `.claude/commands/add-ecc-bundle-component.md`
+- `.claude/ecc-tools.json`
+- `.codex/agents/*.toml`
 
 ## Suggested Sequence
 
@@ -30,8 +30,8 @@ Adds a new component to the everything-claude-code-conventions ECC bundle, such
 
 ## Typical Commit Signals
 
-- 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, .codex/agents/*.toml)
-- Commit the change with a message referencing the ECC bundle
+- Create or update a file under .claude/skills/everything-claude-code/ or .agents/skills/everything-claude-code/ or .claude/commands/ or .claude/identity.json or .claude/ecc-tools.json or .codex/agents/
+- Commit the file with a message indicating addition to ECC bundle
 
 ## Notes
 

.claude/ecc-tools.json

@@ -2,7 +2,7 @@
   "version": "1.3",
   "schemaVersion": "1.0",
   "generatedBy": "ecc-tools",
-  "generatedAt": "2026-04-05T16:40:08.320Z",
+  "generatedAt": "2026-04-05T14:01:38.862Z",
   "repo": "https://github.com/affaan-m/everything-claude-code",
   "profiles": {
     "requested": "developer",

.claude/identity.json

@@ -10,5 +10,5 @@
     "typescript"
   ],
   "suggestedBy": "ecc-tools-repo-analysis",
-  "createdAt": "2026-04-05T16:40:37.988Z"
+  "createdAt": "2026-04-05T16:39:43.047Z"
 }

.claude/skills/everything-claude-code/SKILL.md

@@ -1,103 +1,207 @@
-```markdown
-# everything-claude-code Development Patterns
+---
+name: everything-claude-code-conventions
+description: Development conventions and patterns for everything-claude-code. TypeScript project with conventional commits.
+---
 
-> Auto-generated skill from repository analysis
+# Everything Claude Code Conventions
+
+> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-05
 
 ## Overview
 
-This skill documents the core development patterns, coding conventions, and workflows for the `everything-claude-code` repository. The codebase is written in TypeScript and focuses on modular, convention-driven development without a specific framework. It emphasizes clarity, maintainability, and extensibility, particularly around the ECC (everything-claude-code-conventions) bundle.
+This skill teaches Claude the development patterns and conventions used in everything-claude-code.
 
-## Coding Conventions
+## Tech Stack
 
-### File Naming
+- **Primary Language**: TypeScript
+- **Architecture**: hybrid module organization
+- **Test Location**: separate
 
-- Use **camelCase** for file names.
-  - Example: `myComponent.ts`, `userProfile.test.ts`
+## When to Use This Skill
 
-### Import Style
+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
 
-- Use **relative imports** for all modules.
-  - Example:
-    ```typescript
-    import { myFunction } from './utils';
-    ```
+## Commit Conventions
 
-### Export Style
+Follow these commit message conventions based on 10 analyzed commits.
 
-- Use **named exports** rather than default exports.
-  - Example:
-    ```typescript
-    // utils.ts
-    export function myFunction() { /* ... */ }
+### Commit Style: Conventional Commits
 
-    // usage
-    import { myFunction } from './utils';
-    ```
+### Prefixes Used
 
-### Commit Messages
+- `feat`
 
-- Follow **conventional commit** patterns.
-- Use the `feat` prefix for new features.
-  - Example:  
-    ```
-    feat: add user authentication to ECC bundle (94 chars avg)
-    ```
+### Message Guidelines
 
-## Workflows
+- Average message length: ~82 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
 
-### add-ecc-bundle-component
 
-**Trigger:** When you want to extend the ECC bundle with a new capability, convention, or agent skill.
+*Commit message example*
 
-**Command:** `/add-ecc-bundle-component`
+```text
+feat: add everything-claude-code ECC bundle (.claude/ecc-tools.json)
+```
 
-1. **Create or update** a file in the relevant ECC bundle directory. Common locations include:
-    - `.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`
-    - `.codex/agents/explorer.toml`
-    - `.codex/agents/reviewer.toml`
-    - `.codex/agents/docs-researcher.toml`
-2. **Commit** your changes with a message referencing the ECC bundle, following the conventional commit style.
-    - Example:  
-      ```
-      feat: add new agent config to ECC bundle
-      ```
-3. **Push** your changes and open a pull request if required.
+*Commit message example*
 
-#### Example: Adding a New Tool
+```text
+feat: add everything-claude-code ECC bundle (.claude/skills/everything-claude-code/SKILL.md)
+```
 
-1. Edit `.claude/ecc-tools.json` to include your new tool.
-2. Commit:
-    ```
-    feat: add 'dataCleaner' tool to ECC bundle
-    ```
-3. Push and submit for review.
+*Commit message example*
 
-## Testing Patterns
+```text
+feat: add everything-claude-code ECC bundle (.agents/skills/everything-claude-code/SKILL.md)
+```
 
-- **Test File Naming:** All test files follow the `*.test.*` pattern.
-  - Example: `userService.test.ts`
-- **Testing Framework:** Not explicitly detected; check project documentation or existing test files for specifics.
-- **Test Example:**
-    ```typescript
-    // userService.test.ts
-    import { getUser } from './userService';
+*Commit message example*
 
-    describe('getUser', () => {
-      it('returns user data', () => {
-        // test implementation
-      });
-    });
-    ```
+```text
+feat: add everything-claude-code ECC bundle (.claude/identity.json)
+```
 
-## Commands
+*Commit message example*
 
-| Command                   | Purpose                                                         |
-|---------------------------|-----------------------------------------------------------------|
-| /add-ecc-bundle-component | Add a new component or skill to the ECC bundle                  |
+```text
+feat: add everything-claude-code ECC bundle (.codex/agents/explorer.toml)
+```
 
-```
+*Commit message example*
+
+```text
+feat: add everything-claude-code ECC bundle (.codex/agents/reviewer.toml)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code ECC bundle (.codex/agents/docs-researcher.toml)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
+```
+
+## Architecture
+
+### Project Structure: Single Package
+
+This project uses **hybrid** module organization.
+
+### Guidelines
+
+- This project uses a hybrid organization
+- Follow existing patterns when adding new code
+
+## Code Style
+
+### Language: TypeScript
+
+### Naming Conventions
+
+| Element | Convention |
+|---------|------------|
+| Files | camelCase |
+| Functions | camelCase |
+| Classes | PascalCase |
+| Constants | SCREAMING_SNAKE_CASE |
+
+### Import Style: Relative Imports
+
+### Export Style: Named Exports
+
+
+*Preferred import style*
+
+```typescript
+// Use relative imports
+import { Button } from '../components/Button'
+import { useAuth } from './hooks/useAuth'
+```
+
+*Preferred export style*
+
+```typescript
+// 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.
+
+### Feature Development
+
+Standard feature implementation workflow
+
+**Frequency**: ~30 times per month
+
+**Steps**:
+1. Add feature implementation
+2. Add tests for feature
+3. Update documentation
+
+**Files typically involved**:
+- `.claude/commands/*`
+
+**Example commit sequence**:
+```
+feat: add everything-claude-code ECC bundle (.claude/ecc-tools.json)
+feat: add everything-claude-code ECC bundle (.claude/skills/everything-claude-code/SKILL.md)
+feat: add everything-claude-code ECC bundle (.agents/skills/everything-claude-code/SKILL.md)
+```
+
+### Add Ecc Bundle Component
+
+Adds a new component to the everything-claude-code ECC bundle, such as skills, identity, agent configs, or commands.
+
+**Frequency**: ~5 times per month
+
+**Steps**:
+1. Create or update a file under .claude/skills/everything-claude-code/ or .agents/skills/everything-claude-code/ or .claude/commands/ or .claude/identity.json or .claude/ecc-tools.json or .codex/agents/
+2. Commit the file with a message indicating addition to ECC bundle
+
+**Files typically involved**:
+- `.claude/skills/everything-claude-code/SKILL.md`
+- `.agents/skills/everything-claude-code/SKILL.md`
+- `.claude/commands/*.md`
+- `.claude/identity.json`
+- `.claude/ecc-tools.json`
+- `.codex/agents/*.toml`
+- `.agents/skills/everything-claude-code/agents/*.yaml`
+
+**Example commit sequence**:
+```
+Create or update a file under .claude/skills/everything-claude-code/ or .agents/skills/everything-claude-code/ or .claude/commands/ or .claude/identity.json or .claude/ecc-tools.json or .codex/agents/
+Commit the file with a message indicating addition to ECC bundle
+```
+
+
+## Best Practices
+
+Based on analysis of the codebase, follow these practices:
+
+### Do
+
+- Use conventional commit format (feat:, fix:, etc.)
+- Use camelCase for file names
+- Prefer named exports
+
+### Don't
+
+- Don't write vague commit messages
+- 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.*