@goonnguyen/human-mcp 1.3.0 → 2.0.0

package/.opencode/agent/tester.md

@@ -1,96 +0,0 @@
----
-name: tester
-description: "Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes."
-model: opencode/grok-code
-mode: subagent
----
-
-You are a senior QA engineer specializing in comprehensive testing and quality assurance. Your expertise spans unit testing, integration testing, performance validation, and build process verification. You ensure code reliability through rigorous testing practices and detailed analysis.
-
-**Core Responsibilities:**
-
-1. **Test Execution & Validation**
-   - Run all relevant test suites (unit, integration, e2e as applicable)
-   - Execute tests using appropriate test runners (Jest, Mocha, pytest, etc.)
-   - Validate that all tests pass successfully
-   - Identify and report any failing tests with detailed error messages
-   - Check for flaky tests that may pass/fail intermittently
-
-2. **Coverage Analysis**
-   - Generate and analyze code coverage reports
-   - Identify uncovered code paths and functions
-   - Ensure coverage meets project requirements (typically 80%+)
-   - Highlight critical areas lacking test coverage
-   - Suggest specific test cases to improve coverage
-
-3. **Error Scenario Testing**
-   - Verify error handling mechanisms are properly tested
-   - Ensure edge cases are covered
-   - Validate exception handling and error messages
-   - Check for proper cleanup in error scenarios
-   - Test boundary conditions and invalid inputs
-
-4. **Performance Validation**
-   - Run performance benchmarks where applicable
-   - Measure test execution time
-   - Identify slow-running tests that may need optimization
-   - Validate performance requirements are met
-   - Check for memory leaks or resource issues
-
-5. **Build Process Verification**
-   - Ensure the build process completes successfully
-   - Validate all dependencies are properly resolved
-   - Check for build warnings or deprecation notices
-   - Verify production build configurations
-   - Test CI/CD pipeline compatibility
-
-**Working Process:**
-
-1. First, identify the testing scope based on recent changes or specific requirements
-2. Run `flutter analyze` to identify syntax errors
-3. Run the appropriate test suites using project-specific commands
-4. Analyze test results, paying special attention to failures
-5. Generate and review coverage reports
-6. Validate build processes if relevant
-7. Create a comprehensive summary report
-
-**Output Format:**
-
-Your summary report should include:
-- **Test Results Overview**: Total tests run, passed, failed, skipped
-- **Coverage Metrics**: Line coverage, branch coverage, function coverage percentages
-- **Failed Tests**: Detailed information about any failures including error messages and stack traces
-- **Performance Metrics**: Test execution time, slow tests identified
-- **Build Status**: Success/failure status with any warnings
-- **Critical Issues**: Any blocking issues that need immediate attention
-- **Recommendations**: Actionable tasks to improve test quality and coverage
-- **Next Steps**: Prioritized list of testing improvements
-
-**Quality Standards:**
-- Ensure all critical paths have test coverage
-- Validate both happy path and error scenarios
-- Check for proper test isolation (no test interdependencies)
-- Verify tests are deterministic and reproducible
-- Ensure test data cleanup after execution
-
-**Tools & Commands:**
-You should be familiar with common testing commands:
-- `flutter analyze` and `flutter test` for Flutter projects
-- `npm test` or `yarn test` for JavaScript/TypeScript projects
-- `npm run test:coverage` for coverage reports
-- `pytest` or `python -m unittest` for Python projects
-- `go test` for Go projects
-- `cargo test` for Rust projects
-- Docker-based test execution when applicable
-
-**Important Considerations:**
-- Always run tests in a clean environment when possible
-- Consider both unit and integration test results
-- Pay attention to test execution order dependencies
-- Validate that mocks and stubs are properly configured
-- Ensure database migrations or seeds are applied for integration tests
-- Check for proper environment variable configuration
-- Never ignore failing tests just to pass the build
-- Use file system (in markdown format) to hand over reports in `./plans/reports` directory to each other with this file name format: `NNN-from-agent-name-to-agent-name-task-name-report.md`.
-
-When encountering issues, provide clear, actionable feedback on how to resolve them. Your goal is to ensure the codebase maintains high quality standards through comprehensive testing practices.

package/.opencode/agent/ui-ux-developer.md

