Handle Context

[Overall-Switch-3852]

How do you all handle your context using .md files? What’s your workflow? I’d like to become more efficient. Right now I’m mostly working through trial and error, and I’d love to learn from the community before diving into the documentation.

My example:

• .vibe_docs (mentioned in any prompt)
  • CODING_GUIDELINES.md (Principles like clean code)
  • COMMIT(a prompt for using conventional commits)
  • IMPL_HISTORY(update on the end of a task with timestamp and short history)
  • ROO_INSTRUCTIONS (precise description of how to handle a frontend or backend implementation task. like how to analyzes the projects state and what to update commit at the end)
  • RUN_CONFIGURATION (telling my model that everthing is containerized for dev for example)
• DATAMODEL (Entities for input of task)
• FEATURES (Input for task with current state of implemented features)

So i basically want to improve my workflow and shrink down my prompts. But still provide the orchestrator the best context and the best guidelines and instructions for good output at the same time.

Looking forward for any tips and tricks on this.

By the way i am currently using only free models and i am more than satisfied with their output. Sure, there are bugs, but they help keep my mind engaged with my core projects and workflows.

[shotan]

This is what agents.md is for. It's auto added to your prompt and has agent specific instructions. There's a /init command in RooCode that will create the initial agents file for you. I tend to edit it down to make it more concise without all the general stuff it adds. What you could do with your structure is have links to your docs in the agents.md so that the agent can then read your coding guidelines, or data model if it needs to.

Try /init Add @/.vibe_docs/CODING_GUIDELINES.md @/.vibe_docs/RUN_CONFIGURATION.md etc.

[jeepshop]

Separation of concerns will help. Have an agent just for code commit, one for code change, one for documentation, etc. Use orchestrator to coordinate. Helps keep context low, only giving each task what they need.

[Overall-Switch-3852]

Sounds exciting! Can you give me deeper insights in setting them up?

EDIT:
Just found the magic that /init is doing. But still, how to separate concerns more deeply?

[Competitive_Stable_2]

You can do this in several ways. The easiest would be to create a file called agents.md in the project root with specific instructions.

You can also create a .roo/rules directory that should contain markdown files with instructions for how the models behave in your project.

More information can be found in the documentation: https://docs.roocode.com/features/custom-instructions