opencode-skills-collection 4.0.12 → 4.0.14

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-07-26T01:29:15.078Z",
+  "updatedAt": "2026-07-28T01:21:13.118Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -782,6 +782,7 @@
     "fda-food-safety-auditor",
     "fda-medtech-compliance-auditor",
     "feature-tracking",
+    "fedora-hyprland-installer",
     "ffuf-claude-skill",
     "ffuf-web-fuzzing",
     "figma-automation",
@@ -790,6 +791,7 @@
     "file-uploads",
     "filesystem-context",
     "find-bugs",
+    "find-complementary-founders",
     "finishing-a-development-branch",
     "firebase",
     "firecrawl-scraper",
@@ -1337,6 +1339,7 @@
     "optim-agent",
     "options-flow-analyzer",
     "oral-health-analyzer",
+    "orchestrate",
     "orchestrate-batch-refactor",
     "os-scripting",
     "oss-hunter",

package/bundled-skills/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,988+ skills."
+description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,991+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,988+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,991+ skills
 
 > **Custom-host integration:** This guide documents a low-level, direct-manifest lazy loader for Jetski/Cortex and similar hosts. For Codex or Claude Code, the recommended path is [AAS Core](../users/aas-core.md), which provides neutral, deterministic catalog retrieval and validates exact agent-selected IDs through a bounded, read-only MCP server.
 
@@ -25,7 +25,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With 1,988+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 1,991+ skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -23,7 +23,7 @@ This example shows one way to integrate **agentic-awesome-skills** with a Jetski
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 1,988+ skills installed.
+This pattern avoids context overflow when you have 1,991+ skills installed.
 
 Manifest contract references:
 

package/bundled-skills/docs/maintainers/aas-agent-first-control-plane-v1-design.md

@@ -131,7 +131,7 @@ The server exposes only:
 
 Full skill text is returned only on request and is separated as `untrustedContent`; metadata and prose cannot acquire instruction authority. The server can signal this trust boundary but cannot guarantee how an external model will behave.
 
-Every structured response declares `protocolVersion`, `coreVersion`, `metadataSchemaVersion`, `scorerVersion`, and catalog digest. Incompatible versions fail explicitly.
+Every structured response declares `protocolVersion`, `coreVersion`, `metadataSchemaVersion`, `scorerVersion`, and catalog digest. MCP initialization responds with the server-supported protocol revision so the client can accept it or disconnect; incompatible artifact and schema versions still fail explicitly.
 
 ## CLI lifecycle
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -29,7 +29,7 @@ Preferred homepage:
 Preferred social preview:
 
 - lead with `AAS Core` and the profile → stack → plan flow;
