feat improve custom mode with customize objective, rule & capabilities

[samhvw8]

Now custom mode can customize objective, rule & capabilities can be template via ejs

Context

When tool has remove from custom mode but sometime Roo still want access to there tool because those tool are mentioned in objective, rule & capabilities section.

This pr will address above problems

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Enhance custom modes with EJS template support for objectives, rules, and capabilities, including schema updates, UI changes, and tests.

• Behavior:
  • Custom modes can now override objective, rules, and capabilities sections using EJS templates in src/core/prompts/templates.
  • New copyEjsTemplates plugin in esbuild.js to copy EJS templates to dist/templates.
  • Added EJS rendering support in renderEjs.ts.
• Schema and Types:
  • Updated modeConfigSchema in schemas/index.ts to include objectiveSectionOverride, rulesSectionOverride, and capabilitiesSectionOverride.
  • Updated GlobalSettings and PromptComponent types in types.ts and roo-code.d.ts.
• UI Changes:
  • Updated PromptsView.tsx to allow editing of new override sections.
  • Added translations for new UI elements in prompts.json.
• Tests:
  • Added tests in custom-system-prompt.test.ts to verify new override functionality.

^{This description was created by for c9013fc2437eead3c69441e3d7e7b1caf8a2dc21. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9a6d174

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

The pull request contains a variety of changes, including new features, tests, documentation, and refactoring. While these changes are substantial, they appear to be interconnected, focusing on improving the custom mode with new objectives, rules, and capabilities.

However, if there are distinct groups of changes that can be logically separated without affecting the overall functionality, consider splitting the pull request into smaller ones. For example, documentation updates could be separated from feature additions if they do not directly depend on each other. This can help streamline the review process and ensure each set of changes is thoroughly evaluated.

Please review the changes and assess if any sections can be independently split into separate pull requests.

[ellipsis-dev]

The comment on line 75 refers to 'Pug templates', but the code actually loads EJS templates (objective.ejs, rules.ejs, capabilities.ejs). Consider updating the comment to accurately reflect that these are EJS templates.

Suggested change

	// Load default Pug templates
	// Load default EJS templates

[hannesrudolph]

Thanks for submitting this PR—really appreciate your effort here, and sorry it's been sitting in draft status for so long.

We're closing this for now but would love to see this idea move forward. Please start by creating an issue using our issue-first approach. This way, we can have the dev team properly review and approve the proposal before you resubmit a PR.

Thanks again for your patience and contribution!