Project/tech stack specific instructions?

[pjrulez]

How critical is it to edit the custom instructions for each mode to fit the project's tech stack?

Most role definitions and custom instructions I see are very general. Does it make a big difference if I tailor it to my specific project configuration, dependencies, and versions to have agents know what framework to stick to when doing work?

It's great to break down different aspects of software design tasks, structure them and put them in relationships but where exactly should the project be defined? Goal being the project staying lean and consistent across sessions.

Can you share some examples of instructions before and after along with your observations?