claude-code-coding-agent
Claude Code Coding Agent
Use the Claude Code CLI command claude for delegated coding work.
This skill is for Claude Code only. Do not generalize it to Cursor, Codex, Pi, or other coding agents.
Treat claude as the default launcher, not the only launcher.
If the user explicitly provides a wrapper, alias-like command name, shell function entrypoint, or absolute path for Claude Code, use that user-declared command instead of hardcoding bare claude.
Examples:
/path/to/bin/claude --print "Your task"
claude-xxx-yyy --print "Your task"
Keep the rest of the invocation pattern the same unless the user's wrapper requires something different.
For exact flags and current behavior, prefer the local CLI help over memory:
More from patrick-fu/awesome-skills
brainstorm
Explore ideas, clarify goals, and help the user narrow down directions before planning or coding. Use this whenever the user proposes a new feature or idea, asks \"what do you think about X\", says \"I'm thinking of building Y\", wants to compare approaches, asks how to approach a problem, or seems to be exploring rather than ready to execute. Also use it when the user says \"brainstorm\", \"let's think about this\", \"what's the best way to...\", or any time the right next step is to clarify the problem and converge on a direction, not to write code yet.
10explore-and-plan
Turn a chosen or mostly chosen direction into an executable plan with no meaningful TBDs. Use this whenever the user asks for a plan, implementation plan, technical plan, project plan, rollout plan, or any other actionable proposal. Also use it when the user knows roughly what they want and needs it broken into concrete, ordered steps. If the request is still mainly exploratory, has too many unresolved choices, or is really asking to brainstorm, hand off to the brainstorm skill first and return once the direction is clear enough to plan.
9generate-commit-message
>-
7commit-staged-changes
Create Git commits for already staged changes.
5cursor-coding-agent
>-
4home-config-sync
Initialize and operate a generic personal dotfiles bare repo under ~/.dotfiles with work-tree=$HOME: guide the user to create an empty private remote repo, bootstrap local starter files, push the first commit, deploy onto another machine, update whitelist-managed files, pull remote changes into local home config, resolve stash and merge flows, and push local updates. Use when the user explicitly invokes $home-config-sync or explicitly asks to initialize, manage, or sync a bare-repo dotfiles setup.
3