QuestionQ53

Claude Code Configuration & Workflows

Your team frequently migrates React components to Vue, and you have written a step-by-step workflow for Claude Code to follow during each migration. You want every developer on the team to be able to invoke this workflow by typing /migrate-component, and you want the workflow to stay in sync as the team continues to iterate on it.

Where should you place the skill file?

Explanation

Claude Code skills are defined in a SKILL.md file inside a directory named after the skill, and the skill's directory name becomes its slash-command name (e.g., a skill in migrate-component/SKILL.md is invoked with /migrate-component). Placing the skill under the project's .claude/skills/ directory at the project root and committing it to version control ensures it is a project-level (not personal) skill: every developer who clones or pulls the repository automatically gets the same skill, and any updates made by teammates are picked up the next time they pull, keeping the workflow in sync across the team. Personal skills under ~/.claude/skills/ are local to a single developer's machine and are not shared, settings.json does not support defining skills via a skillOverrides field, and CLAUDE.md is intended for persistent contextual project guidance rather than for defining an invocable slash-command workflow.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!