Skip to main content
skill CX Codex

settings — Claude Code skill: what it does, how to install

This Claude Code skill redirects the legacy /settings call to /project-settings. It forwards the supplied arguments unchanged and invokes the main skill.

MIT 321 installs ★ 40,523 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Donchitos/Claude-Code-Game-Studios --skill settings -a claude-code
Open on GitHub

What settings does

settings prints a rename notice, then invokes the project-settings skill with the original arguments. With no arguments, it calls the skill without any. This alias does not change project settings itself.

Some AI tools already use /settings for a built-in command. The replacement is /project-settings; this skill keeps the old name as a handoff.

What it helps with

  • redirect an old /settings call to /project-settings
  • pass a key argument to the main settings skill
  • forward a setting value or a local option

Example prompts for the agent

  • Run /settings theme=dark to pass a project setting.
  • Call /settings --local theme=dark for a local value.
  • Send /settings theme to the project settings skill.

How to install settings

1Skills CLI (Vercel)

npx skills add Donchitos/Claude-Code-Game-Studios --skill settings -a claude-code

2Manually: put the files in place

~/.claude/skills/settings/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/settings/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about settings

How do I install settings in Claude Code?

Run npx skills add Donchitos/Claude-Code-Game-Studios --skill settings -a claude-code. The skill file is at ~/.claude/skills/settings/SKILL.md.

What does settings do?

It announces that /settings has been renamed to /project-settings, then invokes project-settings with the same arguments.

What arguments can settings pass along?

It accepts a key, a key=value pair, or a local pair prefixed with --local, such as --local key=value.

Source text

SKILL.md · MIT
---
name: settings
description: "Old name of /project-settings. Prints one line, then runs /project-settings."
argument-hint: "[key | key=value | --local key=value]"
user-invocable: true
disable-model-invocation: true
allowed-tools: Skill(project-settings)
model: sonnet
---

# /settings — old name of /project-settings

Several AI tools keep `/settings` for a command of their own, so this skill is now
`/project-settings`.

1. Print this line exactly, as the first line of your reply:

   /settings is now /project-settings. Running /project-settings.

2. Run the `project-settings` skill with the Skill tool, passing these arguments unchanged
   (none, if this is empty): $ARGUMENTS

Do nothing else here: `/project-settings` does the work.

© Donchitos · MIT · Donchitos/Claude-Code-Game-Studios

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set74

The whole set →
help help pinpoints your current game development stage and suggests the next action. Useful when you finish a task or do not know what to do next. CX Codex +1 633installs test-setup The test-setup skill sets up test infrastructure and CI with a tests directory, an engine test runner, and a GitHub Actions workflow. Use it before implementation starts. CX Codex +1 633installs skill-test skill-test is a Claude Code skill that checks skill and agent files for structure and stated behavior. It is used when reviewing project skills before use. CX Codex +1 632installs test-evidence-review test-evidence-review — a skill for Claude Code, Codex, Cursor and other platforms that goes past test existence and checks assertion coverage. It assigns ADEQUATE, INCOMPLETE, MISSING or NOT ASSESSED to each story. CX Codex +1 632installs story-readiness story-readiness validates whether user story files are ready for development by checking acceptance criteria, dependencies, and ADR statuses before coding starts. CX Codex +1 631installs test-flakiness test-flakiness spots flaky tests from CI run logs, groups intermittent failures by cause, and updates quarantine lists in game projects. CX Codex +1 630installs test-helpers test-helpers generates a test helper library for your engine: assertion utilities, factory functions, mocks. Useful when the same setup block keeps getting copied between test files. CX Codex +1 627installs vertical-slice Builds a vertical slice before production starts: one complete start-to-resolution cycle, to see whether the game can actually ship on schedule. CX Codex +1 619installs

Project sponsors

Companies that keep this analytics open