omarchy
Omarchy operating guardrails for day-to-day system work: assume the host is Omarchy by default, choose Omarchy-native workflows first, map user intent to the correct omarchy-* wrapper/script family, and avoid generic Linux commands that conflict with Omarchy behavior. Use whenever handling local system tasks on this host unless the user explicitly says it is not Omarchy; prioritize safe Omarchy commands, prevent non-Omarchy shortcuts (e.g., ad-hoc process killing/relaunch patterns), troubleshoot
β οΈ BytesAgain does not review or verify third-party content. Proceed at your own risk.
π This skill is indexed from ClawHub and is available under its original license. BytesAgain is an independent directory β we do not host or own this content. All rights belong to the original author.