Blog

kmc / CLI / Tools

kmc: my CLI for project commands

By Sebastian Lui · 02/07/2026

Summary

kmc is my small command center for projects: instead of searching for commands, I store them in kmc.json, import scripts, and run them cleanly from a menu or directly in the terminal.

As a project grows, so does its list of commands: development servers, builds, deployments, Docker, migrations, and maintenance scripts. Eventually that knowledge is scattered across README files, shell history, notes, and people's heads.

That is why I built kmc: a small CLI that makes project commands visible and directly executable.

Links:

What kmc does

kmc stores commands locally in a kmc.json file. This file can live in the repository and describes the commands that matter for a project. You can then open the menu with kmc or run a command directly, such as kmc run npm.dev.

The benefit is not merely a shorter command. The project gains a clear command structure.

Why not only package.json?

Real projects often include Makefile targets, Docker Compose commands, Flutter commands, deployment scripts, maintenance tasks, and custom commands. kmc imports existing sources and groups them in one overview without forcing everything into package.json.

Installation

npm install -g @marius4lui/kmc

Who it is for

kmc is useful when you switch between projects or maintain a repository with several recurring commands. New developers, agents, or your future self no longer have to guess how to start, test, maintain, or deploy the project.

My goal is to structure projects so they are easy to understand and operate safely. kmc is a small infrastructure tool for documenting, grouping, and executing commands.