developer-toolkit

Read the task logs stored in the Obsidian page $ARGUMENTS and absorb the context.

인자: $ARGUMENTS

당신은 새로운 도메인 모듈 확장/기능 구현의 계획서를 만드는 역할입니다.

구현 계획서를 기반으로 배치 단위 구현을 실행합니다.

`/call-ralph <프롬프트> m:<max-iterations> c:<completion-promise>`

`/call-verifiers [플래그] [범위] [p:<계획서>]`

Please add comprehensive documentation(TSDocs) to the code in the current file. $ARGUMENTS

Explain how $ARGUMENTS works as if I'm a new developer on the team. Show me the execution flow and usage examples.

**위치**: `~/Desktop/DADA/`

ARGUMENT: &ARGUMENT

인자: $ARGUMENTS

인자: $ARGUMENTS

dev 브랜치에서 pull 받되, 충돌 발생 시 **파일 단위가 아닌 충돌 블록 단위**로 현재 변경사항을 우선 적용한다.

Use this agent when you need to create, update, or enhance documentation for any part of the codebase. This includes developer documentation, README files, API documentation, data flow diagrams, testing documentation, or architectural overviews. The agent will gather comprehensive context from memory, existing documentation, and related files to produce high-quality documentation that captures the complete picture. <example> Context: User has just implemented a new authentication flow and needs documentation. user: "I've finished implementing the JWT cookie-based authentication. Can you document this?" assistant: "I'll use the documentation-architect agent to create comprehensive documentation for the authentication system." <commentary> Since the user needs documentation for a newly implemented feature, use the documentation-architect agent to gather all context and create appropriate documentation. </commentary> </example> <example> Context: User is working on a complex workflow engine and needs to document the data flow. user: "The workflow engine is getting complex. We need to document how data flows through the system." assistant: "Let me use the documentation-architect agent to analyze the workflow engine and create detailed data flow documentation." <commentary> The user needs data flow documentation for a complex system, which is a perfect use case for the documentation-architect agent. </commentary> </example> <example> Context: User has made changes to an API and needs to update the API documentation. user: "I've added new endpoints to the form service API. The docs need updating." assistant: "I'll launch the documentation-architect agent to update the API documentation with the new endpoints." <commentary> API documentation needs updating after changes, so use the documentation-architect agent to ensure comprehensive and accurate documentation. </commentary> </example>

Use this agent when you encounter frontend errors, whether they appear during the build process (TypeScript, bundling, linting errors) or at runtime in the browser console (JavaScript errors, React errors, network issues). This agent specializes in diagnosing and fixing frontend issues with precision. Examples: - <example> Context: User encounters an error in their React application user: "I'm getting a 'Cannot read property of undefined' error in my React component" assistant: "I'll use the frontend-error-fixer agent to diagnose and fix this runtime error" <commentary> Since the user is reporting a browser console error, use the frontend-error-fixer agent to investigate and resolve the issue. </commentary> </example> - <example> Context: Build process is failing user: "My build is failing with a TypeScript error about missing types" assistant: "Let me use the frontend-error-fixer agent to resolve this build error" <commentary> The user has a build-time error, so the frontend-error-fixer agent should be used to fix the TypeScript issue. </commentary> </example> - <example> Context: User notices errors in browser console while testing user: "I just implemented a new feature and I'm seeing some errors in the console when I click the submit button" assistant: "I'll launch the frontend-error-fixer agent to investigate these console errors using the browser tools" <commentary> Runtime errors are appearing during user interaction, so the frontend-error-fixer agent should investigate using browser tools MCP. </commentary> </example>

계획서(.claude/plans/*.md) 대비 구현 코드를 항목별로 엄격하게 검증하는 에이전트. 구현 완료 후 누락/과잉/불일치를 찾아 체크리스트 리포트를 생성한다.

Use this agent when you need to research information on the internet, particularly for debugging issues, finding solutions to technical problems, or gathering comprehensive information from multiple sources. This agent excels at finding relevant discussions in GitHub issues, Reddit threads, Stack Overflow, forums, and other community resources. Use when you need creative search strategies, thorough investigation of a topic, or compilation of findings from diverse sources. Examples: - <example> Context: The user is encountering a specific error with a library and needs to find if others have solved it. user: "I'm getting a 'Module not found' error with the new version of webpack, can you help me debug this?" assistant: "I'll use the web-research-specialist agent to search for similar issues and solutions across various forums and repositories." <commentary> Since the user needs help debugging an issue that others might have encountered, use the web-research-specialist agent to search for solutions. </commentary> </example> - <example> Context: The user needs comprehensive information about a technology or approach. user: "I need to understand the pros and cons of different state management solutions for React." assistant: "Let me use the web-research-specialist agent to research and compile a detailed comparison of different state management solutions." <commentary> The user needs research and comparison from multiple sources, which is perfect for the web-research-specialist agent. </commentary> </example> - <example> Context: The user is implementing a feature and wants to see how others have approached it. user: "How do other developers typically implement infinite scrolling with virtualization?" assistant: "I'll use the web-research-specialist agent to research various implementation approaches and best practices from the community." <commentary> This requires researching multiple implementation approaches from various sources, ideal for the web-research-specialist agent. </commentary> </example>

Use when the user wants to create an agent team, coordinate multiple agents, or needs help deciding team composition for a development task. Triggers on keywords like team, swarm, agent team, parallel agents, role-based development.

Generate architecture diagrams as .excalidraw files from codebase analysis, with optional PNG/SVG export. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, generate excalidraw files, export excalidraw diagrams to PNG or SVG, or convert .excalidraw files to image formats.

현재 세션의 작업 내용을 옵시디언 볼트에 템플릿에 맞춰 저장하고 /clear로 컨텍스트를 초기화한다. 컨텍스트가 길어졌다고 느낄 때 직접 호출.

슬랙 스레드 업로드를 위한 문서 정리 스킬. 원본 메모를 회의록, 건의/제안, 보고서 양식으로 구조화합니다.