create_or_update_rule
Create or update project documentation rules to capture coding patterns, architectural decisions, and lessons learned during development work.
Instructions
Document new coding patterns or architectural decisions AS YOU DISCOVER THEM during work. Call this when: you solve a tricky problem, establish a new pattern, learn a gotcha, make an architectural decision, or implement something that should be standardized. Captures lessons learned, design patterns, and team conventions as searchable knowledge for future work. Don't wait until the end - document insights immediately while context is fresh.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fileName | Yes | Documentation file name. Must end with .md. Example: "api-patterns.md" | |
| title | Yes | Document title for display and search | |
| description | No | Brief summary of the document's purpose | |
| keywords | No | Search keywords. Include technologies, patterns, and concepts covered | |
| alwaysApply | Yes | true: applies to all code (global rule). false: applies only when relevant (contextual) | |
| content | Yes | Full markdown content of the documentation |