@@ -1,97 +0,0 @@
----
-description: >-
-  Use this agent when you need to transform visual designs into functional user
-  interfaces, including converting wireframes, mockups, screenshots, or design
-  blueprints into actual UI code. Examples: <example>Context: User has uploaded
-  a wireframe image and wants to implement it as a React component. user:
-  "Here's a wireframe for our login page, can you implement this?" assistant:
-  "I'll use the ui-ux-developer agent to analyze the wireframe and create the
-  corresponding UI implementation." <commentary>Since the user has a visual
-  design that needs to be converted to code, use the ui-ux-developer agent to
-  analyze the image and implement the interface.</commentary></example>
-  <example>Context: User wants to update the design system after implementing
-  new components. user: "I just added several new components to our app, can you
-  update our design system documentation?" assistant: "I'll use the
-  ui-ux-developer agent to review the new components and update our design
-  system guidelines." <commentary>Since this involves design system maintenance
-  and documentation, use the ui-ux-developer agent.</commentary></example>
-mode: all
-model: openrouter/google/gemini-2.5-pro
-temperature: 0.2
----
-You are a senior UI/UX developer with exceptional skills in transforming visual designs into functional, beautiful user interfaces. You combine technical expertise with artistic sensibility to create outstanding user experiences.
-
-## Core Responsibilities
-
-You will analyze visual inputs (wireframes, mockups, screenshots, design blueprints) and transform them into production-ready UI code. You excel at interpreting design intent, maintaining consistency, and creating scalable interface solutions.
-
-## Required Tools and Resources
-
-- Use the `eyes_analyze` tool from the `human` MCP server to read and analyze all visual inputs (images, videos, design visuals)
-- Use `context7` MCP to access the latest documentation for packages, plugins, and frameworks
-- Always respect rules defined in `AGENTS.md` and architecture guidelines in `./docs/codebase-summary.md`
-- Follow all code standards and architectural patterns documented in `./docs`
-- Maintain and update the design system at `./docs/design-system-guideline.md`
-
-## Analysis and Implementation Process
-
-1. **Visual Analysis**: Use `eyes_analyze` to thoroughly examine provided designs, identifying:
-   - Layout structure and component hierarchy
-   - Typography, colors, spacing, and visual patterns
-   - Interactive elements and their expected behaviors
-   - Responsive design considerations
-   - Accessibility requirements
-
-2. **Technical Planning**: Before coding, determine:
-   - Appropriate component architecture
-   - Required dependencies and frameworks
-   - State management needs
-   - Performance considerations
-
-3. **Implementation**: Create clean, maintainable code that:
-   - Accurately reflects the visual design
-   - Follows established coding standards from `./docs`
-   - Uses semantic HTML and proper accessibility attributes
-   - Implements responsive design principles
-   - Maintains consistency with existing design patterns
-
-## Design System Management
-
-You are responsible for maintaining and evolving the design system:
-- Document new components, patterns, and guidelines in `./docs/design-system-guideline.md`
-- Ensure consistency across all UI implementations
-- Create reusable components that follow established patterns
-- Update design tokens (colors, typography, spacing) as needed
-- Provide clear usage examples and best practices
-
-## Reporting and Documentation
-
-Create detailed reports in `./plans/reports` using the naming convention:
-`NNN-from-ui-ux-developer-to-[recipient]-[task-name]-report.md`
-
-Reports should include:
-- Analysis summary of visual inputs
-- Implementation approach and decisions made
-- Components created or modified
-- Design system updates
-- Recommendations for future improvements
-- Screenshots or examples of the final implementation
-
-## Quality Standards
-
-- Ensure pixel-perfect implementation when specified
-- Maintain excellent performance (optimize images, minimize bundle size)
-- Implement proper error states and loading indicators
-- Test across different screen sizes and devices
-- Validate accessibility compliance (WCAG guidelines)
-- Write clean, well-documented code with meaningful component names
-
-## Communication Style
-
-- Provide clear explanations of design decisions
-- Offer alternative approaches when appropriate
-- Highlight potential usability or technical concerns
-- Suggest improvements to enhance user experience
-- Ask clarifying questions when design intent is unclear
-
-Always strive for the perfect balance between aesthetic excellence and technical implementation, creating interfaces that are both beautiful and functional.

package/.opencode/command/cook.md

@@ -1,7 +0,0 @@
----
-description: Implement a feature
----
-
-Start implementing this task follow your Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<tasks>$ARGUMENTS</tasks>
-

package/.opencode/command/debug.md

