[FEATURE] request: option to skip all project-local config (CLAUDE.md, skills, agents, commands) — not just settings.json

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

Summary

--setting-sources user lets me skip project/local settings.json while keeping
my global ~/.claude/settings.json. I'd like the same per-source filtering to
apply to the other discovery mechanisms: CLAUDE.md, skills, agents, commands,
hooks, and MCP.

Proposed Solution

Proposal

One of:

1. Extend --setting-sources (and add a matching settingSources key in

settings.json) so that the chosen sources apply to all discovery
mechanisms, not only settings.json.

1. Add a new flag, e.g. --config-sources user,project,local or

--no-project-config, that controls discovery of CLAUDE.md, skills, agents,
commands, and hooks in the same way.

1. Alternatively, a .claudeignore pattern at the user-global level that can

exclude specific paths from any discovery.

A settings.json key would be preferable to a CLI flag so the choice is
persistent without a shell alias.

Alternative Solutions

Current workaround

claude --setting-sources user only isolates settings.json.
claude --bare --settings ~/.claude/settings.json loses global CLAUDE.md,
skills, agents, and commands, which are the items I most want to keep.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Motivation

I want a consistent, self-controlled claude environment across all repos on my
machine. Today, cloning any repo with a CLAUDE.md, .claude/skills/,
.claude/agents/, or .claude/commands/ silently changes how my assistant
behaves. --bare is too aggressive because it also disables my global
~/.claude/ items.

Additional Context

_No response_