Support external custom instruction files and extension-based instruction targeting

[godzail]

What specific problem does this solve?

Features Request

I would like to propose two enhancements to improve the flexibility and scalability of RooCode’s custom instruction system:

---

1. Support external instruction files with path reference

Currently, I attempted to include custom instructions from a file located in the .roocode/ folder by referencing external file path (e.g. ./.github/copilot-instructions.md), but it doesn’t seem to work.
It would be very useful to allow the inclusion of custom instruction files from external folders, by specifying their relative or absolute path.

Use Case:

This would allow reusing instruction templates across multiple projects or integrating existing general instruction files from tools like GitHub Copilot.

---

2. Instruction file naming by extension scope

Introduce a naming convention such as py-instruction.md to make instructions language-specific. For example:

• py-instruction.md → valid only for .py files
• ts-instruction.md → valid only for .ts files
• html-instruction.md → for HTML files, etc.

This would allow RooCode to apply precise, language-aware context based on the file being edited, without needing manual toggling or multiple generic instruction files.

---

Benefits

• Better modularity and DRY principles across multiple codebases
• Seamless integration with shared or external instruction sources
• Improved developer experience with language-specific customization

Additional context (optional)

No response

Roo Code Task Links (Optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear impact and context

Interested in implementing this?

• Yes, I'd like to help implement this feature

Implementation requirements

• I understand this needs approval before implementation begins

How should this be solved? (REQUIRED if contributing, optional otherwise)

No response

How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)

No response

Technical considerations (REQUIRED if contributing, optional otherwise)

No response

Trade-offs and risks (REQUIRED if contributing, optional otherwise)

No response

[roomote]

Hi @godzail! I'm here to help out the maintainers and am going to see if I can implement these enhancements. Both features sound very useful:

1. Supporting external instruction files with path references
2. Extension-based instruction targeting (e.g., py-instruction.md for Python files)

I'll explore the codebase to understand how custom instructions are currently implemented and work on adding these capabilities. I'll keep you updated on the progress!

[daniel-lxs]

Thanks for the feature request! I need to clarify something about how Roo Code works that affects your suggestions.

The extension-specific rules idea (like py-instruction.md for Python files) wouldn't actually work with our architecture. Roo Code builds its context when a task starts, not when individual files are accessed. The AI doesn't dynamically load instructions based on what file you're editing - everything needs to be set up at the beginning of the conversation.

However, your first suggestion about supporting external instruction files is interesting. Being able to configure custom paths for instruction files could be useful for sharing rules across projects or teams. That's something we could potentially implement.

If you'd like to pursue the configurable instruction file paths feature, I'd recommend opening a new issue specifically for that. It would help us focus on implementing something that's both feasible and valuable.