@@ -1,10 +0,0 @@
----
-description: Debugging technical issues and providing solutions.
----
- 
-**Reported Issues**:
- $ARGUMENTS
-
-Use the `debugger` subagent to find the root cause of the issues, then analyze and explain the reports to the user.
-
-**IMPORTANT**: **Do not** implement the fix automatically.

package/.opencode/command/fix/ci.md

@@ -1,8 +0,0 @@
----
-description: Analyze Github Actions logs and fix issues
----
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-Then use proper developer agents to implement the plan.

package/.opencode/command/fix/fast.md

@@ -1,5 +0,0 @@
----
-description: Analyze and fix the issue [FAST]
----
-Analyze and fix this issue:
-$ARGUMENTS

package/.opencode/command/fix/hard.md

@@ -1,7 +0,0 @@
----
-description: Use subagents to plan and fix hard issues
----
-
-Think hard to plan & start fixing these issues follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<issues>$ARGUMENTS</issues>
-

package/.opencode/command/fix/test.md

@@ -1,16 +0,0 @@
----
-description: Run test suite and fix issues
----
-
-## Reported Issues:
-<issue>
- $ARGUMENTS
-</issue>
-
-## Workflow:
-1. First use `tester` subagent to run the tests.
-2. Then use `debugger` subagent to find the root cause of the issues.
-3. Then use `planner-researcher` subagent to create a implementation plan with TODO tasks in `./plans` directory.
-4. Then implement the plan.
-5. After finishing, delegate to `code-reviewer` agent to review code.
-6. Repeat this process until all tests pass and no more errors are reported.

package/.opencode/command/git/cm.md

@@ -1,5 +0,0 @@
----
-description: Stage all files and create a commit.
----
-Use `git-manager` agent to stage all files and create a commit.
-**IMPORTANT: DO NOT push the changes to remote repository**

package/.opencode/command/git/cp.md

@@ -1,4 +0,0 @@
----
-description: Stage, commit and push all code in the current branch
----
-Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.

package/.opencode/command/plan/ci.md

@@ -1,12 +0,0 @@
----
-description: Analyze Github Actions logs and provide a plan to fix the issues
----
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT:** Ask the user for confirmation before implementing.

package/.opencode/command/plan/two.md

@@ -1,13 +0,0 @@
----
-description: Research & create an implementation plan with 2 approaches
----
-
-Use the `planner-researcher` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT**: **Do not** start implementing.

package/.opencode/command/plan.md

@@ -1,10 +0,0 @@
----
-description: Research, analyze, and create an implementation plan
----
-
-Use the `planner-researcher` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**IMPORTANT**: **Do not** start implementing.

package/.opencode/command/test.md

@@ -1,7 +0,0 @@
----
-description: Debugging technical issues and providing solutions.
----
-
-Use the `tester` subagent to run tests locally and analyze the summary report.
-
-**IMPORTANT**: **Do not** start implementing.

package/.opencode/command/watzup.md

@@ -1,8 +0,0 @@
----
-description: Review recent changes and wrap up the work
----
-Review my current branch and the most recent commits. 
-Provide a detailed summary of all changes, including what was modified, added, or removed. 
-Analyze the overall impact and quality of the changes.
-
-**IMPORTANT**: **Do not** start implementing.

package/.releaserc.json

@@ -1,26 +0,0 @@
-{
-  "branches": ["main"],
-  "plugins": [
-    "@semantic-release/commit-analyzer",
-    "@semantic-release/release-notes-generator",
-    "@semantic-release/changelog",
-    [
-      "@semantic-release/npm",
-      {
-        "npmPublish": true,
-        "publishConfig": {
-          "access": "public",
-          "registry": "https://registry.npmjs.org/"
-        }
-      }
-    ],
-    [
-      "@semantic-release/git",
-      {
-        "assets": ["package.json", "CHANGELOG.md"],
-        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
-      }
-    ],
-    "@semantic-release/github"
-  ]
-}

package/.serena/project.yml

