Software Development Tools

Use this agent when the user needs to understand open-source libraries, find implementation details in codebases, locate specific source code with GitHub permalinks, research the history or context behind code changes, or get authoritative answers backed by actual code evidence. This agent excels at navigating large open-source repositories and providing citations to exact lines of code. Examples: <example> Context: User wants to understand how a popular library implements a specific feature. user: "How does React Query handle stale time internally?" assistant: "I'm going to use the Task tool to launch the open-source-librarian agent to find the implementation details with source code evidence." <commentary> Since the user is asking about internal implementation of an open-source library, use the open-source-librarian agent to clone the repo, locate the relevant source code, and provide GitHub permalinks to the exact implementation. </commentary> </example> <example> Context: User needs to find documentation and best practices for a library. user: "What's the best way to handle optimistic updates in TanStack Query?" assistant: "I'll use the open-source-librarian agent to research the official documentation and find real-world implementation examples." <commentary> This is a conceptual question about library usage. The open-source-librarian agent will search official docs via context7, find recent articles, and locate code examples with proper citations. </commentary> </example> <example> Context: User wants to understand why a specific change was made to a library. user: "Why did Next.js change their routing approach in version 13?" assistant: "Let me use the open-source-librarian agent to research the history and context behind this architectural change." <commentary> This is a context/history question. The agent will search issues, PRs, release notes, and git history to find the reasoning and provide links to relevant discussions. </commentary> </example> <example> Context: User needs to locate specific source code in an open-source project. user: "Can you show me where Zod validates email formats?" assistant: "I'm going to use the open-source-librarian agent to find the exact source code with a permalink." <commentary> This is an implementation reference request. The agent will clone the repo, search for the email validation logic, and provide a GitHub permalink to the specific lines of code. </commentary> </example>

Use when the user asks about architecture, SOLID principles, hexagonal architecture, or design patterns.

Use this agent when you need to create, update, or improve technical documentation for a codebase. This includes README files, API documentation, architecture docs, user guides, and any other developer-facing documentation. The agent excels at exploring unfamiliar codebases and transforming complex technical concepts into clear, accurate documentation. Examples: <example> Context: User needs documentation for a new API endpoint. user: "I just finished implementing the /users/export endpoint. Can you document it?" assistant: "I'll use the tech-docs-writer agent to create comprehensive API documentation for the new endpoint." <commentary> Since the user needs API documentation created, use the Task tool to launch the tech-docs-writer agent to explore the endpoint implementation and create accurate documentation with verified request/response examples. </commentary> </example> <example> Context: User wants to update outdated README. user: "Our README is out of date and doesn't reflect the current installation process" assistant: "I'll launch the tech-docs-writer agent to audit and update the README with accurate installation instructions." <commentary> Since the user needs documentation updated, use the Task tool to launch the tech-docs-writer agent to verify current installation steps and update the README accordingly. </commentary> </example> <example> Context: User has a todo list with documentation tasks. user: "Please work through the documentation tasks in docs/ai-todo.md" assistant: "I'll use the tech-docs-writer agent to execute the next documentation task from the todo list." <commentary> Since the user has a documentation todo list, use the Task tool to launch the tech-docs-writer agent to read the todo file, identify the current task, and execute it with full verification. </commentary> </example> <example> Context: User completed a feature and needs architecture documentation. user: "I just built a new caching layer. Can you document the architecture?" assistant: "I'll launch the tech-docs-writer agent to explore the caching implementation and create architecture documentation explaining the design decisions and data flow." <commentary> Since the user needs architecture documentation, use the Task tool to launch the tech-docs-writer agent to analyze the caching layer code and create comprehensive architecture docs. </commentary> </example>

1 hook across 1 event