Currently, users must manually set up a prompts folder containing a Markdown file with the starter prompts and a .yaml configuration file.
The documentation encourages the user to use Kappa to generate the prompt automatically.
While this approach works, the overall flow can be automated.
Proposed improvement
We can streamline the process by extracting and internalizing some of Kappa’s core logic:
-
Read kappa-db.json from Mizuchi
-
Build a queue of candidate functions to decompile, ordered by difficulty
-
Generate the initial prompt directly from Mizuchi
To support this, we will likely need a shared utility library that can be reused by both Mizuchi and Kappa.
Out of scope
Generating kappa-db.json from Mizuchi is out of scope for this issue.
We'll likely have a standalone CLI tool (decompcli?) to generate it.
Currently, users must manually set up a
promptsfolder containing a Markdown file with the starter prompts and a.yamlconfiguration file.The documentation encourages the user to use Kappa to generate the prompt automatically.
While this approach works, the overall flow can be automated.
Proposed improvement
We can streamline the process by extracting and internalizing some of Kappa’s core logic:
Read
kappa-db.jsonfrom MizuchiBuild a queue of candidate functions to decompile, ordered by difficulty
Generate the initial prompt directly from Mizuchi
To support this, we will likely need a shared utility library that can be reused by both Mizuchi and Kappa.
Out of scope
Generating
kappa-db.jsonfrom Mizuchi is out of scope for this issue.We'll likely have a standalone CLI tool (
decompcli?) to generate it.