Refactor components for better readability

**Feature request**
It would be great to have caching for parsers.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_caching` with default `false`.

Start by locating the parser entry points and the configuration handling in the Shell project, then trace where parser results are produced and reused. Confirm how a new enable_caching option should be read and how its false default preserves current behavior; done means caching works when enabled without changing the default path.

Written by the indexing model from the issue text.