-- present `1,988+ Agentic Skills` as supporting catalog evidence, not a second product;
+- present `1,991+ Agentic Skills` as supporting catalog evidence, not a second product;
 - mention Codex and Claude as the current Core agent path, with broader host compatibility as distribution support;
 - avoid dense text and tiny logos that disappear in social cards.
 

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -72,7 +72,7 @@ The update process refreshes:
 - Canonical skills index (`skills_index.json`)
 - Compatibility mirror (`data/skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,988+ skills from the skills directory
+- All 1,991+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/users/aas-core.md

@@ -30,7 +30,7 @@ AAS MCP does not scan the repository and does not decide which skills are best.
 > **Release boundary:** AAS Core landed after release 14.6.0. Use an exact Core-capable release rather than an unreviewed moving tag.
 
 ```bash
-npm exec --yes --ignore-scripts --package=agentic-awesome-skills@15.4.0 -- aas mcp configure \
+npm exec --yes --ignore-scripts --package=agentic-awesome-skills@15.5.1 -- aas mcp configure \
   --host codex \
   --scope user \
   --config /absolute/path/to/codex/config.toml \

package/bundled-skills/docs/users/bundles.md

@@ -1062,4 +1062,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: June 2026 | Total Skills: 1,988+ | Total Bundles: 58_
+_Last updated: June 2026 | Total Skills: 1,991+ | Total Bundles: 58_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -17,7 +17,7 @@ Configure AAS Core for Claude Code, describe the task and constraints, let Claud
 - It lets Claude search the verified local catalog without loading the full library into context.
 - It preserves Claude's exact selection without using metadata as an eligibility gate.
 - It keeps MCP discovery read-only and CLI changes approval-gated.
-- It includes 1,988+ skills instead of a narrow single-domain starter pack.
+- It includes 1,991+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,988+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,991+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 1,988+ specialized areas
+- **Domain expertise** across 1,991+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture

package/bundled-skills/docs/users/usage.md

@@ -39,7 +39,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of AAS Core
 
 When you ran `npx agentic-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,988+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Downloaded 1,991+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
 ✅ **Made them available** to your AI assistant
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
@@ -231,7 +231,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Direct-install Step 5: Pick Skills Manually
 
-Don't try to use all 1,988+ skills at once. Here's a sensible approach:
+Don't try to use all 1,991+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -362,7 +362,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 1,988+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,991+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 

package/bundled-skills/docs/users/visual-guide.md

@@ -40,7 +40,7 @@ agentic-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 1,988+ skills live here
+├── 📁 skills/                          ← 1,991+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -53,7 +53,7 @@ agentic-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,988+ total)
+│   └── ... (1,991+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -106,7 +106,7 @@ agentic-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,988+ SKILLS          │
+                    │  1,991+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -207,7 +207,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,988+ total)                │
+│   └── ... (1,991+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/fedora-hyprland-installer/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Antigravity CLI Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/bundled-skills/fedora-hyprland-installer/README.md

@@ -0,0 +1,125 @@
+# 🏔️ hyprfedora
+
+> A safety-first agent skill that installs, configures, verifies, repairs, and removes Hyprland on Fedora Linux while preserving existing desktop packages and user backups.
+
+---
+
+## 🎯 Why This Project Exists
+
+Setting up Hyprland on Fedora can be tedious. You have to configure Wayland portals, sort out PipeWire audio, select launcher/terminal defaults, and configure GPU flags—especially if you're running NVIDIA or hybrid graphics.
+
+After installing this skill through your agent's supported skill mechanism, ask:
+
+> **"Install Hyprland on my Fedora system."**
+
+The agent inspects your system hardware, creates timestamped backups of existing settings, proposes Fedora package changes, and can create a minimal Hyprland configuration after you approve mutating steps. It detects GPU vendors but does not install or configure graphics drivers.
+
+---
+
+## ✨ Key Features
+
+- 🛡️ **Safety First & Mandatory Backups**: Never overwrites your existing `~/.config/hypr/` without creating a timestamped backup in `~/.local/state/fedora-hyprland-installer/backups/`.
+- 🐧 **Fedora-Native**: Built specifically for Fedora. Uses `dnf`, `systemctl`, and standard Fedora package repositories.
+- ⚡ **GPU Aware**: Detects NVIDIA, AMD Radeon, Intel, and hybrid setups and adds a conservative Hyprland-native cursor workaround for detected NVIDIA hardware.
+- 🤝 **Desktop Coexistence**: Never removes GNOME, KDE, or Xfce. Hyprland is added as a session option at your GDM/SDDM login screen.
+- 🛠️ **Scoped Repair**: Reports a missing config or portal package and inactive PipeWire/WirePlumber services; approved fixes can be applied with `repair.sh --apply`.
+- 🧼 **Scoped Removal**: Removes the listed Hyprland-specific packages while preserving your base desktop and backups.
+
+---
+
+## 📦 What Gets Installed
+
+When installing, the skill provisions a minimal, fast, and modern desktop stack:
+
+| Component | Package / Tool | Purpose |
+| :--- | :--- | :--- |
+| **Compositor** | `hyprland` | Dynamic tiling Wayland compositor |
+| **Terminal** | `kitty` | Fast, GPU-accelerated terminal |
+| **Launcher** | `wofi` | Application launcher menu |
+| **Status Bar** | `waybar` | Desktop panel & bar |
+| **Portals** | `xdg-desktop-portal-hyprland`, `xdg-desktop-portal-gtk` | Screen sharing & file dialogs |
+| **Audio** | `pipewire`, `wireplumber` | Low-latency audio & stream routing |
+| **Notifications** | `dunst` | Desktop notification daemon |
+| **Screenshots** | `grim`, `slurp`, `wl-clipboard` | Screen capture & clipboard support |
+
+---
+
+## 🚀 Quick Start & Usage
+
+### Agent usage
+
+Use the installation method documented by your agent or by the repository catalog, then invoke the skill in natural language. The skill does not assume a particular global directory or CLI executable.
+
+- **Fresh Install**: `"Install Hyprland on my Fedora machine."`
+- **Health Check**: `"Verify my Hyprland installation."`
+- **Troubleshoot & Fix**: `"Fix my screen sharing on Hyprland"` or `"Hyprland won't start."`
+- **Update Setup**: `"Update my Hyprland packages."`
+- **Uninstall**: `"Uninstall Hyprland."`
+
+---
+
+## 🛠️ Direct Terminal Utilities
+
+You can also run the built-in utilities in `scripts/` directly:
+
+```bash
+# Detect hardware, OS, and session information
+bash ./scripts/detect-system.sh
+
+# Detect GPU hardware (NVIDIA / AMD / Intel)
+bash ./scripts/detect-gpu.sh
+
+# Run preflight system verification
+bash ./scripts/preflight.sh
+
+# Verify health of your current Hyprland installation
+bash ./scripts/verify.sh
+
+# Run the isolated non-destructive test suite
+bash ./tests/test-scripts.sh
+```
+
+---
+
+## 📁 Repository Structure
+
+```text
+fedora-hyprland-installer/
+├── SKILL.md                 # Antigravity Agent Skill definition & workflow rules
+├── README.md                # Project documentation
+├── LICENSE                  # MIT License
+├── scripts/                 # Modular, safe shell scripts
+│   ├── detect-system.sh
+│   ├── detect-gpu.sh
+│   ├── preflight.sh
+│   ├── install.sh
+│   ├── configure.sh
+│   ├── verify.sh
+│   ├── backup.sh
+│   ├── repair.sh
+│   └── uninstall.sh
+├── references/              # Detailed knowledge base for Fedora, GPUs & Wayland
+│   ├── fedora.md
+│   ├── hyprland.md
+│   ├── nvidia.md
+│   ├── amd.md
+│   ├── intel.md
+│   ├── wayland.md
+│   ├── portals.md
+│   └── troubleshooting.md
+└── tests/                   # Safe, non-destructive test suite
+    ├── test-detection.sh
+    └── test-scripts.sh
+```
+
+---
+
+## 🤝 Contributing
+
+Contributions, bug reports, and improvements are welcome! Feel free to open an issue or submit a pull request on GitHub.
+
+---
+
+## 📜 License
+
+Distributed under the MIT License included in `LICENSE`.

package/bundled-skills/fedora-hyprland-installer/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: fedora-hyprland-installer
+description: Install, configure, verify, repair, update, and uninstall Hyprland on Fedora Linux with GPU-aware detection (NVIDIA/AMD/Intel).
+category: devops
+risk: critical
+source: community
+source_repo: maleksaadi0109/hyprfedora
+source_type: community
+date_added: "2026-07-26"
+author: maleksaadi0109
+tags: [fedora, hyprland, wayland, linux]
+tools: [claude, cursor, gemini]
+license: MIT
+license_source: https://github.com/maleksaadi0109/hyprfedora/blob/3ec6d4fc5eecdb188613dd841dce9926ae5c8319/LICENSE
+---
+
+# Fedora Hyprland Installer Skill
+
+This skill provides an automated, safety-first workflow for managing Hyprland on Fedora Linux.
+
+## Resolve the Skill Directory
+
+Before running a bundled script, resolve `SKILL_DIR` to the directory that
+contains this `SKILL.md`. Do not assume the user's current working directory or
+guess a global installation path. If the agent cannot resolve the installed
+skill directory from its runtime context, stop and ask the user to provide it.
+Invoke bundled shell files explicitly with `bash` and a quoted path, for
+example `bash "$SKILL_DIR/scripts/detect-system.sh"`.
+
+## When to Use
+
+- Use when installing or updating a Fedora-packaged Hyprland desktop stack.
+- Use when verifying a Hyprland session, portals, PipeWire, or WirePlumber on Fedora.
+- Use when diagnosing the limited repair cases documented below or removing the Hyprland-specific packages installed by this workflow.
+
+## Core Directives & Safety Rules
+
+1. **Fedora-First**: Always use Fedora tools (`dnf`, `systemctl`, `loginctl`). Never use `apt`, `pacman`, or `yay`.
+2. **Never Blindly Execute**: Inspect the system prior to any installation or modification.
+3. **Preserve Existing Desktop**: Do not uninstall GNOME, KDE, or any existing desktop environment. Hyprland should be added as a session choice in the display manager (GDM/SDDM/LightDM).
+4. **Mandatory Backup**: Always create a timestamped backup in `~/.local/state/fedora-hyprland-installer/backups/` before writing or altering configurations in `~/.config/hypr/`, `~/.config/waybar/`, etc.
+5. **GPU Awareness**: Check whether the system uses NVIDIA, AMD, Intel, or Hybrid graphics before configuring environment variables or graphics drivers. Never use arbitrary `.run` installers for NVIDIA; rely on Fedora/RPM Fusion repositories.
+6. **Privileged Operations**: Sudo commands must be clearly identified and communicated to the user. Do not hardcode passwords.
+7. **Idempotency**: Running actions multiple times must be safe and avoid duplicate config lines.
+8. **Explicit Consent**: Show the exact package or service changes first. Run scripts that mutate packages or services only after the user confirms; use `repair.sh` without `--apply` for diagnosis.
+
+---
+
+## Workflow Guide
+
+### 1. Installation Workflow
+When the user asks to **"Install Hyprland"** or **"Setup Hyprland on Fedora"**:
+1. Execute `bash "$SKILL_DIR/scripts/detect-system.sh"` and `bash "$SKILL_DIR/scripts/detect-gpu.sh"`.
+2. Execute `bash "$SKILL_DIR/scripts/preflight.sh"` to verify Fedora release, network, package manager, and sudo access.
+3. Execute `bash "$SKILL_DIR/scripts/backup.sh"` to preserve any pre-existing configurations.
+4. Show the package plan with `bash "$SKILL_DIR/scripts/install.sh" --dry-run`; after explicit approval, execute `bash "$SKILL_DIR/scripts/install.sh"` to install Hyprland, Wayland portal packages (`xdg-desktop-portal-hyprland`, `xdg-desktop-portal-gtk`), PipeWire/WirePlumber, terminal, launcher, status bar, and authentication agent.
+5. Execute `bash "$SKILL_DIR/scripts/configure.sh"` to write a clean, functional initial Hyprland config (`~/.config/hypr/hyprland.conf`) tailored to detected terminal/launcher and GPU environment variables.
+6. Execute `bash "$SKILL_DIR/scripts/verify.sh"` to ensure binaries, portal services, PipeWire, and login desktop entries (`/usr/share/wayland-sessions/hyprland.desktop`) exist and validate.
+7. Present a summary report detailing installed packages, backup paths, and login instructions.
+
+### 2. Repair Workflow
+When the user asks to **"Fix Hyprland"**, **"Hyprland won't start"**, **"No audio"**, **"Screen sharing broken"**:
+1. Run `bash "$SKILL_DIR/scripts/detect-system.sh"` and inspect system logs (`journalctl -xe`, `journalctl --user -u xdg-desktop-portal`).
+2. Execute `bash "$SKILL_DIR/scripts/repair.sh"` to report a missing Hyprland config, missing portal package, and inactive PipeWire/WirePlumber services.
+3. Review the proposed changes with the user, then execute `bash "$SKILL_DIR/scripts/repair.sh" --apply` only after approval. The script can create a missing config, install missing portal packages, and enable or restart the checked user services; investigate other faults manually.
+4. Execute `bash "$SKILL_DIR/scripts/verify.sh"`.
+
+### 3. Update Workflow
+When the user asks to **"Update Hyprland"**:
+1. Run `bash "$SKILL_DIR/scripts/backup.sh"`.
+2. Show the package plan with `bash "$SKILL_DIR/scripts/install.sh" --dry-run --update` and obtain approval.
+3. Update Hyprland and related Wayland packages via `bash "$SKILL_DIR/scripts/install.sh" --update`.
+4. Validate configuration syntax and verify system integrity via `bash "$SKILL_DIR/scripts/verify.sh"`.
+
+### 4. Uninstall Workflow
+When the user asks to **"Uninstall Hyprland"**:
+1. Explain to the user which packages will be removed.
+2. Run `bash "$SKILL_DIR/scripts/backup.sh"`.
+3. Show the removal list and obtain approval, then execute `bash "$SKILL_DIR/scripts/uninstall.sh" --yes` to remove the listed Hyprland-specific packages while preserving base desktop environments (GNOME/KDE) and user backup files.
+
+---
+
+## Reference Manuals
+
+- [Fedora Details](references/fedora.md)
+- [Hyprland Config Guide](references/hyprland.md)
+- [NVIDIA Setup & Wayland](references/nvidia.md)
+- [AMD Mesa Stack](references/amd.md)
+- [Intel Mesa Stack](references/intel.md)
+- [Wayland & Environment](references/wayland.md)
+- [Portals & PipeWire](references/portals.md)
+- [Troubleshooting Matrix](references/troubleshooting.md)
+
+## Examples
+
+Inspect the system and preview the package plan without changing it:
+
+```bash
+bash "$SKILL_DIR/scripts/detect-system.sh"
+bash "$SKILL_DIR/scripts/detect-gpu.sh"
+bash "$SKILL_DIR/scripts/install.sh" --dry-run
+```
+
+## Limitations
+
+- Bundled shell files are intentionally non-executable under the repository
+  safety policy and must be invoked explicitly with `bash` as shown above.
+- Fedora package availability varies by Fedora release and enabled repositories. This skill does not enable RPM Fusion or install GPU drivers.
+- GPU detection identifies vendors, not whether a proposed configuration is correct for a particular driver version, hybrid-graphics routing, monitor, or laptop.
+- The repair script covers only the checks it reports; it does not diagnose broken symlinks, kernel parameters, GPU driver mismatches, or every portal/audio failure.
+- Generated configuration is a minimal starting point and is not merged into an existing `hyprland.conf`.
+- Commands that install or remove packages, change services, or regenerate initramfs require review, explicit consent, and suitable privileges.

package/bundled-skills/fedora-hyprland-installer/references/amd.md

@@ -0,0 +1,10 @@
+# AMD Radeon Support
+
+## Driver Architecture
+AMD GPUs use open-source kernel drivers (`amdgpu`) and the Mesa graphics stack included in Fedora by default.
+
+## Verification
+- Verify Mesa openGL driver: `glxinfo | grep "OpenGL vendor"`
+- Verify RADV Vulkan driver: `vulkaninfo | grep driverName`
+
+No proprietary driver installation is required for Hyprland on AMD GPUs.

package/bundled-skills/fedora-hyprland-installer/references/fedora.md

@@ -0,0 +1,24 @@
+# Fedora Linux System Conventions
+
+## Package Management
+Fedora utilizes `dnf` as its primary package manager.
+
+```bash
+sudo dnf install <package>
+sudo dnf remove <package>
+sudo dnf check-update
+```
+
+## Desktop Sessions & Wayland
+Fedora Workstation uses Wayland by default with GDM (GNOME Display Manager) or SDDM (KDE).
+Session files are stored in:
+- `/usr/share/wayland-sessions/hyprland.desktop`
+- `/usr/share/xsessions/` (for X11 fallback sessions)
+
+## System Services
+User-level services are managed via systemd:
+```bash
+systemctl --user status pipewire
+systemctl --user status wireplumber
+systemctl --user status xdg-desktop-portal
+```

package/bundled-skills/fedora-hyprland-installer/references/hyprland.md

@@ -0,0 +1,22 @@
+# Hyprland Compositor & Configuration
+
+## Overview
+Hyprland is a dynamic tiling Wayland compositor that does not sacrifice appearance.
+
+## Key Config Locations
+- Main configuration: `~/.config/hypr/hyprland.conf`
+- Additional split configs: `~/.config/hypr/monitors.conf`, `~/.config/hypr/keybinds.conf`
+
+## Common Keybindings (Default Base)
+- `SUPER + RETURN`: Open terminal
+- `SUPER + SPACE`: Application launcher (`wofi` / `rofi`)
+- `SUPER + Q`: Close focused window
+- `SUPER + M`: Exit Hyprland session
+- `SUPER + R`: Reload Hyprland config
+
+## Monitor Syntax
+```text
+monitor=name,resolution@hz,position,scale
+# Example auto monitor setup:
+monitor=,preferred,auto,1
+```

package/bundled-skills/fedora-hyprland-installer/references/intel.md

@@ -0,0 +1,8 @@
+# Intel Graphics Support
+
+## Driver Architecture
+Intel Integrated & Arc graphics utilize kernel drivers (`i915` or `xe`) and the Mesa Intel driver (`iris` / `ANV`).
+
+## Verification
+- Verify hardware acceleration: `vainfo`
+- Check active driver: `lspci -nnk | grep -A 2 VGA`

package/bundled-skills/fedora-hyprland-installer/references/nvidia.md

@@ -0,0 +1,29 @@
+# NVIDIA Support on Fedora Wayland / Hyprland
+
+## Recommended Environment Variables
+Some NVIDIA setups may require Wayland environment flags in `~/.config/hypr/hyprland.conf`; confirm them against the installed driver and Hyprland versions:
+
+```text
+env = LIBVA_DRIVER_NAME,nvidia
+env = GBM_BACKEND,nvidia-drm
+env = __GLX_VENDOR_LIBRARY_NAME,nvidia
+env = NVD_BACKEND,direct
+```
+
+For cursor rendering issues, use the Hyprland-native config option (Hyprland v0.36+):
+```text
+cursor {
+    no_hardware_cursors = true
+}
+```
+
+> **Note**: The old `WLR_NO_HARDWARE_CURSORS=1` environment variable is **deprecated** since Hyprland v0.36+. Use the `cursor` config block above instead.
+
+## Drivers on Fedora
+If proprietary drivers are required, use packages maintained for Fedora, such as RPM Fusion's `akmod-nvidia`, after reviewing that repository's setup guidance. This skill does not enable RPM Fusion or install GPU drivers.
+Never use raw `.run` installers from NVIDIA's website as they break Fedora kernel updates.
+
+## Hybrid Graphics (Intel + NVIDIA / AMD + NVIDIA)
+Laptops with dual GPUs may need additional configuration:
+- Check active GPU: `supergfxctl` or `prime-run`
+- Verify render offloading: `__NV_PRIME_RENDER_OFFLOAD=1 glxinfo | grep vendor`

package/bundled-skills/fedora-hyprland-installer/references/portals.md

@@ -0,0 +1,18 @@
+# XDG Desktop Portals & PipeWire
+
+## Portals Requirement
+For screen sharing, file open dialogs, and screenshots under Hyprland:
+- `xdg-desktop-portal`
+- `xdg-desktop-portal-hyprland`
+- `xdg-desktop-portal-gtk`
+
+## Service Startup Order
+```text
+Hyprland starts
+  └─ exec-once = dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
+      └─ systemctl --user restart xdg-desktop-portal
+```
+
+## Audio Architecture
+PipeWire handles low-latency audio and video streams (screen sharing). WirePlumber manages session routing.
+Status check: `wpctl status`

package/bundled-skills/fedora-hyprland-installer/references/troubleshooting.md

@@ -0,0 +1,53 @@
+# Hyprland Troubleshooting Matrix
+
+## Symptom 1: Black Screen on Boot (NVIDIA)
+- **Cause**: Missing Wayland environment variables or modeset issue.
+- **Investigation**: Check the installed NVIDIA driver documentation and whether `nvidia_drm.modeset=1` is active. If the symptom is specifically cursor-related, test `cursor { no_hardware_cursors = true }` in `hyprland.conf`.
+
+## Symptom 2: Screen Sharing Not Working (OBS / Browser)
+- **Cause**: Inactive portal or pipewire environment variable missing.
+- **Fix**: Run:
+  ```bash
+  systemctl --user restart xdg-desktop-portal-hyprland
+  systemctl --user restart xdg-desktop-portal
+  ```
+
+## Symptom 3: No Sound Output
+- **Cause**: PipeWire or WirePlumber service failed.
+- **Fix**: Run:
+  ```bash
+  systemctl --user restart pipewire wireplumber
+  ```
+
+## Symptom 4: Cursor Missing or Invisible (NVIDIA)
+- **Cause**: Hardware cursor rendering not supported by GPU driver.
+- **Fix**: Add to `hyprland.conf`:
+  ```text
+  cursor {
+      no_hardware_cursors = true
+  }
+  ```
+
+## Symptom 5: Apps Blurry or Wrong Scale (XWayland)
+- **Cause**: XWayland apps not using native Wayland rendering.
+- **Fix**: Set environment variables in `hyprland.conf`:
+  ```text
+  env = GDK_BACKEND,wayland,x11
+  env = QT_QPA_PLATFORM,wayland;xcb
+  env = MOZ_ENABLE_WAYLAND,1
+  ```
+
+## Symptom 6: Multi-Monitor Not Working
+- **Cause**: Incorrect or missing monitor config.
+- **Fix**: Check connected monitors with `hyprctl monitors` and configure in `hyprland.conf`:
+  ```text
+  monitor=,preferred,auto,1
+  ```
+
+## Symptom 7: Flickering / Tearing (NVIDIA)
+- **Cause**: Missing DRM kernel module setting.
+- **Investigation**: Confirm the installed driver's recommended DRM settings before changing boot configuration. If its documentation requires these options, review and add them to `/etc/modprobe.d/nvidia.conf`:
+  ```text
+  options nvidia_drm modeset=1 fbdev=1
+  ```
+  Regenerating initramfs with `sudo dracut --force` is a privileged, boot-critical change. Back up the current configuration and obtain explicit approval before running it.

package/bundled-skills/fedora-hyprland-installer/references/wayland.md

@@ -0,0 +1,9 @@
+# Wayland Session Environment
+
+## Key Environment Variables
+- `XDG_CURRENT_DESKTOP=Hyprland`
+- `XDG_SESSION_TYPE=wayland`
+- `XDG_SESSION_DESKTOP=Hyprland`
+- `MOZ_ENABLE_WAYLAND=1` (Firefox Wayland native mode)
+- `QT_QPA_PLATFORM=wayland;xcb` (Qt app compatibility)
+- `GDK_BACKEND=wayland,x11` (GTK app compatibility)