claude-settings

Name: claude-settings
Availability: InStock
Author: Descoped

Configure Claude Code settings files with auto-detected project stack.

Updated Mar 4, 2026

Search Tags:#automation #permissions #mcp #claude-code #settings.json #configure #settings.local.json

Ready to run

npx skills add https://github.com/descoped/llm-skills --skill claude-settings-descoped

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-settings
Source: https://github.com/descoped/llm-skills/tree/main/skills/claude-settings
Command: npx skills add https://github.com/descoped/llm-skills --skill claude-settings-descoped

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configure Claude Code project settings for autonomous, unattended work, enabling teams to standardize and persist environment and permission management across projects while minimizing prompts.

Core Features & Use Cases

Shared and personal configuration: manage .claude/settings.json (committed) and .claude/settings.local.json (gitignored) with controlled merging.
Automatic project context detection: auto-detect tech stacks and wire up appropriate hooks, permissions, MCP servers, and plugins.
Safe, repeatable deployments: apply project-wide defaults while allowing local overrides to support diverse workflows.

Quick Start

Use Claude to generate or update the Claude Code settings files for your current project.

Frequently Asked Questions about claude-settings

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

FAQPage Schema

How do I configure Claude Code settings for unattended automation?▼

Configuring Claude Code settings for unattended automation involves generating .claude/settings.json to define permissions, hooks, and MCP servers. This minimizes manual prompts by automatically applying safety defaults and tech-stack-specific rules for autonomous workflows.

What is the difference between settings.json and settings.local.json in Claude Code?▼

The settings.json file contains shared, team-wide configuration that is committed to version control, while settings.local.json holds personal overrides and is gitignored. The Skill merges these to apply project defaults while supporting individual workflows.

How do I set up MCP servers and hooks for my Claude Code project?▼

Setting up MCP servers and hooks requires generating a Claude Code settings configuration. The Skill auto-detects your project's tech stack and wires up appropriate hooks, permissions, MCP servers, and plugins automatically.

Can I auto-detect my tech stack to configure Claude Code permissions?▼

Yes, you can auto-detect your tech stack to configure Claude Code permissions. The Skill analyzes your project context and automatically sets appropriate permissions, safety defaults, and plugin integrations.

What's the best way to standardize Claude Code settings across a development team?▼

The best way to standardize Claude Code settings across a team is committing a shared .claude/settings.json file with project-wide defaults. This ensures consistent environment and permission management while allowing local overrides.