cc-config-placement

Determine global versus project-local placement for Claude Code configuration files.

1|Updated Oct 21, 2016
One-click install
npx skills add https://github.com/jasonkuhrt/dotfiles --skill cc-config-placement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-config-placement
Source: https://github.com/jasonkuhrt/dotfiles/tree/main/.claude/skills/cc-config-placement
Command: npx skills add https://github.com/jasonkuhrt/dotfiles --skill cc-config-placement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when adding rules, commands, or skills to dotfiles - decides global vs project-local placement

Core Features & Use Cases

  • Determine whether Claude Code config belongs in the global dotfiles/claude or the project-local dotfiles/.claude.
  • Clarify the symlink structure and scope for CLAUDE.md, hooks, rules, and settings.
  • Ensure consistent configuration management across multiple projects and dotfiles repositories.

Quick Start

Decide where Claude config should live for a new repository (global under dotfiles/claude or project-local under dotfiles/.claude) and outline the corresponding directory mapping.

Frequently Asked Questions about cc-config-placement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide whether to place Claude config globally or per-project?▼

Global Claude config placement uses dotfiles/claude for shared rules, commands, and skills, while project-local placement uses dotfiles/.claude for repository-specific settings. Choose global for cross-project consistency and local for isolated scope.

What is the correct directory structure for Claude Code configuration in dotfiles?▼

The Claude Code configuration directory structure maps CLAUDE.md, commands, rules, hooks, and settings to either dotfiles/claude for global access or dotfiles/.claude for project-local scope. This enforces consistent configuration management across repositories.

How do I configure symlinks for Claude settings across multiple projects?▼

Configure Claude settings symlinks by mapping global files from dotfiles/claude or local files from dotfiles/.claude to the target project. This structure clarifies the scope for hooks, rules, and CLAUDE.md across multiple dotfiles repositories.

When should I use global versus local configuration for Claude Code?▼

Use global Claude Code configuration when rules, commands, or skills should apply universally across all projects. Use project-local configuration when settings, hooks, or CLAUDE.md content is specific to a single repository's context.

Can I manage CLAUDE.md and hooks differently for each project?▼

Yes, you can manage CLAUDE.md and hooks on a per-project basis by placing them under the project-local dotfiles/.claude directory. This keeps repository-specific configuration isolated from the global dotfiles/claude scope.