Claude Code
Claude Code gets the most out of a toolkit. Skills, agents, commands, rules, settings, hooks, and MCP servers all arrive in Claude Code’s own formats, so there’s little to convert and little to lose. If you’re choosing an app to start with, this is the one with the fewest surprises.
Each launch gets its own folder: Code Config prepares your toolkit there, then starts Claude Code pointing at it.
Before you start
Section titled “Before you start”Install and sign in to Claude Code on this computer, connect Code Config, and choose a toolkit. Use coding-app accounts to choose the account a launch opens.
Start Claude Code with your toolkit
Section titled “Start Claude Code with your toolkit”In the Code Config app, choose your project, toolkit, Claude Code in a terminal, and account, then launch.
From a terminal in your project folder:
csc launch --host claudeThis command uses the project or workspace default toolkit. It does not select whichever toolkit you last viewed in the web app. A launch syncs updates before starting Claude Code.
Add --desktop to open the Claude desktop app with the toolkit instead of Claude Code in a terminal.
Check your tools
Section titled “Check your tools”Confirm the project folder and selected toolkit. Find a skill or command from the toolkit in Claude Code and try it on a small task. Check MCP connection status separately; an app opening does not confirm every server is ready.
Read Action needed and Notes on this launch before relying on a tool. Plugins need installation through Claude Code; listing one in a toolkit does not activate it.
Where each kind of tool goes
Section titled “Where each kind of tool goes”| Content | Delivery |
|---|---|
| Skills, agents, commands, output styles | Written in Claude Code’s formats. |
| Rules and context files | Combined into CLAUDE.md. |
| Toolkit settings and hook bundles | Combined in the launch’s settings.json; hook scripts are placed beside it. |
| Supported MCP servers | Registered for the launch using local credential access, without placing credential values in toolkit definitions. |
Claude Code uses a .claude/skills/ tree. File locations describes launch folders and other files.
What Claude Code doesn’t get from a toolkit
Section titled “What Claude Code doesn’t get from a toolkit”Workflows and marketplace entries are not written as Claude Code configuration. Plugins require Claude Code’s installation step. An MCP server with missing credentials needs local setup; other toolkit content can still be available.