Best Practices for Split Prism Module

.
for development using Net Core 3.1+ Prism I think there are cases where processing is divided by module.

At that time, the initial modules generated by PrismTemplatePack are in the View/ViewModel folder and one class + three classes outside the folder.

Does this indicate that the best practice is not to include model classes in the module when dividing into modules?

Otherwise, for example, if you added a new Module 1 project, you added the Models Interfaces folder where the View Model folder is located.
In addition, add the interface of logic to Interfaces and the implementation of interface to Models.
In this state, if you want to access the logic through the interface from another module, you may need cross-referencing.
Therefore, let's say that Models, Interfaces is a separate project and Module 1 is a module with only View and ViewModel.

If you want to divide this into multiple logic, such as user management programs, you need two modules for each feature, such as LoginViewModule and LoginLogicModule, if you want to divide it into many modules, such as LoginFeatures and User Information EditingFeatures.I think this design is probably wrong.

What are the modular best practices for avoiding cross-referencing?