@@ -1,68 +0,0 @@
-# language of the project (csharp, python, rust, java, typescript, go, cpp, or ruby)
-#  * For C, use cpp
-#  * For JavaScript, use typescript
-# Special requirements:
-#  * csharp: Requires the presence of a .sln file in the project folder.
-language: typescript
-
-# whether to use the project's gitignore file to ignore files
-# Added on 2025-04-07
-ignore_all_files_in_gitignore: true
-# list of additional paths to ignore
-# same syntax as gitignore, so you can use * and **
-# Was previously called `ignored_dirs`, please update your config if you are using that.
-# Added (renamed) on 2025-04-07
-ignored_paths: []
-
-# whether the project is in read-only mode
-# If set to true, all editing tools will be disabled and attempts to use them will result in an error
-# Added on 2025-04-18
-read_only: false
-
-
-# list of tool names to exclude. We recommend not excluding any tools, see the readme for more details.
-# Below is the complete list of tools for convenience.
-# To make sure you have the latest list of tools, and to view their descriptions, 
-# execute `uv run scripts/print_tool_overview.py`.
-#
-#  * `activate_project`: Activates a project by name.
-#  * `check_onboarding_performed`: Checks whether project onboarding was already performed.
-#  * `create_text_file`: Creates/overwrites a file in the project directory.
-#  * `delete_lines`: Deletes a range of lines within a file.
-#  * `delete_memory`: Deletes a memory from Serena's project-specific memory store.
-#  * `execute_shell_command`: Executes a shell command.
-#  * `find_referencing_code_snippets`: Finds code snippets in which the symbol at the given location is referenced.
-#  * `find_referencing_symbols`: Finds symbols that reference the symbol at the given location (optionally filtered by type).
-#  * `find_symbol`: Performs a global (or local) search for symbols with/containing a given name/substring (optionally filtered by type).
-#  * `get_current_config`: Prints the current configuration of the agent, including the active and available projects, tools, contexts, and modes.
-#  * `get_symbols_overview`: Gets an overview of the top-level symbols defined in a given file.
-#  * `initial_instructions`: Gets the initial instructions for the current project.
-#     Should only be used in settings where the system prompt cannot be set,
-#     e.g. in clients you have no control over, like Claude Desktop.
-#  * `insert_after_symbol`: Inserts content after the end of the definition of a given symbol.
-#  * `insert_at_line`: Inserts content at a given line in a file.
-#  * `insert_before_symbol`: Inserts content before the beginning of the definition of a given symbol.
-#  * `list_dir`: Lists files and directories in the given directory (optionally with recursion).
-#  * `list_memories`: Lists memories in Serena's project-specific memory store.
-#  * `onboarding`: Performs onboarding (identifying the project structure and essential tasks, e.g. for testing or building).
-#  * `prepare_for_new_conversation`: Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
-#  * `read_file`: Reads a file within the project directory.
-#  * `read_memory`: Reads the memory with the given name from Serena's project-specific memory store.
-#  * `remove_project`: Removes a project from the Serena configuration.
-#  * `replace_lines`: Replaces a range of lines within a file with new content.
-#  * `replace_symbol_body`: Replaces the full definition of a symbol.
-#  * `restart_language_server`: Restarts the language server, may be necessary when edits not through Serena happen.
-#  * `search_for_pattern`: Performs a search for a pattern in the project.
-#  * `summarize_changes`: Provides instructions for summarizing the changes made to the codebase.
-#  * `switch_modes`: Activates modes by providing a list of their names
-#  * `think_about_collected_information`: Thinking tool for pondering the completeness of collected information.
-#  * `think_about_task_adherence`: Thinking tool for determining whether the agent is still on track with the current task.
-#  * `think_about_whether_you_are_done`: Thinking tool for determining whether the task is truly completed.
-#  * `write_memory`: Writes a named memory (for future reference) to Serena's project-specific memory store.
-excluded_tools: []
-
-# initial prompt for the project. It will always be given to the LLM upon activating the project
-# (contrary to the memories, which are loaded on demand).
-initial_prompt: ""
-
-project_name: "human-mcp"

package/CHANGELOG.md

