marceloeatworld/hyprland-ai-skill
hyprland
FlaggedThis skill should be used when the user asks about "Hyprland configuration", "hyprland.lua", "hyprland.conf", "Hyprland Lua config", "hyprctl", "Hyprland keybinds", "Hyprland window rules", "Hyprland monitors", "Hyprland dispatchers", "Hyprland animations", "Hyprland workspaces", "Hyprland IPC", "Hyprland plugins", "hyprlock", "hypridle", "hyprpaper", "hyprcursor", "hyprpicker", "hyprsunset", "xdg-desktop-portal-hyprland", "Hyprland on NixOS", "Hyprland Home Manager", "Hyprland layouts", "Hyprland dwindle", "Hyprland master layout", "Hyprland FAQ", "Hyprland performance", "Hyprland Nvidia", "Hyprland screen sharing", "Hyprland special workspace", "Hyprland smart gaps", "Hyprland multi-monitor", "Hyprland tearing", or any topic related to configuring, troubleshooting, or extending the Hyprland Wayland compositor and its ecosystem tools.
references/workspace-rules.md
View on GitHub<!-- source: https://wiki.hypr.land/configuring/core/rules/workspace-rules -->
<!-- wiki commit: 41c7222 (2026-11-20 18:16:21 +0100) -->
<!-- auto-generated by scripts/generate-references.sh - DO NOT EDIT MANUALLY -->
---
weight: 20
title: Workspace Rules
---
You can set workspace rules to achieve workspace-specific behaviors.
For instance, you can define a workspace where all windows are drawn without borders or gaps.
Some layouts have their own specific rules, which can be found on the corresponding layout page.
See [Layouts](../../../layouts).
## Syntax
```lua
hl.workspace_rule({
workspace = workspace_selector,
rule1 = some_value,
rule2 = other_value,
})
```
## Rules
<!-- SORT: monitor and default are together because it is easier to understand like that -->
| Rule | Description | Type | Limits |
| --- | --- | --- | --- |
| animation | The animation style to use for this workspace | string | |
| border_size | Set the border size around windows | int | |
| decorate | Whether to draw window decorations or not | bool | |
| default_name | A default name for the workspace | string | |
| float_gaps | Set the gaps for floating windows | css_gaps | |
| gaps_in | Set the gaps between windows | css_gaps | |
| gaps_out | Set the gaps between windows and monitor edges | css_gaps | |
| layout | The layout to use for this workspace | string | |
| layout_opts | A table of layout-specific options for this workspace. Keys and values depend on the layout | table | |
| monitor | Binds a workspace to a monitor. See [syntax](#syntax) and [Monitors](../../monitors) | string | |
| default | Whether this workspace should be the default workspace for the given monitor | bool | |
| no_border | Whether to disable borders | bool | |
| no_rounding | Whether to disable rounded windows | bool | |
| no_shadow | Whether to disable shadows | bool | |
| persistent | Keep this workspace alive even if empty and inactive | bool | |
{{% details title="Examples" closed="true" %}}
```lua
hl.workspace_rule({ workspace = "3", no_rounding = true, decorate = false })
hl.workspace_rule({ workspace = "name:coding", no_rounding = true, decorate = false, gaps_in = 0, gaps_out = 0, no_border = true, monitor = "DP-1" })
hl.workspace_rule({ workspace = "8", border_size = 8 })
hl.workspace_rule({ workspace = "name:Hello", monitor = "DP-1", default = true })
hl.workspace_rule({ workspace = "name:gaming", monitor = "desc:Chimei Innolux Corporation 0x150C", default = true })
hl.workspace_rule({ workspace = "15", animation = "slidevert", default_name = "slider" })
```
{{% /details %}}
### Per-workspace layouts
Use workspace rules to set per-workspace layouts:
```lua
hl.workspace_rule({ workspace = "2", layout = "scrolling" })
hl.workspace_rule({ workspace = "3", layout = "dwindle" })
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |