claude-skill-lord 1.5.0

package/skills/tier-2/claude-code/references/troubleshooting.md

@@ -0,0 +1,456 @@
+# Troubleshooting
+
+Common issues, debugging, and solutions for Claude Code.
+
+## Authentication Issues
+
+### API Key Not Recognized
+
+**Symptoms:**
+- "Invalid API key" errors
+- Authentication failures
+- 401 Unauthorized responses
+
+**Solutions:**
+
+```bash
+# Verify API key is set
+echo $ANTHROPIC_API_KEY
+
+# Re-login
+claude logout
+claude login
+
+# Check API key format (should start with sk-ant-)
+echo $ANTHROPIC_API_KEY | grep "^sk-ant-"
+
+# Test API key directly
+curl https://api.anthropic.com/v1/messages \
+  -H "x-api-key: $ANTHROPIC_API_KEY" \
+  -H "anthropic-version: 2023-06-01" \
+  -H "content-type: application/json" \
+  -d '{"model":"claude-sonnet-4-5-20250929","max_tokens":10,"messages":[{"role":"user","content":"hi"}]}'
+```
+
+### Environment Variable Issues
+
+```bash
+# Add to shell profile
+echo 'export ANTHROPIC_API_KEY=sk-ant-xxxxx' >> ~/.bashrc
+source ~/.bashrc
+
+# Or use .env file
+echo 'ANTHROPIC_API_KEY=sk-ant-xxxxx' > .claude/.env
+
+# Verify it's loaded
+claude config get apiKey
+```
+
+## Installation Problems
+
+### npm Installation Failures
+
+```bash
+# Clear npm cache
+npm cache clean --force
+
+# Remove and reinstall
+npm uninstall -g @anthropic-ai/claude-code
+npm install -g @anthropic-ai/claude-code
+
+# Use specific version
+npm install -g @anthropic-ai/claude-code@1.0.0
+
+# Check installation
+which claude
+claude --version
+```
+
+### Permission Errors
+
+```bash
+# Fix permissions on Unix/Mac
+sudo chown -R $USER ~/.claude
+chmod -R 755 ~/.claude
+
+# Or install without sudo (using nvm)
+nvm install 18
+npm install -g @anthropic-ai/claude-code
+```
+
+### Python Installation Issues
+
+```bash
+# Upgrade pip
+pip install --upgrade pip
+
+# Install in virtual environment
+python -m venv claude-env
+source claude-env/bin/activate
+pip install claude-code
+
+# Install with --user flag
+pip install --user claude-code
+```
+
+## Connection & Network Issues
+
+### Proxy Configuration
+
+```bash
+# Set proxy environment variables
+export HTTP_PROXY=http://proxy.company.com:8080
+export HTTPS_PROXY=http://proxy.company.com:8080
+export NO_PROXY=localhost,127.0.0.1
+
+# Configure in settings
+claude config set proxy http://proxy.company.com:8080
+
+# Test connection
+curl -x $HTTP_PROXY https://api.anthropic.com
+```
+
+### SSL/TLS Errors
+
+```bash
+# Trust custom CA certificate
+export NODE_EXTRA_CA_CERTS=/path/to/ca-bundle.crt
+
+# Disable SSL verification (not recommended for production)
+export NODE_TLS_REJECT_UNAUTHORIZED=0
+
+# Update ca-certificates
+sudo update-ca-certificates  # Debian/Ubuntu
+sudo update-ca-trust         # RHEL/CentOS
+```
+
+### Firewall Issues
+
+```bash
+# Check connectivity to Anthropic API
+ping api.anthropic.com
+telnet api.anthropic.com 443
+
+# Test HTTPS connection
+curl -v https://api.anthropic.com
+
+# Check firewall rules
+sudo iptables -L  # Linux
+netsh advfirewall show allprofiles  # Windows
+```
+
+## MCP Server Problems
+
+### Server Not Starting
+
+```bash
+# Test MCP server command manually
+npx -y @modelcontextprotocol/server-filesystem /tmp
+
+# Check server logs
+cat ~/.claude/logs/mcp-*.log
+
+# Verify environment variables
+echo $GITHUB_TOKEN  # For GitHub MCP
+
+# Test with MCP Inspector
+npx @modelcontextprotocol/inspector
+```
+
+### Connection Timeouts
+
+```json
+{
+  "mcpServers": {
+    "my-server": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-example"],
+      "timeout": 30000,
+      "retries": 3
+    }
+  }
+}
+```
+
+### Permission Denied
+
+```bash
+# Check file permissions
+ls -la /path/to/mcp/server
+
+# Make executable
+chmod +x /path/to/mcp/server
+
+# Check directory access
+ls -ld /path/to/allowed/directory
+```
+
+## Performance Issues
+
+### Slow Responses
+
+**Check network latency:**
+```bash
+ping api.anthropic.com
+```
+
+**Use faster model:**
+```bash
+claude --model haiku "simple task"
+```
+
+**Reduce context:**
+```json
+{
+  "maxTokens": 4096,
+  "context": {
+    "autoTruncate": true
+  }
+}
+```
+
+**Enable caching:**
+```json
+{
+  "caching": {
+    "enabled": true
+  }
+}
+```
+
+### High Memory Usage
+
+```bash
+# Clear cache
+rm -rf ~/.claude/cache/*
+
+# Limit context window
+claude config set maxTokens 8192
+
+# Disable memory
+claude config set memory.enabled false
+
+# Close unused sessions
+claude session list
+claude session close session-123
+```
+
+### Rate Limiting
+
+```bash
+# Check rate limits
+claude usage show
+
+# Wait and retry
+sleep 60
+claude "retry task"
+
+# Implement exponential backoff in scripts
+```
+
+## Tool Execution Errors
+
+### Bash Command Failures
+
+**Check sandboxing settings:**
+```json
+{
+  "sandboxing": {
+    "enabled": true,
+    "allowedPaths": ["/workspace", "/tmp"]
+  }
+}
+```
+
+**Verify command permissions:**
+```bash
+# Make script executable
+chmod +x script.sh
+
+# Check PATH
+echo $PATH
+which command-name
+```
+
+### File Access Denied
+
+```bash
+# Check file permissions
+ls -la file.txt
+
+# Change ownership
+sudo chown $USER file.txt
+
+# Grant read/write permissions
+chmod 644 file.txt
+```
+
+### Write Tool Failures
+
+```bash
+# Check disk space
+df -h
+
+# Verify directory exists
+mkdir -p /path/to/directory
+
+# Check write permissions
+touch /path/to/directory/test.txt
+rm /path/to/directory/test.txt
+```
+
+## Hook Errors
+
+### Hooks Not Running
+
+```bash
+# Verify hooks.json syntax
+cat .claude/hooks.json | jq .
+
+# Check hook script permissions
+chmod +x .claude/scripts/hook.sh
+
+# Test hook script manually
+.claude/scripts/hook.sh
+
+# Check logs
+cat ~/.claude/logs/hooks.log
+```
+
+### Hook Script Errors
+
+```bash
+# Add error handling to hooks
+#!/bin/bash
+set -e  # Exit on error
+set -u  # Exit on undefined variable
+
+# Debug hook execution
+#!/bin/bash
+set -x  # Print commands
+echo "Hook running: $TOOL_NAME"
+```
+
+## Debug Mode
+
+### Enable Debugging
+
+```bash
+# Set debug environment variable
+export CLAUDE_DEBUG=1
+export CLAUDE_LOG_LEVEL=debug
+
+# Run with debug flag
+claude --debug "task"
+
+# View debug logs
+tail -f ~/.claude/logs/debug.log
+```
+
+### Verbose Output
+
+```bash
+# Enable verbose mode
+claude --verbose "task"
+
+# Show all tool calls
+claude --show-tools "task"
+
+# Display thinking process
+claude --show-thinking "task"
+```
+
+## Common Error Messages
+
+### "Model not found"
+
+```bash
+# Use correct model name
+claude --model claude-sonnet-4-5-20250929
+
+# Update claude-code
+npm update -g @anthropic-ai/claude-code
+```
+
+### "Rate limit exceeded"
+
+```bash
+# Wait and retry
+sleep 60
+
+# Check usage
+claude usage show
+
+# Implement rate limiting in code
+```
+
+### "Context length exceeded"
+
+```bash
+# Reduce context
+claude config set maxTokens 100000
+
+# Summarize long content
+claude "summarize this codebase"
+
+# Process in chunks
+claude "analyze first half of files"
+```
+
+### "Timeout waiting for response"
+
+```bash
+# Increase timeout
+claude config set timeout 300
+
+# Check network connection
+ping api.anthropic.com
+
+# Retry with smaller request
+```
+
+## Getting Help
+
+### Collect Diagnostic Info
+
+```bash
+# System info
+claude --version
+node --version
+npm --version
+
+# Configuration
+claude config list --all
+
+# Recent logs
+tail -n 100 ~/.claude/logs/session.log
+
+# Environment
+env | grep CLAUDE
+env | grep ANTHROPIC
+```
+
+### Report Issues
+
+1. **Check existing issues**: https://github.com/anthropics/claude-code/issues
+2. **Gather diagnostic info**
+3. **Create minimal reproduction**
+4. **Submit issue** with:
+   - Claude Code version
+   - Operating system
+   - Error messages
+   - Steps to reproduce
+
+### Support Channels
+
+- **Documentation**: https://docs.claude.com/claude-code
+- **GitHub Issues**: https://github.com/anthropics/claude-code/issues
+- **Support Portal**: support.claude.com
+- **Community Discord**: discord.gg/anthropic
+
+## See Also
+
+- Installation guide: `references/getting-started.md`
+- Configuration: `references/configuration.md`
+- MCP setup: `references/mcp-integration.md`
+- Best practices: `references/best-practices.md`

