Spaces:

danielrosehill
/

Claude-Code-Slash-Commands-Linux-Desktop

Running

App Files Files Community

danielrosehill commited on Oct 26

Commit

279efce

1 Parent(s): 550e3e7

commit

Browse files

This view is limited to 50 files because it contains too many changes. See raw diff

Files changed (50) hide show

.gitignore +24 -0
README.md +43 -6
category.html +35 -0
commands/ai-tools/audit-local-ai-packages.md +97 -0
commands/ai-tools/comfyui/setup-comfyui.md +75 -0
commands/ai-tools/gpu-ai-ml-assessment.md +441 -0
commands/ai-tools/ollama/prune-ollama.md +14 -0
commands/ai-tools/ollama/setup-ollama.md +57 -0
commands/ai-tools/ollama/suggest-ollama-models.md +78 -0
commands/ai-tools/setup-speech-to-text.md +112 -0
commands/backup/identify-backup-targets.md +109 -0
commands/bluetooth/reset-bluetooth.md +330 -0
commands/bluetooth/troubleshoot-bluetooth.md +300 -0
commands/configuration/add-bash-alias.md +9 -0
commands/configuration/check-git-config.md +103 -0
commands/configuration/check-global-gitignore.md +145 -0
commands/configuration/check-path.md +209 -0
commands/configuration/debug-folder-permissions.md +234 -0
commands/configuration/list-ssh-connections.md +91 -0
commands/configuration/manage-api-keys.md +101 -0
commands/configuration/manage-ssh-keys.md +91 -0
commands/configuration/mcp/manage-mcp-servers.md +104 -0
commands/configuration/validate-bashrc.md +99 -0
commands/debugging/check-boot-logs.md +43 -0
commands/debugging/diagnose-crash.md +162 -0
commands/debugging/diagnose-slowdown.md +134 -0
commands/debugging/failed-boot-services.md +7 -0
commands/debugging/review-boot.md +36 -0
commands/dev-tools/node/node-version-check.md +1 -0
commands/dev-tools/node/npm-install.md +1 -0
commands/dev-tools/optimize-vscode-installation.md +131 -0
commands/dev-tools/sdk-check.md +2 -0
commands/dev-tools/setup-docker.md +258 -0
commands/dev-tools/suggest-ides.md +115 -0
commands/dev-tools/yadm/check-yadm.md +51 -0
commands/dev-tools/yadm/manually-update-yadm.md +49 -0
commands/display/list-connected-displays.md +72 -0
commands/display/optimize-display-scaling.md +135 -0
commands/display/setup-multi-monitor.md +90 -0
commands/display/switch-display-profile.md +172 -0
commands/filesystem-organization/chunking/chunk-this-dir.md +5 -0
commands/filesystem-organization/consolidate-folders.md +46 -0
commands/filesystem-organization/flatten.md +7 -0
commands/filesystem-organization/separate-by-filetype.md +3 -0
commands/filesystem-organization/separate-photos-and-video.md +5 -0
commands/filesystem-organization/suggest-folder-structure.md +52 -0
commands/filesystem-organization/tidy-up/desktop-tidy.md +9 -0
commands/filesystem-organization/tidy-up/organize-loose-files.md +32 -0
commands/fonts/install-google-fonts.md +80 -0
commands/fonts/list-fonts.md +79 -0

.gitignore ADDED Viewed

	@@ -0,0 +1,24 @@

+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+env/
+venv/
+.venv/
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+# OS
+.DS_Store
+Thumbs.db
+# Temporary files
+*.tmp
+*.bak
+*~

README.md CHANGED Viewed

@@ -1,11 +1,48 @@
 ---
-title: Claude Code Slash Commands Linux Desktop
-emoji: 🚀
-colorFrom: purple
-colorTo: red
 sdk: static
 pinned: false
-short_description: Slash commands for the Linux desktop using Claude Code
 ---
-Check out the configuration reference at https://huggingface.co/docs/hub/spaces-config-reference

 ---
+title: Claude Code Linux Desktop Slash Commands
+emoji: 🖥️
+colorFrom: blue
+colorTo: indigo
 sdk: static
 pinned: false
+short_description: Searchable collection of Claude Code slash commands for Linux system administration
 ---
