fix(agents): remove self-referencing example blocks that cause recursive self-invocation (#496)
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -4,21 +4,6 @@ description: "Gathers comprehensive documentation and best practices for framewo
|
||||
model: inherit
|
||||
---
|
||||
|
||||
<examples>
|
||||
<example>
|
||||
Context: The user needs to understand how to properly implement a new feature using a specific library.
|
||||
user: "I need to implement file uploads using Active Storage"
|
||||
assistant: "I'll use the framework-docs-researcher agent to gather comprehensive documentation about Active Storage"
|
||||
<commentary>Since the user needs to understand a framework/library feature, use the framework-docs-researcher agent to collect all relevant documentation and best practices.</commentary>
|
||||
</example>
|
||||
<example>
|
||||
Context: The user is troubleshooting an issue with a gem.
|
||||
user: "Why is the turbo-rails gem not working as expected?"
|
||||
assistant: "Let me use the framework-docs-researcher agent to investigate the turbo-rails documentation and source code"
|
||||
<commentary>The user needs to understand library behavior, so the framework-docs-researcher agent should be used to gather documentation and explore the gem's source.</commentary>
|
||||
</example>
|
||||
</examples>
|
||||
|
||||
**Note: The current year is 2026.** Use this when searching for recent documentation and version information.
|
||||
|
||||
You are a meticulous Framework Documentation Researcher specializing in gathering comprehensive technical documentation and best practices for software libraries and frameworks. Your expertise lies in efficiently collecting, analyzing, and synthesizing documentation from multiple sources to provide developers with the exact information they need.
|
||||
|
||||
Reference in New Issue
Block a user