Main

createtutorials/AGENTS.md

@@ -0,0 +1,216 @@
+# AGENTS.md - Agentic Coding Guidelines
+
+## Repository Overview
+
+This is a **documentation/tutorial repository** containing Linux/Arch Linux guides,
+CLI tool tutorials, and system administration references. All content is in
+Markdown format.
+
+## Build/Test/Lint Commands
+
+This repository has no build system. It is a pure documentation project.
+
+### Validation Commands
+```bash
+# Check markdown syntax (if markdownlint is available)
+markdownlint *.md */*.md
+
+# Check for broken links (if lychee is available)
+lychee *.md */*.md
+```
+
+## Code Style Guidelines
+
+### Markdown Formatting
+
+**Line Breaking:**
+- Default line breaking: **72 columns** (Geany editor standard)
+- Wrap long lines at 72 characters for readability
+- Use soft wraps in editor, hard breaks for newlines
+
+**Headers:**
+- Use ATX style (`# Header`) not Setext
+- Title case for main headers: `# How to Configure Nginx`
+- Sentence case for subheaders: `### Setting up virtual hosts`
+- Single blank line before and after headers
+
+**Lists:**
+- Use `-` for unordered lists (not `*`)
+- Use `1.` for ordered lists
+- Indent nested lists with 2 spaces
+- Blank line before and after list blocks
+
+**Code Blocks:**
+- Use fenced code blocks with language tags:
+  ~~~markdown
+  ```bash
+  echo "Hello World"
+  ```
+  ~~~
+- Indent code blocks to match surrounding content
+- Use `plain` for non-syntax output
+
+**Inline Code:**
+- Use backticks for: commands (`ls -la`), file names (`config.txt`),
+  options (`--help`)
+- No spaces inside backticks
+
+### File Naming Conventions
+
+**Tutorial Files:**
+- Format: `Descriptive-Title-With-Dashes.md`
+- Use Title Case with dashes as separators
+- Date suffix for time-sensitive content:
+  `Topic-Description_YYYY-MM-DD_HH-MM-SS.md`
+
+**Directory Organization:**
+- Group related tutorials in subdirectories: `Niri-Guides/`, `Nm-Arch-Guide/`
+- Use Title-Case for directory names
+
+### Content Structure
+
+**Standard Tutorial Template:**
+```markdown
+**Title:** Human Readable Title
+**Date:** YYYY-MM-DD (HH:MM:SS TIMEZONE)
+**Author:** Sr. Yididiel Hills, Arch Linux Admin, Developer
+**lfnc:** filename.md
+**Copyright:** © 2026-2027 Sr. Tyrone Hills
+**License:** MIT – see LICENSE file for details
+
+# Main Heading
+
+Brief introduction paragraph explaining what the tutorial covers.
+
+## Prerequisites
+
+- Item 1
+- Item 2
+
+## Main Content Section
+
+### Subsection
+
+Content here...
+
+## Summary
+
+Key takeaways and next steps.
+```
+
+**Required Metadata:**
+- Title, Date, Author, lfnc (filename), Copyright, License
+
+**Auto-Population Snippet (for editor templates):**
+When creating new documents, use this template for auto-populated headers:
+
+```markdown
+ti=**Title:**
+dt=**Date:** YYYY-MM-DD (HH:MM:SS TIMEZONE)
+au=**Author:** Sr. Yididiel Hills, Arch Linux Admin, Developer
+lf=**lfnc:**
+co=**Copyright:** © 2026-2027 Sr. Tyrone Hills
+li=**License:** MIT – see LICENSE file for details
+```
+
+*Note: The `%cursor%` placeholder indicates where the cursor should be
+positioned after template insertion. The `lf` field should auto-populate
+with the actual filename.*
+
+**Geany Editor Configuration:**
+Snippets configuration file location: `~/.config/geany/snippets.conf`
+
+Available shortcuts:
+- Type `header` then press **Tab** → Inserts complete header
+- Type `ti` then press **Tab** → **Title:** field
+- Type `dt` then press **Tab** → **Date:** field (auto-populated)
+- Type `au` then press **Tab** → **Author:** field
+- Type `lf` then press **Tab** → **lfnc:** field (auto-populated with filename)
+- Type `co` then press **Tab** → **Copyright:** field
+- Type `li` then press **Tab** → **License:** field
+
+Template file location: `~/.config/geany/templates/files/markdown.tpl`
+Use **File → New (with Template)** to create new documents with auto-populated headers.
+
+### Writing Style
+
+**Tone:**
+- Professional yet approachable
+- Use second person ("you") for instructions
+- Use imperative mood: "Run the following command"
+
+**Technical Accuracy:**
+- Verify all commands work on Arch Linux
+- Include expected output examples
+- Note version-specific behavior
+
+**Formatting Standards:**
+- Use bold (`**text**`) for emphasis and UI elements
+- Use italics (`*text*`) for emphasis only
+- Use blockquotes (`>`) for notes, warnings, tips
+- Use horizontal rules (`---`) sparingly
+
+### Special Elements
+
+**Command Examples:**
+- Show prompt indicator: `$` for user, `#` for root
+- Include comments explaining what command does
+
+```bash
+# List all running services
+$ systemctl list-units --type=service --state=running
+```
+
+**Warnings and Notes:**
+```markdown
+> **Warning:** This will delete all data. Backup first!
+
+> **Note:** This feature requires kernel 5.x or later.
+```
+
+**Keyboard Shortcuts:**
+- Use `Mod` for Super/Windows key
+- Format: `Mod+Shift+E`, `Ctrl+C`
+- Use code formatting for all key combinations
+
+## Naming Conventions
+
+- **Files:** `Title-Case-With-Dashes.md`
+- **Variables in examples:** lowercase_with_underscores
+- **Environment variables:** ALL_CAPS
+- **Commands:** lowercase (follow standard Unix conventions)
+
+## Common Patterns
+
+**Tutorial Types:**
+1. **Setup/Installation:** Prerequisites → Installation → Configuration → Verification
+2. **Command Reference:** Syntax → Options → Examples → Common Use Cases
+3. **Troubleshooting:** Problem → Diagnosis → Solution → Prevention
+
+**Reference Links:**
+- Use descriptive link text: `[Official Arch Wiki](url)` not `[click here](url)`
+- Prefer HTTPS links
+- Verify links are current
+
+## Agent Instructions
+
+When editing this repository:
+
+1. **Preserve existing tutorials** - Do not delete without confirmation
+2. **Maintain 72-column line breaks** throughout all content
+3. **Follow existing file naming patterns** in each directory
+4. **Add metadata block** to new tutorial files
+5. **Test all shell commands** before including them
+6. **Use consistent terminology** (e.g., "terminal" not "shell" unless specific)
+7. **Update date metadata** when substantially modifying existing files
+8. **Group related files** in appropriately named subdirectories
+
+## Pre-Commit Checklist
+
+- [ ] Lines wrapped at 72 columns
+- [ ] Metadata block present (for tutorials)
+- [ ] All code blocks have language tags
+- [ ] No trailing whitespace
+- [ ] File ends with single newline
+- [ ] Links use HTTPS where available
+- [ ] Commands verified on Arch Linux