+# Claude Code Linux Desktop Slash Commands
+A comprehensive, searchable collection of [Claude Code](https://claude.com/claude-code) slash commands for Linux desktop system administration and configuration tasks.
+## Features
+- **44 Categories** covering AI tools, system health, hardware, networking, security, and more
+- **111+ Commands** for system administration tasks
+- **Clean Interface** with category browsing and search functionality
+- **Easy Copy** - One-click copying of command names
+- **Expandable Details** - View full command documentation inline
+- **Tag System** - Commands organized with descriptive tags
+## Categories Include
+- AI Tools (Ollama, ComfyUI, ML packages)
+- System Health & Diagnostics
+- Hardware Configuration & Optimization
+- Network Management
+- Package Management
+- Python & Development Tools
+- Security & Backup
+- KDE & Display Configuration
+- And many more...
+## Usage
+1. Browse categories on the home page
+2. Click a category to view all commands in that category
+3. Use search to filter commands by name or description
+4. Click command headers to expand and view full documentation
+5. Click "Copy" to copy the command name to clipboard
+## Source
+This collection is maintained at: [github.com/danielrosehill/Claude-Code-Linux-Desktop-Slash-Commands](https://github.com/danielrosehill/Claude-Code-Linux-Desktop-Slash-Commands)
+Created by [Daniel Rosehill](https://danielrosehill.com)

category.html ADDED Viewed

	@@ -0,0 +1,35 @@

+<!DOCTYPE html>
+<html lang="en">
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Category - Claude Code Commands</title>
+    <link rel="stylesheet" href="styles.css">
+</head>
+<body>
+    <header>
+        <div class="container">
+            <a href="index.html" class="back-link">← Back to Categories</a>
+            <h1 id="categoryTitle">Commands</h1>
+        </div>
+    </header>
+    <main class="container">
+        <div class="search-box">
+            <input type="text" id="searchInput" placeholder="Search commands in this category..." onkeyup="filterCommands()">
+        </div>
+        <div class="commands-list" id="commandsList">
+            <!-- Commands will be loaded here by JavaScript -->
+        </div>
+    </main>
+    <footer>
+        <div class="container">
+            <p>Created by Daniel Rosehill | <a href="https://github.com/danielrosehill/Claude-Code-Linux-Desktop-Slash-Commands" target="_blank">GitHub Repository</a></p>
+        </div>
+    </footer>
+    <script src="script.js"></script>
+</body>
+</html>

commands/ai-tools/audit-local-ai-packages.md ADDED Viewed

	@@ -0,0 +1,97 @@

+---
+description: Evaluate local AI inference packages and suggest additions
+tags: [ai, ml, inference, packages, recommendations, project, gitignored]
+---
+You are helping the user evaluate their local AI inference setup and suggest packages to install.
+## Process
+1. **Check currently installed AI/ML packages**
+   **Python packages:**
+   - `pip list | grep -E "torch|tensorflow|transformers|diffusers|onnx"`
+   **System packages:**
+   - `dpkg -l | grep -E "rocm|cuda|python3-"`
+   **Conda environments:**
+   - `conda env list` (if conda is installed)
+   **Standalone tools:**
+   - Check for: Ollama, ComfyUI, LocalAI, text-generation-webui
+   - Check `~/programs/ai-ml/`
+2. **Assess hardware configuration**
+   - GPU: `rocm-smi` or `nvidia-smi`
+   - RAM: `free -h`
+   - Storage: `df -h`
+   - CPU capabilities: `lscpu | grep -E "Model name|Thread|Core"`
+3. **Categorize AI inference needs**
+   **LLM Inference:**
+   - Ollama (already covered)
+   - llama.cpp
+   - vllm
+   - text-generation-webui (oobabooga)
+   - LocalAI
+   **Image Generation:**
+   - ComfyUI (already covered)
+   - AUTOMATIC1111/stable-diffusion-webui
+   - InvokeAI
+   - Fooocus
+   **Audio/Speech:**
+   - Whisper (speech-to-text)
+   - Coqui TTS
+   - Bark
+   - MusicGen
+   **Video:**
+   - AnimateDiff
+   - Video generation models
+   **Code:**
+   - Continue.dev
+   - Tabby (local copilot)
+   - Aider
+   **Vector DB / RAG:**
+   - ChromaDB
+   - Qdrant
+   - FAISS
+   - LangChain
+4. **Check Python ML libraries**
+   - PyTorch (with ROCm/CUDA)
+   - TensorFlow
+   - transformers (Hugging Face)
+   - diffusers
+   - accelerate
+   - bitsandbytes (quantization)
+   - ONNX Runtime
+   - optimum
+5. **Suggest based on gaps**
+   - Identify what's missing for common workflows
+   - Prioritize based on hardware capabilities
+   - Consider ease of use vs. flexibility
+6. **Installation recommendations**
+   - Provide commands for suggested packages
+   - Recommend conda environments for isolation
+   - Suggest Docker containers for complex setups
+## Output
+Provide a report showing:
+- Currently installed AI/ML packages by category
+- Hardware capability summary
+- Recommended packages to install based on:
+  - User's hardware
+  - Current gaps in capabilities
+  - Popular/useful tools
+- Installation commands for each suggestion
+- Notes on hardware requirements

commands/ai-tools/comfyui/setup-comfyui.md ADDED Viewed

	@@ -0,0 +1,75 @@

+---
+description: Set up ComfyUI for AI image generation
+tags: [ai, ml, comfyui, image-generation, setup, project, gitignored]
+---
+You are helping the user set up ComfyUI for AI image generation.
+## Process
+1. **Check if ComfyUI is already installed**
+   - Check in `~/programs/ai-ml/ComfyUI` (Daniel's typical location)
+   - Look for existing installation
+2. **Install prerequisites**
+   - Python 3.10+ (check: `python3 --version`)
+   - Git (check: `git --version`)
+   - For AMD GPU (ROCm):
+     - Ensure ROCm is installed: `rocminfo`
+     - PyTorch with ROCm support needed
+3. **Clone ComfyUI repository**
+   - Navigate to: `cd ~/programs/ai-ml/`
+   - Clone: `git clone https://github.com/comfyanonymous/ComfyUI.git`
+   - Enter directory: `cd ComfyUI`
+4. **Set up Python environment**
+   - Create venv: `python3 -m venv venv`
+   - Activate: `source venv/bin/activate`
+   - Upgrade pip: `pip install --upgrade pip`
+5. **Install dependencies**
+   - For AMD GPU (ROCm):
+     ```bash
+     pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/rocm6.0
+     ```
+   - Install ComfyUI requirements: `pip install -r requirements.txt`
+6. **Download initial models**
+   - Create model directories if needed
+   - Suggest downloading a base model (SD 1.5 or SDXL):
+     - Models go in: `ComfyUI/models/checkpoints/`
+     - VAE in: `ComfyUI/models/vae/`
+     - LoRAs in: `ComfyUI/models/loras/`
+   - Suggest civitai.com or huggingface.co for models
+7. **Test ComfyUI**
+   - Run: `python main.py`
+   - Should start on `http://127.0.0.1:8188`
+   - Check logs for GPU detection
+8. **Create launch script**
+   - Offer to create `~/programs/ai-ml/ComfyUI/run_comfyui.sh`:
+     ```bash
+     #!/bin/bash
+     cd ~/programs/ai-ml/ComfyUI
+     source venv/bin/activate
+     python main.py
+     ```
+   - Make executable: `chmod +x run_comfyui.sh`
+9. **Suggest useful custom nodes**
+   - ComfyUI Manager (for easy node installation)
+   - ControlNet nodes
+   - Ultimate SD Upscale
+   - Efficiency nodes
+## Output
+Provide a summary showing:
+- Installation status
+- GPU detection status
+- Model directory locations
+- How to launch ComfyUI
+- Recommended next steps (model downloads, custom nodes)
+- Troubleshooting tips for AMD GPU

commands/ai-tools/gpu-ai-ml-assessment.md ADDED Viewed

	@@ -0,0 +1,441 @@

+You are assessing GPU driver status and AI/ML workload capabilities.
+## Your Task
+Evaluate the GPU's driver configuration and suitability for AI/ML workloads, including deep learning frameworks, compute capabilities, and performance optimization.
+### 1. Driver Status Assessment
+- **Installed driver**: Type (proprietary/open-source) and version
+- **Driver source**: Distribution package, vendor installer, or compiled
+- **Driver status**: Loaded, functioning, errors
+- **Kernel module**: Module name and status
+- **Driver age**: Release date and recency
+- **Latest driver**: Compare installed vs. available
+- **Driver compatibility**: Kernel version compatibility
+- **Secure boot status**: Impact on driver loading
+### 2. Compute Framework Support
+- **CUDA availability**: CUDA Toolkit installation status
+- **CUDA version**: Installed CUDA version
+- **CUDA compatibility**: GPU compute capability vs. CUDA requirements
+- **ROCm availability**: For AMD GPUs
+- **ROCm version**: Installed ROCm version
+- **OpenCL support**: OpenCL runtime and version
+- **oneAPI**: Intel oneAPI toolkit status
+- **Framework libraries**: cuDNN, cuBLAS, TensorRT, etc.
+### 3. GPU Compute Capabilities
+- **Compute capability**: NVIDIA CUDA compute version (e.g., 8.6, 8.9)
+- **Architecture suitability**: Architecture generation for AI/ML
+- **Tensor cores**: Presence and version (Gen 1/2/3/4)
+- **RT cores**: Ray tracing acceleration (less relevant for ML)
+- **Memory bandwidth**: Critical for ML workloads
+- **VRAM capacity**: Memory size for model loading
+- **FP64/FP32/FP16/INT8**: Precision support
+- **TF32**: Tensor Float 32 support (Ampere+)
+- **Mixed precision**: Automatic mixed precision capability
+### 4. Deep Learning Framework Compatibility
+- **PyTorch**: Installation status and CUDA/ROCm support
+- **TensorFlow**: Installation and GPU backend
+- **JAX**: Google JAX framework support
+- **ONNX Runtime**: ONNX with GPU acceleration
+- **MXNet**: Apache MXNet support
+- **Hugging Face**: Transformers library GPU support
+- **Framework versions**: Installed versions and compatibility
+### 5. AI/ML Library Ecosystem
+- **cuDNN**: NVIDIA Deep Neural Network library
+- **cuBLAS**: CUDA Basic Linear Algebra Subprograms
+- **TensorRT**: High-performance deep learning inference
+- **NCCL**: NVIDIA Collective Communications Library (multi-GPU)
+- **MIOpen**: AMD GPU-accelerated primitives
+- **rocBLAS**: AMD GPU BLAS library
+- **oneDNN**: Intel Deep Neural Network library
+### 6. Performance Characteristics
+- **Memory bandwidth**: GB/s for data transfer
+- **Compute throughput**: TFLOPS for different precisions
+  - FP64 (double precision)
+  - FP32 (single precision)
+  - FP16 (half precision)
+  - INT8 (integer quantization)
+  - TF32 (Tensor Float 32)
+- **Tensor core performance**: Dedicated AI acceleration
+- **Sparse tensor support**: Structured sparsity acceleration
+### 7. Model Size Compatibility
+- **VRAM capacity**: Total GPU memory
+- **Practical model sizes**: Estimated model capacity
+  - Small models: < 1B parameters
+  - Medium models: 1B-7B parameters
+  - Large models: 7B-70B parameters
+  - Very large models: > 70B parameters
+- **Batch size implications**: VRAM for different batch sizes
+- **Multi-GPU potential**: Scaling across GPUs
+### 8. Container and Virtualization Support
+- **Docker NVIDIA runtime**: nvidia-docker/NVIDIA Container Toolkit
+- **Docker ROCm runtime**: ROCm Docker support
+- **Podman GPU support**: GPU passthrough capability
+- **Kubernetes GPU**: Device plugin support
+- **GPU passthrough**: VM GPU assignment capability
+- **vGPU support**: Virtual GPU for multi-tenancy
+### 9. Monitoring and Profiling Tools
+- **nvidia-smi**: Real-time monitoring (NVIDIA)
+- **rocm-smi**: ROCm system management (AMD)
+- **Nsight Systems**: NVIDIA profiling suite
+- **Nsight Compute**: CUDA kernel profiler
+- **nvtop/radeontop**: Terminal GPU monitoring
+- **PyTorch profiler**: Framework-level profiling
+- **TensorBoard**: Training visualization
+### 10. Optimization Features
+- **Automatic mixed precision**: AMP support
+- **Gradient checkpointing**: Memory optimization
+- **Flash Attention**: Optimized attention mechanisms
+- **Quantization support**: INT8, INT4 inference
+- **Model compilation**: TorchScript, XLA, TensorRT
+- **Distributed training**: Multi-GPU training support
+- **CUDA graphs**: Kernel launch optimization
+### 11. Workload Suitability Assessment
+- **Training capability**: Suitable for training workloads
+- **Inference capability**: Suitable for inference
+- **Model type suitability**:
+  - Computer vision (CNNs)
+  - Natural language processing (Transformers)
+  - Generative AI (Diffusion models, LLMs)
+  - Reinforcement learning
+- **Performance tier**: Consumer, Professional, Data Center
+### 12. Bottleneck and Limitation Analysis
+- **Memory bottlenecks**: VRAM limitations for large models
+- **Compute bottlenecks**: GPU power for training speed
+- **PCIe bandwidth**: Data transfer limitations
+- **Driver limitations**: Missing features or bugs
+- **Power throttling**: Thermal or power constraints
+- **Multi-GPU scaling**: Efficiency of multi-GPU setup
+## Commands to Use
+**GPU and driver detection:**
+- `nvidia-smi` (NVIDIA)
+- `rocm-smi` (AMD)
+- `lspci | grep -i vga`
+- `lspci -v | grep -A 20 VGA`
+**NVIDIA driver details:**
+- `nvidia-smi -q`
+- `cat /proc/driver/nvidia/version`
+- `modinfo nvidia`
+- `nvidia-smi --query-gpu=driver_version --format=csv,noheader`
+**AMD driver details:**
+- `modinfo amdgpu`
+- `rocminfo`
+- `/opt/rocm/bin/rocm-smi --showdriverversion`
+**CUDA/ROCm installation:**
+- `nvcc --version` (CUDA compiler)
+- `which nvcc`
+- `ls /usr/local/cuda*/`
+- `echo $CUDA_HOME`
+- `hipcc --version` (ROCm)
+- `ls /opt/rocm/`
+**Compute capability:**
+- `nvidia-smi --query-gpu=compute_cap --format=csv,noheader`
+- `nvidia-smi -q | grep "Compute Capability"`
+**Libraries check:**
+- `ldconfig -p | grep cudnn`
+- `ldconfig -p | grep cublas`
+- `ldconfig -p | grep tensorrt`
+- `ldconfig -p | grep nccl`
+- `ls /usr/lib/x86_64-linux-gnu/ | grep -i cuda`
+**Python framework check:**
+- `python3 -c "import torch; print(f'PyTorch: {torch.__version__}, CUDA: {torch.cuda.is_available()}, Version: {torch.version.cuda}')"`
+- `python3 -c "import tensorflow as tf; print(f'TensorFlow: {tf.__version__}, GPU: {tf.config.list_physical_devices(\"GPU\")}')"`
+- `python3 -c "import torch; print(f'Tensor Cores: {torch.cuda.get_device_capability()}')"`
+**Container runtime:**
+- `docker run --rm --gpus all nvidia/cuda:11.8.0-base-ubuntu22.04 nvidia-smi`
+- `which nvidia-container-cli`
+- `nvidia-container-cli info`
+**OpenCL:**
+- `clinfo`
+- `clinfo | grep "Device Name"`
+**System libraries:**
+- `dpkg -l | grep -i cuda`
+- `dpkg -l | grep -i nvidia`
+- `dpkg -l | grep -i rocm`
+**Performance info:**
+- `nvidia-smi --query-gpu=name,memory.total,memory.free,driver_version,compute_cap --format=csv`
+- `nvidia-smi dmon -s pucvmet` (dynamic monitoring)
+## Output Format
+### Executive Summary
+```
+GPU: [model]
+Driver: [proprietary/open] v[version] ([status])
+Compute: [CUDA/ROCm] v[version] (Compute [capability])
+AI/ML Readiness: [Ready/Partial/Not Ready]
+Best For: [Training/Inference/Both]
+Recommended Frameworks: [PyTorch, TensorFlow, etc.]
+```
+### Detailed AI/ML Assessment
+**Driver Status:**
+- Type: [Proprietary/Open Source]
+- Version: [version number]
+- Release Date: [date]
+- Status: [Loaded/Error]
+- Kernel Module: [module] ([loaded/not loaded])
+- Latest Available: [version]
+- Update Recommended: [Yes/No]
+- Secure Boot: [Compatible/Issue]
+**Compute Framework Availability:**
+- CUDA Toolkit: [Installed/Not Installed] - v[version]
+- CUDA Driver API: v[version]
+- ROCm: [Installed/Not Installed] - v[version]
+- OpenCL: [Available/Not Available] - v[version]
+- Compute Capability: [X.X] ([architecture name])
+**GPU Compute Specifications:**
+- Architecture: [Turing/Ampere/Ada/RDNA3/Xe]
+- Tensor Cores: [Yes/No] - [Generation]
+- CUDA Cores / SPs: [count]
+- VRAM: [GB] [memory type]
+- Memory Bandwidth: [GB/s]
+- Precision Support:
+  - FP64: [TFLOPS]
+  - FP32: [TFLOPS]
+  - FP16: [TFLOPS]
+  - INT8: [TOPS]
+  - TF32: [Yes/No]
+**AI/ML Libraries:**
+- cuDNN: [version] ([installed/missing])
+- cuBLAS: [version] ([installed/missing])
+- TensorRT: [version] ([installed/missing])
+- NCCL: [version] ([installed/missing])
+- MIOpen: [version] (AMD only)
+- rocBLAS: [version] (AMD only)
+**Deep Learning Framework Support:**
+- PyTorch: [version]
+  - CUDA Enabled: [Yes/No]
+  - CUDA Version: [version]
+  - cuDNN Version: [version]
+- TensorFlow: [version]
+  - GPU Support: [Yes/No]
+  - CUDA Version: [version]
+- JAX: [installed/not installed]
+- ONNX Runtime: [GPU backend available]
+**Container Support:**
+- NVIDIA Container Toolkit: [installed/not installed]
+- Docker GPU Access: [working/not working]
+- Podman GPU Support: [available]
+**Model Capacity Estimates:**
+- Small Models (< 1B params): [batch size X]
+- Medium Models (1B-7B params): [batch size X]
+- Large Models (7B-13B params): [batch size X]
+- Very Large Models (13B-70B params): [requires multi-GPU or not possible]
+Example workload estimates based on [GB] VRAM:
+- LLaMA 7B: [inference only/training possible]
+- Stable Diffusion: [batch size X]
+- BERT Base: [batch size X]
+- GPT-2: [batch size X]
+**Workload Suitability:**
+- Training:
+  - Small models: [Excellent/Good/Fair/Poor]
+  - Medium models: [rating]
+  - Large models: [rating]
+- Inference:
+  - Real-time: [Excellent/Good/Fair/Poor]
+  - Batch: [rating]
+  - Low-latency: [rating]
+**Use Case Recommendations:**
+- Computer Vision (CNNs): [Excellent/Good/Fair/Poor]
+- NLP (Transformers): [rating]
+- Generative AI (LLMs): [rating]
+- Diffusion Models: [rating]
+- Reinforcement Learning: [rating]
+**Performance Tier:**
+- Category: [Consumer/Professional/Data Center]
+- Training Performance: [rating]
+- Inference Performance: [rating]
+- Multi-GPU Scaling: [available/not available]
+**Optimization Features Available:**
+- Automatic Mixed Precision: [Yes/No]
+- Tensor Core Utilization: [Yes/No]
+- TensorRT Optimization: [Available]
+- Flash Attention: [Supported]
+- INT8 Quantization: [Supported]
+- Multi-GPU Training: [Possible with [count] GPUs]
+**Limitations and Bottlenecks:**
+- VRAM Constraint: [assessment]
+- Memory Bandwidth: [adequate/limited]
+- Compute Throughput: [assessment]
+- PCIe Bottleneck: [yes/no]
+- Driver Limitations: [any known issues]
+- Power/Thermal: [throttling concerns]
+**Recommendations:**
+1. [Driver update/optimization suggestions]
+2. [Framework installation recommendations]
+3. [Workload optimization suggestions]
+4. [Hardware upgrade path if applicable]
+5. [Container/virtualization setup if beneficial]
+### AI/ML Readiness Scorecard
+```
+Driver Setup:        [✓/✗/⚠] [details]
+CUDA/ROCm Install:   [✓/✗/⚠] [details]
+Framework Support:   [✓/✗/⚠] [details]
+Library Ecosystem:   [✓/✗/⚠] [details]
+Container Runtime:   [✓/✗/⚠] [details]
+VRAM Capacity:       [✓/✗/⚠] [details]
+Compute Performance: [✓/✗/⚠] [details]
+Overall Readiness: [Ready/Needs Setup/Limited/Not Suitable]
+```
+### AI-Readable JSON
+```json
+{
+  "driver": {
+    "type": "proprietary|open_source",
+    "version": "",
+    "status": "loaded|error",
+    "latest_available": "",
+    "update_recommended": false
+  },
+  "compute_platform": {
+    "cuda": {
+      "installed": false,
+      "version": "",
+      "compute_capability": ""
+    },
+    "rocm": {
+      "installed": false,
+      "version": ""
+    },
+    "opencl": {
+      "available": false,
+      "version": ""
+    }
+  },
+  "gpu_specs": {
+    "architecture": "",
+    "tensor_cores": false,
+    "vram_gb": 0,
+    "memory_bandwidth_gbs": 0,
+    "fp32_tflops": 0,
+    "fp16_tflops": 0,
+    "int8_tops": 0,
+    "tf32_support": false
+  },
+  "libraries": {
+    "cudnn": "",
+    "cublas": "",
+    "tensorrt": "",
+    "nccl": ""
+  },
+  "frameworks": {
+    "pytorch": {
+      "installed": false,
+      "version": "",
+      "cuda_available": false
+    },
+    "tensorflow": {
+      "installed": false,
+      "version": "",
+      "gpu_available": false
+    }
+  },
+  "container_support": {
+    "nvidia_container_toolkit": false,
+    "docker_gpu_working": false
+  },
+  "workload_suitability": {
+    "training": {
+      "small_models": "excellent|good|fair|poor",
+      "medium_models": "",
+      "large_models": ""
+    },
+    "inference": {
+      "real_time": "",
+      "batch": ""
+    }
+  },
+  "model_capacity": {
+    "vram_gb": 0,
+    "small_model_batch_size": 0,
+    "llama_7b_possible": false,
+    "stable_diffusion_batch": 0
+  },
+  "optimization_features": {
+    "amp_support": false,
+    "tensor_core_utilization": false,
+    "tensorrt_available": false,
+    "int8_quantization": false
+  },
+  "bottlenecks": {
+    "vram_limited": false,
+    "compute_limited": false,
+    "pcie_bottleneck": false
+  },
+  "ai_ml_readiness": "ready|needs_setup|limited|not_suitable"
+}
+```
+## Execution Guidelines
+1. **Identify GPU vendor first**: NVIDIA, AMD, or Intel
+2. **Check driver installation**: Verify driver is loaded and working
+3. **Assess compute platform**: CUDA for NVIDIA, ROCm for AMD
+4. **Query compute capability**: Critical for framework compatibility
+5. **Check library installation**: cuDNN, TensorRT, etc.
+6. **Test framework access**: Try importing PyTorch/TensorFlow with GPU
+7. **Evaluate VRAM capacity**: Estimate model sizes
+8. **Check container support**: Important for ML workflows
+9. **Identify bottlenecks**: VRAM, compute, or driver issues
+10. **Provide actionable recommendations**: Setup steps or optimizations
+## Important Notes
+- NVIDIA GPUs have the most mature AI/ML ecosystem
+- CUDA compute capability determines supported features
+- cuDNN is critical for deep learning performance
+- VRAM is often the primary bottleneck for large models
+- Container runtimes simplify framework management
+- AMD ROCm support is improving but less mature than CUDA
+- Intel GPUs are emerging in AI/ML space
+- Tensor cores provide significant speedup for mixed precision
+- Driver version must match CUDA toolkit requirements
+- Some features require specific GPU generations
+- Multi-GPU setups require additional configuration
+- Consumer GPUs can be effective for smaller workloads
+- Professional/datacenter GPUs offer better reliability and support
+Be thorough and practical - provide a clear assessment of AI/ML readiness and actionable next steps.

commands/ai-tools/ollama/prune-ollama.md ADDED Viewed

	@@ -0,0 +1,14 @@

+Review the ollama models that are installed on this computer.
+Your task is to prune those that I do not need to retain (but before doing so, confirm).
+Pruning logic:
+consider for pruning:
+- Models that serve almost the same purpose and for which there is no compelling reason to keep both. Ask which I'd like to keep or suggest for deletion the slightly inferior of the two.
+- Models that are deprecated
+For example:
+- If you were to find llama 3. 1 8B and llama 3.2 8B, you would reasonably suggest that I consider pruning 3.1 as it's an older model and both are quantized.

commands/ai-tools/ollama/setup-ollama.md ADDED Viewed

	@@ -0,0 +1,57 @@

+---
+description: Set up Ollama on the machine for local LLM inference
+tags: [ai, ml, ollama, llm, setup, project, gitignored]
+---
+You are helping the user set up Ollama for local LLM inference.
+## Process
+1. **Check if Ollama is already installed**
+   - Run: `ollama --version`
+   - Check if service is running: `systemctl status ollama` or `sudo systemctl status ollama`
+2. **Install Ollama if needed**
+   - Download and install: `curl -fsSL https://ollama.com/install.sh | sh`
+   - Or manual install from https://ollama.com/download
+   - Verify installation: `ollama --version`
+3. **Start Ollama service**
+   - Start service: `systemctl start ollama` or `sudo systemctl start ollama`
+   - Enable on boot: `systemctl enable ollama` or `sudo systemctl enable ollama`
+   - Check status: `systemctl status ollama`
+4. **Verify GPU support (for AMD on Daniel's system)**
+   - Check if ROCm is detected: `rocm-smi` or `rocminfo`
+   - Ollama should auto-detect AMD GPU
+   - Check Ollama logs for GPU recognition: `journalctl -u ollama -n 50`
+5. **Configure Ollama**
+   - Check default model storage: `~/.ollama/models`
+   - Environment variables (if needed):
+     - `OLLAMA_HOST` - change port/binding
+     - `OLLAMA_MODELS` - custom model directory
+     - `OLLAMA_NUM_PARALLEL` - parallel requests
+   - Edit systemd service if needed: `/etc/systemd/system/ollama.service`
+6. **Test Ollama**
+   - Pull a test model: `ollama pull llama2` (or smaller: `ollama pull tinyllama`)
+   - Run a test: `ollama run tinyllama "Hello, how are you?"`
+   - Verify GPU usage during inference
+7. **Suggest initial models**
+   - Based on Daniel's hardware (AMD GPU), suggest:
+     - General: llama3.2, qwen2.5
+     - Code: codellama, deepseek-coder
+     - Fast: tinyllama, phi
+     - Vision: llava, bakllava
+## Output
+Provide a summary showing:
+- Ollama installation status and version
+- Service status
+- GPU detection status
+- Default configuration
+- Recommended models to pull
+- Next steps for usage

commands/ai-tools/ollama/suggest-ollama-models.md ADDED Viewed

	@@ -0,0 +1,78 @@

+---
+description: Review installed Ollama models and suggest others based on hardware
+tags: [ai, ml, ollama, models, recommendations, project, gitignored]
+---
+You are helping the user review their Ollama models and suggest new ones based on their hardware.
+## Process
+1. **Check currently installed models**
+   - Run: `ollama list`
+   - Show model sizes and last modified dates
+   - Calculate total disk usage
+2. **Assess hardware capabilities**
+   - Check GPU VRAM: `rocm-smi` (for AMD) or `nvidia-smi` (for NVIDIA)
+   - Check system RAM: `free -h`
+   - Determine recommended model sizes:
+     - < 8GB VRAM: 7B models and smaller
+     - 8-16GB VRAM: up to 13B models
+     - 16-24GB VRAM: up to 34B models
+     - 24GB+ VRAM: 70B+ models possible
+3. **Identify user's needs**
+   - Ask about use cases:
+     - General chat
+     - Code generation
+     - Data analysis
+     - Creative writing
+     - Vision/multimodal
+     - Specialized domains
+4. **Suggest models by category**
+   **General Purpose:**
+   - llama3.2 (3B, 8B)
+   - qwen2.5 (7B, 14B, 32B)
+   - mistral (7B)
+   - gemma2 (9B, 27B)
+   **Code:**
+   - codellama (7B, 13B, 34B)
+   - deepseek-coder (6.7B, 33B)
+   - starcoder2 (7B, 15B)
+   **Fast/Small:**
+   - tinyllama (1.1B)
+   - phi3 (3.8B)
+   **Multimodal:**
+   - llava (7B, 13B, 34B)
+   - bakllava (7B)
+   **Specialized:**
+   - meditron (medical)
+   - sqlcoder (SQL generation)
+   - wizardmath (mathematics)
+5. **Consider quantization levels**
+   - Explain different quants (Q4, Q5, Q8, etc.)
+   - Suggest appropriate quant for their VRAM
+6. **Cleanup suggestions**
+   - Identify duplicate models
+   - Suggest removing unused models: `ollama rm <model>`
+   - Free up space for new models
+## Output
+Provide a report showing:
+- Currently installed models and total size
+- Hardware capacity summary
+- Recommended models based on:
+  - Available VRAM
+  - User's use cases
+  - Current gaps in model coverage
+- Commands to install suggested models
+- Models that could be removed to save space

commands/ai-tools/setup-speech-to-text.md ADDED Viewed

	@@ -0,0 +1,112 @@

+---
+description: Check installed STT apps and suggest installations including local Whisper
+tags: [ai, stt, whisper, speech-recognition, audio, project, gitignored]
+---
+You are helping the user set up speech-to-text applications including local Whisper.
+## Process
+1. **Check currently installed STT apps**
+   - System packages: `dpkg -l | grep -E "whisper|speech|voice"`
+   - Python packages: `pip list | grep -E "whisper|speech|vosk"`
+   - Check `~/programs/ai-ml/` for installed apps
+2. **Suggest STT installation candidates**
+   **Whisper (OpenAI) - Recommended:**
+   - Best quality, local inference
+   - Multiple model sizes available
+   - Multilingual support
+   **Other options:**
+   - Vosk - Lightweight, offline
+   - Coqui STT - Mozilla's solution
+   - SpeechNote - Simple GUI
+   - Subtitle Edit - Video subtitling
+   - Subtld - Automatic subtitles
+3. **Install Whisper (local)**
+   **Method 1: Using pip (simple)**
+   ```bash
+   pip install openai-whisper
+   ```
+   **Method 2: Using conda (recommended)**
+   ```bash
+   conda create -n whisper python=3.11 -y
+   conda activate whisper
+   pip install openai-whisper
+   ```
+   **Install dependencies:**
+   ```bash
+   # For audio processing
+   sudo apt install ffmpeg
+   pip install setuptools-rust
+   ```
+4. **Install faster-whisper (optimized)**
+   ```bash
+   pip install faster-whisper
+   ```
+   - Uses CTranslate2 for faster inference
+   - Lower VRAM usage
+5. **Install WhisperX (advanced)**
+   ```bash
+   pip install whisperx
+   ```
+   - Includes alignment and diarization
+   - Better timestamps
+6. **Download Whisper models**
+   - Models are downloaded automatically on first use
+   - Sizes: tiny, base, small, medium, large
+   - Suggest based on VRAM:
+     - < 4GB: tiny or base
+     - 4-8GB: small or medium
+     - 8GB+: large
+7. **Test installation**
+   ```bash
+   whisper audio.mp3 --model base --language en
+   ```
+8. **Install GUI options**
+   **Whisper Desktop:**
+   - Check if available as AppImage or Flatpak
+   **Subtitle Edit:**
+   ```bash
+   sudo apt install subtitleeditor
+   ```
+   **Custom GUI:**
+   - Suggest installing gradio-based Whisper UIs
+9. **Create helper script**
+   - Offer to create `~/scripts/transcribe.sh`:
+     ```bash
+     #!/bin/bash
+     whisper "$1" --model medium --language en --output_format txt
+     ```
+10. **Suggest workflows**
+   - Real-time transcription
+   - Batch processing
+   - Video subtitling
+   - Meeting transcription
+## Output
+Provide a summary showing:
+- Currently installed STT applications
+- Whisper installation status and model sizes
+- GPU acceleration status
+- Suggested models based on hardware
+- Example commands for transcription
+- GUI options available
+- Helper scripts created

commands/backup/identify-backup-targets.md ADDED Viewed

	@@ -0,0 +1,109 @@

+---
+description: Identify filesystem parts to backup and suggest inclusion patterns
+tags: [backup, filesystem, strategy, rclone, project, gitignored]
+---
+You are helping the user identify which parts of their filesystem should be backed up and create appropriate inclusion patterns.
+## Process
+1. **Analyze filesystem structure**
+   - Home directory size: `du -sh ~/*` or `du -h --max-depth=1 ~ | sort -h`
+   - System directories to consider
+   - External drives/mounts
+2. **Categorize data by importance**
+   **Critical (must backup):**
+   - Documents: `~/Documents`
+   - Development work: `~/repos`
+   - Configuration files: `~/.config`, `~/.ssh`, `~/.gnupg`
+   - Scripts: `~/scripts`, `~/.local/bin`
+   - AI documentation: `~/ai-docs`
+   **Important (should backup):**
+   - Pictures/Photos
+   - Videos (personal)
+   - Music (if not streaming)
+   - Downloads (selective)
+   - Email (if local)
+   **Optional (consider backing up):**
+   - Application data: `~/.local/share`
+   - Browser data (bookmarks, passwords)
+   - Game saves
+   **Exclude (don't backup):**
+   - Caches: `~/.cache`
+   - Temporary files: `/tmp`, `~/.tmp`
+   - Virtual machines/disk images
+   - Node modules: `node_modules/`
+   - Python venvs: `venv/`, `.venv/`
+   - Build artifacts: `target/`, `build/`, `dist/`
+   - Large media files (if cloud-synced elsewhere)
+3. **Identify special considerations**
+   - Check for large directories: `du -h --max-depth=2 ~ | sort -h | tail -20`
+   - Look for media libraries
+   - Identify development projects with dependencies
+   - Find version-controlled repos (can skip .git if remote exists)
+4. **Create inclusion/exclusion patterns**
+   **For rclone:**
+   ```
+   # Include patterns
+   + /Documents/**
+   + /repos/**
+   + /.config/**
+   + /.ssh/**
+   + /.gnupg/**
+   + /scripts/**
+   + /.local/bin/**
+   + /ai-docs/**
+   + /Pictures/**
+   # Exclude patterns
+   - /.cache/**
+   - /.local/share/Trash/**
+   - /**/node_modules/**
+   - /**/.venv/**
+   - /**/venv/**
+   - /**/__pycache__/**
+   - /**/.git/**
+   - /.thumbnails/**
+   ```
+   **For rsync:**
+   ```bash
+   --include='/Documents/***'
+   --include='/repos/***'
+   --exclude='**/.cache/'
+   --exclude='**/node_modules/'
+   --exclude='**/.venv/'
+   ```
+5. **Calculate backup size**
+   - Estimate total backup size based on included directories
+   - Consider compression potential
+   - Plan for growth
+6. **Suggest backup frequency**
+   - Critical data: Daily or real-time sync
+   - Important data: Weekly
+   - Optional data: Monthly
+   - System configs: After changes
+7. **Create backup configuration file**
+   - Offer to create `~/scripts/backup-config.txt` with patterns
+   - Create `~/scripts/backup-estimate.sh` to calculate size
+## Output
+Provide a report showing:
+- Categorized list of directories to backup
+- Size estimates for each category
+- Recommended inclusion/exclusion patterns (rclone and rsync format)
+- Total estimated backup size
+- Suggested backup frequency for each category
+- Configuration file content

commands/bluetooth/reset-bluetooth.md ADDED Viewed

	@@ -0,0 +1,330 @@

+# Reset Bluetooth
+You are helping the user completely reset the Bluetooth subsystem to fix persistent issues.
+## Task
+**WARNING:** This will remove all paired Bluetooth devices and require re-pairing.
+1. **Ask user to confirm:**
+   - This will unpair all Bluetooth devices
+   - Devices will need to be paired again
+   - Bluetooth service will be restarted
+2. **Stop Bluetooth service:**
+   ```bash
+   # Stop Bluetooth
+   sudo systemctl stop bluetooth
+   # Verify stopped
+   systemctl is-active bluetooth
+   ```
+3. **Kill any remaining Bluetooth processes:**
+   ```bash
+   # Kill bluetoothd
+   sudo killall bluetoothd 2>/dev/null
+   # Kill bluetooth-related processes
+   ps aux | grep bluetooth | grep -v grep
+   sudo killall -9 bluez-alsa bluez-obexd 2>/dev/null
+   ```
+4. **Remove Bluetooth pairing cache:**
+   ```bash
+   # Remove paired devices database
+   sudo rm -rf /var/lib/bluetooth/*
+   # Show what was removed
+   echo "Removed all paired device data from /var/lib/bluetooth/"
+   ```
+5. **Clear user Bluetooth cache:**
+   ```bash
+   # Remove user Bluetooth cache
+   rm -rf ~/.cache/bluetooth 2>/dev/null
+   rm -rf ~/.local/share/bluetooth 2>/dev/null
+   echo "Cleared user Bluetooth cache"
+   ```
+6. **Reset Bluetooth modules:**
+   ```bash
+   # Remove Bluetooth kernel modules
+   sudo modprobe -r bnep
+   sudo modprobe -r bluetooth
+   sudo modprobe -r btusb
+   sudo modprobe -r btintel  # Intel Bluetooth
+   sudo modprobe -r btrtl    # Realtek Bluetooth
+   echo "Bluetooth modules unloaded"
+   sleep 2
+   ```
+7. **Reload Bluetooth modules:**
+   ```bash
+   # Reload modules
+   sudo modprobe bluetooth
+   sudo modprobe btusb
+   sudo modprobe bnep
+   # Load vendor-specific modules if needed
+   sudo modprobe btintel 2>/dev/null
+   sudo modprobe btrtl 2>/dev/null
+   echo "Bluetooth modules reloaded"
+   ```
+8. **Reset HCI interface:**
+   ```bash
+   # Bring down Bluetooth controller
+   sudo hciconfig hci0 down 2>/dev/null
+   sleep 1
+   # Bring it back up
+   sudo hciconfig hci0 up 2>/dev/null
+   # Reset the controller
+   sudo hciconfig hci0 reset 2>/dev/null
+   echo "HCI interface reset"
+   ```
+9. **Unblock Bluetooth:**
+   ```bash
+   # Unblock Bluetooth (soft and hard)
+   sudo rfkill unblock bluetooth
+   # Verify not blocked
+   rfkill list bluetooth
+   ```
+10. **Start Bluetooth service:**
+    ```bash
+    # Start and enable Bluetooth
+    sudo systemctl start bluetooth
+    sudo systemctl enable bluetooth
+    # Wait for service to fully start
+    sleep 3
+    # Check status
+    systemctl status bluetooth --no-pager
+    ```
+11. **Power on Bluetooth controller:**
+    ```bash
+    # Turn on Bluetooth
+    bluetoothctl power on
+    # Set as discoverable (optional)
+    bluetoothctl discoverable on
+    # Set pairable
+    bluetoothctl pairable on
+    # Show controller info
+    bluetoothctl show
+    ```
+12. **Verify Bluetooth is working:**
+    ```bash
+    # Check service
+    echo "Service status: $(systemctl is-active bluetooth)"
+    # Check controller
+    echo "Controller powered: $(bluetoothctl show | grep Powered)"
+    # Check for adapters
+    hciconfig -a
+    # Start scanning to test
+    echo "Starting scan for 10 seconds..."
+    timeout 10 bluetoothctl scan on
+    bluetoothctl devices
+    ```
+13. **Create reset report:**
+    ```bash
+    cat > /tmp/bluetooth-reset-report.txt << EOF
+    Bluetooth Reset Report
+    ======================
+    Date: $(date)
+    === Service Status ===
+    $(systemctl status bluetooth --no-pager)
+    === Controller Info ===
+    $(bluetoothctl show)
+    === Hardware Info ===
+    $(hciconfig -a)
+    === RF Kill Status ===
+    $(rfkill list bluetooth)
+    === Loaded Modules ===
+    $(lsmod | grep -E "bluetooth|bnep|btusb")
+    === Kernel Messages (last 20) ===
+    $(dmesg | grep -i bluetooth | tail -20)
+    Next Steps:
+    1. Your Bluetooth has been reset
+    2. All previous pairings have been removed
+    3. Put your device in pairing mode
+    4. Use: bluetoothctl scan on
+    5. Use: bluetoothctl pair <DEVICE_MAC>
+    6. Use: bluetoothctl connect <DEVICE_MAC>
+    EOF
+    cat /tmp/bluetooth-reset-report.txt
+    ```
+## USB Bluetooth Adapter Reset
+If using USB Bluetooth adapter:
+```bash
+# Find USB Bluetooth device
+usb_bt=$(lsusb | grep -i bluetooth | head -1)
+echo "Found: $usb_bt"
+# Get bus and device numbers
+bus=$(echo $usb_bt | awk '{print $2}')
+dev=$(echo $usb_bt | awk '{print $4}' | tr -d ':')
+# Reset USB device
+echo "Resetting USB device: Bus $bus Device $dev"
+sudo usb_modeswitch -v 0x$(lsusb | grep -i bluetooth | awk '{print $6}' | cut -d: -f1) \
+                     -p 0x$(lsusb | grep -i bluetooth | awk '{print $6}' | cut -d: -f2) \
+                     --reset-usb 2>/dev/null
+# Alternative: unbind and rebind
+device_path="/sys/bus/usb/devices/$bus-*"
+echo "Unbinding and rebinding USB device"
+echo "$bus-*" | sudo tee /sys/bus/usb/drivers/usb/unbind 2>/dev/null
+sleep 2
+echo "$bus-*" | sudo tee /sys/bus/usb/drivers/usb/bind 2>/dev/null
+```
+## Firmware Reload
+If firmware issues persist:
+```bash
+# Check firmware files
+ls -l /lib/firmware/ | grep -i bluetooth
+# Reload firmware (device-specific)
+# For Intel Bluetooth:
+sudo rmmod btintel
+sudo modprobe btintel
+# For Realtek:
+sudo rmmod btrtl
+sudo modprobe btrtl
+# Check if firmware loaded
+dmesg | grep -i "bluetooth.*firmware" | tail -5
+```
+## Complete System Reset
+Nuclear option if nothing else works:
+```bash
+# Stop everything
+sudo systemctl stop bluetooth
+sudo killall -9 bluetoothd
+# Remove all data
+sudo rm -rf /var/lib/bluetooth/*
+rm -rf ~/.cache/bluetooth
+rm -rf ~/.local/share/bluetooth
+# Remove and reload all modules
+sudo modprobe -r bnep bluetooth btusb btintel btrtl
+sleep 3
+sudo modprobe bluetooth btusb bnep
+# Remove config (will regenerate)
+sudo mv /etc/bluetooth/main.conf /etc/bluetooth/main.conf.backup
+# Reboot system
+echo "A system reboot is recommended for complete reset"
+# sudo reboot
+```
+## Post-Reset Pairing
+Guide user through pairing:
+```bash
+cat << 'EOF'
+To pair a device after reset:
+1. Put device in pairing mode
+2. Start Bluetooth scan:
+   bluetoothctl scan on
+3. Find your device MAC address in the list
+4. Pair the device:
+   bluetoothctl pair XX:XX:XX:XX:XX:XX
+5. Trust the device:
+   bluetoothctl trust XX:XX:XX:XX:XX:XX
+6. Connect:
+   bluetoothctl connect XX:XX:XX:XX:XX:XX
+7. Stop scanning:
+   bluetoothctl scan off
+For audio devices, you may need to restart PipeWire:
+   systemctl --user restart pipewire wireplumber
+EOF
+```
+## Troubleshooting
+**Reset didn't work:**
+```bash
+# Try full reboot
+sudo reboot
+# Or try removing Bluetooth packages and reinstalling
+# sudo apt remove bluez bluetooth
+# sudo apt install bluez bluetooth
+```
+**Service won't start:**
+```bash
+# Check for errors
+journalctl -u bluetooth --since "5 minutes ago" --no-pager
+# Check if masked
+sudo systemctl unmask bluetooth
+# Force restart
+sudo systemctl restart bluetooth
+```
+**No adapters found:**
+```bash
+# Check hardware detection
+lsusb | grep -i bluetooth
+lspci | grep -i bluetooth
+# Check kernel modules
+lsmod | grep bluetooth
+```
+## Notes
+- Backup `/var/lib/bluetooth/` before reset if you want to preserve pairings
+- Some devices may require specific PIN codes during pairing
+- Audio devices may need additional PipeWire/PulseAudio configuration
+- Bluetooth 5.0+ devices are backward compatible
+- LE (Low Energy) devices may require special pairing procedures
+- System reboot recommended after complete reset
+- Check `/var/log/syslog` for detailed Bluetooth errors

commands/bluetooth/troubleshoot-bluetooth.md ADDED Viewed

	@@ -0,0 +1,300 @@

+# Troubleshoot Bluetooth
+You are helping the user diagnose and fix Bluetooth connectivity issues.
+## Task
+1. **Check Bluetooth service status:**
+   ```bash
+   # Service status
+   systemctl status bluetooth
+   # Is it running?
+   systemctl is-active bluetooth
+   # Is it enabled to start on boot?
+   systemctl is-enabled bluetooth
+   ```
+2. **Check Bluetooth hardware:**
+   ```bash
+   # List Bluetooth adapters
+   hciconfig -a
+   # Or using rfkill
+   rfkill list bluetooth
+   # Check if Bluetooth is soft/hard blocked
+   rfkill list
+   # Detailed hardware info
+   lsusb | grep -i bluetooth
+   lspci | grep -i bluetooth
+   ```
+3. **Check Bluetooth controller status:**
+   ```bash
+   # Controller info
+   bluetoothctl show
+   # List controllers
+   bluetoothctl list
+   # Check if powered on
+   bluetoothctl show | grep "Powered:"
+   ```
+4. **Check for firmware issues:**
+   ```bash
+   # Look for firmware errors in journal
+   journalctl -u bluetooth | grep -i firmware
+   # Check dmesg for Bluetooth firmware loading
+   dmesg | grep -i "bluetooth\|firmware" | tail -20
+   # Check kernel modules
+   lsmod | grep bluetooth
+   ```
+5. **Common fixes - Restart Bluetooth:**
+   ```bash
+   # Restart Bluetooth service
+   sudo systemctl restart bluetooth
+   # Reset Bluetooth controller
+   sudo hciconfig hci0 down
+   sudo hciconfig hci0 up
+   # Or use bluetoothctl
+   bluetoothctl power off
+   sleep 2
+   bluetoothctl power on
+   ```
+6. **Unblock Bluetooth if blocked:**
+   ```bash
+   # Check if blocked
+   rfkill list bluetooth
+   # Unblock if soft-blocked
+   sudo rfkill unblock bluetooth
+   # Power on controller
+   bluetoothctl power on
+   ```
+7. **Scan for devices:**
+   ```bash
+   # Start scanning
+   bluetoothctl scan on
+   # Wait 10 seconds
+   sleep 10
+   # List discovered devices
+   bluetoothctl devices
+   # Stop scanning
+   bluetoothctl scan off
+   ```
+8. **Check paired devices:**
+   ```bash
+   # List paired devices
+   bluetoothctl paired-devices
+   # Show info about specific device
+   bluetoothctl info DEVICE_MAC_ADDRESS
+   ```
+9. **Remove and re-pair problematic device:**
+   ```bash
+   # Ask user for device MAC address
+   # Remove device
+   bluetoothctl remove DEVICE_MAC_ADDRESS
+   # Scan again
+   bluetoothctl scan on
+   sleep 10
+   # Pair device
+   bluetoothctl pair DEVICE_MAC_ADDRESS
+   # Trust device
+   bluetoothctl trust DEVICE_MAC_ADDRESS
+   # Connect to device
+   bluetoothctl connect DEVICE_MAC_ADDRESS
+   ```
+10. **Check Bluetooth configuration:**
+    ```bash
+    # Main config file
+    cat /etc/bluetooth/main.conf
+    # Check for problematic settings
+    grep -E "^(Name|Class|DiscoverableTimeout|AutoEnable)" /etc/bluetooth/main.conf
+    ```
+11. **Check for interference:**
+    ```bash
+    # Check WiFi and Bluetooth coexistence
+    iw dev | grep -i channel
+    # Bluetooth operates on 2.4GHz
+    # WiFi on 2.4GHz can interfere
+    echo "Consider switching WiFi to 5GHz if available"
+    ```
+12. **Detailed diagnostics:**
+    ```bash
+    # Bluetooth subsystem logs
+    journalctl -u bluetooth --since "1 hour ago" --no-pager
+    # Kernel Bluetooth messages
+    dmesg | grep -i bluetooth | tail -30
+    # Check for errors
+    journalctl -u bluetooth | grep -iE "error|fail|timeout"
+    ```
+13. **Audio-specific Bluetooth issues:**
+    ```bash
+    # Check PulseAudio/PipeWire Bluetooth modules
+    pactl list | grep -i bluetooth
+    # PipeWire Bluetooth
+    pw-cli ls Device | grep -i bluetooth
+    # Load Bluetooth module (PulseAudio)
+    # pactl load-module module-bluetooth-discover
+    # Restart audio with Bluetooth
+    systemctl --user restart pipewire pipewire-pulse wireplumber
+    ```
+14. **Generate diagnostic report:**
+    ```bash
+    cat > /tmp/bluetooth-diagnostic.txt << EOF
+    Bluetooth Diagnostic Report
+    ===========================
+    Date: $(date)
+    === Service Status ===
+    $(systemctl status bluetooth --no-pager)
+    === Hardware Detection ===
+    $(rfkill list bluetooth)
+    $(hciconfig -a)
+    === Controller Info ===
+    $(bluetoothctl show)
+    === Paired Devices ===
+    $(bluetoothctl paired-devices)
+    === Recent Bluetooth Logs ===
+    $(journalctl -u bluetooth --since "1 hour ago" --no-pager | tail -50)
+    === Kernel Messages ===
+    $(dmesg | grep -i bluetooth | tail -30)
+    === Loaded Modules ===
+    $(lsmod | grep bluetooth)
+    === Configuration ===
+    $(grep -v "^#\|^$" /etc/bluetooth/main.conf)
+    EOF
+    cat /tmp/bluetooth-diagnostic.txt
+    ```
+## Common Issues & Solutions
+**Bluetooth not starting:**
+```bash
+# Check if service masked
+systemctl unmask bluetooth
+sudo systemctl enable --now bluetooth
+```
+**Device pairs but won't connect:**
+```bash
+# Remove and re-pair
+bluetoothctl remove DEVICE_MAC
+bluetoothctl scan on
+# Wait for device to appear
+bluetoothctl pair DEVICE_MAC
+bluetoothctl trust DEVICE_MAC
+bluetoothctl connect DEVICE_MAC
+```
+**Audio stuttering or quality issues:**
+```bash
+# Check Bluetooth audio codec
+pactl list | grep -i "bluetooth\|codec"
+# Try different codec
+# Edit /etc/bluetooth/main.conf
+# [General]
+# Enable=Source,Sink,Media,Socket
+```
+**Bluetooth adapter not found:**
+```bash
+# Reload Bluetooth module
+sudo rmmod btusb
+sudo modprobe btusb
+# Or all Bluetooth modules
+sudo rmmod bnep btusb bluetooth
+sudo modprobe bluetooth
+sudo modprobe btusb
+sudo modprobe bnep
+```
+**Random disconnections:**
+```bash
+# Increase page timeout
+sudo hciconfig hci0 pageto 8192
+# Disable power management for USB Bluetooth
+# Add to /etc/udev/rules.d/50-bluetooth.rules:
+# ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="YOUR_VENDOR", ATTR{power/autosuspend}="-1"
+```
+**LE (Low Energy) devices not working:**
+```bash
+# Enable LE in bluetoothctl
+bluetoothctl
+[bluetooth]# menu scan
+[bluetooth]# transport le
+[bluetooth]# scan on
+```
+## Reset Bluetooth Completely
+If nothing else works:
+```bash
+# Stop Bluetooth
+sudo systemctl stop bluetooth
+# Remove paired devices cache
+sudo rm -rf /var/lib/bluetooth/*
+# Restart Bluetooth
+sudo systemctl start bluetooth
+# Re-pair all devices
+```
+## Notes
+- Most Bluetooth adapters work with btusb kernel module
+- Firmware files typically in `/lib/firmware/`
+- Check if kernel has Bluetooth support: `zgrep BLUETOOTH /proc/config.gz`
+- Some devices require specific pairing codes
+- Audio devices may need PulseAudio/PipeWire Bluetooth modules
+- USB Bluetooth adapters: check with `usb-devices | grep -A 10 Bluetooth`
+- Bluetooth 5.x adapters are backward compatible with older devices
+- Distance and obstacles affect connection quality

commands/configuration/add-bash-alias.md ADDED Viewed

	@@ -0,0 +1,9 @@

+I would like to add a bash alias. I will provide the alias or ask for your suggestions as to an appropriate alias.
+To come up with an appropriate alias - identify one that is unlikely to conflict with other aliases.
+Either way:
+Create the new bash alias(es) in ~/.bash_aliases
+Then you can use sourcebash to reload the bash alias file.

commands/configuration/check-git-config.md ADDED Viewed

	@@ -0,0 +1,103 @@

+---
+description: Check user's basic git config and make any desired edits
+tags: [git, configuration, settings, development, project, gitignored]
+---
+You are helping the user review and configure their git settings.
+## Process
+1. **Display current git configuration**
+   - Global config: `git config --global --list`
+   - Local config (if in repo): `git config --local --list`
+   - Show config file location: `git config --global --list --show-origin`
+2. **Check essential settings**
+   **User identity:**
+   ```bash
+   git config --global user.name
+   git config --global user.email
+   ```
+   - Verify these are set correctly
+   - If not set, ask user for values
+   **Default editor:**
+   ```bash
+   git config --global core.editor
+   ```
+   - Suggest: `nano`, `vim`, `code --wait`, etc.
+   **Default branch name:**
+   ```bash
+   git config --global init.defaultBranch
+   ```
+   - Recommend: `main` or `master`
+3. **Suggest useful configurations**
+   **Color output:**
+   ```bash
+   git config --global color.ui auto
+   ```
+   **Credential helper:**
+   ```bash
+   git config --global credential.helper store
+   # or for cache: git config --global credential.helper 'cache --timeout=3600'
+   ```
+   **Push behavior:**
+   ```bash
+   git config --global push.default simple
+   git config --global push.autoSetupRemote true
+   ```
+   **Pull behavior:**
+   ```bash
+   git config --global pull.rebase false  # merge (default)
+   # or: git config --global pull.rebase true  # rebase
+   # or: git config --global pull.ff only  # fast-forward only
+   ```
+   **Line endings:**
+   ```bash
+   git config --global core.autocrlf input  # Linux/Mac
+   ```
+   **Diff and merge tools:**
+   ```bash
+   git config --global diff.tool meld
+   git config --global merge.tool meld
+   ```
+4. **Aliases (optional but useful)**
+   Ask if user wants common aliases:
+   ```bash
+   git config --global alias.st status
+   git config --global alias.co checkout
+   git config --global alias.br branch
+   git config --global alias.ci commit
+   git config --global alias.unstage 'reset HEAD --'
+   git config --global alias.last 'log -1 HEAD'
+   git config --global alias.lg "log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit"
+   ```
+5. **GPG signing (optional)**
+   ```bash
+   git config --global commit.gpgsign true
+   git config --global user.signingkey <GPG-KEY-ID>
+   ```
+6. **Show updated configuration**
+   - Display all global settings
+   - Highlight changes made
+## Output
+Provide a summary showing:
+- Current git configuration
+- Missing essential settings
+- Recommended configurations
+- Changes made (if any)
+- Next steps or additional suggestions

commands/configuration/check-global-gitignore.md ADDED Viewed

	@@ -0,0 +1,145 @@

+---
+description: Check if user has global gitignore and create one if not
+tags: [git, configuration, gitignore, development, project, gitignored]
+---
+You are helping the user set up a global gitignore file.
+## Process
+1. **Check if global gitignore exists**
+   - Run: `git config --global core.excludesfile`
+   - Check common locations:
+     - `~/.gitignore_global`
+     - `~/.gitignore`
+     - `~/.config/git/ignore`
+2. **If global gitignore doesn't exist, create one**
+   - Choose location: `~/.gitignore_global`
+   - Configure git to use it:
+     ```bash
+     git config --global core.excludesfile ~/.gitignore_global
+     ```
+3. **Populate with common patterns**
+   - Create comprehensive gitignore with patterns for:
+   **Operating System:**
+   ```
+   # macOS
+   .DS_Store
+   .AppleDouble
+   .LSOverride
+   # Linux
+   *~
+   .directory
+   .Trash-*
+   # Windows
+   Thumbs.db
+   Desktop.ini
+   ```
+   **IDEs and Editors:**
+   ```
+   # VS Code
+   .vscode/
+   *.code-workspace
+   # JetBrains
+   .idea/
+   *.iml
+   # Vim
+   *.swp
+   *.swo
+   *~
+   # Emacs
+   *~
+   \#*\#
+   ```
+   **Languages and Frameworks:**
+   ```
+   # Python
+   __pycache__/
+   *.py[cod]
+   *$py.class
+   .venv/
+   venv/
+   ENV/
+   .Python
+   *.egg-info/
+   dist/
+   build/
+   # Node.js
+   node_modules/
+   npm-debug.log
+   yarn-error.log
+   .npm/
+   # Ruby
+   *.gem
+   .bundle/
+   vendor/bundle/
+   # Rust
+   target/
+   Cargo.lock
+   # Go
+   *.exe
+   *.test
+   *.out
+   ```
+   **Build artifacts:**
+   ```
+   *.o
+   *.a
+   *.so
+   *.dylib
+   *.dll
+   *.class
+   *.jar
+   ```
+   **Misc:**
+   ```
+   # Logs
+   *.log
+   logs/
+   # Temporary files
+   *.tmp
+   *.temp
+   .cache/
+   # Environment files
+   .env
+   .env.local
+   # Database files
+   *.sqlite
+   *.db
+   ```
+4. **Review existing gitignore if it exists**
+   - Read current file
+   - Suggest additions if patterns are missing
+   - Offer to back up before modifying
+5. **Test the configuration**
+   - Verify config: `git config --global core.excludesfile`
+   - Show the file: `cat ~/.gitignore_global`
+## Output
+Provide a summary showing:
+- Global gitignore location
+- Whether it was created or already existed
+- List of patterns included
+- Verification of git configuration

commands/configuration/check-path.md ADDED Viewed

	@@ -0,0 +1,209 @@

+# Check and Analyze PATH
+You are helping the user analyze what's on their PATH and suggest additions or improvements.
+## Your tasks:
+1. **Display current PATH:**
+   ```bash
+   echo $PATH | tr ':' '\n'
+   ```
+2. **Check which paths actually exist:**
+   ```bash
+   echo $PATH | tr ':' '\n' | while read p; do
+     if [ -d "$p" ]; then
+       echo "✓ $p"
+     else
+       echo "✗ $p (does not exist)"
+     fi
+   done
+   ```
+3. **Check for duplicate PATH entries:**
+   ```bash
+   echo $PATH | tr ':' '\n' | sort | uniq -d
+   ```
+4. **Identify where PATH is being set:**
+   Check common locations:
+   ```bash
+   grep -n "PATH" ~/.bashrc ~/.bash_profile ~/.profile /etc/environment /etc/profile 2>/dev/null
+   ```
+5. **Check for common development tool paths:**
+   **Programming languages:**
+   - Python user packages: `~/.local/bin`
+   - Rust cargo: `~/.cargo/bin`
+   - Go: `~/go/bin` or `$GOPATH/bin`
+   - Ruby gems: Check with `gem environment`
+   - Node/npm: Check with `npm config get prefix`
+   **Package managers:**
+   - Homebrew: `/home/linuxbrew/.linuxbrew/bin`
+   - SDKMAN: `~/.sdkman/candidates/*/current/bin`
+   - pipx: `~/.local/bin`
+   **Version managers:**
+   - pyenv: `~/.pyenv/bin`
+   - rbenv: `~/.rbenv/bin`
+   - nvm: (check ~/.nvm/)
+   - asdf: `~/.asdf/bin`
+   **System tools:**
+   - User binaries: `~/bin`, `~/.local/bin`
+   - Snap: `/snap/bin`
+   - Flatpak: `/var/lib/flatpak/exports/bin`
+6. **Check what's installed in each PATH directory:**
+   For each directory in PATH:
+   ```bash
+   echo "Contents of $dir:"
+   ls -la "$dir" | head -10
+   ```
+7. **Suggest missing common paths:**
+   Check and suggest if not in PATH:
+   - `~/.local/bin` (Python user packages, pipx)
+   - `~/bin` (User scripts)
+   - `~/.cargo/bin` (Rust packages)
+   - `~/go/bin` (Go packages)
+   - `/snap/bin` (Snap packages)
+   - `~/.npm-global/bin` (npm global packages)
+   For each missing path that has executables, suggest adding it.
+8. **Check for security issues:**
+   - Warn if `.` (current directory) is in PATH
+   - Warn if world-writable directories are in PATH:
+     ```bash
+     echo $PATH | tr ':' '\n' | while read p; do
+       if [ -d "$p" ] && [ -w "$p" ]; then
+         ls -ld "$p"
+       fi
+     done
+     ```
+9. **Check PATH order/precedence:**
+   Explain that earlier paths take precedence.
+   Show which binary would be executed:
+   ```bash
+   which -a python python3 java gcc git node npm
+   ```
+10. **Check for conflicting tools:**
+    ```bash
+    type -a python
+    type -a python3
+    type -a java
+    ```
+11. **Suggest PATH organization:**
+    Recommended order:
+    1. User binaries (`~/bin`, `~/.local/bin`)
+    2. Version managers (pyenv, rbenv, nvm)
+    3. Language-specific paths (cargo, go)
+    4. Homebrew
+    5. System binaries (`/usr/local/bin`, `/usr/bin`, `/bin`)
+12. **Check environment-specific paths:**
+    **Python:**
+    ```bash
+    python3 -m site --user-base
+    # Suggests adding $(python3 -m site --user-base)/bin
+    ```
+    **Node/npm:**
+    ```bash
+    npm config get prefix
+    # Suggests adding <prefix>/bin
+    ```
+    **Go:**
+    ```bash
+    go env GOPATH
+    # Suggests adding $GOPATH/bin
+    ```
+    **Rust:**
+    ```bash
+    echo $CARGO_HOME
+    # Suggests adding ~/.cargo/bin
+    ```
+13. **Generate suggested PATH setup:**
+    Based on findings, create suggested additions for ~/.bashrc:
+    ```bash
+    # User binaries
+    export PATH="$HOME/bin:$PATH"
+    export PATH="$HOME/.local/bin:$PATH"
+    # Python
+    export PATH="$HOME/.local/bin:$PATH"
+    # Rust
+    export PATH="$HOME/.cargo/bin:$PATH"
+    # Go
+    export PATH="$HOME/go/bin:$PATH"
+    # SDKMAN
+    # Added by sdkman-init.sh
+    # pyenv
+    export PYENV_ROOT="$HOME/.pyenv"
+    export PATH="$PYENV_ROOT/bin:$PATH"
+    eval "$(pyenv init --path)"
+    # Homebrew
+    eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
+    ```
+14. **Check for broken symlinks in PATH:**
+    ```bash
+    echo $PATH | tr ':' '\n' | while read dir; do
+      if [ -d "$dir" ]; then
+        find "$dir" -maxdepth 1 -type l ! -exec test -e {} \; -print 2>/dev/null
+      fi
+    done
+    ```
+15. **Provide recommendations:**
+    - Remove non-existent directories from PATH
+    - Add missing common paths that have executables
+    - Fix duplicate entries
+    - Correct PATH order if needed
+    - Remove security issues (`.` in PATH, world-writable dirs)
+    - Consolidate PATH modifications into one file (prefer ~/.bashrc)
+    - Document what each PATH addition is for
+16. **Show how to temporarily modify PATH:**
+    ```bash
+    # Add to front (takes precedence)
+    export PATH="/new/path:$PATH"
+    # Add to end
+    export PATH="$PATH:/new/path"
+    # Remove from PATH
+    export PATH=$(echo $PATH | tr ':' '\n' | grep -v "/path/to/remove" | tr '\n' ':')
+    ```
+17. **Show how to make PATH changes permanent:**
+    ```bash
+    echo 'export PATH="$HOME/bin:$PATH"' >> ~/.bashrc
+    source ~/.bashrc
+    ```
+## Important notes:
+- Changes to PATH only affect current shell unless made permanent
+- Order matters - earlier paths have precedence
+- Don't add current directory (`.`) to PATH
+- Use absolute paths when possible
+- Source ~/.bashrc after changes: `source ~/.bashrc`
+- Some tools (pyenv, conda, nvm) modify PATH dynamically
+- Check for PATH modifications in multiple files

commands/configuration/debug-folder-permissions.md ADDED Viewed

	@@ -0,0 +1,234 @@

+# Debug System Folder Permissions
+You are helping the user debug systemwide folder permissions and ensure they are set appropriately.
+## Your tasks:
+1. **Gather information from user:**
+   Ask:
+   - Are they experiencing specific permission errors?
+   - Which directories or operations are affected?
+   - What user/group should have access?
+2. **Check common system directories:**
+   **Root filesystem:**
+   ```bash
+   ls -ld /
+   # Should be: drwxr-xr-x root root
+   ```
+   **Essential system directories:**
+   ```bash
+   ls -ld /bin /sbin /usr /usr/bin /usr/sbin /lib /lib64
+   # Should be: drwxr-xr-x root root
+   ```
+   **Variable data:**
+   ```bash
+   ls -ld /var /var/log /var/tmp
+   # /var: drwxr-xr-x root root
+   # /var/log: drwxrwxr-x root syslog (or root root)
+   # /var/tmp: drwxrwxrwt root root (sticky bit)
+   ```
+   **Temporary directories:**
+   ```bash
+   ls -ld /tmp
+   # Should be: drwxrwxrwt root root (sticky bit important!)
+   ```
+   **Home directories:**
+   ```bash
+   ls -ld /home /home/$USER
+   # /home: drwxr-xr-x root root
+   # /home/$USER: drwxr-xr-x $USER $USER (or drwx------ for privacy)
+   ```
+3. **Check for permission issues:**
+   **World-writable directories without sticky bit (security risk):**
+   ```bash
+   sudo find / -type d -perm -0002 ! -perm -1000 2>/dev/null
+   ```
+   **Files with SUID bit (potential security issue if unexpected):**
+   ```bash
+   sudo find / -type f -perm -4000 2>/dev/null
+   ```
+   **Files with SGID bit:**
+   ```bash
+   sudo find / -type f -perm -2000 2>/dev/null
+   ```
+4. **Check /etc permissions:**
+   ```bash
+   ls -la /etc | head -20
+   # /etc itself: drwxr-xr-x root root
+   # Most files should be 644 (rw-r--r--)
+   # Some may be 640 or 600 for security
+   ```
+   **Sensitive files:**
+   ```bash
+   ls -l /etc/shadow /etc/gshadow /etc/ssh/sshd_config
+   # /etc/shadow: -rw-r----- root shadow
+   # /etc/ssh/sshd_config: -rw-r--r-- root root
+   ```
+5. **Check user home directory structure:**
+   ```bash
+   ls -la ~/ | grep "^d"
+   ```
+   Common directories and recommended permissions:
+   - `~/.ssh`: 700 (drwx------)
+   - `~/.ssh/id_rsa`: 600 (-rw-------)
+   - `~/.ssh/id_rsa.pub`: 644 (-rw-r--r--)
+   - `~/.ssh/authorized_keys`: 600 (-rw-------)
+   - `~/.gnupg`: 700 (drwx------)
+   - `~/bin`: 755 (drwxr-xr-x)
+   - `~/.local`: 755 (drwxr-xr-x)
+   - `~/.config`: 755 (drwxr-xr-x)
+6. **Check /opt and /usr/local:**
+   ```bash
+   ls -ld /opt /usr/local /usr/local/bin
+   # Typically: drwxr-xr-x root root
+   # But may be group-writable for admin group
+   ```
+7. **Check mount points:**
+   ```bash
+   mount | grep "^/" | awk '{print $3}' | while read mp; do
+     ls -ld "$mp"
+   done
+   ```
+8. **Check ownership of user files:**
+   Find files in home directory not owned by user:
+   ```bash
+   find ~/ -not -user $USER 2>/dev/null
+   ```
+9. **Check group memberships:**
+   ```bash
+   groups
+   id
+   ```
+   Common groups users might need:
+   - `sudo` - for administrative access
+   - `docker` - for Docker access
+   - `video` - for video devices
+   - `audio` - for audio devices
+   - `plugdev` - for removable devices
+   - `dialout` - for serial ports
+10. **Fix common issues:**
+    **Fix sticky bit on /tmp:**
+    ```bash
+    sudo chmod 1777 /tmp
+    ```
+    **Fix ~/.ssh permissions:**
+    ```bash
+    chmod 700 ~/.ssh
+    chmod 600 ~/.ssh/id_rsa
+    chmod 644 ~/.ssh/id_rsa.pub
+    chmod 600 ~/.ssh/authorized_keys
+    chmod 600 ~/.ssh/config
+    ```
+    **Fix ownership of home directory:**
+    ```bash
+    sudo chown -R $USER:$USER ~/
+    ```
+    **Fix common directories:**
+    ```bash
+    chmod 755 ~/.local ~/.config ~/bin
+    ```
+11. **Check for ACL (Access Control Lists):**
+    ```bash
+    getfacl /path/to/directory
+    ```
+    If ACLs are in use (indicated by `+` in ls -l):
+    ```bash
+    ls -la | grep "+"
+    ```
+12. **Check SELinux context (if enabled):**
+    ```bash
+    getenforce
+    ls -Z /path/to/directory
+    ```
+13. **Check for immutable flags:**
+    ```bash
+    lsattr /path/to/file
+    ```
+    If files have `i` flag, they can't be modified even by root:
+    ```bash
+    sudo chattr -i /path/to/file
+    ```
+14. **Specific directory recommendations:**
+    **/var/www (web server):**
+    ```bash
+    sudo chown -R www-data:www-data /var/www
+    sudo find /var/www -type d -exec chmod 755 {} \;
+    sudo find /var/www -type f -exec chmod 644 {} \;
+    ```
+    **/srv (service data):**
+    ```bash
+    sudo chown -R root:root /srv
+    sudo chmod 755 /srv
+    ```
+    **Shared directories:**
+    ```bash
+    sudo chown root:groupname /shared/directory
+    sudo chmod 2775 /shared/directory  # SGID bit for group
+    ```
+15. **Check logs for permission denials:**
+    ```bash
+    sudo journalctl -p err | grep -i "permission denied"
+    dmesg | grep -i "permission denied"
+    sudo grep "permission denied" /var/log/syslog
+    ```
+16. **Report findings:**
+    Summarize:
+    - Incorrect permissions on system directories
+    - Security issues (world-writable without sticky, unexpected SUID)
+    - User home directory issues
+    - Files/directories with wrong ownership
+    - Missing group memberships
+    - ACL or SELinux issues
+17. **Provide recommendations:**
+    - Fix commands for identified issues
+    - Whether to add user to specific groups
+    - Security improvements for sensitive directories
+    - Standard permission schemes for common directories
+    - Whether to use ACLs for complex permission needs
+## Important notes:
+- Always backup or test in safe environment first
+- Changing system permissions incorrectly can break the system
+- Use sudo carefully when fixing permissions
+- Don't recursively chmod/chown system directories without understanding
+- Some non-standard permissions may be intentional
+- Check application documentation for required permissions
+- SELinux/AppArmor may also affect access beyond traditional permissions
+- Sticky bit on /tmp is critical for security
+- SUID/SGID bits on unexpected files are security risks

commands/configuration/list-ssh-connections.md ADDED Viewed

	@@ -0,0 +1,91 @@

+---
+description: Review which SSH connection names/hosts the user has configured
+tags: [ssh, configuration, hosts, network, project, gitignored]
+---
+You are helping the user review their SSH connection configurations.
+## Process
+1. **Check if SSH config exists**
+   - Look for: `~/.ssh/config`
+   - If not found, offer to create one
+2. **Parse SSH config file**
+   - Read `~/.ssh/config`
+   - Extract Host entries
+   - For each host, show:
+     - Host alias
+     - HostName (IP/domain)
+     - User
+     - Port
+     - IdentityFile (SSH key)
+     - Other options
+3. **Display in organized format**
+   - Present as table or list:
+     ```
+     Alias: server1
+     HostName: 192.168.1.100
+     User: admin
+     Port: 22
+     Key: ~/.ssh/id_rsa
+     ---
+     ```
+4. **Check system-wide SSH config**
+   - Also check `/etc/ssh/ssh_config` for global settings
+   - Note any system-wide host configurations
+5. **Test connectivity (optional)**
+   - Ask if user wants to test connections
+   - For each host:
+     ```bash
+     ssh -T user@host
+     # or
+     ssh -o ConnectTimeout=5 user@host "echo Connection successful"
+     ```
+6. **Identify stale connections**
+   - Look for connections to:
+     - IPs that might have changed
+     - Servers that may no longer exist
+     - Old project servers
+7. **Suggest config improvements**
+   - Recommend useful SSH config options:
+     ```
+     Host *
+       ServerAliveInterval 60
+       ServerAliveCountMax 3
+       TCPKeepAlive yes
+       ControlMaster auto
+       ControlPath ~/.ssh/sockets/%r@%h-%p
+       ControlPersist 600
+     ```
+8. **Offer to create new entries**
+   - If user wants to add new SSH hosts
+   - Template:
+     ```
+     Host shortname
+       HostName hostname.com
+       User username
+       Port 22
+       IdentityFile ~/.ssh/id_ed25519
+       ForwardAgent yes
+     ```
+9. **Security check**
+   - Verify file permissions: `chmod 600 ~/.ssh/config`
+   - Look for insecure settings (password auth, etc.)
+## Output
+Provide a summary showing:
+- List of configured SSH hosts
+- Connection details for each
+- Stale/inactive connections (if identified)
+- Connectivity test results (if performed)
+- Suggested improvements
+- New entries added (if any)

commands/configuration/manage-api-keys.md ADDED Viewed

	@@ -0,0 +1,101 @@

+---
+description: Review API keys on PATH and add new ones if requested
+tags: [api, keys, environment, configuration, project, gitignored]
+---
+You are helping the user manage their API keys and environment variables.
+## Process
+1. **Check for API keys in environment**
+   - List environment variables: `env | grep -E "API|KEY|TOKEN"`
+   - Check common locations:
+     - `~/.bashrc`
+     - `~/.zshrc`
+     - `~/.profile`
+     - `~/.env`
+     - Project-specific `.env` files
+2. **Display current API keys (safely)**
+   - Show key names and partial values (mask full keys)
+   - Example: `OPENAI_API_KEY=sk-*********************`
+3. **Common API keys to check for**
+   - OpenAI API
+   - Anthropic API (Claude)
+   - OpenRouter API
+   - Hugging Face token
+   - GitHub token
+   - Google Cloud API
+   - AWS credentials
+   - Azure credentials
+   - Database connection strings
+4. **Add new API keys**
+   - Ask user which API keys they want to add
+   - For each key:
+     - Key name (e.g., `OPENAI_API_KEY`)
+     - Key value (handle securely)
+     - Scope (global, project-specific, etc.)
+5. **Choose storage location**
+   **Option 1: Shell config (global)**
+   - Add to `~/.bashrc` or `~/.zshrc`:
+     ```bash
+     export OPENAI_API_KEY="sk-..."
+     export ANTHROPIC_API_KEY="sk-..."
+     ```
+   - Reload: `source ~/.bashrc`
+   **Option 2: .env file (project-specific)**
+   - Create/update `.env` file
+   - Add to `.gitignore`
+   - Use with dotenv library
+   **Option 3: Secret manager**
+   - Suggest using `pass`, `gnome-keyring`, or similar
+   - More secure for sensitive keys
+6. **Set appropriate permissions**
+   - For files containing keys:
+     ```bash
+     chmod 600 ~/.env
+     chmod 600 ~/.bashrc
+     ```
+7. **Test API keys**
+   - Offer to test each key (if user wants)
+   - Example for OpenAI:
+     ```bash
+     curl https://api.openai.com/v1/models \
+       -H "Authorization: Bearer $OPENAI_API_KEY" \
+       | jq .
+     ```
+8. **Security recommendations**
+   - REFRAIN from providing unsolicited security advice
+   - Only mention if asked:
+     - Don't commit keys to git
+     - Use `.gitignore` for `.env` files
+     - Rotate keys periodically
+     - Use environment-specific keys (dev, prod)
+9. **Create helper script (optional)**
+   - Offer to create script to load environment:
+     ```bash
+     #!/bin/bash
+     # load-env.sh
+     if [ -f .env ]; then
+       export $(cat .env | xargs)
+     fi
+     ```
+## Output
+Provide a summary showing:
+- Currently configured API keys (names only, values masked)
+- New API keys added
+- Storage location for each key
+- Test results (if performed)
+- Next steps for using the keys

commands/configuration/manage-ssh-keys.md ADDED Viewed

	@@ -0,0 +1,91 @@

+---
+description: Review installed SSH key pairs and delete old ones if desired
+tags: [ssh, security, keys, configuration, project, gitignored]
+---
+You are helping the user manage their SSH keys.
+## Process
+1. **List SSH keys**
+   - List keys in `~/.ssh/`: `ls -la ~/.ssh/`
+   - Identify key pairs:
+     - Private keys (no extension, or `.pem`)
+     - Public keys (`.pub`)
+     - Known hosts file
+     - Config file
+2. **Display public keys with details**
+   - For each public key:
+     ```bash
+     for key in ~/.ssh/*.pub; do
+       echo "=== $key ==="
+       ssh-keygen -l -f "$key"
+       echo ""
+     done
+     ```
+   - Shows: key length, fingerprint, comment
+3. **Check if keys are loaded in ssh-agent**
+   - List loaded keys: `ssh-add -l`
+   - If agent not running: `eval "$(ssh-agent -s)"`
+4. **Identify key usage**
+   - Check `~/.ssh/config` for key assignments
+   - Ask user about each key:
+     - Where is it used? (GitHub, servers, etc.)
+     - Is it still needed?
+     - When was it created?
+5. **Check key security**
+   - Verify key types (RSA, ED25519, etc.)
+   - Check key lengths:
+     - RSA: Minimum 2048-bit, prefer 4096-bit
+     - ED25519: 256-bit (modern, recommended)
+   - Suggest upgrading old/weak keys
+6. **Delete old/unused keys**
+   - For each key user wants to remove:
+     ```bash
+     rm ~/.ssh/old_key
+     rm ~/.ssh/old_key.pub
+     ```
+   - Update `~/.ssh/config` if key was referenced
+   - Remove from ssh-agent: `ssh-add -d ~/.ssh/old_key`
+7. **Generate new keys if needed**
+   - Suggest ED25519 for new keys:
+     ```bash
+     ssh-keygen -t ed25519 -C "user@email.com"
+     ```
+   - Or RSA 4096:
+     ```bash
+     ssh-keygen -t rsa -b 4096 -C "user@email.com"
+     ```
+8. **Update permissions**
+   - Ensure correct permissions:
+     ```bash
+     chmod 700 ~/.ssh
+     chmod 600 ~/.ssh/id_*
+     chmod 644 ~/.ssh/id_*.pub
+     chmod 600 ~/.ssh/config
+     ```
+9. **Add keys to ssh-agent**
+   - Add keys: `ssh-add ~/.ssh/id_ed25519`
+   - Persist across reboots (add to `~/.bashrc`):
+     ```bash
+     eval "$(ssh-agent -s)"
+     ssh-add ~/.ssh/id_ed25519
+     ```
+## Output
+Provide a summary showing:
+- List of SSH keys with details (type, length, fingerprint)
+- Keys currently loaded in ssh-agent
+- Keys deleted (if any)
+- New keys generated (if any)
+- Security recommendations
+- Next steps for adding keys to services

commands/configuration/mcp/manage-mcp-servers.md ADDED Viewed

	@@ -0,0 +1,104 @@

+---
+description: Review installed MCP servers and work with user to add new ones
+tags: [mcp, ai, configuration, servers, project, gitignored]
+---
+You are helping the user manage their MCP (Model Context Protocol) servers.
+## Process
+1. **Check MCP configuration**
+   - Look for MCP config: `~/mcp/` or `~/.config/mcp/`
+   - Check Claude Code config: `~/.config/claude/`
+   - Identify MCP server config files
+2. **List currently installed MCP servers**
+   - Parse configuration files
+   - For each server, show:
+     - Server name
+     - Server type/purpose
+     - Status (running/stopped)
+     - Configuration details
+3. **Check running MCP servers**
+   - Look for running processes:
+     ```bash
+     ps aux | grep mcp
+     ```
+   - Check if servers are accessible
+4. **Suggest useful MCP servers**
+   **Common MCP servers:**
+   - Filesystem MCP (file operations)
+   - GitHub MCP (GitHub integration)
+   - Database MCP (PostgreSQL, SQLite, etc.)
+   - Browser MCP (web automation)
+   - Context7 MCP (documentation)
+   - Memory MCP (persistent memory)
+   - Search MCP (web search)
+5. **Install new MCP servers**
+   - For each server user wants:
+     - Check installation method (npm, pip, docker, etc.)
+     - Install dependencies
+     - Configure server
+     - Add to MCP config
+   **Example: Installing filesystem MCP**
+   ```bash
+   npm install -g @anthropic/mcp-server-filesystem
+   ```
+   **Example: Installing custom MCP server**
+   ```bash
+   git clone <repo-url>
+   cd <repo>
+   npm install
+   ```
+6. **Configure MCP servers**
+   - Add server to config file
+   - Example config:
+     ```json
+     {
+       "mcpServers": {
+         "filesystem": {
+           "command": "mcp-server-filesystem",
+           "args": ["/path/to/allowed/directory"]
+         },
+         "github": {
+           "command": "mcp-server-github",
+           "env": {
+             "GITHUB_TOKEN": "your-token-here"
+           }
+         }
+       }
+     }
+     ```
+7. **Test MCP server connectivity**
+   - Start servers
+   - Verify they're accessible by Claude Code
+   - Test basic operations
+8. **Document MCP setup**
+   - Offer to create `~/mcp/README.md` documenting:
+     - Installed servers
+     - Configuration
+     - Usage examples
+     - Troubleshooting
+9. **Suggest workflows**
+   - Recommend MCP server combinations for common tasks
+   - Show example use cases
+## Output
+Provide a summary showing:
+- Currently installed MCP servers
+- Server status and configuration
+- New servers installed (if any)
+- Configuration changes made
+- Usage examples
+- Next steps or recommendations

commands/configuration/validate-bashrc.md ADDED Viewed

	@@ -0,0 +1,99 @@

+# Bashrc Validation
+You are helping the user validate their .bashrc configuration for syntax errors, issues, and best practices.
+## Your tasks:
+1. **Locate bashrc files:**
+   - Check `~/.bashrc`
+   - Check `~/.bash_profile`
+   - Check `~/.profile`
+   - Check `/etc/bash.bashrc` (system-wide)
+   - Note which files exist and their sizes
+2. **Syntax validation:**
+   - Test bashrc syntax: `bash -n ~/.bashrc`
+   - If errors are found, report the line numbers and error messages
+   - Check for common syntax issues:
+     - Unclosed quotes
+     - Unmatched brackets
+     - Missing 'fi', 'done', 'esac' keywords
+3. **Source validation:**
+   - Test if bashrc can be sourced without errors in a subshell:
+     ```bash
+     bash -c 'source ~/.bashrc && echo "Sourcing successful"'
+     ```
+   - Capture any error messages
+4. **Check for common issues:**
+   - Duplicate PATH entries:
+     ```bash
+     bash -c 'source ~/.bashrc; echo $PATH | tr ":" "\n" | sort | uniq -d'
+     ```
+   - Check for sourcing non-existent files:
+     ```bash
+     grep -n "source\|^\." ~/.bashrc | while read line; do
+       # Extract and check if files exist
+     done
+     ```
+   - Look for potentially problematic patterns:
+     - Infinite loops
+     - Commands that might hang (network calls without timeouts)
+     - Unguarded recursive sourcing
+5. **Check initialization order:**
+   - Explain which files are loaded and in what order for:
+     - Login shells
+     - Non-login interactive shells
+     - Non-interactive shells
+   - Check if the proper guards are in place (e.g., checking for interactive shell)
+6. **Performance analysis:**
+   - Time how long bashrc takes to load:
+     ```bash
+     time bash -c 'source ~/.bashrc; exit'
+     ```
+   - If it takes more than 0.5 seconds, identify potential slow sections:
+     - Look for commands that might be slow (network calls, heavy computations)
+     - Check for unnecessary repeated operations
+7. **Check for security issues:**
+   - World-writable bashrc: `ls -la ~/.bashrc`
+   - Suspicious commands (downloads, eval with user input, etc.)
+   - Sourcing files from world-writable directories
+8. **Validate environment manager initialization:**
+   - Check if environment managers are properly initialized:
+     - pyenv: `grep "pyenv init" ~/.bashrc`
+     - conda: `grep "conda initialize" ~/.bashrc`
+     - nvm: `grep "nvm.sh" ~/.bashrc`
+     - rbenv: `grep "rbenv init" ~/.bashrc`
+     - sdkman: `grep "sdkman-init.sh" ~/.bashrc`
+   - Verify they're in the correct order (PATH modifications should come after system PATH is set)
+9. **Check for best practices:**
+   - Interactive shell guard at the top:
+     ```bash
+     [[ $- != *i* ]] && return
+     ```
+   - Proper PATH modification (appending/prepending, not replacing)
+   - Using `command -v` instead of `which`
+   - Proper quoting of variables
+10. **Report findings:**
+    - Summary of validation results (PASS/FAIL)
+    - List of any errors or warnings
+    - Performance metrics
+    - Recommendations:
+      - Fixes for any syntax errors
+      - Optimization suggestions if slow
+      - Security improvements if needed
+      - Best practice improvements
+    - If bashrc is missing, offer to create a basic one
+## Important notes:
+- Don't modify the bashrc unless explicitly asked
+- Be careful when testing - use subshells to avoid affecting the current environment
+- Distinguish between critical errors and style suggestions
+- Consider that some "issues" might be intentional for the user's workflow

commands/debugging/check-boot-logs.md ADDED Viewed

	@@ -0,0 +1,43 @@

+You are analyzing system boot logs to identify failures and issues.
+## Your Task
+1. **Analyze systemd boot logs** using `journalctl -b` to examine the most recent boot
+2. **Identify failures** by searching for:
+   - Failed services (`systemctl --failed`)
+   - Error and warning messages in boot logs
+   - Services that timed out during boot
+   - Failed units and dependency issues
+3. **Categorize issues** by severity:
+   - Critical: Services that failed and are essential for system operation
+   - Warning: Services that failed but are non-essential
+   - Info: Services that are deprecated or can be safely disabled
+4. **Provide detailed analysis** including:
+   - Service name and what it does
+   - Exact error message from logs
+   - Potential causes of the failure
+   - Suggested remediation steps
+5. **Suggest cleanup actions** for:
+   - Deprecated services that can be disabled
+   - Unnecessary services slowing down boot
+   - Configuration fixes for failed services
+## Commands to Use
+- `journalctl -b -p err` - Show errors from current boot
+- `journalctl -b -p warning` - Show warnings from current boot
+- `systemctl --failed` - List failed units
+- `systemctl list-units --state=failed` - Detailed failed units
+- `journalctl -u <service-name>` - Check specific service logs
+- `systemd-analyze critical-chain` - Show boot time-critical chain
+## Output Format
+Present findings in a clear, organized manner:
+1. Summary of boot health
+2. Critical failures requiring immediate attention
+3. Warnings and non-critical issues
+4. Recommendations for cleanup and optimization
+5. Specific commands to fix identified issues
+Be thorough but concise. Focus on actionable insights.

commands/debugging/diagnose-crash.md ADDED Viewed

	@@ -0,0 +1,162 @@

+# Diagnose Program Crash
+You are helping the user diagnose a recent program crash. Ask for additional context from the user, but start by checking obvious places in the logs.
+## Your tasks:
+1. **Gather information from the user:**
+   Ask the user:
+   - What program crashed?
+   - When did it crash (approximate time)?
+   - What were they doing when it crashed?
+   - Does it crash consistently or intermittently?
+   - Any error messages displayed?
+2. **Check system journal for crash information:**
+   - Recent errors: `sudo journalctl -p err -b`
+   - Last 100 log entries: `sudo journalctl -n 100 --no-pager`
+   - If user knows approximate time:
+     ```bash
+     sudo journalctl --since "10 minutes ago" -p warning
+     sudo journalctl --since "YYYY-MM-DD HH:MM:SS"
+     ```
+   - Search for specific program name:
+     ```bash
+     sudo journalctl -b | grep -i "<program-name>"
+     ```
+3. **Check kernel logs (dmesg):**
+   - Recent kernel messages: `dmesg | tail -100`
+   - Look for segmentation faults, OOM kills, kernel panics
+   - Search for program name: `dmesg | grep -i "<program-name>"`
+   - Check for OOM (Out of Memory) kills:
+     ```bash
+     dmesg | grep -i "killed process"
+     sudo journalctl -k | grep -i "out of memory"
+     ```
+4. **Check for core dumps:**
+   - Check if core dumps are enabled: `ulimit -c`
+   - System core dump pattern: `cat /proc/sys/kernel/core_pattern`
+   - Look for core dumps:
+     ```bash
+     find /var/lib/systemd/coredump -name "*<program-name>*" -mtime -1
+     find . -name "core*" -mtime -1
+     ```
+   - If systemd-coredump is used:
+     ```bash
+     coredumpctl list
+     coredumpctl info <pid>
+     coredumpctl dump <pid> -o /tmp/core.dump
+     ```
+5. **Check application-specific logs:**
+   - User logs: `~/.local/share/applications/`
+   - Xsession errors: `cat ~/.xsession-errors`
+   - Application cache: `~/.cache/<program-name>/`
+   - Application config: `~/.config/<program-name>/`
+   - System logs: `/var/log/`
+   - Application-specific locations:
+     - Web browsers: `~/.mozilla/`, `~/.config/google-chrome/`
+     - Snaps: `snap logs <snap-name>`
+     - Flatpaks: `flatpak logs`
+6. **Check crash reporter systems:**
+   - Ubuntu Apport crashes:
+     ```bash
+     ls -lt /var/crash/
+     ubuntu-bug <program-name>  # to file bug report
+     ```
+   - GNOME crash reports (if applicable): `~/.local/share/gnome-shell/`
+   - KDE crash reports: `~/.local/share/drkonqi/`
+7. **Check resource issues at crash time:**
+   - Memory usage: `free -h`
+   - Disk space: `df -h`
+   - Check if system was swapping heavily before crash
+   - Recent high memory usage: `sudo journalctl | grep -i "out of memory"`
+8. **Check for dependency issues:**
+   - Missing libraries:
+     ```bash
+     ldd $(which <program-name>)
+     ```
+   - Check if program still exists and is executable:
+     ```bash
+     which <program-name>
+     ls -la $(which <program-name>)
+     ```
+   - Version information: `<program-name> --version`
+9. **Check for recent system changes:**
+   - Recent package updates: `grep " install \| upgrade " /var/log/dpkg.log | tail -50`
+   - Recent system updates: `grep "upgrade" /var/log/apt/history.log | tail -20`
+   - Kernel changes: `ls -lt /boot/vmlinuz-*`
+10. **Graphics/display-related crashes:**
+    If GUI application:
+    - X server errors: `grep -i "error\|segfault" /var/log/Xorg.0.log`
+    - Wayland compositor logs: `journalctl -b | grep -i "kwin\|wayland"`
+    - GPU issues:
+      ```bash
+      nvidia-smi  # for NVIDIA
+      dmesg | grep -i "gpu\|nvidia\|amdgpu\|radeon"
+      ```
+11. **Check for known issues:**
+    - Search package bug tracker: `ubuntu-bug --package <package-name>`
+    - Check if issue is reproducible
+    - Check program's GitHub issues (if applicable)
+12. **Analyze crash signatures:**
+    Look for common crash indicators:
+    - **Segmentation fault (SIGSEGV)**: Memory access violation
+    - **SIGABRT**: Program called abort()
+    - **SIGILL**: Illegal instruction
+    - **SIGBUS**: Bus error
+    - **SIGFPE**: Floating point exception
+    - **OOM Killer**: Process killed due to out of memory
+    - **Stack trace**: If available in logs
+13. **Try to reproduce the crash:**
+    If possible, guide user to:
+    - Run program from terminal to see error output:
+      ```bash
+      <program-name> 2>&1 | tee /tmp/program-output.log
+      ```
+    - Run with debug logging (if supported):
+      ```bash
+      <program-name> --debug
+      <program-name> --verbose
+      ```
+    - Check environment variables that might affect behavior
+14. **Report findings:**
+    Summarize:
+    - Probable cause of crash (if identified)
+    - Relevant log entries
+    - Any error messages or stack traces found
+    - Resource issues if any
+    - Recent system changes that might be related
+15. **Provide recommendations:**
+    Based on findings, suggest:
+    - **If OOM kill**: Reduce memory usage, close other programs, add more RAM/swap
+    - **If segfault**: Check for updates, try reinstalling program, report bug
+    - **If dependency issue**: Reinstall program and dependencies
+    - **If config issue**: Reset configuration, move config to backup
+    - **If disk full**: Free up disk space
+    - **If recent update**: Consider downgrading or wait for fix
+    - **If reproducible**: Enable debug mode, create bug report with steps
+    - **If GPU-related**: Update drivers, check GPU health
+    - How to enable better crash reporting (core dumps, apport)
+    - Consider running program under debugger (gdb) if user is technical
+## Important notes:
+- Use sudo for system logs and journal access
+- Times in logs are usually in UTC - account for timezone
+- Be sensitive that crashes can be frustrating for users
+- Some log files can be very large - use grep and tail to filter
+- Core dumps can be very large - ask before extracting
+- Privacy: don't ask to see sensitive information from logs
+- If no obvious cause is found, explain what additional info would help

commands/debugging/diagnose-slowdown.md ADDED Viewed

	@@ -0,0 +1,134 @@

+# Diagnose System Slowdown
+You are helping the user diagnose system laginess and performance issues.
+## Your tasks:
+1. **Gather initial information:**
+   Ask the user:
+   - When did the slowdown start?
+   - Is it constant or intermittent?
+   - What activities trigger it? (startup, specific applications, general use)
+   - Any recent changes? (updates, new software, configuration changes)
+2. **Check current system load:**
+   - System load averages: `uptime`
+   - Detailed load info: `w`
+   - Number of processes: `ps aux | wc -l`
+3. **CPU analysis:**
+   - Real-time CPU usage: `top -b -n 1 | head -20`
+   - Per-core CPU usage: `mpstat -P ALL 1 1` (if sysstat installed)
+   - Top CPU consumers: `ps aux --sort=-%cpu | head -20`
+   - CPU frequency and throttling:
+     ```bash
+     cat /proc/cpuinfo | grep MHz
+     sudo cpupower frequency-info  # if available
+     ```
+   - Check for thermal throttling:
+     ```bash
+     sensors  # if lm-sensors installed
+     cat /sys/class/thermal/thermal_zone*/temp
+     ```
+4. **Memory analysis:**
+   - Memory usage: `free -h`
+   - Detailed memory info: `cat /proc/meminfo`
+   - Swap usage: `swapon --show`
+   - Top memory consumers: `ps aux --sort=-%mem | head -20`
+   - Check for memory leaks or runaway processes
+   - OOM (Out of Memory) events: `sudo journalctl -k | grep -i "out of memory"`
+5. **Disk I/O analysis:**
+   - Disk usage: `df -h`
+   - Inode usage: `df -i`
+   - I/O statistics: `iostat -x 1 5` (if sysstat installed)
+   - Top I/O processes: `sudo iotop -b -n 1 | head -20` (if iotop installed)
+   - Check for high disk wait: `top` and look at `wa` (wait) percentage
+   - Disk health: `sudo smartctl -H /dev/sda` (for each drive)
+6. **Process analysis:**
+   - List all running processes: `ps aux`
+   - Process tree: `pstree -p`
+   - Zombie processes: `ps aux | grep Z`
+   - Processes in D state (uninterruptible sleep): `ps aux | grep " D "`
+   - Long-running processes: `ps -eo pid,user,start,time,cmd --sort=-time | head -20`
+7. **Check for system resource contention:**
+   - Context switches: `vmstat 1 5`
+   - Interrupts: `cat /proc/interrupts`
+   - Check if system is swapping heavily: `vmstat 1 5` (look at si/so columns)
+8. **Network issues (can cause perceived slowness):**
+   - Network connections: `ss -s`
+   - Active connections: `netstat -tunap | wc -l` or `ss -tunap | wc -l`
+   - DNS resolution test: `time nslookup google.com`
+   - Check for network errors: `ip -s link`
+9. **Graphics/Desktop environment (for GUI slowness):**
+   - Check X server or Wayland compositor CPU usage
+   - GPU usage (if nvidia): `nvidia-smi` or `watch -n 1 nvidia-smi`
+   - For AMD: `radeontop` (if installed)
+   - Check compositor settings (KDE Plasma on Wayland)
+   - Desktop effects CPU usage
+10. **Check system logs for errors:**
+    - Recent errors: `sudo journalctl -p err -b`
+    - Kernel messages: `dmesg | tail -50`
+    - System log: `sudo journalctl -xe --no-pager | tail -100`
+    - Look for specific issues:
+      - Hardware errors
+      - Driver issues
+      - Service failures
+      - Filesystem errors
+11. **Check for background services/processes:**
+    - List all services: `systemctl list-units --type=service --state=running`
+    - Failed services: `systemctl --failed`
+    - Check for update managers, indexing services (updatedb, baloo, tracker)
+    - Snap services: `snap list` and check for snap updates
+    - Flatpak: `flatpak list`
+12. **Application-specific checks:**
+    If slowness is application-specific:
+    - Browser: check extensions, tabs, cache size
+    - Database: check for long-running queries
+    - IDE: check for indexing, plugins
+    - Check application logs: `~/.local/share/applications/` or specific app log locations
+13. **Historical data (if available):**
+    - Check sar data: `sar -u` (if sysstat/sar configured)
+    - Check historical logs: `sudo journalctl --since "1 day ago" -p err`
+14. **Analyze and report findings:**
+    Categorize issues found:
+    - **CPU bottleneck**: High CPU usage, identify culprit processes
+    - **Memory bottleneck**: High memory usage, swapping, suggest adding RAM or killing processes
+    - **Disk I/O bottleneck**: High wait times, slow disk, suggest SSD upgrade or I/O optimization
+    - **Thermal throttling**: High temperatures causing CPU slowdown
+    - **Runaway processes**: Specific process consuming excessive resources
+    - **Resource leaks**: Memory or handle leaks in specific applications
+    - **Background tasks**: Indexing, updates, backups running
+    - **Network issues**: DNS problems, slow network affecting system
+15. **Provide recommendations:**
+    Based on findings, suggest:
+    - Kill or restart specific problematic processes
+    - Disable unnecessary services
+    - Adjust swappiness: `sudo sysctl vm.swappiness=10`
+    - Clean up disk space if low
+    - Update or reinstall problematic drivers
+    - Install missing performance tools (sysstat, iotop, htop)
+    - Schedule resource-intensive tasks for off-hours
+    - Hardware upgrades (RAM, SSD) if appropriate
+    - Investigate and fix application-specific issues
+    - Check for and apply system updates
+    - Reboot if system has been up for extended period with memory leaks
+## Important notes:
+- Install missing diagnostic tools if needed (sysstat, iotop, htop, lm-sensors)
+- Use sudo for system-level diagnostics
+- Be systematic - check CPU, memory, disk, and network in order
+- Correlate findings with user's description of when slowness occurs
+- Don't immediately kill processes - confirm with user first
+- Consider both hardware and software causes

commands/debugging/failed-boot-services.md ADDED Viewed

	@@ -0,0 +1,7 @@

+During the boot process, I noticed that several services failed
+Please review the logs to identify which those were and remediate:
+- If they can fixed, fix them
+- If they refer to old processes, remove them
+- If you are not sure, ask

commands/debugging/review-boot.md ADDED Viewed

	@@ -0,0 +1,36 @@

+Review system boot process and identify issues.
+Your task:
+1. Scan boot messages and journal logs:
+   ```bash
+   journalctl -b  # Current boot
+   journalctl -b -1  # Previous boot
+   ```
+2. Identify issues:
+   - Failed services
+   - Error messages
+   - Warnings
+   - Slow-starting services
+   - Dependency problems
+3. Analyze boot performance:
+   ```bash
+   systemd-analyze  # Overall boot time
+   systemd-analyze blame  # Time per service
+   systemd-analyze critical-chain  # Critical path
+   ```
+4. Suggest remediation:
+   - Fix failed services
+   - Disable unnecessary services
+   - Resolve dependency issues
+   - Optimize slow services
+5. Provide actionable recommendations:
+   - Commands to investigate specific issues
+   - Configuration changes needed
+   - Services to disable or reconfigure
+   - Further diagnostic steps
+Proactively identify and suggest fixes for boot-time issues.

commands/dev-tools/node/node-version-check.md ADDED Viewed

	@@ -0,0 +1 @@


1	+ Check which version of node I have installed on this computer.

commands/dev-tools/node/npm-install.md ADDED Viewed

	@@ -0,0 +1 @@


1	+ Install Node Package Manager (npm).

commands/dev-tools/optimize-vscode-installation.md ADDED Viewed

	@@ -0,0 +1,131 @@

+---
+description: Evaluate VS Code installation and suggest optimizations like repo source changes
+tags: [vscode, development, optimization, configuration, project, gitignored]
+---
+You are helping the user optimize their VS Code installation.
+## Process
+1. **Check how VS Code is installed**
+   ```bash
+   which code
+   dpkg -l | grep code
+   snap list | grep code
+   flatpak list | grep code
+   ```
+   - Identify installation method: apt, snap, flatpak, manual
+2. **Check VS Code version**
+   ```bash
+   code --version
+   ```
+   - Compare with latest version
+   - Check if updates are available
+3. **Evaluate current installation method**
+   **APT (official repo) - Recommended:**
+   - Pros: Native integration, automatic updates, best performance
+   - Cons: Requires adding Microsoft repo
+   **Snap:**
+   - Pros: Easy install, sandboxed
+   - Cons: Slower startup, snap overhead, potential issues with extensions
+   **Flatpak:**
+   - Pros: Sandboxed, cross-distro
+   - Cons: Some filesystem access limitations
+   **Manual .deb:**
+   - Pros: Control over updates
+   - Cons: Manual update process
+4. **Suggest migration if needed**
+   **If installed via Snap, suggest migrating to APT:**
+   ```bash
+   # Remove snap version
+   sudo snap remove code
+   # Add official Microsoft repo
+   wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > packages.microsoft.gpg
+   sudo install -o root -g root -m 644 packages.microsoft.gpg /etc/apt/trusted.gpg.d/
+   sudo sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/code stable main" > /etc/apt/sources.list.d/vscode.list'
+   # Install via apt
+   sudo apt update && sudo apt install code
+   ```
+   **If privacy-conscious, suggest VSCodium:**
+   ```bash
+   flatpak install flathub com.vscodium.codium
+   ```
+5. **Check VS Code configuration**
+   - Review settings: `~/.config/Code/User/settings.json`
+   - Check for optimization opportunities:
+     - Telemetry settings
+     - Auto-save
+     - File watcher limits
+     - Extension recommendations
+6. **Optimize performance settings**
+   Suggest adding to settings.json:
+   ```json
+   {
+     "files.watcherExclude": {
+       "**/.git/objects/**": true,
+       "**/node_modules/**": true,
+       "**/.venv/**": true
+     },
+     "files.exclude": {
+       "**/__pycache__": true,
+       "**/.pytest_cache": true
+     },
+     "search.exclude": {
+       "**/node_modules": true,
+       "**/venv": true
+     },
+     "telemetry.telemetryLevel": "off"
+   }
+   ```
+7. **Check installed extensions**
+   ```bash
+   code --list-extensions
+   ```
+   - Identify potentially redundant extensions
+   - Suggest disabling unused extensions for performance
+8. **Suggest useful extensions**
+   - Based on detected project types
+   - Common useful extensions:
+     - GitLens
+     - Prettier
+     - ESLint/Pylint
+     - Docker
+     - Remote-SSH
+     - Live Server (web dev)
+9. **Check for conflicts**
+   - Multiple VS Code installations
+   - Conflicting extensions
+   - Settings sync issues
+10. **Create backup of settings**
+    - Offer to backup:
+      - `~/.config/Code/User/settings.json`
+      - `~/.config/Code/User/keybindings.json`
+      - Extension list
+## Output
+Provide a report showing:
+- Current installation method and version
+- Recommended installation method
+- Migration steps (if applicable)
+- Performance optimization suggestions
+- Extension recommendations
+- Configuration backup status
+- Next steps

commands/dev-tools/sdk-check.md ADDED Viewed

	@@ -0,0 +1,2 @@


1	+ Check which development SDKs I have installed on my computer.
2	+ Start with identifying what's on path. Then see what I might have elsewhere on the filesystem.

commands/dev-tools/setup-docker.md ADDED Viewed

	@@ -0,0 +1,258 @@

+# Check and Setup Docker
+You are helping the user check if Docker is configured and set it up if needed.
+## Your tasks:
+1. **Check if Docker is already installed:**
+   - Check Docker: `docker --version`
+   - Check Docker Compose: `docker-compose --version` or `docker compose version`
+   - Check Docker service: `systemctl status docker`
+2. **If Docker is installed, verify configuration:**
+   - Check Docker info: `docker info`
+   - Check user can run Docker: `docker ps`
+   - If permission denied, user needs to be added to docker group
+   - Check Docker storage driver and location
+   - Check Docker network configuration
+3. **If Docker is NOT installed, proceed with installation:**
+   **Remove old versions:**
+   ```bash
+   sudo apt-get remove docker docker-engine docker.io containerd runc
+   ```
+   **Update and install prerequisites:**
+   ```bash
+   sudo apt-get update
+   sudo apt-get install ca-certificates curl gnupg lsb-release
+   ```
+   **Add Docker's official GPG key:**
+   ```bash
+   sudo mkdir -p /etc/apt/keyrings
+   curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
+   ```
+   **Set up repository:**
+   ```bash
+   echo \
+     "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
+     $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
+   ```
+   **Install Docker Engine:**
+   ```bash
+   sudo apt-get update
+   sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
+   ```
+4. **Post-installation setup:**
+   **Enable Docker service:**
+   ```bash
+   sudo systemctl enable docker
+   sudo systemctl start docker
+   ```
+   **Add user to docker group:**
+   ```bash
+   sudo usermod -aG docker $USER
+   ```
+   Then log out and back in, or run: `newgrp docker`
+5. **Verify Docker installation:**
+   ```bash
+   docker --version
+   docker run hello-world
+   docker ps
+   docker images
+   ```
+6. **Install Docker Compose (if not included):**
+   Modern Docker includes Compose v2 as a plugin.
+   Check: `docker compose version`
+   If needed, install standalone:
+   ```bash
+   sudo apt-get install docker-compose-plugin
+   ```
+7. **Configure Docker daemon (optional):**
+   Edit `/etc/docker/daemon.json`:
+   ```json
+   {
+     "log-driver": "json-file",
+     "log-opts": {
+       "max-size": "10m",
+       "max-file": "3"
+     },
+     "storage-driver": "overlay2",
+     "dns": ["8.8.8.8", "8.8.4.4"]
+   }
+   ```
+   Then restart: `sudo systemctl restart docker`
+8. **Check Docker storage location:**
+   ```bash
+   docker info | grep "Docker Root Dir"
+   sudo du -sh /var/lib/docker
+   ```
+   If storage is on a small partition, consider changing location.
+9. **Configure storage location (if needed):**
+   In `/etc/docker/daemon.json`:
+   ```json
+   {
+     "data-root": "/new/path/to/docker"
+   }
+   ```
+   Then:
+   ```bash
+   sudo systemctl stop docker
+   sudo mv /var/lib/docker /new/path/to/docker
+   sudo systemctl start docker
+   ```
+10. **Set up Docker networking:**
+    Check networks:
+    ```bash
+    docker network ls
+    ```
+    Create custom networks if needed:
+    ```bash
+    docker network create my-network
+    ```
+11. **Configure resource limits (optional):**
+    For laptops/desktops, may want to limit resources:
+    In `/etc/docker/daemon.json`:
+    ```json
+    {
+      "default-ulimits": {
+        "nofile": {
+          "Name": "nofile",
+          "Hard": 64000,
+          "Soft": 64000
+        }
+      }
+    }
+    ```
+12. **Set up Docker Hub authentication (optional):**
+    ```bash
+    docker login
+    ```
+13. **Test Docker functionality:**
+    Run various test commands:
+    ```bash
+    docker run hello-world
+    docker run -it ubuntu bash
+    docker ps -a
+    docker images
+    docker system info
+    ```
+14. **Install useful Docker tools (optional):**
+    Ask user if they want:
+    - **Portainer** (Docker management UI)
+    - **ctop** (Container monitoring)
+    - **lazydocker** (Terminal UI for Docker)
+    ```bash
+    # ctop
+    sudo wget -O /usr/local/bin/ctop https://github.com/bcicen/ctop/releases/download/v0.7.7/ctop-0.7.7-linux-amd64
+    sudo chmod +x /usr/local/bin/ctop
+    ```
+15. **Configure Docker logging:**
+    Check current logging:
+    ```bash
+    docker info | grep "Logging Driver"
+    ```
+    Configure in `/etc/docker/daemon.json`:
+    ```json
+    {
+      "log-driver": "json-file",
+      "log-opts": {
+        "max-size": "10m",
+        "max-file": "5",
+        "labels": "production"
+      }
+    }
+    ```
+16. **Set up Docker cleanup:**
+    Suggest adding to crontab:
+    ```bash
+    # Clean up unused containers, images, networks weekly
+    0 3 * * 0 docker system prune -af --volumes
+    ```
+    Or show manual cleanup:
+    ```bash
+    docker system prune -a
+    docker volume prune
+    docker network prune
+    ```
+17. **Check for common issues:**
+    - Docker daemon not running: `sudo systemctl start docker`
+    - Permission denied: `sudo usermod -aG docker $USER` and re-login
+    - Storage full: `docker system df` and cleanup
+    - Network issues: Check DNS in daemon.json
+    - Firewall blocking: Check ufw/iptables
+18. **Provide best practices:**
+    - Don't run containers as root when possible
+    - Use Docker Compose for multi-container apps
+    - Tag images properly
+    - Clean up regularly with `docker system prune`
+    - Use .dockerignore files
+    - Monitor disk usage: `docker system df`
+    - Use specific image tags, not `latest`
+    - Scan images for vulnerabilities: `docker scan <image>`
+    - Keep Docker updated
+    - Use multi-stage builds to reduce image size
+    - Limit container resources in production
+19. **Show basic Docker commands:**
+    - `docker run <image>` - Run a container
+    - `docker ps` - List running containers
+    - `docker ps -a` - List all containers
+    - `docker images` - List images
+    - `docker pull <image>` - Pull an image
+    - `docker build -t <name> .` - Build an image
+    - `docker exec -it <container> bash` - Enter container
+    - `docker logs <container>` - View logs
+    - `docker stop <container>` - Stop container
+    - `docker rm <container>` - Remove container
+    - `docker rmi <image>` - Remove image
+    - `docker compose up` - Start compose stack
+    - `docker system prune` - Clean up
+20. **Report findings:**
+    Summarize:
+    - Docker installation status
+    - Version information
+    - User permissions status
+    - Storage configuration
+    - Service status
+    - Any issues found
+## Important notes:
+- User must log out and back in after being added to docker group
+- Docker can use significant disk space - monitor it
+- Don't run untrusted images
+- Docker Desktop is different from Docker Engine (we're installing Engine)
+- Rootless Docker is available for better security but more complex
+- Docker Compose v2 is now a plugin (`docker compose` not `docker-compose`)
+- Keep Docker updated for security patches

commands/dev-tools/suggest-ides.md ADDED Viewed

	@@ -0,0 +1,115 @@

+---
+description: Suggest IDEs the user may wish to install
+tags: [development, ide, editors, tools, project, gitignored]
+---
+You are helping the user identify useful IDEs and code editors to install.
+## Process
+1. **Check currently installed editors/IDEs**
+   ```bash
+   which code vim nvim nano emacs gedit kate
+   dpkg -l | grep -E "code|editor|ide"
+   flatpak list | grep -E "code|editor|ide"
+   ```
+2. **Identify user's programming needs**
+   - Ask about programming languages used:
+     - Python
+     - JavaScript/TypeScript
+     - Java/Kotlin
+     - C/C++/Rust
+     - Go
+     - Web development
+     - Data science
+     - Mobile development
+3. **Suggest IDEs by category**
+   **General Purpose (recommended):**
+   - **VS Code** - Most popular, extensive plugins
+   - **VSCodium** - VS Code without telemetry
+   - **JetBrains Fleet** - Modern, lightweight
+   - **Sublime Text** - Fast, elegant
+   - **Atom** (deprecated, suggest alternatives)
+   **Language-Specific:**
+   - **PyCharm** - Python (Community/Professional)
+   - **IntelliJ IDEA** - Java/Kotlin
+   - **WebStorm** - JavaScript/TypeScript
+   - **RustRover** - Rust
+   - **GoLand** - Go
+   - **Android Studio** - Android development
+   **Lightweight Editors:**
+   - **Neovim** - Modern Vim
+   - **Helix** - Modern modal editor
+   - **Micro** - Terminal editor, easy to use
+   - **Geany** - GTK editor with IDE features
+   **Data Science:**
+   - **JupyterLab** - Notebooks
+   - **RStudio** - R development
+   - **Spyder** - Python for scientific computing
+   **Web Development:**
+   - **Zed** - Collaborative, fast
+   - **Brackets** - Live preview
+4. **Installation methods**
+   **VS Code:**
+   ```bash
+   # Official repo
+   wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > packages.microsoft.gpg
+   sudo install -o root -g root -m 644 packages.microsoft.gpg /etc/apt/trusted.gpg.d/
+   sudo sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/code stable main" > /etc/apt/sources.list.d/vscode.list'
+   sudo apt update && sudo apt install code
+   ```
+   **VSCodium:**
+   ```bash
+   flatpak install flathub com.vscodium.codium
+   ```
+   **JetBrains Toolbox:**
+   ```bash
+   # Download from jetbrains.com/toolbox/
+   # Or use snap: snap install jetbrains-toolbox --classic
+   ```
+   **Neovim:**
+   ```bash
+   sudo apt install neovim
+   ```
+5. **Suggest based on current setup**
+   - If Python user: Suggest PyCharm
+   - If web dev: Suggest VS Code with extensions
+   - If systems programming: Suggest Neovim with LSP
+   - If prefer FOSS: Suggest VSCodium
+6. **Recommend extensions/plugins**
+   - For VS Code/VSCodium:
+     - Python
+     - Pylance
+     - GitLens
+     - Docker
+     - Remote SSH
+     - Prettier
+     - ESLint
+7. **Alternative: Check installed editors quality**
+   - Vim/Neovim configuration quality
+   - VS Code extension count
+   - Suggest improvements to existing setup
+## Output
+Provide a report showing:
+- Currently installed editors/IDEs
+- Recommended IDEs based on user's needs
+- Installation commands for suggestions
+- Extension/plugin recommendations
+- Comparison of options (pros/cons)

commands/dev-tools/yadm/check-yadm.md ADDED Viewed

	@@ -0,0 +1,51 @@

+# Check YADM Status
+You are helping the user check the status of their YADM (Yet Another Dotfiles Manager) repository.
+## Task
+1. Check which files YADM is currently tracking:
+   ```bash
+   yadm list -a
+   ```
+2. Show the current repository status (modified, staged, untracked files):
+   ```bash
+   yadm status
+   ```
+3. Show recent commit history (last 10 commits):
+   ```bash
+   yadm log --oneline -10
+   ```
+4. Check if there are any unpushed commits:
+   ```bash
+   yadm log origin/main..HEAD --oneline
+   ```
+   (Note: Replace 'main' with the actual branch name if different, e.g., 'master')
+5. Show which remote repository YADM is connected to:
+   ```bash
+   yadm remote -v
+   ```
+6. Summarize the findings for the user:
+   - Total number of tracked files
+   - Any uncommitted changes
+   - Any unpushed commits
+   - Current branch
+   - Remote repository location
+## Additional Checks (Optional)
+If requested, you can also:
+- Show files that have been modified: `yadm diff --name-only`
+- Check for files that should be tracked but aren't: Look for common dotfiles in the home directory
+- Verify the YADM repository is healthy: `yadm fsck`
+## Notes
+- YADM is a wrapper around git specifically for managing dotfiles
+- All git commands work with yadm by replacing 'git' with 'yadm'
+- The YADM repository is stored in `~/.local/share/yadm/repo.git`

commands/dev-tools/yadm/manually-update-yadm.md ADDED Viewed

	@@ -0,0 +1,49 @@

+# Manually Update YADM
+You are helping the user manually update their YADM (Yet Another Dotfiles Manager) repository.
+## Task
+1. First, check the current status of the YADM repository:
+   ```bash
+   yadm status
+   ```
+2. Show the user what files have been modified:
+   ```bash
+   yadm diff
+   ```
+3. Ask the user which files they want to add to the commit. If they want to add all changes, use:
+   ```bash
+   yadm add -u
+   ```
+   Or for specific files:
+   ```bash
+   yadm add <file1> <file2> ...
+   ```
+4. Show the staged changes:
+   ```bash
+   yadm status
+   ```
+5. Ask the user for a commit message, then create the commit:
+   ```bash
+   yadm commit -m "user's commit message"
+   ```
+6. Push the changes to the remote repository:
+   ```bash
+   yadm push
+   ```
+7. Confirm the update was successful and show the final status.
+## Notes
+- YADM works exactly like git but is specifically for dotfiles
+- Be careful not to commit sensitive information like API keys or passwords
+- If the user has a pre-commit hook or other git hooks configured, they will run automatically
+- If there are conflicts or issues, guide the user through resolving them

commands/display/list-connected-displays.md ADDED Viewed

	@@ -0,0 +1,72 @@

+# List Connected Displays
+You are helping the user identify all connected displays and their current configurations.
+## Task
+1. **Detect display server** (Wayland vs X11):
+   ```bash
+   echo $XDG_SESSION_TYPE
+   ```
+2. **For Wayland systems:**
+   ```bash
+   # Using kscreen-doctor (KDE)
+   kscreen-doctor -o
+   # Using wlr-randr (wlroots-based compositors)
+   wlr-randr
+   # Using gnome-randr (GNOME)
+   gnome-randr
+   ```
+3. **For X11 systems:**
+   ```bash
+   xrandr --query
+   ```
+4. **Get detailed information:**
+   ```bash
+   # List all display devices
+   ls /sys/class/drm/card*/card*/status
+   # Check connected displays
+   for p in /sys/class/drm/card*/card*/status; do
+     echo "$(dirname $p): $(cat $p)"
+   done
+   ```
+5. **Show current resolution and refresh rate:**
+   ```bash
+   # X11
+   xrandr | grep -E "^[^ ]|[0-9]+\.[0-9]+\*"
+   # Wayland (KDE)
+   kscreen-doctor -j | jq -r '.outputs[] | "\(.name): \(.currentMode.size.width)x\(.currentMode.size.height)@\(.currentMode.refreshRate)Hz"'
+   ```
+## Present to User
+Summarize the findings:
+- Number of connected displays
+- Display names/identifiers
+- Current resolution and refresh rate for each
+- Primary display
+- Display position/arrangement
+- Whether using Wayland or X11
+## Additional Information
+If requested, also show:
+- Supported resolutions and refresh rates
+- Display manufacturer and model (from EDID)
+- Connection type (HDMI, DisplayPort, etc.)
+- Color depth and color space
+## Notes
+- Command availability depends on desktop environment and display server
+- KDE Plasma uses kscreen-doctor
+- GNOME may use different tools
+- Some information requires parsing EDID data from `/sys/class/drm/`

commands/display/optimize-display-scaling.md ADDED Viewed

	@@ -0,0 +1,135 @@

+# Optimize Display Scaling
+You are helping the user configure HiDPI scaling and fractional scaling for optimal display clarity.
+## Task
+1. **Check current display information:**
+   ```bash
+   # Display server type
+   echo $XDG_SESSION_TYPE
+   # Current resolution and size
+   kscreen-doctor -o  # Wayland/KDE
+   # OR
+   xrandr --query  # X11
+   # Calculate DPI
+   xdpyinfo | grep -B 2 resolution  # X11
+   ```
+2. **Determine optimal scaling:**
+   - Display resolution
+   - Physical size (diagonal in inches)
+   - Calculate PPI: `sqrt(width² + height²) / diagonal_inches`
+   - Recommended scaling:
+     - PPI < 110: 100% (1x)
+     - PPI 110-140: 125% (1.25x)
+     - PPI 140-180: 150% (1.5x)
+     - PPI 180-220: 200% (2x)
+     - PPI > 220: 250% or higher
+3. **For KDE Plasma (Wayland or X11):**
+   ```bash
+   # Set global scale factor (Wayland)
+   kscreen-doctor output.DP-1.scale.1.5
+   # Or use GUI
+   kcmshell6 kcm_kscreen
+   ```
+   **Via settings file:**
+   ```bash
+   # Edit KDE scaling
+   kwriteconfig6 --file kdeglobals --group KScreen --key ScaleFactor 1.5
+   kquitapp6 plasmashell && kstart plasmashell
+   ```
+4. **For GNOME (Wayland):**
+   ```bash
+   # Enable fractional scaling
+   gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
+   # Set scale factor (200% = 2.0)
+   gsettings set org.gnome.desktop.interface scaling-factor 2
+   ```
+5. **For X11 systems (general):**
+   ```bash
+   # Set Xft DPI
+   echo "Xft.dpi: 144" >> ~/.Xresources
+   xrdb -merge ~/.Xresources
+   # Set scale factor for Qt applications
+   export QT_SCALE_FACTOR=1.5
+   # Set scale factor for GTK applications
+   export GDK_SCALE=2
+   export GDK_DPI_SCALE=0.5
+   ```
+6. **Configure per-application scaling:**
+   ```bash
+   # For specific Qt apps
+   QT_SCALE_FACTOR=1.5 application-name
+   # Add to .bashrc or application launcher
+   echo 'export QT_SCALE_FACTOR=1.5' >> ~/.bashrc
+   ```
+7. **Adjust font DPI:**
+   ```bash
+   # KDE
+   kwriteconfig6 --file kcmfonts --group General --key forceFontDPI 144
+   # GNOME
+   gsettings set org.gnome.desktop.interface text-scaling-factor 1.25
+   ```
+8. **Handle cursor size:**
+   ```bash
+   # Set cursor size
+   gsettings set org.gnome.desktop.interface cursor-size 32  # GNOME
+   kwriteconfig6 --file kcminputrc --group Mouse --key cursorSize 32  # KDE
+   ```
+## Verify Configuration
+1. **Check current settings:**
+   ```bash
+   echo $QT_SCALE_FACTOR
+   echo $GDK_SCALE
+   gsettings get org.gnome.desktop.interface scaling-factor  # GNOME
+   ```
+2. **Test applications:**
+   - Open various applications (browser, terminal, file manager)
+   - Check text clarity
+   - Verify UI element sizes
+   - Test both Qt and GTK applications
+3. **Log out and back in** to apply system-wide changes
+## Troubleshooting
+- **Blurry applications:** Some apps don't support fractional scaling on X11
+- **Inconsistent scaling:** Mix of Qt and GTK apps may scale differently
+- **Wayland vs X11:** Wayland generally handles fractional scaling better
+- **XWayland apps:** May appear blurry on Wayland with fractional scaling
+**Solutions:**
+```bash
+# Force XWayland scaling
+kwriteconfig6 --file kwinrc --group Xwayland --key Scale 1.5
+# Disable fractional scaling for specific apps
+env QT_SCALE_FACTOR=1 application-name
+```
+## Notes
+- Wayland provides better fractional scaling support than X11
+- Some applications may require restart to apply scaling
+- Integer scaling (1x, 2x) is sharper than fractional (1.25x, 1.5x)
+- Consider display distance when choosing scale factor
+- Multi-monitor setups with different DPI may require per-monitor scaling

commands/display/setup-multi-monitor.md ADDED Viewed

	@@ -0,0 +1,90 @@

+# Setup Multi-Monitor Configuration
+You are helping the user configure multiple monitors on their Linux desktop.
+## Task
+1. **Detect current setup:**
+   ```bash
+   # Check display server type
+   echo $XDG_SESSION_TYPE
+   # List connected displays
+   kscreen-doctor -o  # KDE/Wayland
+   # OR
+   xrandr --query  # X11
+   ```
+2. **Ask the user about their desired configuration:**
+   - Which display should be primary?
+   - How should displays be arranged? (left-of, right-of, above, below, mirrored)
+   - What resolution for each display?
+   - What refresh rate for each display?
+3. **For X11 systems using xrandr:**
+   ```bash
+   # Example: Two monitors side by side
+   xrandr --output HDMI-1 --mode 1920x1080 --rate 60 \
+          --output DP-1 --mode 2560x1440 --rate 144 --right-of HDMI-1 --primary
+   # Example: Mirror displays
+   xrandr --output HDMI-1 --mode 1920x1080 \
+          --output DP-1 --same-as HDMI-1 --mode 1920x1080
+   ```
+4. **For Wayland/KDE systems using kscreen-doctor:**
+   ```bash
+   # Example: Configure displays
+   kscreen-doctor output.HDMI-1.mode.1920x1080@60 \
+                  output.DP-1.mode.2560x1440@144 \
+                  output.DP-1.position.1920,0 \
+                  output.DP-1.primary
+   ```
+5. **For GNOME (Wayland):**
+   ```bash
+   # Use gnome-control-center or gnome-randr
+   gnome-randr modify DP-1 --mode 2560x1440 --rate 144 --primary --pos 1920x0
+   ```
+6. **Make configuration persistent:**
+   **X11:**
+   - Configuration is typically saved by the desktop environment
+   - Can add xrandr commands to `~/.xprofile` or startup scripts
+   **Wayland/KDE:**
+   - KDE saves configuration automatically in `~/.local/share/kscreen/`
+   **Create startup script if needed:**
+   ```bash
+   # Create script
+   cat > ~/.config/autostart-scripts/monitor-setup.sh << 'EOF'
+   #!/bin/bash
+   # Monitor setup commands here
+   EOF
+   chmod +x ~/.config/autostart-scripts/monitor-setup.sh
+   ```
+7. **Test and verify:**
+   - Check if all displays are showing correctly
+   - Verify resolution and refresh rates
+   - Test primary display setting
+   - Check display arrangement by moving windows
+## Troubleshooting
+If issues occur:
+- Check if displays are detected: `xrandr --listmonitors` or `kscreen-doctor -o`
+- Verify supported modes for each display
+- Try lower refresh rates if displays flicker
+- Check cable connections and quality
+- Look for errors in logs: `journalctl -b | grep -i drm`
+## Notes
+- Commands differ significantly between X11 and Wayland
+- Desktop environment may provide GUI tools (System Settings)
+- Some configurations may require restarting the display manager
+- High refresh rates require appropriate cables (DisplayPort 1.4, HDMI 2.1)

commands/display/switch-display-profile.md ADDED Viewed

	@@ -0,0 +1,172 @@

+# Switch Display Profile
+You are helping the user switch between different display configurations/profiles (e.g., docked, laptop only, presentation).
+## Task
+1. **Check current display setup:**
+   ```bash
+   # Display server type
+   echo $XDG_SESSION_TYPE
+   # Connected displays
+   kscreen-doctor -o  # KDE/Wayland
+   # OR
+   xrandr --query  # X11
+   ```
+2. **Ask user which profile they want:**
+   - **Laptop only** (internal display only)
+   - **Docked** (external monitors only or primary external)
+   - **Extended** (laptop + external monitors)
+   - **Mirrored** (same output on all displays)
+   - **Presentation** (external display as primary)
+   - **Custom** (user-defined configuration)
+3. **KDE Plasma - Use saved profiles:**
+   ```bash
+   # List saved display configurations
+   ls ~/.local/share/kscreen/
+   # KDE automatically switches profiles based on connected displays
+   # Force reload configuration
+   kscreen-doctor --reload
+   ```
+4. **Create/Use autorandr (X11):**
+   ```bash
+   # Install if not present
+   sudo apt install autorandr
+   # Save current configuration as profile
+   autorandr --save profile-name
+   # Switch to saved profile
+   autorandr --load profile-name
+   # Auto-detect and load appropriate profile
+   autorandr --change
+   ```
+5. **Manual X11 configuration examples:**
+   **Laptop only:**
+   ```bash
+   xrandr --output eDP-1 --auto --primary \
+          --output HDMI-1 --off \
+          --output DP-1 --off
+   ```
+   **Docked (external monitors only):**
+   ```bash
+   xrandr --output eDP-1 --off \
+          --output HDMI-1 --auto --primary \
+          --output DP-1 --auto --right-of HDMI-1
+   ```
+   **Extended (laptop + external):**
+   ```bash
+   xrandr --output eDP-1 --auto \
+          --output HDMI-1 --auto --primary --above eDP-1
+   ```
+   **Mirrored:**
+   ```bash
+   xrandr --output eDP-1 --auto \
+          --output HDMI-1 --auto --same-as eDP-1
+   ```
+6. **Wayland/KDE configuration:**
+   ```bash
+   # Laptop only
+   kscreen-doctor output.eDP-1.enable \
+                  output.HDMI-1.disable \
+                  output.DP-1.disable
+   # Docked
+   kscreen-doctor output.eDP-1.disable \
+                  output.HDMI-1.enable output.HDMI-1.primary \
+                  output.DP-1.enable output.DP-1.position.1920,0
+   # Extended
+   kscreen-doctor output.eDP-1.enable \
+                  output.HDMI-1.enable output.HDMI-1.primary \
+                  output.HDMI-1.position.0,-1080
+   ```
+7. **Create quick-switch scripts:**
+   ```bash
+   # Create scripts directory
+   mkdir -p ~/.local/bin/display-profiles
+   # Example: Laptop only script
+   cat > ~/.local/bin/display-profiles/laptop-only.sh << 'EOF'
+   #!/bin/bash
+   xrandr --output eDP-1 --auto --primary \
+          --output HDMI-1 --off \
+          --output DP-1 --off
+   notify-send "Display Profile" "Switched to: Laptop Only"
+   EOF
+   chmod +x ~/.local/bin/display-profiles/laptop-only.sh
+   ```
+8. **Create keyboard shortcuts (KDE):**
+   ```bash
+   # Add custom shortcut
+   kwriteconfig6 --file kglobalshortcutsrc \
+                 --group "Display Profile - Laptop" \
+                 --key "_k_friendly_name" "Laptop Display Only"
+   ```
+9. **Automatic profile switching with udev:**
+   ```bash
+   # Create udev rule for auto-switching when docking
+   sudo tee /etc/udev/rules.d/95-monitor-hotplug.rules << 'EOF'
+   ACTION=="change", SUBSYSTEM=="drm", RUN+="/usr/local/bin/display-switch.sh"
+   EOF
+   # Create switch script
+   sudo tee /usr/local/bin/display-switch.sh << 'EOF'
+   #!/bin/bash
+   export DISPLAY=:0
+   export XAUTHORITY=/home/daniel/.Xauthority
+   /usr/bin/autorandr --change
+   EOF
+   sudo chmod +x /usr/local/bin/display-switch.sh
+   sudo udevadm control --reload-rules
+   ```
+## Verify Configuration
+- Check display arrangement with GUI or commands
+- Test window movement between displays
+- Verify primary display setting
+- Check resolution and refresh rates
+- Test systray/panel positioning
+## Troubleshooting
+**Profile not loading:**
+- Verify display names with `xrandr` or `kscreen-doctor -o`
+- Check saved profile files
+- Ensure all referenced displays are connected
+**Automatic switching not working:**
+- Check udev rule syntax
+- Verify script permissions and paths
+- Check logs: `journalctl -f` while connecting/disconnecting displays
+**Black screen after switching:**
+- Use Ctrl+Alt+F2 to access TTY
+- Reset display configuration: `xrandr --auto`
+- Restart display manager: `sudo systemctl restart sddm` (or gdm, lightdm)
+## Notes
+- autorandr is the most reliable tool for X11 profile management
+- KDE Plasma handles profile switching automatically on Wayland
+- Save profiles for different scenarios (home office, conference room, etc.)
+- Consider using descriptive names for profiles
+- Test profiles before relying on them for important presentations

commands/filesystem-organization/chunking/chunk-this-dir.md ADDED Viewed

	@@ -0,0 +1,5 @@

+This folder contains a lot of files.
+Please chunk them by creating numeric subfolders each containing a specific number of files.
+I will provide the desired number.

commands/filesystem-organization/consolidate-folders.md ADDED Viewed

	@@ -0,0 +1,46 @@

+You are helping Daniel consolidate redundant or overlapping folders into a more organized structure.
+## Your Task
+1. **Analyze subdirectories**: List all subdirectories in the current working directory
+2. **Identify overlaps**: Look for:
+   - Folders with similar names or purposes
+   - Folders containing similar types of files
+   - Multiple folders that could logically be merged
+   - Poorly named folders that could be better organized
+3. **Analyze contents**: For each folder, show:
+   - Number of files
+   - File types present
+   - Apparent purpose based on names and contents
+4. **Propose consolidation plan**: Suggest:
+   - Which folders should be merged
+   - What the consolidated folder should be named
+   - Whether any subfolders should be created within the consolidated folder
+   - Any folders that should be renamed for clarity
+5. **Present the plan**: Show Daniel:
+   - Current folder structure with file counts
+   - Proposed new structure
+   - Exactly which folders will be merged and where their contents will go
+6. **Ask for confirmation**: Get Daniel's approval before making any changes
+7. **Execute if approved**:
+   - Create new folder structure
+   - Move files from old folders to new locations
+   - Remove empty old folders
+   - Provide a summary of what was done
+## Guidelines
+- Look for semantic similarities, not just name matches
+- Consider the logical grouping of content
+- Suggest hierarchical structures where appropriate (parent/child folders)
+- Be conservative - when in doubt, ask rather than assuming
+- Preserve all files - never delete data
+- Suggest meaningful, descriptive folder names
+## Safety
+- NEVER delete files, only move them
+- If filename conflicts occur, append numeric suffixes
+- Keep original folders until Daniel confirms they can be removed
+- Ask before proceeding with moves and deletions
+- Provide a detailed log of all changes made

commands/filesystem-organization/flatten.md ADDED Viewed

	@@ -0,0 +1,7 @@

+Flatten the folder hierarchy.
+All the files in the subfolders should be moved to this level in the filesystem.
+Resolve any filename clashes by appending unique characters.
+If this directory structure contains media (images or video) then after flattening the hierarchy ask me (the user) if I would like you to run a checksum based check to identify and remove any duplicates.

commands/filesystem-organization/separate-by-filetype.md ADDED Viewed

	@@ -0,0 +1,3 @@

+This folder contains media of different formats
+Create subfolders for common media types - for example audio,  photos,  video
+Move the corresponding files into the relevant folders. E.g. mv *.mp4 -> /video

commands/filesystem-organization/separate-photos-and-video.md ADDED Viewed

	@@ -0,0 +1,5 @@

+This folder contains a mixture of photos and video
+Create subfolders /photos and /videos
+Move photos into photos and videos into videos

commands/filesystem-organization/suggest-folder-structure.md ADDED Viewed

	@@ -0,0 +1,52 @@

+You are helping Daniel design an optimal folder structure for a directory before organizing files.
+## Your Task
+1. **Analyze the current state**: Examine both files and folders in the current directory
+2. **Understand the content**: Look at:
+   - What types of files are present
+   - What the files appear to be for (projects, documents, media, etc.)
+   - Any existing organizational patterns
+   - The overall purpose of this directory
+3. **Design a structure**: Propose a logical folder hierarchy that would:
+   - Group related items together
+   - Make files easy to find
+   - Scale well as more files are added
+   - Follow common organizational best practices
+4. **Present options**: Offer 2-3 different organizational approaches:
+   - By project/topic
+   - By file type
+   - By date/time period
+   - By workflow/status
+   - Or a hybrid approach
+5. **Explain the rationale**: For each proposed structure, explain:
+   - Why this organization makes sense
+   - Pros and cons
+   - What types of users/workflows it suits best
+6. **Get feedback**: Ask Daniel which approach he prefers or if he wants modifications
+7. **Provide implementation guidance**: Once approved, explain how to implement it (or offer to run /organize-loose-files or /consolidate-folders)
+## Guidelines
+- Consider Daniel's existing organizational patterns in other directories
+- Suggest structures that are intuitive and maintainable
+- Don't over-complicate - deeper isn't always better
+- Consider future growth and scalability
+- Use clear, descriptive folder names
+- Suggest naming conventions if helpful
+## Example Structures to Consider
+- **Flat categorical**: Top-level folders by category (Documents, Images, Projects, etc.)
+- **Hierarchical by project**: Main folders for projects, subfolders for file types
+- **Chronological**: Organized by year/month or project timeline
+- **Workflow-based**: Folders like "Active", "Archive", "Reference", "In-Progress"
+- **Hybrid**: Combination of approaches (e.g., projects at top level, then by file type)
+## Output
+Present folder structure proposals using tree format for clarity, showing:
+- Proposed folder names
+- Purpose of each folder
+- Example of what would go in each folder
+- Estimated number of files that would go in each folder based on current contents

commands/filesystem-organization/tidy-up/desktop-tidy.md ADDED Viewed

	@@ -0,0 +1,9 @@

+Recurse to my desktop (~/Desktop)
+Help me clean it up!
+See what non-launcher files I have
+Create filetype folders like audio and move files of that association into those subfolders.
+If you think you can see files which are probably no longer needed, ask me if they can be deleted

commands/filesystem-organization/tidy-up/organize-loose-files.md ADDED Viewed

	@@ -0,0 +1,32 @@

+You are helping Daniel organize loose files in a directory into a logical folder structure.
+## Your Task
+1. **Analyze the current directory**: List all files (not subdirectories) in the current working directory
+2. **Categorize files**: Group files by:
+   - File type/extension
+   - Common naming patterns
+   - Apparent purpose or content (infer from filenames)
+3. **Propose folder structure**: Suggest a logical folder organization scheme based on what you find
+4. **Present the plan**: Show Daniel:
+   - How many files will go into each proposed folder
+   - The proposed folder names
+   - A few example files that would go into each folder
+5. **Ask for confirmation**: Get Daniel's approval before making any changes
+6. **Execute if approved**: Create the folders and move files accordingly
+## Guidelines
+- Be intelligent about categorization - don't just group by file extension
+- Look for patterns in filenames (dates, projects, categories)
+- Suggest meaningful folder names
+- If there are many files of the same type doing different things, subcategorize them
+- Always preserve file names when moving
+- Create a summary report after completion showing what was organized
+## Safety
+- NEVER delete files
+- NEVER overwrite existing files
+- If a filename conflict occurs during move, append a number suffix
+- Ask before proceeding with the actual file moves

commands/fonts/install-google-fonts.md ADDED Viewed

	@@ -0,0 +1,80 @@

+---
+description: Install Google Fonts provided by the user
+tags: [fonts, google-fonts, typography, installation, project, gitignored]
+---
+You are helping the user install Google Fonts by name.
+## Process
+1. **Get font names from user**
+   - Ask user which Google Fonts they want to install
+   - Accept multiple font names
+2. **Choose installation method**
+   **Method 1: Using google-font-installer (if available)**
+   - Install tool: `pip install gftools`
+   - Download font: `gftools download-family "Font Name"`
+   **Method 2: Using font-downloader**
+   - Install: `sudo apt install font-manager`
+   - Or use: `pip install font-downloader`
+   **Method 3: Manual download**
+   - Download from: `https://fonts.google.com/`
+   - Or use GitHub: `https://github.com/google/fonts/tree/main/`
+3. **Download fonts**
+   - For each font name:
+     - Convert name to lowercase with dashes (e.g., "Roboto Mono" → "roboto-mono")
+     - Download from: `https://fonts.google.com/download?family=Font+Name`
+     - Or clone specific font: `git clone https://github.com/google/fonts.git --depth 1 --filter=blob:none --sparse && cd fonts && git sparse-checkout set ofl/<font-name>`
+4. **Install fonts**
+   - Create user font directory: `mkdir -p ~/.local/share/fonts/google-fonts`
+   - Extract and copy font files:
+     ```bash
+     unzip <font>.zip -d ~/.local/share/fonts/google-fonts/<font-name>/
+     ```
+   - Only copy .ttf and .otf files
+5. **Update font cache**
+   - Run: `fc-cache -fv`
+   - Verify installation: `fc-list | grep -i "<font-name>"`
+6. **Provide usage examples**
+   - Show how to use in applications
+   - Show how to set as system font
+   - Show how to use in CSS/web design
+## Example Workflow
+```bash
+# Example: Installing "Roboto" and "Open Sans"
+mkdir -p ~/.local/share/fonts/google-fonts
+cd /tmp
+# Download Roboto
+wget "https://fonts.google.com/download?family=Roboto" -O roboto.zip
+unzip roboto.zip -d ~/.local/share/fonts/google-fonts/roboto/
+# Download Open Sans
+wget "https://fonts.google.com/download?family=Open+Sans" -O open-sans.zip
+unzip open-sans.zip -d ~/.local/share/fonts/google-fonts/open-sans/
+# Update cache
+fc-cache -fv
+# Verify
+fc-list | grep -i "roboto\|open sans"
+```
+## Output
+Provide a summary showing:
+- Fonts requested by user
+- Download and installation status for each
+- Installation location
+- Verification that fonts are available
+- Usage examples

commands/fonts/list-fonts.md ADDED Viewed

	@@ -0,0 +1,79 @@

+---
+description: List installed fonts and offer to install additional fonts
+tags: [fonts, typography, system, customization, project, gitignored]
+---
+You are helping the user review their installed fonts and install additional ones if requested.
+## Process
+1. **List currently installed fonts**
+   - System fonts: `fc-list | cut -d: -f2 | sort -u | wc -l` (count)
+   - Show font families: `fc-list : family | sort -u`
+   - List font directories:
+     - System: `/usr/share/fonts/`
+     - User: `~/.local/share/fonts/`
+2. **Categorize installed fonts**
+   - Serif fonts
+   - Sans-serif fonts
+   - Monospace/coding fonts
+   - Display/decorative fonts
+   - Icon fonts
+3. **Check for common font packages**
+   - `dpkg -l | grep -E "fonts-|ttf-"`
+   - Common packages:
+     - `fonts-liberation`
+     - `fonts-noto`
+     - `fonts-roboto`
+     - `ttf-mscorefonts-installer`
+     - `fonts-powerline`
+4. **Suggest useful font additions**
+   **For coding:**
+   - Fira Code (ligatures)
+   - JetBrains Mono
+   - Cascadia Code
+   - Victor Mono
+   - Source Code Pro
+   **For design:**
+   - Inter
+   - Poppins
+   - Montserrat
+   - Raleway
+   **System fonts:**
+   - Noto fonts (comprehensive Unicode)
+   - Liberation fonts (MS Office compatible)
+   **Icons:**
+   - Font Awesome
+   - Material Design Icons
+   - Nerd Fonts
+5. **Installation methods**
+   - APT: `sudo apt install fonts-<name>`
+   - Manual installation:
+     ```bash
+     mkdir -p ~/.local/share/fonts
+     # Copy font files to directory
+     fc-cache -fv
+     ```
+   - Google Fonts downloader (see separate command)
+6. **Test font installation**
+   - Refresh font cache: `fc-cache -fv`
+   - Verify font: `fc-list | grep -i <font-name>`
+   - Show sample: `fc-match <font-name>`
+## Output
+Provide a report showing:
+- Total number of installed font families
+- List of installed fonts by category
+- Missing commonly-used fonts
+- Suggested fonts to install based on use case
+- Installation commands