{"owner":"LGUG2Z","repo":"komorebi","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":339,"categories":["project-spec"],"hasMcp":false,"mcpConfig":null,"found":["docs/design.md"],"skills":{"docs/design.md":"---\nhide:\n  - toc\n---\n\n## Description\n\n_komorebi_ only responds to [WinEvents](https://docs.microsoft.com/en-us/windows/win32/winauto/event-constants) and the\nmessages it receives on a dedicated socket.\n\n_komorebic_ is a CLI that writes messages on _komorebi_'s socket.\n\n_komorebi_ doesn't handle any keyboard or mouse inputs; a third party program (e.g.\n[whkd](https://github.com/LGUG2Z/whkd)) is needed in order to translate keyboard and mouse events to _komorebic_ commands.\n\nThis architecture, popularised by [_bspwm_](https://github.com/baskerville/bspwm) on Linux and\n[_yabai_](https://github.com/koekeishiya/yabai) on macOS, is outlined as follows:\n\n\n```\n          PROCESS                SOCKET\nwhkd/ahk  -------->  komorebic  <------>  komorebi\n```\n\n## Data Model\n\n_komorebi_ holds a list of physical monitors.\n\nA monitor is just a rectangle of the available work area which contains one or more virtual workspaces.\n\nA workspace holds a list of containers.\n\nA container is just a rectangle where one or more application windows can be displayed.\n\nThis means that:\n\n- Every monitor has its own collection of virtual workspaces\n- Workspaces only know about containers and their dimensions, not about individual application windows\n- Every application window must belong to a container, even if that container only contains one application window\n- Many application windows can be stacked and cycled through in the same container within a workspace\n"},"files":{"docs/design.md":"---\nhide:\n  - toc\n---\n\n## Description\n\n_komorebi_ only responds to [WinEvents](https://docs.microsoft.com/en-us/windows/win32/winauto/event-constants) and the\nmessages it receives on a dedicated socket.\n\n_komorebic_ is a CLI that writes messages on _komorebi_'s socket.\n\n_komorebi_ doesn't handle any keyboard or mouse inputs; a third party program (e.g.\n[whkd](https://github.com/LGUG2Z/whkd)) is needed in order to translate keyboard and mouse events to _komorebic_ commands.\n\nThis architecture, popularised by [_bspwm_](https://github.com/baskerville/bspwm) on Linux and\n[_yabai_](https://github.com/koekeishiya/yabai) on macOS, is outlined as follows:\n\n\n```\n          PROCESS                SOCKET\nwhkd/ahk  -------->  komorebic  <------>  komorebi\n```\n\n## Data Model\n\n_komorebi_ holds a list of physical monitors.\n\nA monitor is just a rectangle of the available work area which contains one or more virtual workspaces.\n\nA workspace holds a list of containers.\n\nA container is just a rectangle where one or more application windows can be displayed.\n\nThis means that:\n\n- Every monitor has its own collection of virtual workspaces\n- Workspaces only know about containers and their dimensions, not about individual application windows\n- Every application window must belong to a container, even if that container only contains one application window\n- Many application windows can be stacked and cycled through in the same container within a workspace\n"},"items":[{"name":"design.md","path":"docs/design.md","rawUrl":"https://raw.githubusercontent.com/LGUG2Z/komorebi/HEAD/docs/design.md","title":"docs - UI Design System & Style Tokens","category":"project-spec","format":"markdown","content":"---\nhide:\n  - toc\n---\n\n## Description\n\n_komorebi_ only responds to [WinEvents](https://docs.microsoft.com/en-us/windows/win32/winauto/event-constants) and the\nmessages it receives on a dedicated socket.\n\n_komorebic_ is a CLI that writes messages on _komorebi_'s socket.\n\n_komorebi_ doesn't handle any keyboard or mouse inputs; a third party program (e.g.\n[whkd](https://github.com/LGUG2Z/whkd)) is needed in order to translate keyboard and mouse events to _komorebic_ commands.\n\nThis architecture, popularised by [_bspwm_](https://github.com/baskerville/bspwm) on Linux and\n[_yabai_](https://github.com/koekeishiya/yabai) on macOS, is outlined as follows:\n\n\n```\n          PROCESS                SOCKET\nwhkd/ahk  -------->  komorebic  <------>  komorebi\n```\n\n## Data Model\n\n_komorebi_ holds a list of physical monitors.\n\nA monitor is just a rectangle of the available work area which contains one or more virtual workspaces.\n\nA workspace holds a list of containers.\n\nA container is just a rectangle where one or more application windows can be displayed.\n\nThis means that:\n\n- Every monitor has its own collection of virtual workspaces\n- Workspaces only know about containers and their dimensions, not about individual application windows\n- Every application window must belong to a container, even if that container only contains one application window\n- Many application windows can be stacked and cycled through in the same container within a workspace\n","frontmatter":{"hide":["toc"]},"isInternal":false,"tokens":339,"sizeBytes":1454}],"systemPromptSnippet":"<yakaai_skills repo=\"LGUG2Z/komorebi\">\n<!-- File: docs/design.md (Tokens: ~339 | Category: project-spec) -->\n---\nhide:\n  - toc\n---\n\n## Description\n\n_komorebi_ only responds to [WinEvents](https://docs.microsoft.com/en-us/windows/win32/winauto/event-constants) and the\nmessages it receives on a dedicated socket.\n\n_komorebic_ is a CLI that writes messages on _komorebi_'s socket.\n\n_komorebi_ doesn't handle any keyboard or mouse inputs; a third party program (e.g.\n[whkd](https://github.com/LGUG2Z/whkd)) is needed in order to translate keyboard and mouse events to _komorebic_ commands.\n\nThis architecture, popularised by [_bspwm_](https://github.com/baskerville/bspwm) on Linux and\n[_yabai_](https://github.com/koekeishiya/yabai) on macOS, is outlined as follows:\n\n\n```\n          PROCESS                SOCKET\nwhkd/ahk  -------->  komorebic  <------>  komorebi\n```\n\n## Data Model\n\n_komorebi_ holds a list of physical monitors.\n\nA monitor is just a rectangle of the available work area which contains one or more virtual workspaces.\n\nA workspace holds a list of containers.\n\nA container is just a rectangle where one or more application windows can be displayed.\n\nThis means that:\n\n- Every monitor has its own collection of virtual workspaces\n- Workspaces only know about containers and their dimensions, not about individual application windows\n- Every application window must belong to a container, even if that container only contains one application window\n- Many application windows can be stacked and cycled through in the same container within a workspace\n</yakaai_skills>"}