feat: add everything-claude-code-conventions ECC bundle (.claude/commands/add-or-update-plugin-marketplace-system.md)

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

@@ -1,175 +1,409 @@
-```markdown
-# everything-claude-code Development Patterns
+---
+name: everything-claude-code-conventions
+description: Development conventions and patterns for everything-claude-code. JavaScript 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-01
 
 ## Overview
 
-This skill teaches the core development patterns, coding conventions, and common workflows used in the `everything-claude-code` repository. The codebase is primarily JavaScript, with no major framework, and is organized around modular skills, agent definitions, command workflows, and extensible install targets. The repository emphasizes clear documentation, conventional commits, and maintainable architecture for agent and workflow development.
+This skill teaches Claude the development patterns and conventions used in everything-claude-code.
 
-## Coding Conventions
+## Tech Stack
 
-- **File Naming:**  
-  Use `camelCase` for JavaScript files and directories.  
-  *Example:*  
-  ```
-  scripts/lib/installTargets.js
-  agentPrompts.md
-  ```
+- **Primary Language**: JavaScript
+- **Architecture**: hybrid module organization
+- **Test Location**: separate
 
-- **Import Style:**  
-  Use **relative imports** for modules.  
-  *Example:*  
-  ```js
-  const installTarget = require('../lib/installTargets');
-  ```
+## When to Use This Skill
 
-- **Export Style:**  
-  Both CommonJS (`module.exports`) and ES module (`export`) styles are present.  
-  *Example (CommonJS):*  
-  ```js
-  module.exports = function mySkill() { ... };
-  ```
-  *Example (ES Module):*  
-  ```js
-  export function mySkill() { ... }
-  ```
+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 Messages:**  
-  Use [Conventional Commits](https://www.conventionalcommits.org/).  
-  Prefixes: `fix`, `feat`, `docs`, `chore`  
-  *Example:*  
-  ```
-  feat: add Gemini install target support
-  fix: correct agent prompt registration logic
-  ```
+## Commit Conventions
 
-- **Documentation:**  
-  Each skill or agent should have a `SKILL.md` or `.md` documentation file explaining its purpose and usage.
+Follow these commit message conventions based on 500 analyzed commits.
 
-## Workflows
+### Commit Style: Conventional Commits
 
-### Add New Skill
-**Trigger:** When introducing a new skill for agents or workflows  
-**Command:** `/add-skill`
+### Prefixes Used
 
-1. Create a new `SKILL.md` file under `skills/`, `.agents/skills/`, or `.claude/skills/`.
-2. Document the skill's purpose, usage, and configuration.
-3. Optionally update manifests or documentation if the skill is significant.
+- `fix`
+- `feat`
+- `docs`
+- `chore`
 
-*Example:*
+### Message Guidelines
+
+- Average message length: ~56 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
+
+
+*Commit message example*
+
+```text
+refactor: simplify redundant checks; normalize getInstalledPlugin inputs
 ```
-skills/myNewSkill/SKILL.md
+
+*Commit message example*
+
+```text
+fix: preserve file permissions in writeJsonAtomic
 ```
 
+*Commit message example*
+
+```text
+style: apply linter formatting to pluginRegistry.js
+```
+
+*Commit message example*
+
+```text
+chore: update yarn.lock
+```
+
+*Commit message example*
+
+```text
+feat(plugin): add marketplace add/install system
+```
+
+*Commit message example*
+
+```text
+fix: ship marketplaces.json as empty stub to prevent duplicate-add error
+```
+
+*Commit message example*
+
+```text
+fix: normalize lookups, atomic writes, reject empty marketplace specifier
+```
+
+*Commit message example*
+
+```text
+refactor: extract shared readJsonFile helper; fix single-dash flag parsing
+```
+
+## 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*
+
+```typescript
+// 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*
+
+```typescript
+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.
+
+### Feature Development
+
+Standard feature implementation workflow
+
+**Frequency**: ~14 times per month
+
+**Steps**:
+1. Add feature implementation
+2. Add tests for feature
+3. Update documentation
+
+**Files typically involved**:
+- `.opencode/*`
+- `.opencode/plugins/*`
+- `.opencode/plugins/lib/*`
+- `**/*.test.*`
+
+**Example commit sequence**:
+```
+feat(team-builder): use `claude agents` command for agent discovery (#1021)
+fix: extract inline SessionStart bootstrap to separate file (#1035)
+feat: add hexagonal architecture SKILL. (#1034)
+```
+
+### Add New Command Or Agentic Workflow
+
+Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
+
+**Frequency**: ~3 times per month
+
+**Steps**:
+1. Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
+2. Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
+3. Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
+4. Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
+5. Optionally add documentation or examples
+
+**Files typically involved**:
+- `commands/*.md`
+- `agents/*.md`
+- `skills/*/SKILL.md`
+- `scripts/*.sh`
+- `examples/*`
+
+**Example commit sequence**:
+```
+Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
+Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
+Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
+Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
+Optionally add documentation or examples
+```
+
+### Add Or Update Plugin Marketplace System
+
+Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Edit or create scripts/lib/pluginRegistry.js for registry helpers
+2. Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
+3. Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
+4. Update or add tests in tests/lib/pluginRegistry.test.js
+5. Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
+6. Optionally update root docs (README.md, AGENTS.md, etc.)
+
+**Files typically involved**:
+- `scripts/lib/pluginRegistry.js`
+- `scripts/pluginMarketplace.js`
+- `scripts/pluginInstall.js`
+- `.claude-plugin/marketplaces.json`
+- `.claude-plugin/installed-plugins.json`
+- `tests/lib/pluginRegistry.test.js`
+- `commands/plugin-marketplace.md`
+- `commands/plugin-install.md`
+- `README.md`
+- `AGENTS.md`
+
+**Example commit sequence**:
+```
+Edit or create scripts/lib/pluginRegistry.js for registry helpers
+Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
+Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
+Update or add tests in tests/lib/pluginRegistry.test.js
+Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
+Optionally update root docs (README.md, AGENTS.md, etc.)
+```
+
+### Add New Install Target Or Adaptation
+
+Adds a new install target (e.g., Gemini, CodeBuddy) to the system, including scripts, schemas, and tests.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
+2. Update manifests/install-modules.json to register the new target
+3. Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
+4. Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
+5. Add or update tests in tests/lib/install-targets.test.js
+6. Update documentation (README.md, .gemini/GEMINI.md, etc.)
+
+**Files typically involved**:
+- `.gemini/*`
+- `.codebuddy/*`
+- `manifests/install-modules.json`
+- `schemas/ecc-install-config.schema.json`
+- `schemas/install-modules.schema.json`
+- `scripts/lib/install-manifests.js`
+- `scripts/lib/install-targets/*.js`
+- `tests/lib/install-targets.test.js`
+- `README.md`
+
+**Example commit sequence**:
+```
+Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
+Update manifests/install-modules.json to register the new target
+Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
+Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
+Add or update tests in tests/lib/install-targets.test.js
+Update documentation (README.md, .gemini/GEMINI.md, etc.)
+```
+
+### Add Or Update Hook Or Session Management
+
+Implements or refines hooks and session management logic, including accumulator patterns, session start/end, and related tests.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
+2. Update hooks/hooks.json for hook configuration
+3. Add or update tests in tests/hooks/*.test.js
+4. Optionally update shell scripts (scripts/hooks/*.sh)
+5. Optionally update adapters (.cursor/hooks/after-file-edit.js)
+
+**Files typically involved**:
+- `scripts/hooks/*.js`
+- `hooks/hooks.json`
+- `tests/hooks/*.test.js`
+- `scripts/hooks/*.sh`
+- `.cursor/hooks/after-file-edit.js`
+
+**Example commit sequence**:
+```
+Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
+Update hooks/hooks.json for hook configuration
+Add or update tests in tests/hooks/*.test.js
+Optionally update shell scripts (scripts/hooks/*.sh)
+Optionally update adapters (.cursor/hooks/after-file-edit.js)
+```
+
+### Add Or Update Skill Or Agent
+
+Adds or updates a skill or agent definition, often including a new SKILL.md and/or agent .md, sometimes with supporting config.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create or edit skills/*/SKILL.md
+2. Create or edit agents/*.md
+3. Optionally update mcp-configs/mcp-servers.json or other config files
+4. Optionally update AGENTS.md or related documentation
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `agents/*.md`
+- `mcp-configs/mcp-servers.json`
+- `AGENTS.md`
+
+**Example commit sequence**:
+```
+Create or edit skills/*/SKILL.md
+Create or edit agents/*.md
+Optionally update mcp-configs/mcp-servers.json or other config files
+Optionally update AGENTS.md or related documentation
+```
+
+### Dependabot Or Automated Dependency Update
+
+Automated workflow to update dependencies via Dependabot or similar, touching lockfiles and workflow YAMLs.
+
+**Frequency**: ~4 times per month
+
+**Steps**:
+1. Update package.json and/or yarn.lock
+2. Update .github/workflows/*.yml as needed for new dependency versions
+3. Commit with a standardized message referencing the dependency and version
+
+**Files typically involved**:
+- `package.json`
+- `yarn.lock`
+- `.github/workflows/*.yml`
+
+**Example commit sequence**:
+```
+Update package.json and/or yarn.lock
+Update .github/workflows/*.yml as needed for new dependency versions
+Commit with a standardized message referencing the dependency and version
+```
+
+
+## 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
+
 ---
 
-### Add New Agent or Agent Prompt
-**Trigger:** When introducing a new agent persona or capability  
-**Command:** `/add-agent`
-
-1. Create a new agent definition (e.g., `agents/myAgent.md` or `.opencode/prompts/agents/myAgent.txt`).
-2. Register the agent in the relevant configuration file (e.g., `.opencode/opencode.json`).
-3. Update `AGENTS.md` or related documentation.
-
-*Example:*
-```
-agents/supportAgent.md
-```
-
----
-
-### Add or Update Command Workflow
-**Trigger:** When introducing or improving a workflow command  
-**Command:** `/add-command`
-
-1. Create or update a command file under `commands/` (e.g., `commands/review.md`).
-2. Optionally update related documentation or scripts.
-3. Address review feedback and refine command logic.
-
----
-
-### Add Install Target or Adapter
-**Trigger:** When supporting a new platform or integration  
-**Command:** `/add-install-target`
-
-1. Add new install scripts and documentation under a dot-directory (e.g., `.gemini/`, `.codebuddy/`).
-2. Update `manifests/install-modules.json` and relevant schema files.
-3. Implement or update `scripts/lib/install-targets/*.js` for the new target.
-4. Add or update tests for the install target.
-
-*Example:*
-```
-.gemini/install.sh
-scripts/lib/install-targets/gemini.js
-tests/lib/install-targets.test.js
-```
-
----
-
-### Refactor or Collapse Commands to Skills
-**Trigger:** When modernizing command logic under the skills architecture  
-**Command:** `/refactor-to-skill`
-
-1. Update or remove `commands/*.md` files.
-2. Add or update `skills/*/SKILL.md` files.
-3. Update documentation (`README.md`, `AGENTS.md`, `WORKING-CONTEXT.md`, etc.).
-4. Update manifests if required.
-
----
-
-### Documentation and Guidance Update
-**Trigger:** When clarifying, updating, or adding documentation  
-**Command:** `/update-docs`
-
-1. Edit or create documentation files (`README.md`, `WORKING-CONTEXT.md`, `docs/*.md`, etc.).
-2. Sync or update guidance in multiple language versions if needed.
-3. Optionally update related configuration or manifest files.
-
----
-
-### CI/CD Workflow Update
-**Trigger:** When improving or fixing CI/CD processes  
-**Command:** `/update-ci`
-
-1. Edit `.github/workflows/*.yml` files.
-2. Update lockfiles (`package-lock.json`, `yarn.lock`) or validation scripts.
-3. Update or add test files for CI/CD logic.
-
----
-
-## Testing Patterns
-
-- **Test Files:**  
-  Test files follow the pattern `*.test.js`.
-
-- **Framework:**  
-  No specific testing framework detected; structure your tests in standard Node.js or your preferred test runner.
-
-*Example:*
-```
-tests/lib/install-targets.test.js
-```
-
-- **Test Example:**
-  ```js
-  // install-targets.test.js
-  const installTarget = require('../../scripts/lib/install-targets/gemini');
-
-  test('should install Gemini target', () => {
-    expect(installTarget()).toBe(true);
-  });
-  ```
-
-## Commands
-
-| Command            | Purpose                                                        |
-|--------------------|----------------------------------------------------------------|
-| /add-skill         | Add a new skill module and document it                         |
-| /add-agent         | Add a new agent definition or prompt                           |
-| /add-command       | Add or update a command workflow                               |
-| /add-install-target| Add a new install target or adapter                            |
-| /refactor-to-skill | Refactor commands into skill-based modules                     |
-| /update-docs       | Update documentation or guidance files                         |
-| /update-ci         | Update CI/CD workflows, lockfiles, or validation scripts       |
-```
+*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*

.claude/commands/add-new-command-or-agentic-workflow.md

@@ -0,0 +1,41 @@
+---
+name: add-new-command-or-agentic-workflow
+description: Workflow command scaffold for add-new-command-or-agentic-workflow in everything-claude-code.
+allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
+---
+
+# /add-new-command-or-agentic-workflow
+
+Use this workflow when working on **add-new-command-or-agentic-workflow** in `everything-claude-code`.
+
+## Goal
+
+Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
+
+## Common Files
+
+- `commands/*.md`
+- `agents/*.md`
+- `skills/*/SKILL.md`
+- `scripts/*.sh`
+- `examples/*`
+
+## Suggested Sequence
+
+1. Understand the current state and failure mode before editing.
+2. Make the smallest coherent change that satisfies the workflow goal.
+3. Run the most relevant verification for touched files.
+4. Summarize what changed and what still needs review.
+
+## Typical Commit Signals
+
+- Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
+- Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
+- Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
+- Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
+- Optionally add documentation or examples
+
+## Notes
+
+- Treat this as a scaffold, not a hard-coded script.
+- Update the command if the workflow evolves materially.

.claude/commands/add-new-skill.md

@@ -1,37 +0,0 @@
----
-name: add-new-skill
-description: Workflow command scaffold for add-new-skill in everything-claude-code.
-allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
----
-
-# /add-new-skill
-
-Use this workflow when working on **add-new-skill** in `everything-claude-code`.
-
-## Goal
-
-Adds a new skill to the codebase, typically as a new agent capability or workflow module.
-
-## Common Files
-
-- `skills/*/SKILL.md`
-- `.agents/skills/*/SKILL.md`
-- `.claude/skills/*/SKILL.md`
-
-## Suggested Sequence
-
-1. Understand the current state and failure mode before editing.
-2. Make the smallest coherent change that satisfies the workflow goal.
-3. Run the most relevant verification for touched files.
-4. Summarize what changed and what still needs review.
-
-## Typical Commit Signals
-
-- Create a new SKILL.md file under skills/ or .agents/skills/ or .claude/skills/
-- Document the skill's purpose, usage, and configuration.
-- Optionally update manifests or documentation if the skill is significant.
-
-## Notes
-
-- Treat this as a scaffold, not a hard-coded script.
-- Update the command if the workflow evolves materially.

.claude/commands/add-or-update-plugin-marketplace-system.md

@@ -0,0 +1,42 @@
+---
+name: add-or-update-plugin-marketplace-system
+description: Workflow command scaffold for add-or-update-plugin-marketplace-system in everything-claude-code.
+allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
+---
+
+# /add-or-update-plugin-marketplace-system
+
+Use this workflow when working on **add-or-update-plugin-marketplace-system** in `everything-claude-code`.
+
+## Goal
+
+Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
+
+## Common Files
+
+- `scripts/lib/pluginRegistry.js`
+- `scripts/pluginMarketplace.js`
+- `scripts/pluginInstall.js`
+- `.claude-plugin/marketplaces.json`
+- `.claude-plugin/installed-plugins.json`
+- `tests/lib/pluginRegistry.test.js`
+
+## Suggested Sequence
+
+1. Understand the current state and failure mode before editing.
+2. Make the smallest coherent change that satisfies the workflow goal.
+3. Run the most relevant verification for touched files.
+4. Summarize what changed and what still needs review.
+
+## Typical Commit Signals
+
+- Edit or create scripts/lib/pluginRegistry.js for registry helpers
+- Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
+- Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
+- Update or add tests in tests/lib/pluginRegistry.test.js
+- Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
+
+## Notes
+
+- Treat this as a scaffold, not a hard-coded script.
+- Update the command if the workflow evolves materially.

.claude/commands/refactoring.md

@@ -1,35 +0,0 @@
----
-name: refactoring
-description: Workflow command scaffold for refactoring in everything-claude-code.
-allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
----
-
-# /refactoring
-
-Use this workflow when working on **refactoring** in `everything-claude-code`.
-
-## Goal
-
-Code refactoring and cleanup workflow
-
-## Common Files
-
-- `src/**/*`
-
-## Suggested Sequence
-
-1. Understand the current state and failure mode before editing.
-2. Make the smallest coherent change that satisfies the workflow goal.
-3. Run the most relevant verification for touched files.
-4. Summarize what changed and what still needs review.
-
-## Typical Commit Signals
-
-- Ensure tests pass before refactor
-- Refactor code structure
-- Verify tests still pass
-
-## Notes
-
-- Treat this as a scaffold, not a hard-coded script.
-- Update the command if the workflow evolves materially.

.claude/ecc-tools.json

@@ -2,7 +2,7 @@
   "version": "1.3",
   "schemaVersion": "1.0",
   "generatedBy": "ecc-tools",
-  "generatedAt": "2026-04-01T22:51:43.152Z",
+  "generatedAt": "2026-04-01T22:56:13.232Z",
   "repo": "https://github.com/affaan-m/everything-claude-code",
   "profiles": {
     "requested": "full",
@@ -149,8 +149,8 @@
     ".claude/team/everything-claude-code-team-config.json",
     ".claude/enterprise/controls.md",
     ".claude/commands/feature-development.md",
-    ".claude/commands/refactoring.md",
-    ".claude/commands/add-new-skill.md"
+    ".claude/commands/add-new-command-or-agentic-workflow.md",
+    ".claude/commands/add-or-update-plugin-marketplace-system.md"
   ],
   "packageFiles": {
     "runtime-core": [
@@ -179,8 +179,8 @@
     ],
     "workflow-pack": [
       ".claude/commands/feature-development.md",
-      ".claude/commands/refactoring.md",
-      ".claude/commands/add-new-skill.md"
+      ".claude/commands/add-new-command-or-agentic-workflow.md",
+      ".claude/commands/add-or-update-plugin-marketplace-system.md"
     ]
   },
   "moduleFiles": {
@@ -210,8 +210,8 @@
     ],
     "workflow-pack": [
       ".claude/commands/feature-development.md",
-      ".claude/commands/refactoring.md",
-      ".claude/commands/add-new-skill.md"
+      ".claude/commands/add-new-command-or-agentic-workflow.md",
+      ".claude/commands/add-or-update-plugin-marketplace-system.md"
     ]
   },
   "files": [
@@ -292,13 +292,13 @@
     },
     {
       "moduleId": "workflow-pack",
-      "path": ".claude/commands/refactoring.md",
-      "description": "Workflow command scaffold for refactoring."
+      "path": ".claude/commands/add-new-command-or-agentic-workflow.md",
+      "description": "Workflow command scaffold for add-new-command-or-agentic-workflow."
     },
     {
       "moduleId": "workflow-pack",
-      "path": ".claude/commands/add-new-skill.md",
-      "description": "Workflow command scaffold for add-new-skill."
+      "path": ".claude/commands/add-or-update-plugin-marketplace-system.md",
+      "description": "Workflow command scaffold for add-or-update-plugin-marketplace-system."
     }
   ],
   "workflows": [
@@ -307,12 +307,12 @@
       "path": ".claude/commands/feature-development.md"
     },
     {
-      "command": "refactoring",
-      "path": ".claude/commands/refactoring.md"
+      "command": "add-new-command-or-agentic-workflow",
+      "path": ".claude/commands/add-new-command-or-agentic-workflow.md"
     },
     {
-      "command": "add-new-skill",
-      "path": ".claude/commands/add-new-skill.md"
+      "command": "add-or-update-plugin-marketplace-system",
+      "path": ".claude/commands/add-or-update-plugin-marketplace-system.md"
     }
   ],
   "adapters": {
@@ -321,8 +321,8 @@
       "identityPath": ".claude/identity.json",
       "commandPaths": [
         ".claude/commands/feature-development.md",
-        ".claude/commands/refactoring.md",
-        ".claude/commands/add-new-skill.md"
+        ".claude/commands/add-new-command-or-agentic-workflow.md",
+        ".claude/commands/add-or-update-plugin-marketplace-system.md"
       ]
     },
     "codex": {

.claude/identity.json

@@ -10,5 +10,5 @@
     "javascript"
   ],
   "suggestedBy": "ecc-tools-repo-analysis",
-  "createdAt": "2026-04-01T22:52:48.730Z"
+  "createdAt": "2026-04-01T22:56:57.484Z"
 }

.claude/research/everything-claude-code-research-playbook.md

@@ -18,4 +18,4 @@ Use this when the task is documentation-heavy, source-sensitive, or requires bro
 
 - Primary language: JavaScript
 - Framework: Not detected
-- Workflows detected: 9
+- Workflows detected: 7

.claude/rules/everything-claude-code-guardrails.md

@@ -25,8 +25,8 @@ Generated by ECC Tools from repository history. Review before treating it as a h
 ## Detected Workflows
 
 - feature-development: Standard feature implementation workflow
-- refactoring: Code refactoring and cleanup workflow
-- add-new-skill: Adds a new skill to the codebase, typically as a new agent capability or workflow module.
+- add-new-command-or-agentic-workflow: Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
+- add-or-update-plugin-marketplace-system: Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
 
 ## Review Reminder
 

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

@@ -1,175 +1,409 @@
-```markdown
-# everything-claude-code Development Patterns
+---
+name: everything-claude-code-conventions
+description: Development conventions and patterns for everything-claude-code. JavaScript 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-01
 
 ## Overview
 
-This skill teaches the core development patterns, coding conventions, and common workflows used in the `everything-claude-code` repository. The codebase is primarily JavaScript, with no major framework, and is organized around modular skills, agent definitions, command workflows, and extensible install targets. The repository emphasizes clear documentation, conventional commits, and maintainable architecture for agent and workflow development.
+This skill teaches Claude the development patterns and conventions used in everything-claude-code.
 
-## Coding Conventions
+## Tech Stack
 
-- **File Naming:**  
-  Use `camelCase` for JavaScript files and directories.  
-  *Example:*  
-  ```
-  scripts/lib/installTargets.js
-  agentPrompts.md
-  ```
+- **Primary Language**: JavaScript
+- **Architecture**: hybrid module organization
+- **Test Location**: separate
 
-- **Import Style:**  
-  Use **relative imports** for modules.  
-  *Example:*  
-  ```js
-  const installTarget = require('../lib/installTargets');
-  ```
+## When to Use This Skill
 
-- **Export Style:**  
-  Both CommonJS (`module.exports`) and ES module (`export`) styles are present.  
-  *Example (CommonJS):*  
-  ```js
-  module.exports = function mySkill() { ... };
-  ```
-  *Example (ES Module):*  
-  ```js
-  export function mySkill() { ... }
-  ```
+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 Messages:**  
-  Use [Conventional Commits](https://www.conventionalcommits.org/).  
-  Prefixes: `fix`, `feat`, `docs`, `chore`  
-  *Example:*  
-  ```
-  feat: add Gemini install target support
-  fix: correct agent prompt registration logic
-  ```
+## Commit Conventions
 
-- **Documentation:**  
-  Each skill or agent should have a `SKILL.md` or `.md` documentation file explaining its purpose and usage.
+Follow these commit message conventions based on 500 analyzed commits.
 
-## Workflows
+### Commit Style: Conventional Commits
 
-### Add New Skill
-**Trigger:** When introducing a new skill for agents or workflows  
-**Command:** `/add-skill`
+### Prefixes Used
 
-1. Create a new `SKILL.md` file under `skills/`, `.agents/skills/`, or `.claude/skills/`.
-2. Document the skill's purpose, usage, and configuration.
-3. Optionally update manifests or documentation if the skill is significant.
+- `fix`
+- `feat`
+- `docs`
+- `chore`
 
-*Example:*
+### Message Guidelines
+
+- Average message length: ~56 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
+
+
+*Commit message example*
+
+```text
+refactor: simplify redundant checks; normalize getInstalledPlugin inputs
 ```
-skills/myNewSkill/SKILL.md
+
+*Commit message example*
+
+```text
+fix: preserve file permissions in writeJsonAtomic
 ```
 
+*Commit message example*
+
+```text
+style: apply linter formatting to pluginRegistry.js
+```
+
+*Commit message example*
+
+```text
+chore: update yarn.lock
+```
+
+*Commit message example*
+
+```text
+feat(plugin): add marketplace add/install system
+```
+
+*Commit message example*
+
+```text
+fix: ship marketplaces.json as empty stub to prevent duplicate-add error
+```
+
+*Commit message example*
+
+```text
+fix: normalize lookups, atomic writes, reject empty marketplace specifier
+```
+
+*Commit message example*
+
+```text
+refactor: extract shared readJsonFile helper; fix single-dash flag parsing
+```
+
+## 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*
+
+```typescript
+// 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*
+
+```typescript
+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.
+
+### Feature Development
+
+Standard feature implementation workflow
+
+**Frequency**: ~14 times per month
+
+**Steps**:
+1. Add feature implementation
+2. Add tests for feature
+3. Update documentation
+
+**Files typically involved**:
+- `.opencode/*`
+- `.opencode/plugins/*`
+- `.opencode/plugins/lib/*`
+- `**/*.test.*`
+
+**Example commit sequence**:
+```
+feat(team-builder): use `claude agents` command for agent discovery (#1021)
+fix: extract inline SessionStart bootstrap to separate file (#1035)
+feat: add hexagonal architecture SKILL. (#1034)
+```
+
+### Add New Command Or Agentic Workflow
+
+Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
+
+**Frequency**: ~3 times per month
+
+**Steps**:
+1. Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
+2. Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
+3. Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
+4. Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
+5. Optionally add documentation or examples
+
+**Files typically involved**:
+- `commands/*.md`
+- `agents/*.md`
+- `skills/*/SKILL.md`
+- `scripts/*.sh`
+- `examples/*`
+
+**Example commit sequence**:
+```
+Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
+Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
+Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
+Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
+Optionally add documentation or examples
+```
+
+### Add Or Update Plugin Marketplace System
+
+Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Edit or create scripts/lib/pluginRegistry.js for registry helpers
+2. Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
+3. Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
+4. Update or add tests in tests/lib/pluginRegistry.test.js
+5. Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
+6. Optionally update root docs (README.md, AGENTS.md, etc.)
+
+**Files typically involved**:
+- `scripts/lib/pluginRegistry.js`
+- `scripts/pluginMarketplace.js`
+- `scripts/pluginInstall.js`
+- `.claude-plugin/marketplaces.json`
+- `.claude-plugin/installed-plugins.json`
+- `tests/lib/pluginRegistry.test.js`
+- `commands/plugin-marketplace.md`
+- `commands/plugin-install.md`
+- `README.md`
+- `AGENTS.md`
+
+**Example commit sequence**:
+```
+Edit or create scripts/lib/pluginRegistry.js for registry helpers
+Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
+Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
+Update or add tests in tests/lib/pluginRegistry.test.js
+Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
+Optionally update root docs (README.md, AGENTS.md, etc.)
+```
+
+### Add New Install Target Or Adaptation
+
+Adds a new install target (e.g., Gemini, CodeBuddy) to the system, including scripts, schemas, and tests.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
+2. Update manifests/install-modules.json to register the new target
+3. Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
+4. Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
+5. Add or update tests in tests/lib/install-targets.test.js
+6. Update documentation (README.md, .gemini/GEMINI.md, etc.)
+
+**Files typically involved**:
+- `.gemini/*`
+- `.codebuddy/*`
+- `manifests/install-modules.json`
+- `schemas/ecc-install-config.schema.json`
+- `schemas/install-modules.schema.json`
+- `scripts/lib/install-manifests.js`
+- `scripts/lib/install-targets/*.js`
+- `tests/lib/install-targets.test.js`
+- `README.md`
+
+**Example commit sequence**:
+```
+Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
+Update manifests/install-modules.json to register the new target
+Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
+Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
+Add or update tests in tests/lib/install-targets.test.js
+Update documentation (README.md, .gemini/GEMINI.md, etc.)
+```
+
+### Add Or Update Hook Or Session Management
+
+Implements or refines hooks and session management logic, including accumulator patterns, session start/end, and related tests.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
+2. Update hooks/hooks.json for hook configuration
+3. Add or update tests in tests/hooks/*.test.js
+4. Optionally update shell scripts (scripts/hooks/*.sh)
+5. Optionally update adapters (.cursor/hooks/after-file-edit.js)
+
+**Files typically involved**:
+- `scripts/hooks/*.js`
+- `hooks/hooks.json`
+- `tests/hooks/*.test.js`
+- `scripts/hooks/*.sh`
+- `.cursor/hooks/after-file-edit.js`
+
+**Example commit sequence**:
+```
+Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
+Update hooks/hooks.json for hook configuration
+Add or update tests in tests/hooks/*.test.js
+Optionally update shell scripts (scripts/hooks/*.sh)
+Optionally update adapters (.cursor/hooks/after-file-edit.js)
+```
+
+### Add Or Update Skill Or Agent
+
+Adds or updates a skill or agent definition, often including a new SKILL.md and/or agent .md, sometimes with supporting config.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create or edit skills/*/SKILL.md
+2. Create or edit agents/*.md
+3. Optionally update mcp-configs/mcp-servers.json or other config files
+4. Optionally update AGENTS.md or related documentation
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `agents/*.md`
+- `mcp-configs/mcp-servers.json`
+- `AGENTS.md`
+
+**Example commit sequence**:
+```
+Create or edit skills/*/SKILL.md
+Create or edit agents/*.md
+Optionally update mcp-configs/mcp-servers.json or other config files
+Optionally update AGENTS.md or related documentation
+```
+
+### Dependabot Or Automated Dependency Update
+
+Automated workflow to update dependencies via Dependabot or similar, touching lockfiles and workflow YAMLs.
+
+**Frequency**: ~4 times per month
+
+**Steps**:
+1. Update package.json and/or yarn.lock
+2. Update .github/workflows/*.yml as needed for new dependency versions
+3. Commit with a standardized message referencing the dependency and version
+
+**Files typically involved**:
+- `package.json`
+- `yarn.lock`
+- `.github/workflows/*.yml`
+
+**Example commit sequence**:
+```
+Update package.json and/or yarn.lock
+Update .github/workflows/*.yml as needed for new dependency versions
+Commit with a standardized message referencing the dependency and version
+```
+
+
+## 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
+
 ---
 
-### Add New Agent or Agent Prompt
-**Trigger:** When introducing a new agent persona or capability  
-**Command:** `/add-agent`
-
-1. Create a new agent definition (e.g., `agents/myAgent.md` or `.opencode/prompts/agents/myAgent.txt`).
-2. Register the agent in the relevant configuration file (e.g., `.opencode/opencode.json`).
-3. Update `AGENTS.md` or related documentation.
-
-*Example:*
-```
-agents/supportAgent.md
-```
-
----
-
-### Add or Update Command Workflow
-**Trigger:** When introducing or improving a workflow command  
-**Command:** `/add-command`
-
-1. Create or update a command file under `commands/` (e.g., `commands/review.md`).
-2. Optionally update related documentation or scripts.
-3. Address review feedback and refine command logic.
-
----
-
-### Add Install Target or Adapter
-**Trigger:** When supporting a new platform or integration  
-**Command:** `/add-install-target`
-
-1. Add new install scripts and documentation under a dot-directory (e.g., `.gemini/`, `.codebuddy/`).
-2. Update `manifests/install-modules.json` and relevant schema files.
-3. Implement or update `scripts/lib/install-targets/*.js` for the new target.
-4. Add or update tests for the install target.
-
-*Example:*
-```
-.gemini/install.sh
-scripts/lib/install-targets/gemini.js
-tests/lib/install-targets.test.js
-```
-
----
-
-### Refactor or Collapse Commands to Skills
-**Trigger:** When modernizing command logic under the skills architecture  
-**Command:** `/refactor-to-skill`
-
-1. Update or remove `commands/*.md` files.
-2. Add or update `skills/*/SKILL.md` files.
-3. Update documentation (`README.md`, `AGENTS.md`, `WORKING-CONTEXT.md`, etc.).
-4. Update manifests if required.
-
----
-
-### Documentation and Guidance Update
-**Trigger:** When clarifying, updating, or adding documentation  
-**Command:** `/update-docs`
-
-1. Edit or create documentation files (`README.md`, `WORKING-CONTEXT.md`, `docs/*.md`, etc.).
-2. Sync or update guidance in multiple language versions if needed.
-3. Optionally update related configuration or manifest files.
-
----
-
-### CI/CD Workflow Update
-**Trigger:** When improving or fixing CI/CD processes  
-**Command:** `/update-ci`
-
-1. Edit `.github/workflows/*.yml` files.
-2. Update lockfiles (`package-lock.json`, `yarn.lock`) or validation scripts.
-3. Update or add test files for CI/CD logic.
-
----
-
-## Testing Patterns
-
-- **Test Files:**  
-  Test files follow the pattern `*.test.js`.
-
-- **Framework:**  
-  No specific testing framework detected; structure your tests in standard Node.js or your preferred test runner.
-
-*Example:*
-```
-tests/lib/install-targets.test.js
-```
-
-- **Test Example:**
-  ```js
-  // install-targets.test.js
-  const installTarget = require('../../scripts/lib/install-targets/gemini');
-
-  test('should install Gemini target', () => {
-    expect(installTarget()).toBe(true);
-  });
-  ```
-
-## Commands
-
-| Command            | Purpose                                                        |
-|--------------------|----------------------------------------------------------------|
-| /add-skill         | Add a new skill module and document it                         |
-| /add-agent         | Add a new agent definition or prompt                           |
-| /add-command       | Add or update a command workflow                               |
-| /add-install-target| Add a new install target or adapter                            |
-| /refactor-to-skill | Refactor commands into skill-based modules                     |
-| /update-docs       | Update documentation or guidance files                         |
-| /update-ci         | Update CI/CD workflows, lockfiles, or validation scripts       |
-```
+*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*

.claude/team/everything-claude-code-team-config.json

@@ -8,8 +8,8 @@
   ],
   "commandFiles": [
     ".claude/commands/feature-development.md",
-    ".claude/commands/refactoring.md",
-    ".claude/commands/add-new-skill.md"
+    ".claude/commands/add-new-command-or-agentic-workflow.md",
+    ".claude/commands/add-or-update-plugin-marketplace-system.md"
   ],
-  "updatedAt": "2026-04-01T22:51:43.152Z"
+  "updatedAt": "2026-04-01T22:56:13.232Z"
 }