[FEATURE] per-project control to skip global CLAUDE.md and hooks

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem

Global ~/.claude/CLAUDE.md and global hooks (from ~/.claude/settings.json) always load in every session, regardless of working directory. There's no way for a project to opt out.

For users with rich global configs (plugins, brain systems, workspace automation), this means every repo session — even ones that need only repo-local context — gets flooded with irrelevant instructions and injected context.

Proposed Solution

## Requested Feature

Allow project-level settings (.claude/settings.json) to control what global context loads:

```json
{
"skipGlobalCLAUDEMd": true,
"skipGlobalHooks": true
}

  Or a CLI flag:

`claude --minimal   # only load repo-local CLAUDE.md + settings`

  What works today (and what doesn't)

  ┌──────────────────────────┬────────────────────────────────────────────┐
  │         Control          │           Per-project override?            │
  ├──────────────────────────┼────────────────────────────────────────────┤
  │ Plugins (enabledPlugins) │ Yes — can set to false in project settings │
  ├──────────────────────────┼────────────────────────────────────────────┤
  │ Model, effort level      │ Yes — project overrides global             │
  ├──────────────────────────┼────────────────────────────────────────────┤
  │ Global CLAUDE.md         │ No — always loads                          │
  ├──────────────────────────┼────────────────────────────────────────────┤
  │ Global hooks             │ No — always fire                           │
  └──────────────────────────┴────────────────────────────────────────────┘

  **Use** case

  I maintain a rich global setup for my personal workspace. When I open Claude in a code repo, I want only the repo's .claude/CLAUDE.md and .claude/settings.json — clean context, no noise. I'll opt in to additional tools explicitly when needed.

### Alternative Solutions

_No response_

### Priority

Low - Nice to have

### Feature Category

CLI commands and flags

### Use Case Example

_No response_

### Additional Context

_No response_