AgentToolHub
Skill

rust-testing

rust-testing — a Claude Code skill from affaan-m/everything-claude-code

Features

  • ✓Comprehensive AI agent harnessing system
  • ✓Skills, instincts, and memory optimization
  • ✓Continuous learning and security scanning
  • ✓Cross-platform compatibility with Claude Code and more
  • ✓Evolved from 10+ months of real product development
  • ✓Visit GitHub for detailed tool listings

Installation Guide

Option 1: Install as Plugin (Recommended)

The easiest way to use this repo - install as a Claude Code plugin:

bash
# Add this repo as a marketplace
/plugin marketplace add https://github.com/affaan-m/everything-claude-code

# Install the plugin
/plugin install everything-claude-code@everything-claude-code

Or add directly to your ~/.claude/settings.json:

json
{
  "extraKnownMarketplaces": {
    "ecc": {
      "source": {
        "source": "github",
        "repo": "affaan-m/everything-claude-code"
      }
    }
  },
  "enabledPlugins": {
    "everything-claude-code@everything-claude-code": true
  }
}

This gives you instant access to all commands, agents, skills, and hooks.

var(--color-accent)]/40 pl-3 my-2 text-[var(--text-tertiary)]">Note: The Claude Code plugin system does not support distributing rules via plugins ([upstream limitation). You need to install rules manually:

>
>
bash
> # Clone the repo first
> git clone https://github.com/affaan-m/everything-claude-code.git
>
> # Option A: User-level rules (applies to all projects)
> mkdir -p ~/.claude/rules
> cp -r everything-claude-code/rules/common ~/.claude/rules/
> cp -r everything-claude-code/rules/typescript ~/.claude/rules/   # pick your stack
> cp -r everything-claude-code/rules/python ~/.claude/rules/
> cp -r everything-claude-code/rules/golang ~/.claude/rules/
> cp -r everything-claude-code/rules/php ~/.claude/rules/
>
> # Option B: Project-level rules (applies to current project only)
> mkdir -p .claude/rules
> cp -r everything-claude-code/rules/common .claude/rules/
> cp -r everything-claude-code/rules/typescript .claude/rules/     # pick your stack
>

---

Option 2: Manual Installation

If you prefer manual control over what's installed:

bash
# Clone the repo
git clone https://github.com/affaan-m/everything-claude-code.git

# Copy agents to your Claude config
cp everything-claude-code/agents/*.md ~/.claude/agents/

# Copy rules directories (common + language-specific)
mkdir -p ~/.claude/rules
cp -r everything-claude-code/rules/common ~/.claude/rules/
cp -r everything-claude-code/rules/typescript ~/.claude/rules/   # pick your stack
cp -r everything-claude-code/rules/python ~/.claude/rules/
cp -r everything-claude-code/rules/golang ~/.claude/rules/
cp -r everything-claude-code/rules/php ~/.claude/rules/

# Copy skills first (primary workflow surface)
# Recommended (new users): core/general skills only
cp -r everything-claude-code/.agents/skills/* ~/.claude/skills/
cp -r everything-claude-code/skills/search-first ~/.claude/skills/

# Optional: add niche/framework-specific skills only when needed
# for s in django-patterns django-tdd laravel-patterns springboot-patterns; do
# cp -r everything-claude-code/skills/$s ~/.claude/skills/
# done

# Optional: keep legacy slash-command compatibility during migration
mkdir -p ~/.claude/commands
cp everything-claude-code/commands/*.md ~/.claude/commands/

#### Install hooks

Do not copy the raw repo hooks/hooks.json into ~/.claude/settings.json or ~/.claude/hooks/hooks.json. That file is plugin/repo-oriented and is meant to be installed through the ECC installer or loaded as a plugin, so raw copying is not a supported manual install path.

Use the installer to install only the Claude hook runtime so command paths are rewritten correctly:

bash
# macOS / Linux
bash ./install.sh --target claude --modules hooks-runtime
powershell
# Windows PowerShell
pwsh -File .\install.ps1 --target claude --modules hooks-runtime

That writes resolved hooks to ~/.claude/hooks/hooks.json and leaves any existing ~/.claude/settings.json untouched.

If you installed ECC via /plugin install, do not copy those hooks into settings.json. Claude Code v2.1+ already auto-loads plugin hooks/hooks.json, and duplicating them in settings.json causes duplicate execution and cross-platform hook conflicts.

Windows note: the Claude config directory is %USERPROFILE%\\.claude, not ~/claude.

#### Configure MCPs

Copy desired MCP server definitions from mcp-configs/mcp-servers.json into your official Claude Code config in ~/.claude/settings.json, or into a project-scoped .mcp.json if you want repo-local MCP access.

If you already run your own copies of ECC-bundled MCPs, set:

bash
export ECC_DISABLED_MCPS="github,context7,exa,playwright,sequential-thinking,memory"

ECC-managed install and Codex sync flows will skip or remove those bundled servers instead of re-adding duplicates.

Important: Replace YOUR_*_HERE placeholders with your actual API keys.

---

Reviews