opi 0.0.1

Operations Interface — a project control center for your terminal
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88

# opi

**Operations Interface** — a project control center for your terminal.

Go into any repository, type `opi`, and get a usable interface for that
project — without configuring anything first.

> **Status: `0.0.1` is a placeholder that reserves the crate name.**
> The tool is not implemented yet. The first working release (`0.1.0`) will do
> one thing: make a project's `package.json` scripts immediately runnable.

## What it will do

Its primary job is to be a better `npm run`. The start screen shows the
project's scripts — grouped by prefix, labelled from `scripts-info`, with the
package manager detected rather than typed:

```
casoon.dev                                      pnpm
  Scripts
  ─────────────────────────────────────────────────────────
  Development
  › dev              Startet casoon.dev
    dev:landings     Startet die Produkt-Landingpages
  Build
    build            Baut Website + Landingpages
    build:landings   Baut nur die Landingpages
  Check
    check            Lint + Formatierung prüfen
    check:fix        Fehler automatisch beheben
  ─────────────────────────────────────────────────────────
  U  Updates       C  Clean       S  Secrets       H  Health
  /  Search        ?  Help
```

`Enter` runs the highlighted script. That is the shortest path, and nothing is
placed in front of it — maintenance areas sit behind hotkeys.

Three speeds, all backed by the same task model:

```bash
opi              # navigate:  ↓ ↓ Enter
opi              # search:    /dev land ↵
opi dev          # direct, no interface
```

Later releases add project health with parallel checks, dependency updates,
clean with real sizes, and secret scanning — each orchestrating an established
tool (`tsc`, ESLint, Biome, Vitest, Knip, No Secrets, `pnpm audit`, Taze) rather
than reimplementing it.

## Design rules

- **Zero configuration.** `opi` must be useful in an unmodified repository. A
  tool you have to configure first never gets started in someone else's project.
- **`package.json` is the only interface.** No `opi.toml`, no second source of
  truth. `scripts`, optionally `scripts-info`, optionally an `opi` key for
  refinement.
- **No task system of its own.** `opi` does not define tasks with their own
  commands — that would put it in competition with npm scripts, `just`, `make`
  and Taskfile for no gain.
- **Orchestration, not reimplementation.** `opi` is a UX layer over proven
  tooling.

## Install

```bash
cargo install opi
```

## Documentation

- [docs/project-state.md](docs/project-state.md) — what this is and where it stands
- [docs/constraints.md](docs/constraints.md) — the boundaries the implementation respects
- [docs/decisions.md](docs/decisions.md) — the decisions in force, and why

Terminal presentation comes from [runemark](https://github.com/casoon/runemark),
the shared presentation layer for these CLI tools.

## Name

`opi` is unrelated to [OdradekAI/opi](https://github.com/OdradekAI/opi), which
owns the `opi-*` crate namespace on crates.io. Installing both puts two `opi`
binaries in `~/.cargo/bin`.

## License

MIT ([LICENSE](LICENSE)).