package/skills/tier-2/codebase-onboarding/SKILL.md

@@ -0,0 +1,233 @@
+---
+name: codebase-onboarding
+description: Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.
+origin: ECC
+---
+
+# Codebase Onboarding
+
+Systematically analyze an unfamiliar codebase and produce a structured onboarding guide. Designed for developers joining a new project or setting up Claude Code in an existing repo for the first time.
+
+## When to Use
+
+- First time opening a project with Claude Code
+- Joining a new team or repository
+- User asks "help me understand this codebase"
+- User asks to generate a CLAUDE.md for a project
+- User says "onboard me" or "walk me through this repo"
+
+## How It Works
+
+### Phase 1: Reconnaissance
+
+Gather raw signals about the project without reading every file. Run these checks in parallel:
+
+```
+1. Package manifest detection
+   → package.json, go.mod, Cargo.toml, pyproject.toml, pom.xml, build.gradle,
+     Gemfile, composer.json, mix.exs, pubspec.yaml
+
+2. Framework fingerprinting
+   → next.config.*, nuxt.config.*, angular.json, vite.config.*,
+     django settings, flask app factory, fastapi main, rails config
+
+3. Entry point identification
+   → main.*, index.*, app.*, server.*, cmd/, src/main/
+
+4. Directory structure snapshot
+   → Top 2 levels of the directory tree, ignoring node_modules, vendor,
+     .git, dist, build, __pycache__, .next
+
+5. Config and tooling detection
+   → .eslintrc*, .prettierrc*, tsconfig.json, Makefile, Dockerfile,
+     docker-compose*, .github/workflows/, .env.example, CI configs
+
+6. Test structure detection
+   → tests/, test/, __tests__/, *_test.go, *.spec.ts, *.test.js,
+     pytest.ini, jest.config.*, vitest.config.*
+```
+
+### Phase 2: Architecture Mapping
+
+From the reconnaissance data, identify:
+
+**Tech Stack**
+- Language(s) and version constraints
+- Framework(s) and major libraries
+- Database(s) and ORMs
+- Build tools and bundlers
+- CI/CD platform
+
+**Architecture Pattern**
+- Monolith, monorepo, microservices, or serverless
+- Frontend/backend split or full-stack
+- API style: REST, GraphQL, gRPC, tRPC
+
+**Key Directories**
+Map the top-level directories to their purpose:
+
+<!-- Example for a React project — replace with detected directories -->
+```
+src/components/  → React UI components
+src/api/         → API route handlers
+src/lib/         → Shared utilities
+src/db/          → Database models and migrations
+tests/           → Test suites
+scripts/         → Build and deployment scripts
+```
+
+**Data Flow**
+Trace one request from entry to response:
+- Where does a request enter? (router, handler, controller)
+- How is it validated? (middleware, schemas, guards)
+- Where is business logic? (services, models, use cases)
+- How does it reach the database? (ORM, raw queries, repositories)
+
+### Phase 3: Convention Detection
+
+Identify patterns the codebase already follows:
+
+**Naming Conventions**
+- File naming: kebab-case, camelCase, PascalCase, snake_case
+- Component/class naming patterns
+- Test file naming: `*.test.ts`, `*.spec.ts`, `*_test.go`
+
+**Code Patterns**
+- Error handling style: try/catch, Result types, error codes
+- Dependency injection or direct imports
+- State management approach
+- Async patterns: callbacks, promises, async/await, channels
+
+**Git Conventions**
+- Branch naming from recent branches
+- Commit message style from recent commits
+- PR workflow (squash, merge, rebase)
+- If the repo has no commits yet or only a shallow history (e.g. `git clone --depth 1`), skip this section and note "Git history unavailable or too shallow to detect conventions"
+
+### Phase 4: Generate Onboarding Artifacts
+
+Produce two outputs:
+
+#### Output 1: Onboarding Guide
+
+```markdown
+# Onboarding Guide: [Project Name]
+
+## Overview
+[2-3 sentences: what this project does and who it serves]
+
+## Tech Stack
+<!-- Example for a Next.js project — replace with detected stack -->
+| Layer | Technology | Version |
+|-------|-----------|---------|
+| Language | TypeScript | 5.x |
+| Framework | Next.js | 14.x |
+| Database | PostgreSQL | 16 |
+| ORM | Prisma | 5.x |
+| Testing | Jest + Playwright | - |
+
+## Architecture
+[Diagram or description of how components connect]
+
+## Key Entry Points
+<!-- Example for a Next.js project — replace with detected paths -->
+- **API routes**: `src/app/api/` — Next.js route handlers
+- **UI pages**: `src/app/(dashboard)/` — authenticated pages
+- **Database**: `prisma/schema.prisma` — data model source of truth
+- **Config**: `next.config.ts` — build and runtime config
+
+## Directory Map
+[Top-level directory → purpose mapping]
+
+## Request Lifecycle
+[Trace one API request from entry to response]
+
+## Conventions
+- [File naming pattern]
+- [Error handling approach]
+- [Testing patterns]
+- [Git workflow]
+
+## Common Tasks
+<!-- Example for a Node.js project — replace with detected commands -->
+- **Run dev server**: `npm run dev`
+- **Run tests**: `npm test`
+- **Run linter**: `npm run lint`
+- **Database migrations**: `npx prisma migrate dev`
+- **Build for production**: `npm run build`
+
+## Where to Look
+<!-- Example for a Next.js project — replace with detected paths -->
+| I want to... | Look at... |
+|--------------|-----------|
+| Add an API endpoint | `src/app/api/` |
+| Add a UI page | `src/app/(dashboard)/` |
+| Add a database table | `prisma/schema.prisma` |
+| Add a test | `tests/` matching the source path |
+| Change build config | `next.config.ts` |
+```
+
+#### Output 2: Starter CLAUDE.md
+
+Generate or update a project-specific CLAUDE.md based on detected conventions. If `CLAUDE.md` already exists, read it first and enhance it — preserve existing project-specific instructions and clearly call out what was added or changed.
+
+```markdown
+# Project Instructions
+
+## Tech Stack
+[Detected stack summary]
+
+## Code Style
+- [Detected naming conventions]
+- [Detected patterns to follow]
+
+## Testing
+- Run tests: `[detected test command]`
+- Test pattern: [detected test file convention]
+- Coverage: [if configured, the coverage command]
+
+## Build & Run
+- Dev: `[detected dev command]`
+- Build: `[detected build command]`
+- Lint: `[detected lint command]`
+
+## Project Structure
+[Key directory → purpose map]
+
+## Conventions
+- [Commit style if detectable]
+- [PR workflow if detectable]
+- [Error handling patterns]
+```
+
+## Best Practices
+
+1. **Don't read everything** — reconnaissance should use Glob and Grep, not Read on every file. Read selectively only for ambiguous signals.
+2. **Verify, don't guess** — if a framework is detected from config but the actual code uses something different, trust the code.
+3. **Respect existing CLAUDE.md** — if one already exists, enhance it rather than replacing it. Call out what's new vs existing.
+4. **Stay concise** — the onboarding guide should be scannable in 2 minutes. Details belong in the code, not the guide.
+5. **Flag unknowns** — if a convention can't be confidently detected, say so rather than guessing. "Could not determine test runner" is better than a wrong answer.
+
+## Anti-Patterns to Avoid
+
+- Generating a CLAUDE.md that's longer than 100 lines — keep it focused
+- Listing every dependency — highlight only the ones that shape how you write code
+- Describing obvious directory names — `src/` doesn't need an explanation
+- Copying the README — the onboarding guide adds structural insight the README lacks
+
+## Examples
+
+### Example 1: First time in a new repo
+**User**: "Onboard me to this codebase"
+**Action**: Run full 4-phase workflow → produce Onboarding Guide + Starter CLAUDE.md
+**Output**: Onboarding Guide printed directly to the conversation, plus a `CLAUDE.md` written to the project root
+
+### Example 2: Generate CLAUDE.md for existing project
+**User**: "Generate a CLAUDE.md for this project"
+**Action**: Run Phases 1-3, skip Onboarding Guide, produce only CLAUDE.md
+**Output**: Project-specific `CLAUDE.md` with detected conventions
+
+### Example 3: Enhance existing CLAUDE.md
+**User**: "Update the CLAUDE.md with current project conventions"
+**Action**: Read existing CLAUDE.md, run Phases 1-3, merge new findings
+**Output**: Updated `CLAUDE.md` with additions clearly marked