This repository is a structured and centralized collection of my personal system configurations, workflow customizations, and environment-level adjustments for development tools and general software setups.
The primary objective of this project is not instructional. It is not intended to replace official documentation or provide comprehensive step-by-step guides. Instead, it functions as a curated archive of ready-to-use configuration files that represent how I structure, optimize, and maintain my working environment.
To maintain consistency across different tools and components, each section of this repository may follow a standardized documentation structure. When applicable, the following topics are used:
-
Overview: A brief description of what the tool or tweak is, its main purpose, and why it is relevant. May include a link to the official documentation and minimal installation guidance when necessary. -
Configurations: Links to the configuration files provided in this repository, with a short explanation of their structure and what aspects of the tool they control. -
Inspirations: References to themes, repositories, or style guides that influenced the visual design or structural approach, when applicable. -
Tips: Practical notes and small technical clarifications that help avoid common mistakes or improve compatibility and usability. -
Known Issues: A short summary of limitations or edge cases, with links to official documentation or issue trackers when relevant.
The emphasis is on standardization, organization, and portability. All files are grouped into dedicated directories with clear naming conventions, ensuring that the repository remains maintainable and easy to navigate. The structure is intentionally uniform to reduce friction for anyone who wants to reuse or adapt the configurations.
If you find any part of this repository useful, feel free to copy, adapt, or fork it according to your own requirements. It should be viewed as a practical reference implementation rather than a prescriptive standard.
Important
Some configurations may assume familiarity with the associated tools, as the focus is on sharing finalized setups rather than explaining every individual configuration decision.
The
command-line interface
is a central component of the development workflow, and small adjustments to its
appearance and behavior can significantly improve readability and overall
efficiency. This section documents a set of lightweight customizations for
Windows Terminal and
Windows PowerShell,
focusing on elements such as color schemes, font configuration, prompt
structure, and general terminal behavior. The intention is to create a cleaner
and more consistent terminal environment while keeping the setup simple,
portable, and easy to reproduce across systems.
Configuration in this section includes setting up PowerShell, applying Windows
Terminal themes, installing
Nerd Fonts for extended glyph
support, customizing the prompt with
Oh My Posh, displaying
system information with
FastFetch, and enhancing
folder and file visualization using
Terminal Icons. Detailed
installation and configuration steps are documented separately to keep this
section concise. See Installation Guide for the
full setup process.
You can access my configuration file here:
The CLI setup uses a few JSON files, each handling a specific aspect of
terminal behavior, appearance, or profile settings for easy management and
portability:
-
Defaults configuration: Defines global terminal settings, including color scheme, font, cursor style, opacity, padding, and window behavior. These defaults apply to all profiles to ensure a consistent environment. -
Profile adjustments: Contains profile-specific settings such as command line arguments, tab layout, and session behavior, allowing finer control over individual terminal sessions. -
Color scheme: Stores the terminal’s color palette, controlling foreground, background, cursor, and selection colors. This file can be swapped or modified to change the visual appearance without affecting other configurations.
Prompt customization is handled via Oh My Posh, initialized through the PowerShell profile ($PROFILE). The profile loads a theme JSON stored locally, which defines the segments and visual structure of the prompt. This setup ensures that every new shell session automatically applies the configured prompt and visual elements.
FastFetch configuration works similarly and also uses a JSON-based format. It defines which modules are shown, their layout, and styling. You can use pre-made presets or customize it manually to adjust the information and appearance displayed in the terminal
The prompt design for Oh My Posh in this setup was created from scratch, but
its structure and segment layout were guided by existing examples for practical
reference. The YS Theme served as
a key inspiration, providing a clear and organized approach to segment
placement, symbols, and overall prompt flow.
For the color palette, inspiration came from the
Catppuccin theme, whose soft and
balanced tones were used as a reference to ensure readability and visual harmony
across the prompt. Combining these influences allowed the prompt to maintain
both a functional structure and an appealing, consistent aesthetic.
The FastFetch configuration was also inspired by existing presets. Its layout and module arrangement took cues from organized examples in the FastFetch Presets repository. These references helped create a setup that is both functional and visually cohesive.
| Theme Name | Theme Source |
|---|---|
| Theme 26 | Repository |
| Theme 10 | Repository |
| Theme 6 | Repository |
If you wish to explore additional pre-made themes, you can find ready-to-use
color schemes for Windows Terminal on the
Windows Terminal Themes website.
These themes can be applied directly to your terminal or used as inspiration to
create your own custom color scheme.
For Oh My Posh prompts, a variety of themes are available on the
Oh My Posh Themes page. You can
download these themes or adapt them to customize the appearance and layout of
your prompt.
Pre-made themes are also available on the
FastFetch Presets
page. These presets let you quickly customize the information displayed in your
terminal. Instead of creating a configuration from scratch, you can use an
existing preset as a base and modify it to match your preferred layout, colors,
and modules.
Some users may choose to install
PowerShell 7
for improved performance, cross-platform compatibility, and access to the latest
features. Once installed, all terminal configurations, Oh My Posh themes, and
font settings can be applied directly in PowerShell 7 instead of the traditional
Windows PowerShell:
winget install --id Microsoft.PowerShell --source wingetWhile this CLI configuration provides a streamlined and visually consistent environment, there are some limitations to be aware of. Certain color or font settings may render differently depending on the terminal version or system display scaling.
Oh My Posh prompt themes rely on the profile loading correctly. If the PowerShell execution policy restricts script running, the prompt may fail to initialize until the policy is adjusted. Similarly, Fastfetch output can vary depending on the system's hardware, OS version, or installed permissions, and some sections may not display if required system information is unavailable. Using Fastfetch ensures a quick system summary, but its appearance may change across different setups.
Finally, updates to Windows Terminal, PowerShell, or Oh My Posh may occasionally introduce changes that require reapplying or adjusting these configuration files to maintain full compatibility, including any Fastfetch customizations.
Komorebi is a tiling window
manager for Windows that automatically organizes open application windows into
structured layouts. Instead of manually resizing and positioning windows, it
arranges them in predefined tiling patterns, improving productivity and workflow
efficiency. It is especially useful for users who prefer keyboard-driven
navigation and a more organized desktop experience.
To install Komorebi, you can download it directly from the official repository
or install it using a package manager. After installation, you may need to
configure it and set it to start with Windows. Since the steps can vary, it’s
important to follow the official
documentation
to ensure everything is set up correctly.
Warning
The documentation provides important recommendations, such as:
enabling long path support
and
disabling unnecessary system animations.
You can access my configuration file here:
Komorebi is configured primarily through the
komorebi.json
file, where you define layouts, workspace behavior, window rules, and general
manager settings. This file controls how windows are arranged, how many
workspaces are available, and how specific applications should behave.
A
whkdrc
file is used by WHKD, a Windows hotkey
daemon, to map key combinations to commands. WHKD essentially runs
Komorebic
in the background, interpreting the whkdrc bindings and executing actions. In
Komorebi, it manages shortcuts for controlling the window manager, such as
changing layouts, moving windows, switching workspaces, and resizing containers.
Here is a table showing the keybindings from my personal whkdrc configuration:
| Shortcut | Action Description |
|---|---|
| alt + escape | Close the current window |
| alt + a | Move focus to the window on the left |
| alt + s | Move focus to the window below |
| alt + w | Move focus to the window above |
| alt + d | Move focus to the window on the right |
| win + a | Shift the current window left |
| win + s | Shift the current window down |
| win + w | Shift the current window up |
| win + d | Shift the current window right |
| alt + space | Swap or promote the current window |
| alt + z | Toggle floating mode |
| alt + x | Toggle monocle mode (maximized window) |
| alt + r | Stack the window to the left |
| alt + f | Stack the window downward |
| alt + t | Stack the window upward |
| alt + g | Stack the window to the right |
| alt + c | Remove window from stack |
| alt + q | Go to previous stacked window |
| alt + e | Go to next stacked window |
| alt + oem_plus (+) | Widen window horizontally |
| alt + oem_minus (-) | Narrow window horizontally |
| alt + shift + oem_plus (+) | Increase window height |
| alt + shift + oem_minus (-) | Decrease window height |
| alt + 1 | Switch to workspace 0 |
| alt + 2 | Switch to workspace 1 |
| alt + 3 | Switch to workspace 2 |
| alt + 4 | Switch to workspace 3 |
| alt + 5 | Switch to workspace 4 |
| alt + 6 | Switch to workspace 5 |
| win + 1 | Move window to workspace 0 |
| win + 2 | Move window to workspace 1 |
| win + 3 | Move window to workspace 2 |
| win + 4 | Move window to workspace 3 |
| win + 5 | Move window to workspace 4 |
| win + 6 | Move window to workspace 5 |
| ctrl + alt + k | Full Restart Komorebi |
Warning
In my komorebi.json config, I use the
JetBrains Mono font. You can
change it to any font you like.
In my whkdrc for Komorebi, I use OEM keys (oem_1, oem_plus, oem_102,
etc.) for shortcuts. They let me map layout-specific characters, ensuring my
keybindings work across different keyboard layouts.
On Windows, keys like oem_1, oem_plus, and oem_102 refer to OEM
(Original Equipment Manufacturer) keys. These are layout-dependent keys,
usually punctuation or special character keys, whose output changes depending on
the keyboard language (for example ;, `, ~, [, ], etc.). The
numbering follows Windows virtual-key codes. The number does not represent
the printed symbol, but a layout-specific key position. Because of that, the
mapped character can vary from country to country.
To determine the correct OEM value, use the
kbdlayout website, which provides the
virtual-key code associated with each key in a specific keyboard layout.
For reference, consult the official Microsoft documentation for the
United States Keyboard Layout
to review the standard virtual-key definitions. If you are working with a
different keyboard layout, such as
theBrazilian Keyboard Layout (ABNT2),
you can use the kbdlayout website as previously described to look up the
corresponding virtual-key mappings and OEM values.
Komorebi has a few known issues, such as occasional inconsistencies after waking from sleep, minor crashes in edge cases, and problems with window placement when using multiple workspaces. These issues are actively being addressed, and updates often improve stability and performance.
Warning
Many common issues are already explained in the
documentations
The goal of this section is to create CSS style overrides that modify parts of the HTML page to make content easier to see, improve readability, and enhance the overall user experience. These custom styles aim to make the page simpler and more pleasant to interact with.
To implement the custom CSS configurations listed below, you can use the Stylus browser extension or any other extension that allows injecting custom styles into web pages. The following steps guide you through creating a new style and configuring it for the desired website:
- Install the
Stylusextension from the Chrome Web Store . - Open the Chrome extensions page and select
Managefor Stylus. - Click the
Write new stylebutton (or the+icon) to create a new style. - Assign a descriptive name to the style you are creating.
- Paste your CSS code into the provided code editor.
- Set the style’s target by selecting
URLs starting withand entering the appropriate websiteURL(e.g.,https://www.google.com). - Save the style by clicking the
Savebutton or pressingCtrl + S.
You can access my configuration file here:
This CSS code customizes the Google search results page. It centers all content, limits the main page width, and keeps the floating search bar aligned in the center. It also hides extra elements like “People also search for,” the AI Mode option, and the footer, while preventing the search bar from stretching too much when focused.
This CSS code adjusts the YouTube comments section by limiting its width and centering it on the page, making the comments easier to read and visually balanced.
Since these styles are injected via CSS, some page elements might not display correctly or could behave unexpectedly. If you encounter any issues, you can easily resolve them by disabling Stylus or any other extension that injects custom CSS into pages.
VS Code is a lightweight,
cross-platform code editor developed by Microsoft. It supports multiple
programming languages, has a powerful extension ecosystem, and provides built-in
tools like debugging, Git integration, and a terminal, making it a versatile
environment for both development and everyday coding tasks.
You can download VS Code directly from its
official website. Installation
is straightforward: choose your operating system, run the installer, and
follow the prompts. Once installed, you can launch the editor immediately and
start coding.
You can access my configuration file here:
In VS Code,
settings.json is
the main configuration file where you can customize the editor’s appearance
and behavior, including themes, fonts, tab size, auto-save, and
language-specific settings. This file gives you full control over VS Code,
allowing you to tailor both how it looks and how it responds to your workflow.
In order for the settings to work properly, install the following extensions
(if you don’t want to use any of them, simply remove them from the
settings.json file):
| Name | Functionality | Download Link |
|---|---|---|
| Git Bash | Terminal shell for Git commands on Windows | Download |
| JetBrains Mono | Programming font used in editor and terminal | Download |
| Error Lens | Highlights errors and warnings inline in the editor | Download |
| Bearded Icons | Icon theme for VS Code | Download |
| Mayukai Mono | VS Code color theme | Download |
| Prettier - Code formatter | Formats code automatically according to style rules | Download |
| Red Hat YAML | YAML language support and formatter | Download |
The following extensions are not included in the settings.json configuration,
but I highly recommend them as they are very useful for improving productivity
and code readability.
| Name | Functionality | Download Link |
|---|---|---|
| Highlight Trailing White Spaces | Highlights trailing whitespace in files | Download |
| indent-rainbow | Colors indentation levels for better readability | Download |
| WakaTime | Tracks coding activity and time spent on projects | Download |
YASB (Yet Another Status Bar) is a
customizable status bar for Windows that displays system information and
dynamic data directly on the desktop. It is lightweight, flexible, and
configurable through external configuration files, allowing users to tailor the
layout, styling, and displayed information, including system metrics and
external data sources.
To install YASB, download the latest release from the official repository or a
package manager, then follow the setup instructions in the
documentation. The
installation process generally requires extracting the files, executing the
application, and configuring it according to your system specifications.
You can access my configuration file here:
YASB is configured through a
YAML file (default)
that uses simple key value pairs organized by indentation, with nested settings
structured hierarchically to group related options under broader categories. In
addition to the configuration file, YASB also uses a
CSS file (default)
to define the visual appearance of the bar, including colors, spacing, fonts,
and overall layout.
YASB provides many configuration options for customizing its
behavior,
keybinds and
appearance. In this guide, I will
focus on the most important components, the widgets, as they are the core
elements of the interface.
The widgets
present in my configuration are:
| Widget Name | Description |
|---|---|
| Custom (Super Start Menu) | Custom start menu button that triggers the system start menu when left-clicked. |
| Komorebi Workspaces | Displays Komorebi workspaces and allows switching between them. |
| Applications | Shows custom application shortcuts with clickable icons for launching predefined apps. |
| Systray | Displays the system tray with background applications and status icons. |
| Media | Shows current media playback information with optional controls and dropdown media menu. |
| Taskbar | Displays open windows and allows interaction such as toggling or opening the context menu. |
| Memory | Shows current memory usage with an alternative detailed view toggle. |
| CPU | Displays CPU usage percentage with optional frequency view. |
| Disk | Shows disk usage information for a specified volume. |
| Recycle Bin | Displays recycle bin status including item count and size. |
| Microphone | Shows microphone level and mute status with a dropdown device menu. |
| Volume | Displays system volume level with mute toggle and expandable audio menu. |
| Clock | Shows current time and date with an alternate format toggle. |
| Power Menu | Provides a popup menu with power options such as lock, restart, and shutdown. |
Note
Most animations and tooltips are disabled!
The design of YASB was created entirely from scratch, handcrafted without copying anyone else's code. While the implementation is original, the visual style was inspired by a few existing themes and concepts. The table below highlights some of the key inspirations that influenced the look and feel of YASB.
| Theme Name | Visual Appearance | Theme Source |
|---|---|---|
| Spectrum Symphony | Image |
Repository |
| Soft Segment | Image |
Repository |
| Pillbox | Image |
Repository |
| Fluent Onyx | Image |
Repository |
In addition to the visual inspirations listed above, the color palette of YASB
was primarily based on the Catppuccin
theme, and its official
style guide
was also used as a reference. This combination provides a soft and harmonious
range of tones that enhances readability and ensures overall aesthetic
consistency.
If you want, you can customize YASB by editing the configuration files to suit
your own needs and preferences. For those who prefer ready-made visuals, there
is also a repository of
community-made themes that you
can download. Applying a theme from the repository changes the entire appearance
of YASB instantly, without needing to modify any code.
In the yasb configuration file, you can set icons for each widget using Unicode
codes like \uf1f8, \uec04, or \uf4bc. These codes represent glyphs from
an icon font, often provided by patched fonts like
Nerd Fonts, allowing the widget to display a
symbol alongside dynamic information such as CPU usage, disk space, or recycle
bin status. Wrapping the code in a tag ensures it renders correctly, and
you can switch to alternate labels using mouse actions.
UWP (Universal Windows Platform)
provides a modern, native replacement for traditional Win32 tools like the
Character Map and Windows Font Viewer. With full high-DPI and touch support,
it lets you easily browse and select icons, ensuring your status bar symbols
are consistent with Windows without relying on external fonts.
YASB is generally stable, but on Windows it may cause minor issues like taskbar conflicts or unexpected widget behavior. Windows updates can affect windows, the taskbar, or visual effects. High-frequency updates or animations may slightly impact performance on older hardware. Always back up your configuration and monitor system behavior.
Warning
Many common issues are already explained or resolved in the
FAQ