I need some help deciding on a name for a package. First some

## Background
  
Inside of `expkv-def` and `expkv-cs` I use quite similar code (originally almost identical, but I updated the code in `expkv-def` which wasn't absolutely necessary in `expkv-cs` -- this means: I was too lazy to make the same enhancements on `expkv-cs` because the gain was much smaller/not worth it). Now since I'm working on joining all the `expkv` packages into a single bundle I also decided to generalise that code and put it in an auxiliary package. But if I already generalised that code I can as well document it and let others use it if they want to. This leads to the problem at hand.
  
The package will provide a prefix-oriented parser (so it will support setting up own parsers which can handle `<p-prefix> <t-prefix> <name> = <definition>` lists (with `p-prefix` and possibly `definition` being optional, and `t-prefix` being either mandatory or forbidden -- behaviour selectable via some syntax (to be decided)) and a definable action (either based on the `t-prefix` or one standard action which might handle `p-prefix`es)).[^1]
  
The question is: How to *name* such a package.

## Constraints

The package name should be abbreviated to either two or three letters (three is preferred, two is ok). It should fit in the following list:

- `expkv-cs` expandable **c**ontrol **s**equences with `expkv`

- `expkv-def` **def**ine keys with and for `expkv`

- `expkv-opt` parse package and class **opt**ions with `expkv`

[^1]: Those are many parenthesis, sorry.