This repository provides a structured set of guidelines for implementing standardized patterns across React, Node.js, and Next.js environments. It bridges the gap between frontend interface design and backend API optimization.
Engineers can apply specific data engineering best practices for ClickHouse analytical workloads and utilize a formal evaluation harness to implement eval-driven development within Claude Code sessions.
Follow the documented setup, then try a first task.
Installs: Installs the complete everything-claude-code plugin collection, including its commands, agents, skills, and hooks. · Claude Code
Enter this command in a Claude Code agent session to add the repository as a marketplace. This is not a terminal command.
/plugin marketplace add affaan-m/everything-claude-code
After adding the marketplace, enter this command in the Claude Code agent session to install the plugin. This is not a terminal command.
/plugin install everything-claude-code@everything-claude-code
Installs: Enables the complete everything-claude-code plugin collection through Claude Code settings, including the skills directory declared by its plugin manifest. · Claude Code
Manually add the documented `extraKnownMarketplaces` entry for GitHub repository `affaan-m/everything-claude-code` and set `everything-claude-code@everything-claude-code` to `true` under `enabledPlugins` in `~/.claude/settings.json`.
Installs: Manually installs the repository's agents, rules, commands, and complete skills bundle into the user's Claude configuration; hooks and desired MCP servers are configured separately. · Claude Code
Run from: Run the terminal commands from the directory in which the `everything-claude-code` repository folder should be created.
In a terminal, clone the repository.
git clone https://github.com/affaan-m/everything-claude-code.git
In the same terminal working directory, copy all supplied agent definitions into the Claude agents directory.
cp everything-claude-code/agents/*.md ~/.claude/agents/
Copy all supplied rules into the Claude rules directory.
cp everything-claude-code/rules/*.md ~/.claude/rules/
Copy all supplied commands into the Claude commands directory.
cp everything-claude-code/commands/*.md ~/.claude/commands/
Copy the complete skills bundle into the Claude skills directory.
cp -r everything-claude-code/skills/* ~/.claude/skills/
Manually copy the hook definitions from `hooks/hooks.json` into `~/.claude/settings.json`.
If desired, manually copy MCP server definitions from `mcp-configs/mcp-servers.json` into `~/.claude.json`. Replace every `YOUR_*_HERE` placeholder with the corresponding actual API key while keeping secrets out of the repository.
Uses eval-harness
Use the eval-harness skill to define one capability evaluation for <feature-name>. I will provide the intended behavior and constraints. Produce a compact evaluation definition with the task, three concrete success criteria, and the expected output; do not implement the feature or run the evaluation yet.
Uses security-review
Use the security-review skill to review <file-or-snippet> for one security-sensitive concern: <authentication, user input, secrets, API endpoint, payment, sensitive data, or third-party API integration>. Return a short checklist of confirmed issues, uncertain findings that need more context, and recommended fixes. Do not modify the code.
Uses tdd-workflow
Use the tdd-workflow skill to create a small test-first plan for fixing <bug-description> in <project-or-file-path>. Identify the first failing test to write, the minimum implementation needed to pass it, relevant edge and error cases, and the appropriate unit, integration, or E2E test level. Do not edit files yet.
Claude