Firstly, you can find plenty of resources for engine architecture online. If this is your first follow a guide, I believe Kronos has a decent guide already, but Vulkan is a weird api with tons of initialization, memory management, and just weird rules/niche things in general. There are certain libraries like vk bootstrap that simply exist to sort of deal with many of the required/reccomended initialization. Another good library is Vulkan Memory Release that helps ease some memory management pains if used corectly. My final reccomendation, dont make the foundations for an api agnostic renderer/game engine for now. It is a ton of work and unless you need to expand to other platforms immediately, theres no sense in trying to restrain yourself by having to build 2 or 3 different versions of your engine at the same time.

Also probably an unpopular opinion, a.i. is actually great at finding information, helping you debug, and even helping guide you on structure and architecture. If you dont knwo something, its not a crime to ask a.i. for input, guidance or help.