Ask HN: Best way to do scoped commands in a CLI app

I'm building a CLI and want to allow commands to be scoped to a project.

I'm trying to decide between:

A. `blah edit foo` (familiar...like brew)

B. `blah foo edit` (least typing...but project name could clash with command names)

C. `blah project foo edit` (explicit...like RESTful paths)

D. `blah --project=foo edit`

E. `blah project foo --edit`

Wondering if there was any guidance on this from the UNIX people. Perhaps scoping should be done using the file system. `cd path/to/project && blah edit`. Like git does with `git --cwd=path/to/project`. Maybe a virtual FS could even be used. Then you wouldn't have to continuously type in the scope with each command. Interesting thinking about how to maintain state in the terminal...thinking about how Python's virtual env bin/activate modifies the shell.

EDIT: Found an interesting guide here: https://clig.dev/#subcommands

> Either `noun verb` or `verb noun` ordering works, but `noun verb` seems to be more common.