anchi-kit 1.2.3 → 1.2.6

package/.cursor/skills/claude-code/references/troubleshooting.md

@@ -0,0 +1,456 @@
+# Troubleshooting
+
+Common issues, debugging, and solutions for Cursor.
+
+## 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' > .cursor/.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 ~/.cursor
+chmod -R 755 ~/.cursor
+
+# 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 ~/.cursor/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 ~/.cursor/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 .cursor/hooks.json | jq .
+
+# Check hook script permissions
+chmod +x .cursor/scripts/hook.sh
+
+# Test hook script manually
+.cursor/scripts/hook.sh
+
+# Check logs
+cat ~/.cursor/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 ~/.cursor/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 ~/.cursor/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:
+   - Cursor version
+   - Operating system
+   - Error messages
+   - Steps to reproduce
+
+### Support Channels
+
+- **Documentation**: https://docs.cursor.com/claude-code
+- **GitHub Issues**: https://github.com/anthropics/claude-code/issues
+- **Support Portal**: support.cursor.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/.cursor/skills/code-review/references/code-review-reception.md

@@ -0,0 +1,209 @@
+---
+name: receiving-code-review
+description: Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
+---
+
+# Code Review Reception
+
+## Overview
+
+Code review requires technical evaluation, not emotional performance.
+
+**Core principle:** Verify before implementing. Ask before assuming. Technical correctness over social comfort.
+
+## The Response Pattern
+
+```
+WHEN receiving code review feedback:
+
+1. READ: Complete feedback without reacting
+2. UNDERSTAND: Restate requirement in own words (or ask)
+3. VERIFY: Check against codebase reality
+4. EVALUATE: Technically sound for THIS codebase?
+5. RESPOND: Technical acknowledgment or reasoned pushback
+6. IMPLEMENT: One item at a time, test each
+```
+
+## Forbidden Responses
+
+**NEVER:**
+- "You're absolutely right!" (explicit CLAUDE.md violation)
+- "Great point!" / "Excellent feedback!" (performative)
+- "Let me implement that now" (before verification)
+
+**INSTEAD:**
+- Restate the technical requirement
+- Ask clarifying questions
+- Push back with technical reasoning if wrong
+- Just start working (actions > words)
+
+## Handling Unclear Feedback
+
+```
+IF any item is unclear:
+  STOP - do not implement anything yet
+  ASK for clarification on unclear items
+
+WHY: Items may be related. Partial understanding = wrong implementation.
+```
+
+**Example:**
+```
+your human partner: "Fix 1-6"
+You understand 1,2,3,6. Unclear on 4,5.
+
+❌ WRONG: Implement 1,2,3,6 now, ask about 4,5 later
+✅ RIGHT: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding."
+```
+
+## Source-Specific Handling
+
+### From your human partner
+- **Trusted** - implement after understanding
+- **Still ask** if scope unclear
+- **No performative agreement**
+- **Skip to action** or technical acknowledgment
+
+### From External Reviewers
+```
+BEFORE implementing:
+  1. Check: Technically correct for THIS codebase?
+  2. Check: Breaks existing functionality?
+  3. Check: Reason for current implementation?
+  4. Check: Works on all platforms/versions?
+  5. Check: Does reviewer understand full context?
+
+IF suggestion seems wrong:
+  Push back with technical reasoning
+
+IF can't easily verify:
+  Say so: "I can't verify this without [X]. Should I [investigate/ask/proceed]?"
+
+IF conflicts with your human partner's prior decisions:
+  Stop and discuss with your human partner first
+```
+
+**your human partner's rule:** "External feedback - be skeptical, but check carefully"
+
+## YAGNI Check for "Professional" Features
+
+```
+IF reviewer suggests "implementing properly":
+  grep codebase for actual usage
+
+  IF unused: "This endpoint isn't called. Remove it (YAGNI)?"
+  IF used: Then implement properly
+```
+
+**your human partner's rule:** "You and reviewer both report to me. If we don't need this feature, don't add it."
+
+## Implementation Order
+
+```
+FOR multi-item feedback:
+  1. Clarify anything unclear FIRST
+  2. Then implement in this order:
+     - Blocking issues (breaks, security)
+     - Simple fixes (typos, imports)
+     - Complex fixes (refactoring, logic)
+  3. Test each fix individually
+  4. Verify no regressions
+```
+
+## When To Push Back
+
+Push back when:
+- Suggestion breaks existing functionality
+- Reviewer lacks full context
+- Violates YAGNI (unused feature)
+- Technically incorrect for this stack
+- Legacy/compatibility reasons exist
+- Conflicts with your human partner's architectural decisions
+
+**How to push back:**
+- Use technical reasoning, not defensiveness
+- Ask specific questions
+- Reference working tests/code
+- Involve your human partner if architectural
+
+**Signal if uncomfortable pushing back out loud:** "Strange things are afoot at the Circle K"
+
+## Acknowledging Correct Feedback
+
+When feedback IS correct:
+```
+✅ "Fixed. [Brief description of what changed]"
+✅ "Good catch - [specific issue]. Fixed in [location]."
+✅ [Just fix it and show in the code]
+
+❌ "You're absolutely right!"
+❌ "Great point!"
+❌ "Thanks for catching that!"
+❌ "Thanks for [anything]"
+❌ ANY gratitude expression
+```
+
+**Why no thanks:** Actions speak. Just fix it. The code itself shows you heard the feedback.
+
+**If you catch yourself about to write "Thanks":** DELETE IT. State the fix instead.
+
+## Gracefully Correcting Your Pushback
+
+If you pushed back and were wrong:
+```
+✅ "You were right - I checked [X] and it does [Y]. Implementing now."
+✅ "Verified this and you're correct. My initial understanding was wrong because [reason]. Fixing."
+
+❌ Long apology
+❌ Defending why you pushed back
+❌ Over-explaining
+```
+
+State the correction factually and move on.
+
+## Common Mistakes
+
+| Mistake | Fix |
+|---------|-----|
+| Performative agreement | State requirement or just act |
+| Blind implementation | Verify against codebase first |
+| Batch without testing | One at a time, test each |
+| Assuming reviewer is right | Check if breaks things |
+| Avoiding pushback | Technical correctness > comfort |
+| Partial implementation | Clarify all items first |
+| Can't verify, proceed anyway | State limitation, ask for direction |
+
+## Real Examples
+
+**Performative Agreement (Bad):**
+```
+Reviewer: "Remove legacy code"
+❌ "You're absolutely right! Let me remove that..."
+```
+
+**Technical Verification (Good):**
+```
+Reviewer: "Remove legacy code"
+✅ "Checking... build target is 10.15+, this API needs 13+. Need legacy for backward compat. Current impl has wrong bundle ID - fix it or drop pre-13 support?"
+```
+
+**YAGNI (Good):**
+```
+Reviewer: "Implement proper metrics tracking with database, date filters, CSV export"
+✅ "Grepped codebase - nothing calls this endpoint. Remove it (YAGNI)? Or is there usage I'm missing?"
+```
+
+**Unclear Item (Good):**
+```
+your human partner: "Fix items 1-6"
+You understand 1,2,3,6. Unclear on 4,5.
+✅ "Understand 1,2,3,6. Need clarification on 4 and 5 before implementing."
+```
+
+## The Bottom Line
+
+**External feedback = suggestions to evaluate, not orders to follow.**
+
+Verify. Question. Then implement.
+
+No performative agreement. Technical rigor always.