JAP is a modular terminal framework that was created because I needed a flexible and expandable system for my own workflow. The goal was to automate recurring tasks, standardize the working environment, and at the same time keep it open for individual extensions.
I created JAP because no existing tool offered me the freedom and structure I wanted.
I wanted a terminal plugin system that:
- works according to my ideas,
- is easy to expand,
- speeds up my daily workflow, and
- runs smoothly both locally and on servers (Linux).
Over time, more and more features and small automations were added.
At some point, I had to decide: Do I turn JAP into a large, monolithic tool - or do I break it down into modular components?
I opted for the modular approach.
cd ~ && bash -c "$(curl -fsSL https://japzsh.com/install.sh)"| Method | Command |
|---|---|
| curl | bash -c "$(curl -fsSL https://japzsh.com/install.sh)" |
| wget | bash -c "$(wget -O- https://japzsh.com/install.sh)" |
| fetch | bash -c "$(fetch -o -https://japzsh.com/install.sh)" |
After installation, JAP can be used directly via the terminal:
jap <command>jap helplist all commands