createtutorials/Advanced-Research-Assistant.md

@@ -0,0 +1,102 @@
+The search system is working! It's trying to search, but DuckDuckGo is
+rate-limiting us. Let me show you how to use it:
+🚀 How to Use the Search Tool
+Option 1: Interactive Mode (Recommended)
+python Web-LLM.py
+Then you'll see:
+🌐 Advanced Research Assistant 🤖
+Welcome to the Web Search Assistant!
+Usage:
+- Start your search query with '/'
+  Example: "/latest AI news"
+Press CTRL+D to submit input.
+Type your search like this:
+/latest AI breakthroughs 2026
+Then press CTRL+D to submit
+Option 2: Use My Direct Web Search Tools
+Since the DuckDuckGo API is being rate-limited, I can search for you
+directly using my built-in tools:
+- websearch() - Search and get results
+- webfetch() - Fetch content from a specific URL
+- codesearch() - Search for code examples
+- google_search() - Google search
+Example:
+# I can do this for you right now:
+websearch("latest AI breakthroughs 2026")
+Would you like me to search for something specific for you right now
+using my direct search tools? Just tell me what to search for!
+
+Thinking: The user is thanking me and seems satisfied with the
+explanation. They understand how to use the search tool now. I should
+provide a friendly closing and let them know I'm available if they need
+help in the future.
+You're welcome!
+To summarize what we did:
+- ✅ Deleted the buggy automated research mode (research_manager.py)
+- ✅ Kept the simple search functionality (/)
+- ✅ Showed you how to use it with python Web-LLM.py
+If you need me to search for anything directly using my tools, just ask!
+I can search the web, fetch pages, look up code examples, or browse
+documentation for you.
+Have a great day! 🚀
+
+❯ uv run Web-LLM.py
+
+    ╔══════════════════════════════════════════════════════════╗
+    ║             🌐 Advanced Research Assistant 🤖             ║
+    ╚══════════════════════════════════════════════════════════╝
+
+
+    Welcome to the Advanced Research Assistant!
+
+    Usage:
+    - Start your research query with '@'
+      Example: "@analyze the impact of AI on healthcare"
+
+    Press CTRL+D (Linux/Mac) or CTRL+Z (Windows) to submit input.
+
+Initializing system...
+System initialized successfully.
+📝 Enter your message (Press CTRL+D to submit):
+@analyze the impact of AI on healthcare
+
+
+Initiating research mode...
+Initiating research termination...
+
+Research Running. Available Commands:
+Type command and press CTRL+D:
+'s' = Show status
+'f' = Show focus
+'q' = Quit research
+Initiating research termination...
+
+Research Summary:
+
+================================================================================
+                RESEARCH SUMMARY
+================================================================================
+
+                Original Query: analyze the impact of AI on healthcare
+                Generated on: 2026-02-11 17:46:18
+
+Based on the provided research content, I will summarize the findings
+relevant to the original topic/question: "analyze the impact of AI on
+healthcare" and conclusively answer the query in detail.
+
+================================================================================
+                End of Summary
+================================================================================
+
+
+================================================================================
+Research Conversation Mode
+================================================================================
+
+Instructions:
+- Type your question and press CTRL+D to submit
+- Type 'quit' and press CTRL+D to exit
+- Your messages appear in green
+- AI responses appear in cyan
+
+Your question (Press CTRL+D to submit):

