Skip to content
View Gerrrt's full-sized avatar
⌨️
How does one code?
⌨️
How does one code?

Block or report Gerrrt

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Gerrrt/README.md

👋

$ whoami
red/blue operator · CLI craftsman · builder of an over-engineered terminal

.files ⌨️

I build a cross-platform dotfiles fleet — a unified Zsh · Neovim · Tmux environment that feels identical on macOS, Windows/WSL2, and a rack of Linux distros, with optional red (offensive) and blue (defensive) layers bolted on top.

Live showcase Core


🧬 The architecture (the part that makes it interesting)

Three layers. One source of truth. No copy-paste.

            ┌─────────────────────────┐
            │      dotfiles-core      │   authored ONCE
            │  zsh · nvim · tmux ·    │
            │   git · starship        │
            └────────────┬────────────┘
                         │  git subtree  (vendored, self-contained)
       ┌─────────┬───────┼───────┬─────────┐
       ▼         ▼       ▼       ▼         ▼
    macOS     Linux ×5  Kali 🔴  Defense 🔵  …each clone stands alone
   (OS layer)         (role layer)
  • Core — identical on every machine, authored once, fanned out via git subtree.
  • OS-native — package manager, clipboard, paths. The only per-OS surface.
  • Role — offensive (Kali) and defensive (Defense) tradecraft on top.

A green make audit in dotfiles-core gates every change before Core is vendored out. Nothing ships red.


🗺️ The Fleet

Repo What it is
🧬 dotfiles-core The shared core — authored once, vendored everywhere
🍎 dotfiles-MacBook macOS — Homebrew, AeroSpace tiling, desktop tooling
🪟 dotfiles-Windows Windows host — PowerShell, Terminal, WSL2 bridge
🐧 Linux Arch · Fedora · openSUSE · Gentoo · Alpine
🔴 dotfiles-Kali Offensive role layer — recon → exploit → evasion
🔵 dotfiles-Defense Defensive role layer — detection & hunt tooling
🌐 dotfiles-web The public showcase + docs site

🔴🔵 The part I think is kinda cool

htpx is a structured, ATT&CK-tagged, red↔blue-paired corpus — every attack technique sits beside its detection. One source of truth drives both the offensive cheatsheet and the purple-team detections. Fast modern-CLI configs are a commodity; a paired methodology corpus is not. That's the thing worth stealing.


📡 Reach me

Email

Built to be stolen from. Or borrowed. Or… whatever.

Pinned Loading

  1. dotfiles-core dotfiles-core Public

    🧬 The shared Core of a cross-platform dotfiles system — zsh · nvim · tmux · starship, authored once and vendored into every OS. Zero drift.

    Shell

  2. dotfiles-MacBook dotfiles-MacBook Public

    🍎 The macOS layer — Homebrew, AeroSpace tiling, sketchybar & karabiner, over a shared zsh/nvim/tmux core. Keyboard-driven, drift-free.

    Shell

  3. dotfiles-Windows dotfiles-Windows Public

    🪟 The Windows host layer — PowerShell, Windows Terminal, scoop/winget, psmux (native tmux) & the WSL2 bridge. A first-class CLI on Windows.

    PowerShell

  4. dotfiles-Kali dotfiles-Kali Public

    🔴 The offensive role layer — recon→exploit→evasion field refs (hacktheplanet/exploitdev) on a Kali/WSL2 base. Engagement-ready.

    Shell

  5. dotfiles-web dotfiles-web Public

    🌐 The public showcase & docs for a cross-platform dotfiles system. Built with Astro, themed Tokyo Night, shipped on GitHub Pages.

    Astro