@@ -1,62 +0,0 @@
-# [1.3.0](https://github.com/mrgoonie/human-mcp/compare/v1.2.1...v1.3.0) (2025-09-15)
-
-
-### Bug Fixes
-
-* **test:** resolve SSE transport timeouts and server lifecycle issues ([53baad5](https://github.com/mrgoonie/human-mcp/commit/53baad54c3482e3dfc4c22865f2c04c390718a04))
-
-
-### Features
-
-* add OpenCode agent definitions for code review, debugging, docs, git and planning ([69ef21f](https://github.com/mrgoonie/human-mcp/commit/69ef21fc018a20320cb0cf2113ea01785500b313))
-* **transport:** add Cloudflare R2 HTTP transport file access ([8459b83](https://github.com/mrgoonie/human-mcp/commit/8459b8322172019a9b2cee944c02471113444c19))
-* **transport:** implement SSE fallback for legacy MCP client compatibility ([a2a8041](https://github.com/mrgoonie/human-mcp/commit/a2a8041220577597061efd37e6e1ae167ae40ec5))
-
-## [1.2.1](https://github.com/mrgoonie/human-mcp/compare/v1.2.0...v1.2.1) (2025-09-08)
-
-
-### Bug Fixes
-
-* update tool names to comply with MCP validation pattern ([3c23e10](https://github.com/mrgoonie/human-mcp/commit/3c23e101e843095fb33703dd9431a89936c18308))
-
-# [1.2.0](https://github.com/mrgoonie/human-mcp/compare/v1.1.0...v1.2.0) (2025-09-08)
-
-
-### Features
-
-* make HTTP transport config options configurable via config object ([d9da0f1](https://github.com/mrgoonie/human-mcp/commit/d9da0f1ec01b53dd21ace64e781d6bec269bd763))
-
-# [1.1.0](https://github.com/mrgoonie/human-mcp/compare/v1.0.2...v1.1.0) (2025-09-08)
-
-
-### Features
-
-* add HTTP transport with Docker deployment ([971af50](https://github.com/mrgoonie/human-mcp/commit/971af50cae5ccb50b83a70c29099e4c801b8fcad))
-
-## [1.0.2](https://github.com/mrgoonie/human-mcp/compare/v1.0.1...v1.0.2) (2025-09-08)
-
-
-### Bug Fixes
-
-* **ci:** configure NPM package for public publishing ([3222450](https://github.com/mrgoonie/human-mcp/commit/3222450edae2f40e86cba29dea5c3dfd35bf4fd1))
-
-## [1.0.1](https://github.com/mrgoonie/human-mcp/compare/v1.0.0...v1.0.1) (2025-09-08)
-
-
-### Bug Fixes
-
-* **config:** update NPM publishing configuration for scoped package ([caa26cd](https://github.com/mrgoonie/human-mcp/commit/caa26cd36d6967a935921b62e7478f4074cac671))
-
-# 1.0.0 (2025-09-08)
-
-
-### Bug Fixes
-
-* resolve timeout issues and improve MCP SDK integration ([ccd7f8d](https://github.com/mrgoonie/human-mcp/commit/ccd7f8d44dc9b8f9e5432092e40fa6dd99759dae))
-* **tests:** resolve type mismatches and schema alignment ([f68308b](https://github.com/mrgoonie/human-mcp/commit/f68308bc476be2e47a35da92d9b766c0c2d02a93))
-
-
-### Features
-
-* add claude agent definitions for code review, database, debugging, docs and git management ([8203456](https://github.com/mrgoonie/human-mcp/commit/8203456615ca498074657a07a25cea99b9d538fb))
-* add semantic-release automation with GitHub Actions ([3733a38](https://github.com/mrgoonie/human-mcp/commit/3733a38b1ab90ef37e44af2726ec0b3cec88932e))

package/CLAUDE.md

@@ -1,141 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-Human MCP is a Model Context Protocol server that provides AI coding agents with visual analysis capabilities for debugging UI issues, processing screenshots, videos, and GIFs using Google Gemini AI.
-
-## Development Commands
-
-### Core Commands
-- `bun run dev` - Start development server with hot reload
-- `bun run build` - Build for production (outputs to dist/)
-- `bun run start` - Run production build
-- `bun test` - Run test suite
-- `bun run typecheck` - Run TypeScript type checking
-- `bun run inspector` - Launch MCP inspector for testing tools
-
-### Testing with MCP Inspector
-The inspector tool is crucial for testing MCP tools during development:
-```bash
-bun run inspector
-```
-
-## Architecture
-
-### Core Structure
-```
-src/
-├── index.ts          # Entry point, starts stdio server
-├── server.ts         # MCP server setup and initialization  
-├── tools/eyes/       # Vision analysis tools (main functionality)
-├── prompts/          # Pre-built debugging prompts
-├── resources/        # Documentation resources
-└── utils/           # Configuration, logging, error handling
-```
-
-### Key Components
-
-**Vision Analysis (tools/eyes/)**
-- `index.ts` - Registers eyes_analyze and eyes_compare tools
-- `processors/` - Handles image, video, and GIF processing
-- `utils/gemini-client.ts` - Google Gemini API integration
-- `schemas.ts` - Zod validation schemas for tool inputs
-
-**Configuration (utils/config.ts)**
-- Environment-based configuration using Zod validation
-- Required: `GOOGLE_GEMINI_API_KEY`
-- Optional settings for timeouts, caching, rate limits
-
-## MCP Tools
-
-**Important**: Tool names must comply with MCP validation pattern `^[a-zA-Z0-9_-]{1,64}$`. Only alphanumeric characters, underscores, and hyphens are allowed. No dots, spaces, or other special characters.
-
-### eyes_analyze
-Primary tool for visual analysis of images, videos, and GIFs:
-- Supports file paths, URLs, and base64 data URIs
-- Configurable detail levels (quick/detailed)
-- Frame extraction for videos and GIFs
-- Custom analysis prompts
-
-### eyes_compare  
-Compares two images to identify visual differences:
-- Three comparison types: pixel, structural, semantic
-- Detailed difference reporting
-- Impact assessment and recommendations
-
-## Important Development Notes
-
-### Google Gemini Documentation
-- [Gemini API](https://ai.google.dev/gemini-api/docs?hl=en)
-- [Gemini Models](https://ai.google.dev/gemini-api/docs/models)
-- [Video Understanding](https://ai.google.dev/gemini-api/docs/video-understanding?hl=en)
-- [Image Understanding](https://ai.google.dev/gemini-api/docs/image-understanding)
-- [Document Understanding](https://ai.google.dev/gemini-api/docs/document-processing)
-- [Audio Understanding](https://ai.google.dev/gemini-api/docs/audio)
-- [Speech Generation](https://ai.google.dev/gemini-api/docs/speech-generation)
-- [Image Generation](https://ai.google.dev/gemini-api/docs/image-generation)
-- [Video Generation](https://ai.google.dev/gemini-api/docs/video)
-
-### Error Handling
-- All tool operations use centralized error handling via `utils/errors.ts`
-- Errors are logged and returned as structured MCP responses
-- Network timeouts are configurable via environment variables
-
-### Media Processing
-- Images: PNG, JPEG, WebP, GIF (static)
-- Videos: MP4, WebM, MOV, AVI (uses ffmpeg via fluent-ffmpeg)  
-- GIFs: Frame extraction using Sharp library
-- All processors handle file paths, URLs, and base64 data
-
-### TypeScript Configuration
-- Uses ESNext modules with bundler resolution
-- Path mapping: `@/*` maps to `src/*`
-- Strict type checking enabled
-- No emit mode (Bun handles compilation)
-
-### Google Gemini Integration
-- Uses Google Generative AI SDK
-- Model selection based on detail level
-- Configurable via `GOOGLE_GEMINI_MODEL` environment variable
-- Default: `gemini-2.5-flash`
-
-## Testing
-
-Run tests with `bun test`. The project uses Bun's built-in test runner.
-
-For manual testing of MCP tools, use the inspector:
-```bash
-bun run inspector
-```
-
-This launches a web interface for testing tool functionality interactively.
-
----
-
-## Development Rules
-
-### General
-- Use `pnpm` instead of `npm` or `yarn` for package management
-- Use `context7` mcp tools for exploring latest docs of plugins/packages
-- Use `senera` mcp tools for semantic retrieval and editing capabilities
-
-### Code Quality Guidelines
-- Read and follow strictly codebase structure and code standards in `./docs`
-- Don't be too harsh on code linting, but make sure there are no syntax errors and code are compilable
-- Prioritize functionality and readability over strict style enforcement and code formatting
-- Use reasonable code quality standards that enhance developer productivity
-- Use try catch error handling & cover security standards
-- Use `code-reviewer` agent to review code after every implementation
-
-### Pre-commit/Push Rules
-- Run linting before commit
-- Run tests before push (DO NOT ignore failed tests just to pass the build or github actions)
-- Keep commits focused on the actual code changes
-- **DO NOT** commit and push any confidential information (such as dotenv files, API keys, database credentials, etc.) to git repository!
-- NEVER automatically add AI attribution signatures like:
-  "🤖 Generated with [Claude Code]"
-  "Co-Authored-By: Claude noreply@anthropic.com"
-  Any AI tool attribution or signature
-- Create clean, professional commit messages without AI references. Use conventional commit format.