Update custom rules documentation #59
Conversation
Prompt: Update @docs/advanced-usage/custom-rules.md for the new UI and *global* rules support. Note that global rules and the UI are only supported for general rules, not mode-specific ones. Don't add examples or guidelines. Check @docs/features/slash-commands/workflows.mdx for inspiration and the UI in @/Users/christiaan/Git/kilocode/webview-ui/src/components/kilocode/rules/KiloRulesToggleModal.tsx.
chrarnoldus
requested review from
EamonNerbonne,
HadesArchitect,
Copilot and
kevinvandijk
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the Custom Rules guide by introducing global rules support and detailing the new UI-based rule management options.
- Adds distinction between project and global rules
- Documents the built-in UI for creating, editing, and toggling rules
- Updates loading order and troubleshooting steps to include global rules
Comments suppressed due to low confidence (4)
docs/advanced-usage/custom-rules.md:25
- The term “general rules” may conflict with “global rules” elsewhere. Consider renaming “general rules” to “global rules” or clarifying the distinction to avoid confusion.
The built-in rules management UI is available for general rules only. Mode-specific rules must be managed through the file system.
docs/advanced-usage/custom-rules.md:61
- Since mode-specific rules aren’t supported in the UI, consider adding a note here to clarify that only project and global rules appear in this list.
- View all active rules (both project and global)
docs/advanced-usage/custom-rules.md:200
- [nitpick] The troubleshooting list uses the same ‘1.’ marker for every item. For clarity, you may want to use distinct numbers or rely on Markdown's auto-numbering.
1. **Check rule status in the UI**: Use the rules management interface to verify that your rules are active and properly loaded
docs/advanced-usage/custom-rules.md:72
- Consider clarifying that “priority order” refers to load sequence (global → project → legacy) and that project rules still override global settings when conflicts arise.
Rules are loaded in the following priority order:
|
Hey, the PR looks good to me, but I'm not sure about Custom Instructions. Are they staying all the same? Is there something to adjust there? https://kilocode.ai/docs/advanced-usage/custom-instructions |
Staying the same for now, but they are arguably redundant now (global rules and custom instructions do the same thing), so maybe we want to revisit this. |
No description provided.