### General items * [ ] Think about how to generate the rules, considering a configuration structure for generation. * [ ] Support generation by phase * [ ] Support rule type (e.g., `920-prot... related`) * [ ] Support tags * [ ] Support paranoia levels * [ ] Each rule should be represented as a YAML file. * [ ] Maintain a configuration file that identifies and contains metadata of the associated rules (Ruleset?). * [ ] Ensure rules related to paranoia level implementation in ModSec disappear, as they must be generated during translation. ### Short-term concrete tasks * [ ] Check the enum for actions and consider creating an interface to eliminate the problem when actions have parameters. * [ ] Adjust parser to remove `#` from comments. * [ ] Adjust exported YAML (review code in `crs-toolchain`) to properly handle multiline comments. * [ ] Explore text templates for export to Seclang: [[text/template](https://pkg.go.dev/text/template)](https://pkg.go.dev/text/template).
General items
920-prot... related)Short-term concrete tasks
#from comments.crs-toolchain) to properly handle multiline comments.