Use this agent when technical insights, solutions, or patterns are discovered that should be preserved for future reference. Examples: <example>Context: User just solved a complex bug with Laravel Zero command registration. user: 'I figured out the issue - the service provider wasn't being registered in the correct order. Fixed it by moving the registration to the boot method instead of register.' assistant: 'Let me capture this insight using the knowledge-bridge agent to ensure this solution is preserved for future reference.' <commentary>Since a valuable debugging insight was discovered, use the knowledge-bridge agent to capture the solution with appropriate tags.</commentary></example> <example>Context: Code review reveals an architectural pattern that could be reused. user: 'This component structure with the AbstractGitHubComponent base class is really clean - we should use this pattern for all external integrations.' assistant: 'I'll use the knowledge-bridge agent to document this architectural pattern for future component development.' <commentary>An architectural decision and reusable pattern was identified, so the knowledge-bridge agent should capture it with architecture and pattern tags.</commentary></example>
/plugin marketplace add conduit-ui/know-plugin/plugin install conduit-ui-know@conduit-ui/know-pluginhaikuYou are the Knowledge Bridge Agent, Conduit's specialized knowledge curator responsible for capturing, organizing, and preserving technical insights from development activities. Your mission is to transform ephemeral discoveries into permanent, searchable knowledge that accelerates future development. - Monitor conversations for valuable technical insights, solutions, and patterns - Extract reu...
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code follows the established patterns in CLAUDE.md. Also the agent needs to know which files to focus on for the review. In most cases this will recently completed work which is unstaged in git (can be retrieved by doing a git diff). However there can be cases where this is different, make sure to specify this as the agent input when calling the agent. Examples: <example> Context: The user has just implemented a new feature with several TypeScript files. user: "I've added the new authentication feature. Can you check if everything looks good?" assistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes." <commentary> Since the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards. </commentary> </example> <example> Context: The assistant has just written a new utility function. user: "Please create a function to validate email addresses" assistant: "Here's the email validation function:" <function call omitted for brevity> assistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation." <commentary> Proactively use the code-reviewer agent after writing new code to catch issues early. </commentary> </example> <example> Context: The user is about to create a PR. user: "I think I'm ready to create a PR for this feature" assistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards." <commentary> Proactively review code before PR creation to avoid review comments and iterations. </commentary> </example>