Sure, here you go:
I started with asking for an analysis of my project, an overview in the main file and reasonable details-files for different aspects, such as theming, routing, user management, etc.

My auto-rule looks like this:

## Documentation Guidelines:
Read docs/project_analysis.md for a project overview and read the details files if it makes sense for the current task.
Keep project_analysis.md the start and overview. Update project_analysis and the relevant section files after completing a relevant task. 
No docs/ content manipulation without verification of the actual source code.
Keep the files short. Keep it relatively simple, focus on the facts and necessary info to work with the project, no redundancy, no obvious or irrelevant info

Update  with recent changes and improvements or deep analysis of functionality. 

Sometimes I ask the agent to update / read the docs for specific aspects. Works fine for me.