Maneuver-centric Project Structure for Skill Graphs

Skill graphs represent maneuvers that can be turned on during run-time. Right now, the project structure feels very un-organized I would like to change the standard project sturcture accordingly to resemble a repository of skill graphs including proofs and additional parts when necessary (for instalce, source code/implementations).

Current view:


What I would like to have:

-Fixed folder called "SkillGraphs (repository)"; fixed means that this folder should not be removable
-Fixed folder called "Programs/Proofs", where generated hybrid programs and finished proofs are saved automatically
-...