CLAUDE CODE MARKETPLACES

claudecode

This skill should be used when the user asks "how to use Claude Code", "Claude Code commands", "Claude Code features", "what can Claude Code do", "Claude Code tips", "Claude Code shortcuts", "how to configure Claude Code", or needs guidance on working effectively with Claude Code CLI.

npx skills add https://github.com/majiayu000/claude-skill-registry --skill claudecode
SKILL.md

Claude Code

Guide to working effectively with Claude Code CLI.

Purpose

Provide quick reference for:

  • Essential commands and shortcuts
  • Configuration and settings
  • Best practices for effective prompting
  • Plugin and skill development
  • Workflow optimization

Essential Commands

Slash Commands

CommandDescription
/helpShow help and available commands
/clearClear conversation history
/compactSummarize conversation to save context
/configOpen configuration settings
/costShow token usage and costs
/doctorDiagnose installation issues
/initInitialize CLAUDE.md in project
/loginAuthenticate with Anthropic
/logoutSign out
/memoryView/edit memory files
/modelSwitch AI model
/permissionsManage tool permissions
/pr-commentsView PR comments
/reviewReview code changes
/statusShow current session status
/vimToggle vim keybindings

Keyboard Shortcuts

ShortcutAction
Ctrl+CCancel current operation
Ctrl+DExit Claude Code
Ctrl+LClear screen
Ctrl+RSearch command history
TabAutocomplete files/commands
Up/DownNavigate history
EscCancel input (vim mode)

Context Management

CLAUDE.md Files

Project instructions stored in CLAUDE.md:

# Project Instructions

## Build Commands
- `npm run build` - Build project
- `npm test` - Run tests

## Code Style
- Use TypeScript strict mode
- Prefer functional components

## Important Files
- `src/config.ts` - Configuration
- `src/types/` - Type definitions

Location Priority:

  1. ./CLAUDE.md - Current directory (highest)
  2. ~/.claude/CLAUDE.md - Global (lowest)

Memory Files

Persistent memory across sessions:

# View memory
/memory

# Memory stored in
~/.claude/memory.md

Tool Permissions

Permission Levels

LevelDescription
askAsk before each use
allowAlways allow
denyAlways deny

Configure Permissions

/permissions

# Or in settings
/config

Common Permission Patterns

# Allow running tests
- tool: Bash
  prompt: "run tests"

# Allow npm commands
- tool: Bash
  prompt: "npm"

# Allow git operations
- tool: Bash
  prompt: "git"

Effective Prompting

Be Specific

# Good
"Add error handling to the fetchUser function in src/api/users.ts
that catches network errors and returns a default user object"

# Less effective
"Add error handling to the code"

Provide Context

# Good
"The build is failing with 'Cannot find module ./utils'.
Check the import paths in src/components/Header.tsx"

# Less effective
"Fix the build error"

Break Down Complex Tasks

# Step by step
1. "First, read the current implementation in src/auth/"
2. "Now add a logout function that clears the session"
3. "Update the tests in tests/auth.test.ts"

Use File References

# Reference specific files
"Update @src/config.ts to add a new API endpoint"

# Reference multiple files
"Compare @src/old.ts with @src/new.ts and list differences"

Model Selection

Available Models

ModelBest For
claude-sonnetFast, everyday tasks (default)
claude-opusComplex reasoning, architecture
claude-haikuQuick answers, simple tasks

Switch Models

/model opus    # For complex tasks
/model sonnet  # Default balance
/model haiku   # Quick operations

Working with Code

Read Before Edit

Always read files before modifying:

# Claude will read first
"Update the validation in src/forms/login.ts"

# Explicit read
"Read src/forms/login.ts and explain the validation logic"

Incremental Changes

# Prefer small, focused changes
"Add input validation to the email field"

# Then
"Add input validation to the password field"

# Rather than
"Rewrite the entire form with validation"

Test After Changes

"Run the tests to verify the changes work"

# Or be specific
"Run npm test -- --grep 'login'"

Git Integration

Common Workflows

# Check status
"Show git status"

# Create commit
"Commit these changes with message: Add user validation"

# Create PR
"Create a pull request for this feature"

# Review PR
/review

Commit Best Practices

Claude auto-adds co-author:

Co-Authored-By: Claude <noreply@anthropic.com>

Background Tasks

Run Tasks in Background

# Long-running commands
"Run the build in the background"

# Check status
/tasks

# View output
"Show output from task abc123"

Plugins & Skills

Available Skills

Invoke with slash commands:

/commit          # Create git commit
/review          # Review code changes
/pr-comments     # View PR feedback

Custom Skills

Create in .claude/skills/ or .windsurf/skills/:

skills/
└── my-skill/
    ├── SKILL.md         # Skill definition
    └── references/      # Supporting docs

See references/skill-development.md for details.

Troubleshooting

Common Issues

IssueSolution
Slow responsesUse /compact to reduce context
Tool deniedCheck /permissions
File not foundUse absolute paths or check cwd
API errorsRun /doctor

Debug Mode

# Verbose output
claude --debug

# Check configuration
claude --version
/config

Reset Session

# Clear conversation
/clear

# Fresh start
# Exit and restart claude

Best Practices Summary

  1. Read before writing - Understand existing code first
  2. Be specific - Clear instructions get better results
  3. Incremental changes - Small steps, verify each
  4. Use context files - Maintain CLAUDE.md for projects
  5. Manage permissions - Set up trusted patterns
  6. Use the right model - Opus for complex, Haiku for simple
  7. Compact regularly - Keep context manageable

Additional Resources

Reference Files

  • references/skill-development.md - Creating custom skills
  • references/hooks.md - Event hooks for automation

External Resources

Installs0
GitHub Stars391
LanguageHTML
AddedJun 10, 2026
View on GitHub