Refine and populate documentation for Terminal tools and shell environment according to Antigravity spec

Author: shadil-rayyan

Antigravity.md

@@ -0,0 +1,147 @@
+# CodeCampus OS — Official User Guide Specification
+
+## Purpose
+
+This document defines the writing standards for the CodeCampus OS User Guide.
+
+The guide is designed for:
+- Beginner software engineers
+- Computer Science & Engineering (CSE) students
+- Self-learners who are new to Linux-based development environments
+
+The goal is **not** to simply list tools, but to teach students:
+- What each tool is
+- Why it exists
+- How it is used in real-world software development workflows
+
+CodeCampus differentiates itself from other setups (such as Omakub) by providing:
+- Deep, student-focused explanations
+- Clear installation instructions for multiple Linux distributions
+- Practical guidance instead of surface-level descriptions
+
+---
+
+## Writing Style Rules
+
+- Clear, direct, and professional
+- Beginner-friendly, but **never dumbed down**
+- No marketing language
+- No generic or AI-style filler content
+- Prefer explanations over buzzwords
+- Assume curiosity and willingness to learn, not prior expertise
+
+---
+
+## Required Structure for Every Tool Section
+
+Every tool **must** follow the structure below exactly.
+
+---
+
+## Tool Name
+
+Use a clear and descriptive main heading.
+
+Example:
+```markdown
+## Git
+````
+
+---
+
+### What is it?
+
+Explain:
+
+* What the tool is
+* What problem it solves
+* Where it fits in the software development ecosystem
+
+This section must be understandable to a first-year CS student with minimal prior exposure.
+
+---
+### Installation (Optional)
+
+!!! note
+    CodeCampus OS includes this tool by default.
+    Use the commands below only if installing on another distribution.
+
+=== "Ubuntu / Debian"
+    ```bash
+    sudo apt install git
+    ```
+
+=== "Arch / Manjaro"
+    ```bash
+    sudo pacman -S git
+    ```
+
+=== "Fedora"
+    ```bash
+    sudo dnf install git
+    ```
+
+=== "openSUSE"
+    ```bash
+    sudo zypper install git
+    ```
+
+### Why this tool matters (In Depth)
+
+This is the **most important section**.
+
+Explain in detail:
+
+* Why students should care about this tool
+* How it improves productivity or understanding
+* What problems students will face without it
+* Where and how it is used in real-world projects
+
+Write this as a thoughtful explanation, not bullet-point hype.
+
+---
+
+### How students will actually use it
+
+Explain:
+
+* Common real-world usage scenarios
+* Typical beginner-level workflows or commands
+* How the tool fits into daily development work
+
+If commands are shown, clearly explain **what each command does and why it is used**.
+
+---
+
+### Professional Insight (Top 1% Knowledge)
+
+Provide insight that:
+
+* Beginners usually do not know
+* Reflects how experienced engineers think about this tool
+* Helps students avoid common mistakes or bad habits
+
+This section should feel like advice from a senior engineer or mentor.
+
+---
+
+## Formatting Rules
+
+* Use Markdown headings only
+* Use tables **only** for installation instructions
+* Avoid emojis
+* Avoid unnecessary bullet lists
+* Prefer clear paragraphs and explanations
+
+---
+
+## End Goal
+
+After reading a tool section, a student should:
+
+* Understand **why** the tool exists
+* Know **how** to install it on their Linux distribution
+* Know **when and how** to use it correctly
+* Feel confident exploring the tool further on their own
+
+

docs/Desktop/launchers/ulancher.md

@@ -0,0 +1,50 @@
+# Ulauncher
+
+### What is it?
+
+Ulauncher is a fast, keyboard-driven application launcher for Linux. It is designed to help users find and open applications, search through files, and perform system tasks without ever moving their hands away from the keyboard. For developers, it serves as the central interface for navigating their operating system, analogous to Alfred on macOS.
+
+### Installation (Optional)
+
+!!! note
+    CodeCampus OS includes Ulauncher by default.
+    Use the commands below only if you are installing it on a different Linux distribution.
+
+=== "Ubuntu / Debian"
+    ```bash
+    sudo add-apt-repository ppa:agornostal/ulauncher
+    sudo apt update
+    sudo apt install ulauncher
+    ```
+
+=== "Arch / Manjaro"
+    ```bash
+    sudo pacman -S ulauncher
+    ```
+
+=== "Fedora"
+    ```bash
+    sudo dnf install ulauncher
+    ```
+
+### Why this tool matters (In Depth)
+
+In professional software development, maintaining focus and minimizing friction are essential for productivity. Every time a developer lifts their hand from the keyboard to navigate a graphical menu with a mouse, they incur a cognitive "context switch" penalty. While seemingly minor, these interruptions break the "flow state"—the period of deep concentration required for complex problem-solving.
+
+Ulauncher eliminates this friction by providing a unified, keyboard-first command interface. Beyond simple application launching, it reduces the need to navigate through complex file structures or multiple browser tabs for simple tasks. By integrating system commands, file searches, and web shortcuts into a single prompt, Ulauncher allows you to navigate your entire development environment at the speed of thought. Mastering a launcher is a fundamental step in transitioning from a casual user to a high-output software engineer.
+
+### How students will actually use it
+
+Students will primarily use Ulauncher to navigate their daily development environment without distraction:
+
+*   **Launching Applications:** Press `Alt + Space` and type the first few letters of your tool (e.g., `cod` for VS Code, `ter` for Terminal) and hit Enter.
+*   **Quick Calculations:** Perform math directly in the search bar (e.g., `2^10` or `150 * 1.05`) to avoid opening a separate calculator application.
+*   **File and Folder Search:** Find specific project directories or configuration files instantly without browsing through a file manager.
+*   **Web Search Shortcuts:** Use predefined keywords to search the web. For example, typing `g react hooks` will immediately open a Google search in your browser, saving you the steps of opening the browser and navigating to the search bar.
+
+### Professional Insight (Top 1% Knowledge)
+
+The true power of Ulauncher lies in its community-driven extensions. While beginners use it as a simple search bar, experienced engineers use it to bridge disparate workflows. You should explore extensions that allow you to search your clipboard history, manage Docker containers, or open specific VS Code projects directly from the launcher.
+
+A professional habit is the rigorous minimization of keystrokes. You can customize keyword triggers for your most frequent tasks—for example, reducing the StackOverflow search trigger to a single letter `s`. This creates a personalized, high-speed command center where any developer task is only two or three keystrokes away. Reaching this level of muscle memory separates senior engineers who can navigate systems effortlessly from those who are slowed down by their interface.
+

docs/Desktop/learning/codecompass.md

@@ -0,0 +1,75 @@
+
+## CodeCompass – Official Website
+
+**CodeCompass** is the **official hub** for everything related to the Codekub learning ecosystem.
+
+It brings together:
+
+* Beginner guides
+* Tool explanations
+* Learning resources
+* Developer workflows
+
+CodeCompass helps students understand **not just what to install, but why they are using it**.
+
+---
+
+## CSE Starter Kit
+
+The **CSE Starter Kit** is a beginner-focused section of CodeCompass.
+
+It is designed for:
+
+* First-year CSE / IT students
+* Programming beginners
+* Students new to Linux and developer tools
+
+What it contains:
+
+* Step-by-step beginner guides
+* Clear explanations of tools (Git, Docker, Neovim, VS Code, etc.)
+* Learning paths for programming and system tools
+* No assumptions of prior knowledge
+
+Think of it as:
+
+> **“Everything a CSE student wishes they had on day one.”**
+
+---
+
+## DevSetup
+
+**DevSetup** is a practical tools page.
+
+It provides:
+
+* Ready-to-use terminal commands
+* One-line installers
+* Setup instructions for development tools
+
+Purpose:
+
+* Save time
+* Avoid setup mistakes
+* Ensure consistent environments
+
+Instead of searching random blogs, you get **tested, copy-paste-safe commands**.
+
+---
+
+## Repeto
+
+**Repeto** focuses on **real-world experience and opportunities**.
+
+It covers:
+
+* Internships
+* Research opportunities
+* Hackathons
+* Repeated practice & application learning
+
+Why it exists:
+
+* Beginners often learn tools but don’t know **where to apply them**
+* Repetro bridges the gap between **learning and experience**
+

docs/Desktop/learning/distrosea.md

@@ -0,0 +1,41 @@
+# DistroSea
+
+### What is it?
+
+DistroSea is a web-based platform that allows users to run and explore various Linux distributions directly within a browser without any local installation. It provides a virtualization layer that hosts a remote Linux environment, which users interact with through a browser-based desktop or terminal interface.
+
+In the Linux ecosystem, DistroSea serves as an **exploration and evaluation tool**. It is designed to help users experiment with different operating systems and desktop environments (like GNOME, KDE Plasma, or XFCE) before committing to a permanent installation on their hardware.
+
+### Installation (Optional)
+
+!!! note
+    DistroSea is a web-based service and does not require installation.
+    It is accessible via any modern web browser.
+
+*   **Website:** [distrosea.com](https://distrosea.com/)
+
+### Why this tool matters (In Depth)
+
+For students entering the Linux world, the primary barrier to entry is fragmentation. With hundreds of distributions and dozens of desktop environments available, choosing a starting point can be overwhelming. DistroSea matters because it **lowers the cost of experimentation to zero**. 
+
+By providing a sandboxed, disposable environment, it allows students to overcome the "fear of breaking things" that often accompanies a first-time Linux installation. It allows them to observe how different package managers (like `apt`, `pacman`, or `dnf`) work in practice and how various systems handle default configurations. This hands-on experience transforms abstract knowledge about "Linux distros" into concrete technical understanding, leading to more informed decisions about their own development environment.
+
+### How students will actually use it
+
+Students will use DistroSea as a safe playground for system exploration:
+
+*   **Distro Hopping (Risk-Free):** Testing multiple distributions—such as Ubuntu, Arch Linux, or Fedora—to compare their user interfaces and default toolsets.
+*   **Desktop Environment Evaluation:** Launching different versions of the same distro to see whether they prefer the workflow of GNOME, the customization of KDE, or the minimalism of XFCE.
+*   **Safe Command Practice:** Using the browser terminal to practice high-risk commands (like modifying filesystem tables or system configurations) without any risk to their host machine.
+*   **Quick Troubleshooting:** Verifying if a specific software package or configuration behaves differently on a clean, remote distribution compared to their local setup.
+
+### Professional Insight (Top 1% Knowledge)
+
+Experienced engineers treat DistroSea as a **pre-flight verification tool**. While it is not a substitute for a local development environment, a professional uses it to quickly verify the layout or default behavior of a system they might soon be deploying to a server or a client's machine.
+
+A professional habit is to use tools like this to **audit default environments**. For example, an engineer might launch a DistroSea session simply to check which version of a library or kernel a specific distro ships with by default. This saves the time of downloading a multi-gigabyte ISO and setting up a local virtual machine just for a five-minute check. 
+
+The "Top 1%" insight here is understanding the **limitations of the abstraction**. A senior engineer knows that a browser-based session will never reflect the true latency, hardware compatibility, or performance of a bare-metal installation. They use DistroSea to judge "logic and layout," while reserving "performance and stability" judgements for a local, dedicated environment. Use DistroSea to narrow your choices, but always perform your final benchmarks on your actual hardware.
+
+
+

docs/Desktop/learning/education.md

@@ -0,0 +1,42 @@
+# Educational Resources
+
+### What is it?
+
+Educational resources in the software development ecosystem are curated platforms—such as Exercism, MIT OpenCourseWare, and The Missing Semester—that provide structured paths for learning computer science fundamentals, programming languages, and professional engineering tools. These resources bridge the gap between casual interest and professional proficiency by offering high-quality, often free, curricula.
+
+In the software development ecosystem, these platforms belong to the **lifelong learning and skill-acquisition layer**. They allow students to follow standardized, university-grade curricula or focused technical paths at their own pace, independent of traditional institutional constraints.
+
+### Installation (Optional)
+
+!!! note
+    These resources are web-based platforms accessible through a browser.
+    Recommended starting points include:
+
+*   **MIT Missing Semester:** [missing.csail.mit.edu](https://missing.csail.mit.edu/)
+*   **Exercism:** [exercism.org](https://exercism.org/)
+*   **MIT OpenCourseWare:** [ocw.mit.edu](https://ocw.mit.edu/)
+*   **The Odin Project:** [theodinproject.com](https://theodinproject.com/)
+
+### Why this tool matters (In Depth)
+
+A university degree often focuses on theoretical computer science, sometimes neglecting the practical day-to-day tools used in the industry. Conversely, many online tutorials focus only on "how to build" without explaining "how it works." Educational resources matter because they allow students to **fill these critical gaps**.
+
+Platforms like "The Missing Semester" are particularly important because they teach the manual skills—shell scripting, version control, and debugging—that senior engineers expect but universities rarely teach formally. Exercism matters because it provides a **mentor-driven feedback loop**; writing code is one thing, but having a senior engineer review your implementation of an algorithm provides insights into idiomatic patterns and code quality that self-study alone cannot provide.
+
+For students, these resources provide a way to build a "T-shaped" skill set—deep expertise in one area (like web development via The Odin Project) combined with a broad understanding of computer science fundamentals (via OSSU or MIT OCW). This breadth and depth are what define a prepared engineering candidate in the modern job market.
+
+### How students will actually use it
+
+Students will use these resources to build a comprehensive and practical engineering foundation:
+
+*   **Closing Tool Gaps:** Following "The Missing Semester" to master the Linux terminal, Git, and Vim, ensuring they are productive in a professional environment.
+*   **Language Proficiency:** Using Exercism to solve dozens of small, focused problems in a new language (like Go or Rust) to internalize its syntax and best practices.
+*   **Project-Based Learning:** Following "The Odin Project" or "freeCodeCamp" to build real-world applications (like a terminal-based game or a web server) for their portfolio.
+*   **Deep Theory:** Watching MIT OCW lectures on "Introduction to Algorithms" or "Operating Systems" to build the theoretical foundation necessary for senior-level systems design.
+*   **Community Mentorship:** Participating in Exercism's mentorship program to learn how experienced developers think about code structure and performance.
+
+### Professional Insight (Top 1% Knowledge)
+
+The "Top 1%" of engineers don't stop using these resources once they get a job. They treat their education as a **perpetual engineering project**. A senior developer might return to Exercism to learn a functional language (like Haskell) just to expand their mental models of data flow, or revisit an MIT OCW course on distributed systems when their team is scaling an application.
+
+A professional habit is to **curate your own curriculum**. Don't just follow a platform blindly; analyze your weaknesses and find the world-class resource that addresses them. Furthermore, understand the value of **mentorship and code review**. The fastest way to grow is to have your code torn apart by someone better than you. By actively seeking feedback on platforms like Exercism, you develop the thick skin and analytical eye necessary to succeed in high-stakes professional environments. Treat these resources not as "homework," but as your personal research and development department.