Troubleshooting Guide
This guide covers common issues and their solutions when using Claude-Craft.
Table of Contents
- Installation Issues
- Agent Issues
- Command Issues
- Configuration Issues
- Tool Issues
- Performance Issues
- Getting Help
Installation Issues
Commands Not Recognized After Installation
Symptoms:
- Slash commands like
/symfony:check-compliancedon't work - Claude doesn't recognize installed commands
Solutions:
Restart Claude Code
bash# Exit Claude Code completely exit # Start fresh claudeVerify installation
bashls -la .claude/commands/ # Should show command directoriesCheck command file format
bashhead -5 .claude/commands/symfony/check-compliance.md # Should start with proper markdown header
Files Not Found During Installation
Symptoms:
- "Source file not found" errors
- Missing rules or templates
Solutions:
Verify Claude-Craft path
bash# Check you're running from claude-craft directory pwd ls -la Dev/scripts/Check language files exist
bashls -la Dev/i18n/en/Symfony/rules/Use absolute TARGET path
bash# Instead of make install-symfony TARGET=./backend # Use make install-symfony TARGET=/full/path/to/backend
Permission Denied Errors
Symptoms:
- Can't execute installation scripts
- Can't write to target directory
Solutions:
Make scripts executable
bashchmod +x Dev/scripts/*.sh chmod +x Project/*.sh chmod +x Infra/*.sh chmod +x Tools/*/*.shCheck target directory permissions
bashls -la ~/my-project/ # Ensure you have write permissionsRun with appropriate user
bash# Don't use sudo unless necessary # Check directory ownership ls -la ~/my-project
Installation Creates Empty Directory
Symptoms:
.claude/directory created but empty or missing files
Solutions:
Check for errors in output
bash# Run with verbose output make install-symfony TARGET=./backend 2>&1 | tee install.logVerify source exists
bashls -la Dev/i18n/en/Symfony/Try direct script execution
bash./Dev/scripts/install-symfony-rules.sh --lang=en ./backend
Agent Issues
Agent Not Available
Symptoms:
@api-designeror other agents don't respond- "Unknown agent" type errors
Solutions:
Verify agent files exist
bashls -la .claude/agents/ # Should list agent .md filesCheck agent file format
bashhead -20 .claude/agents/api-designer.md # Should have proper frontmatter with name and descriptionReinstall agents
bashmake install-common TARGET=. OPTIONS="--force"
Agent Gives Irrelevant Responses
Symptoms:
- Agent doesn't follow its specialized instructions
- Generic responses instead of expert advice
Solutions:
Provide more context
markdown@symfony-reviewer Review my UserService implementation Context: - Symfony 7 with API Platform - Clean Architecture - DDD approach Code to review: [paste code here]Be specific in your request
markdown# Instead of @database-architect Help with my database # Use @database-architect Design the schema for User aggregate with: - User entity (id, email, password_hash) - Role entity (many-to-many with User) - Permission entity (many-to-many with Role) - Audit trail for user changesCheck project context file
bashcat .claude/rules/00-project-context.md # Ensure it describes your project accurately
Agent Conflicts with Project Rules
Symptoms:
- Agent suggestions contradict project conventions
- Inconsistent advice
Solutions:
Update project context
- Add specific conventions to
00-project-context.md - Include team preferences and constraints
- Add specific conventions to
Be explicit in requests
markdown@api-designer Design endpoint following our RESTful conventions (see 00-project-context.md for our API standards)
Command Issues
Command Not Found
Symptoms:
/symfony:generate-crudreturns "unknown command"- Command suggestions don't appear
Solutions:
Check command directory
bashls .claude/commands/symfony/ # Should include generate-crud.mdVerify namespace
bash# Commands are in format: /{namespace}:{command} # Available namespaces: ls .claude/commands/ # common/, symfony/, flutter/, python/, react/, reactnative/, docker/List available commands
bash# In Claude Code, type: /help
Command Execution Errors
Symptoms:
- Command starts but fails
- Unexpected output or errors
Solutions:
Check prerequisites
- Some commands require specific tools
- Verify required dependencies installed
Review command file
bashcat .claude/commands/symfony/generate-crud.md # Understand what the command expectsProvide required parameters
bash# Instead of /symfony:generate-crud # Use /symfony:generate-crud User --with-api --with-tests
Command Output Incorrect
Symptoms:
- Generated code doesn't match project style
- Wrong technology patterns used
Solutions:
Update project context
bash# Edit .claude/rules/00-project-context.md # Add specific patterns and conventionsCustomize templates
bash# Edit templates in .claude/templates/ # Adjust to match your project style
Configuration Issues
YAML Configuration Invalid
Symptoms:
make config-validatefails- Syntax errors in configuration
Solutions:
Check YAML syntax
bash# Validate YAML yq e '.' claude-projects.yamlCommon YAML errors:
yaml# Wrong: inconsistent indentation projects: - name: "project" path: "/path" # 2 spaces technologies: ["symfony"] # 3 spaces - ERROR! # Correct: consistent indentation projects: - name: "project" path: "/path" technologies: ["symfony"]Validate with tool
bashmake config-validate CONFIG=claude-projects.yaml
Project Not Found in Configuration
Symptoms:
- "Project not found" when installing
- Project not listed
Solutions:
Check project name spelling
bash# List projects make config-list CONFIG=claude-projects.yaml # Names are case-sensitiveVerify configuration file path
bash# Default looks for claude-projects.yaml in current directory # Specify explicitly: make config-install CONFIG=/path/to/config.yaml PROJECT=myproject
Configuration Not Applied
Symptoms:
- Changes to config don't take effect
- Old settings persist
Solutions:
Reinstall with force
bashmake config-install CONFIG=claude-projects.yaml PROJECT=myproject OPTIONS="--force"Check for conflicts
bash# Remove existing installation rm -rf /path/to/project/.claude # Reinstall make config-install CONFIG=claude-projects.yaml PROJECT=myproject
Tool Issues
StatusLine Not Displaying
Symptoms:
- Status bar empty or default
- Custom status line not showing
Solutions:
Verify script installed
bashls -la ~/.claude/statusline.sh # Should exist and be executableCheck settings.json
bashcat ~/.claude/settings.json | jq '.statusLine' # Should show: # { # "type": "command", # "command": "~/.claude/statusline.sh" # }Test script manually
bashecho '{"model":{"display_name":"Test","id":"claude-opus"}}' | ~/.claude/statusline.sh # Should output formatted status lineCheck for jq
bashwhich jq # Install if missing: brew install jq / apt install jq
MultiAccount Profile Issues
Symptoms:
- Can't switch profiles
- Profile not recognized
Solutions:
List profiles
bash./claude-accounts.sh listCheck profile directory
bashls -la ~/.claude-profiles/ # Should contain profile directoriesVerify profile mode file
bashcat ~/.claude-profiles/myprofile/.mode # Should contain "shared" or "isolated"Recreate problematic profile
bash./claude-accounts.sh remove myprofile ./claude-accounts.sh add myprofile --mode=shared
ProjectConfig yq Errors
Symptoms:
- "yq: command not found"
- YAML parsing errors
Solutions:
Install yq
bash# macOS brew install yq # Linux sudo snap install yq # or sudo wget https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64 -O /usr/local/bin/yq sudo chmod +x /usr/local/bin/yqVerify yq version
bashyq --version # Should be v4.x (mikefarah/yq, not kislyuk/yq)
Performance Issues
Slow Command Execution
Symptoms:
- Commands take long to respond
- StatusLine updates slowly
Solutions:
Check cache settings
bash# In ~/.claude/statusline.conf SESSION_CACHE_TTL=60 # Reduce if too slow WEEKLY_CACHE_TTL=300 # Reduce if too slowClear caches
bashrm /tmp/.ccusage_*Check network
- Some features require network (ccusage)
- Slow network = slow updates
Large Context Window Usage
Symptoms:
- 📊 indicator shows high percentage quickly
- "Context limit" warnings
Solutions:
Start fresh conversation
bashexit claudeBe concise in requests
- Avoid pasting large code blocks
- Reference files instead of pasting
Use agents for complex tasks
markdown# Instead of pasting entire codebase @research-assistant Find all authentication-related files in src/
Getting Help
Check Documentation
- Main docs:
docs/directory - Agent reference:
docs/AGENTS.md - Commands reference:
docs/COMMANDS.md - Technologies guide:
docs/TECHNOLOGIES.md
Get Version Info
# Installation scripts
./Dev/scripts/install-symfony-rules.sh --version
# Tools
./Tools/MultiAccount/claude-accounts.sh --version
./Tools/ProjectConfig/claude-projects.sh --versionReport Issues
If you encounter bugs:
Gather information:
- Claude-Craft version
- Operating system
- Steps to reproduce
- Error messages
Check existing issues on GitHub
Create new issue with details
Ask for Help
@research-assistant I'm having trouble with [describe issue]
Environment:
- OS: [your OS]
- Claude-Craft version: [version]
- Technology: [symfony/flutter/etc.]
What I tried:
1. [step 1]
2. [step 2]
Error message:
[paste error]Quick Fixes Checklist
When something doesn't work:
- [ ] Restart Claude Code
- [ ] Verify installation (
ls .claude/) - [ ] Check file permissions
- [ ] Validate configuration
- [ ] Clear caches
- [ ] Check dependencies (jq, yq)
- [ ] Try reinstall with
--force - [ ] Check documentation
- [ ] Ask for help