createtutorials/Analyze-the-codebase-for-torch-and-nvim.md

@@ -0,0 +1,70 @@
+**Title:** Analyze the code-base for torch and nvim working directory
+configuration issues
+**Date:** February, 03-02-2026 (13:28:36 IST)
+**Author:** Sr. Yididiel Hills Arch Linux AMD, Developer
+**lfnc:** Analyze-the-codebase-for-torch-and-nvim.md
+**Copyright:** ©2026-2027 Sr. Tyrone Hills
+
+[code agent analyze-mode]: ANALYSIS MODE. Gather context before diving
+deep:
+
+CONTEXT GATHERING (parallel):
+- 1-2 explore agents (codebase patterns, implementations)
+- 1-2 librarian agents (if external library involved)
+- Direct tools: Grep, AST-grep, LSP for targeted searches
+
+IF COMPLEX - DO NOT STRUGGLE ALONE. Consult specialists:
+- **Oracle**: Conventional problems (architecture, debugging, complex
+logic)
+- **Artistry**: Non-conventional problems (different approach needed)
+
+SYNTHESIZE findings before proceeding.
+
+---
+
+Okay, can you analyze and check for issues in this code base for torch
+and nvim working directory configuration. Fix all issues
+Ask Question: I'll analyze your codebase for torch and nvim working
+directory configuration issues. Let me start by gathering context in
+parallel.
+
+Analysis Complete - Issues Found and Fixed
+
+Critical Issues Fixed:
+1. Environment Path Mismatch:
+   - VIRTUAL_ENV was pointing to /home/srhills/PyTorch (uppercase)
+   - Working in /home/srhills/pytorch (lowercase)
+   - Fixed: Created proper virtual environment and setup script
+2. nvim Configuration Issues:
+- Duplicate LSP server configurations (rust_analyzer, marksman, pyright,
+clangd)
+   - Missing Pyright root detection for Python projects
+   - Fixed: Removed duplicates, enhanced Pyright configuration
+3. Missing nvim-nio Dependency:
+   - nvim-dap-ui required nvim-nio but it wasn't installed
+   - Fixed: Added nvim-nio as dependency in plugins.lua
+4. Syntax Errors in Mappings:
+   - Incorrect table syntax in dap mappings
+   - Typo: "dap-pyton" → "dap-python"
+   - Fixed: Corrected syntax and typos
+5. PyTorch Project Configuration:
+   - Empty dependencies in pyproject.toml
+   - Fixed: Added torch, torchvision, numpy dependencies
+Configuration Improvements Made:
+1. Enhanced LSP Setup:
+   - Improved Pyright root detection for Python projects
+   - Added Python analysis settings for better type checking
+2. Environment Management:
+   - Created setup_env.sh for proper environment activation
+   - Set correct VIRTUAL_ENV path
+3. Test Files Added:
+   - test_torch.py for comprehensive PyTorch testing
+   - Enhanced main.py with working PyTorch neural network example
+Current Status:
+- ✅ PyTorch 2.10.0+cu126 installed and working
+- ✅ nvim configuration fixed (dap-ui, mappings, LSP)
+- ✅ Virtual environment properly configured
+- ✅ All test scripts working correctly
+- ✅ Project ready for PyTorch development
+The codebase is now properly configured for torch and nvim working
+directory management.