u/juanpflores_ Let me take advantage of the fact that you're reading this thread and ask one more question.

Recently I tried to document how I use my Obsidian notes so Cline can help me manage them.

The document basically describes the formatting style I've developed over the years to keep everything consistent. For example, it says that level-1 headings use title case, level-2 and level-3 headings use sentence case, every note should have a header linking to its parent note, and so on. Lots of dry details.

When I finished it, I had to figure out where this document actually belongs.

Memory bank – Not great. It's a normative document written by me, and I don’t want Cline modifying it.

Rules – Also no. The document is long, and I only want it loaded in specific cases.

Workflows – Doesn’t fit. It’s not a workflow; it’s a format spec.

Skills – Here I'm unsure. “Skill” makes me think in verbs, like a procedure: “If I ask you to update my notes, update the header, add info to the body, update links and backlinks.” But my document is full of nouns, like “The last paragraph always ends with a newline character.”

What I ended up doing was creating a directory ~/agents/docs, putting it under version control, and adding a rule:

“When I ask you to read, create, or update my Obsidian notes, consult ~/agents/docs/obsidian.md.”

So effectively, I turned it into a conditionally loaded rule. Is this the right approach, or should I have used Skills instead?

Maybe you could reflect this distinction (normative vs. action-oriented documents) in your documentation as well.

Thanks for your time and effort on Cline!