PreSession Hook from obra/superpowers injects this along with more logic for getting rid of rationalizing out of using skills:
> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
While this may result in overzealous activation of skills, I've found that if I have a skill related, I _want_ to use it. It has worked well for me.
I took this for a spin today. Coming from a long-time iTerm2 user, the first thing I noticed was how snappy everything feels, especially when resizing the window. The straight-forward configuration was extremely nice as well and can be stored in my dotfiles now (iTerm was a giant dump of XML).
A few things that keep me from switching to it full time:
- More of a nitpick than anything, but the only way to disable cursor blinking is to disable shell integration. Unfortunately, this means taking away things like native scrolling and likely some other things I don't know about. I see there is a discussion here to possibly address this: https://github.com/ghostty-org/ghostty/discussions/2812
I feel like this would be a no-brainer switch for me once the above are addressed.
AutoHotkey is what made me fall love programming after disliking it after getting my degree. After switching to a macbook, AutoHotkey is probably what I miss most from being on Windows. It really has it all.
AutoHotkey was a lifesaver for me when I used to work on Windows. Universal CapsLock VIM movement keys, app-specific shortcuts, clipboard manipulation, text expansion, autocorrect. It really is an amazing tool. For mac, I've been able to cobble together a mix of karabiner, phoenix, and espanso to do all of what just AutoHotkey could do.
Coincidentally, my AHK config was my first open source repo on GitHub. I'm glad to see it moving forward.
The problem I have with these type of sites is how "issues" are always spun as a negative. I honestly wish GitHub had chosen a different word since a lot of projects use Issues for roadmap, planning, backlog, and more - not just actual bugs.
Unfortunately, GH Discussions hasn't really taken off because of, in my opinion, lack of integrations and bad SEO.
Karabiner for key remapping has been instrumental for me. I use it for a "hyper key" on CapsLock to provide Vim-like movement keys, text selection, app-specific bind overrides, etc. There is also a library out there for configuring it with TypeScript (Deno).
Hammerspoon for window management is also amazing, though I recently switched to Phoenix because it can be configured in TypeScript. It allows me to have hotkeys to swap to specific apps or toggle between groups of apps.
I used to be a very heavy AHK user and developed a rather extensive config. Here is my config along with a boilerplate to help you start one that is similar:
I have been using asdf for quite a few years, and I've always been impressed. It's honestly a breath of fresh air to only have a single set of commands to remember for node, go, ruby, python, even crystal. For node, it even respects existing .nvmrc files.
Elliot from Payload here. In addition to Dan's comments above, the main advantage of using Payload's Admin is that it can integrate directly with your auth as well as offer a richer editing experience beyond the normal CRUD that others provide.
For instance:
- Field-based access control - This allows a developer to use code to write complex functions in order to regular access to a field. This can also reference the currently logged in user's permissions/fields etc.
- Conditional logic - Functions can be written to show/hide certain fields in the admin UI
- Dynamic field types - Complex layouts can be built with the Block and Array field types. This allows the ability to build out more of a "page builder" type input vs. simple CRUD.
I hope that answers your question. Here are some links to the docs on each of those: