Save project-management prompts inside a Bolt project

[mbhvl]

Storing prompts in a project directory lets me copy/paste useful project-management prompts into Bolt quickly.
I have a directory /prompts into which I save them.
Bolt appears to read them and stick to them, at least some of the time.

For example I have one called FeatureMVVM.prompt which simply says:

Move all files for a feature into /src/features/<feature_name>.
Name Model files <feature_name>Model.
Name View files <feature_name>View.
Name ModelView files <feature_name>ViewModel.
Store any components for a feature in subdirectory /src/features/<feature_name>/components.
Store any types for a feature in subdirectory /src/features/<feature_name>/types.
When I refer to the FeatureMVVM naming-convention I am refering to this systematic approach to file-names and locations.
Please do not randomly rename files or randomly create new files when relevant MVVM files already exist.

I can even prompt Bolt follow the instructions in FeatureMVVM.prompt and it will do so!

But also I have noticed that if I add such prompts to the project, apparently Bolt reads them and seems to notice them even when I don't explicitly say so. It even seems to refer to them (e.g. citing FeatureMVVM name-convention) in its own answers.

In the case of the prompt above it stops Bolt from "knocking over all the chess pieces" when it enthusiastically writes new code; without this in place it tends to create duplicate files for the same function with slightly different names very quickly.

I have a number of other prompts saved in the /prompts directory and this makes managing a growing project much easier.

Can anyone confirm if this is real or am I just imagining it?