{"owner":"coze-dev","repo":"coze-studio","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md"],"skills":{"CLAUDE.md":"# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n\n## Project Overview\n\nCoze Studio is an all-in-one AI agent development platform with both frontend (React + TypeScript) and backend (Go) components. The project uses a sophisticated monorepo architecture managed by Rush.js with 135+ frontend packages organized in a hierarchical dependency system.\n\n## Development Commands\n\n### Environment Setup\n```bash\n# Clone and setup\ngit clone https://github.com/coze-dev/coze-studio.git\ncd coze-studio\n\n# Install frontend dependencies\nrush update\n\n# For Docker-based development\ncd docker\ncp .env.example .env\n# Configure model settings in backend/conf/model/\ndocker compose up -d\n# Access at http://localhost:8888\n```\n\n### Development Workflow\n```bash\n# Start middleware services (MySQL, Redis, Elasticsearch, etc.)\nmake middleware\n\n# Start Go backend in development mode\nmake server\n\n# Start frontend development server\ncd frontend/apps/coze-studio\nnpm run dev\n\n# Full development environment\nmake debug\n```\n\n### Build Commands\n```bash\n# Build frontend only\nmake fe\n\n# Build Go server\nmake build_server\n\n# Build everything with Docker\nmake web\n\n# Rush monorepo commands\nrush build                    # Build all packages\nrush rebuild -o @coze-studio/app  # Build specific package\nrush test                     # Run all tests\nrush lint                     # Lint all packages\n```\n\n### Testing\n```bash\n# Run tests (Vitest-based)\nrush test\nnpm run test                  # In specific package\nnpm run test:cov             # With coverage\n\n# Backend tests\ncd backend && go test ./...\n```\n\n## Architecture Overview\n\n### Frontend Architecture\n- **Monorepo**: Rush.js with 135+ packages across 4 dependency levels\n- **Build System**: Rsbuild (Rspack-based) for fast builds\n- **UI Framework**: React 18 + TypeScript + Semi Design + Tailwind CSS\n- **State Management**: Zustand for global state\n- **Package Organization**:\n  - `arch/`: Core infrastructure (level-1)\n  - `common/`: Shared components and utilities (level-2)\n  - `agent-ide/`, `workflow/`, `studio/`: Feature domains (level-3)\n  - `apps/coze-studio`: Main application (level-4)\n\n### Backend Architecture (Go)\n- **Framework**: Hertz HTTP framework\n- **Architecture**: Domain-Driven Design (DDD) with microservices\n- **Structure**:\n  - `domain/`: Business logic and entities\n  - `application/`: Application services and use cases\n  - `api/`: HTTP handlers and routing\n  - `infra/`: Infrastructure implementations\n  - `crossdomain/`: Cross-cutting concerns\n\n### Key Architectural Patterns\n- **Adapter Pattern**: Extensive use for loose coupling between layers\n- **Interface Segregation**: Clear contracts between domains\n- **Event-Driven**: NSQ message queue for async communication\n- **API-First**: Comprehensive OpenAPI specifications\n\n## Database & Infrastructure\n\n### Docker Services Stack\n- **Database**: MySQL 8.4.5\n- **Cache**: Redis 8.0\n- **Search**: Elasticsearch 8.18.0 with SmartCN analyzer\n- **Vector DB**: Milvus v2.5.10 for embeddings\n- **Storage**: MinIO for object storage\n- **Message Queue**: NSQ (nsqlookupd, nsqd, nsqadmin)\n- **Configuration**: etcd 3.5\n\n### Database Management\n```bash\n# Sync database schema\nmake sync_db\n\n# Dump database schema\nmake dump_db\n\n# Initialize SQL data\nmake sql_init\n\n# Atlas migration management\nmake atlas-hash\n```\n\n## Key Development Patterns\n\n### Frontend Package Development\n- Each package follows consistent structure with `README.md`, `package.json`, `tsconfig.json`, `eslint.config.js`\n- Adapter pattern extensively used for decoupling (e.g., `-adapter` suffix packages)\n- Base/Core pattern for shared functionality (e.g., `-base` suffix packages)\n- Use workspace references (`workspace:*`) for internal dependencies\n\n### Backend Development\n- Follow DDD principles with clear domain boundaries\n- Use dependency injection via interfaces\n- Implement proper error handling with custom error types\n- Write comprehensive tests for domain logic\n\n### Model Configuration\nBefore deployment, configure AI models in `backend/conf/model/`:\n1. Copy template from `backend/conf/model/template/`\n2. Set `id`, `meta.conn_config.api_key`, and `meta.conn_config.model`\n3. Supported providers: OpenAI, Volcengine Ark, Claude, Gemini, Qwen, DeepSeek, Ollama\n\n## Testing Strategy\n\n### Coverage Requirements by Package Level\n- **Level 1**: 80% coverage, 90% increment\n- **Level 2**: 30% coverage, 60% increment\n- **Level 3-4**: 0% coverage (flexible)\n\n### Testing Framework\n- **Frontend**: Vitest for unit/integration tests\n- **Backend**: Go's built-in testing framework\n- **E2E**: Separate e2e subspace configuration\n\n## Common Issues & Solutions\n\n### Frontend Development\n- Use `rush update` instead of `npm install` at root level\n- Build packages in dependency order using `rush build`\n- For hot reload issues, check Rsbuild configuration in specific package\n\n### Backend Development\n- Ensure middleware services are running (`make middleware`)\n- Check database connectivity and schema sync\n- Verify model configurations are properly set\n\n### Docker Issues\n- Ensure sufficient resources (minimum 2 Core, 4GB RAM)\n- Check port conflicts (8888 for frontend, various for services)\n- Use `make clean` to reset Docker volumes if needed\n\n## IDL and Code Generation\n\nThe project uses Interface Definition Language (IDL) for API contract management:\n- IDL files in `idl/` directory (Thrift format)\n- Frontend code generation via `@coze-arch/idl2ts-*` packages\n- Backend uses generated Go structs\n\n## Plugin Development\n\nFor custom plugin development:\n- Reference templates in `backend/conf/plugin/pluginproduct/`\n- Follow OAuth schema in `backend/conf/plugin/common/oauth_schema.json`\n- Configure authentication keys for third-party services\n\n## Contributing\n\n- Use conventional commits via `rush commit`\n- Run linting with `rush lint-staged` (pre-commit hook)\n- Ensure tests pass before submitting PRs\n- Follow team-based package organization and tagging conventions"},"files":{"CLAUDE.md":"# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n\n## Project Overview\n\nCoze Studio is an all-in-one AI agent development platform with both frontend (React + TypeScript) and backend (Go) components. The project uses a sophisticated monorepo architecture managed by Rush.js with 135+ frontend packages organized in a hierarchical dependency system.\n\n## Development Commands\n\n### Environment Setup\n```bash\n# Clone and setup\ngit clone https://github.com/coze-dev/coze-studio.git\ncd coze-studio\n\n# Install frontend dependencies\nrush update\n\n# For Docker-based development\ncd docker\ncp .env.example .env\n# Configure model settings in backend/conf/model/\ndocker compose up -d\n# Access at http://localhost:8888\n```\n\n### Development Workflow\n```bash\n# Start middleware services (MySQL, Redis, Elasticsearch, etc.)\nmake middleware\n\n# Start Go backend in development mode\nmake server\n\n# Start frontend development server\ncd frontend/apps/coze-studio\nnpm run dev\n\n# Full development environment\nmake debug\n```\n\n### Build Commands\n```bash\n# Build frontend only\nmake fe\n\n# Build Go server\nmake build_server\n\n# Build everything with Docker\nmake web\n\n# Rush monorepo commands\nrush build                    # Build all packages\nrush rebuild -o @coze-studio/app  # Build specific package\nrush test                     # Run all tests\nrush lint                     # Lint all packages\n```\n\n### Testing\n```bash\n# Run tests (Vitest-based)\nrush test\nnpm run test                  # In specific package\nnpm run test:cov             # With coverage\n\n# Backend tests\ncd backend && go test ./...\n```\n\n## Architecture Overview\n\n### Frontend Architecture\n- **Monorepo**: Rush.js with 135+ packages across 4 dependency levels\n- **Build System**: Rsbuild (Rspack-based) for fast builds\n- **UI Framework**: React 18 + TypeScript + Semi Design + Tailwind CSS\n- **State Management**: Zustand for global state\n- **Package Organization**:\n  - `arch/`: Core infrastructure (level-1)\n  - `common/`: Shared components and utilities (level-2)\n  - `agent-ide/`, `workflow/`, `studio/`: Feature domains (level-3)\n  - `apps/coze-studio`: Main application (level-4)\n\n### Backend Architecture (Go)\n- **Framework**: Hertz HTTP framework\n- **Architecture**: Domain-Driven Design (DDD) with microservices\n- **Structure**:\n  - `domain/`: Business logic and entities\n  - `application/`: Application services and use cases\n  - `api/`: HTTP handlers and routing\n  - `infra/`: Infrastructure implementations\n  - `crossdomain/`: Cross-cutting concerns\n\n### Key Architectural Patterns\n- **Adapter Pattern**: Extensive use for loose coupling between layers\n- **Interface Segregation**: Clear contracts between domains\n- **Event-Driven**: NSQ message queue for async communication\n- **API-First**: Comprehensive OpenAPI specifications\n\n## Database & Infrastructure\n\n### Docker Services Stack\n- **Database**: MySQL 8.4.5\n- **Cache**: Redis 8.0\n- **Search**: Elasticsearch 8.18.0 with SmartCN analyzer\n- **Vector DB**: Milvus v2.5.10 for embeddings\n- **Storage**: MinIO for object storage\n- **Message Queue**: NSQ (nsqlookupd, nsqd, nsqadmin)\n- **Configuration**: etcd 3.5\n\n### Database Management\n```bash\n# Sync database schema\nmake sync_db\n\n# Dump database schema\nmake dump_db\n\n# Initialize SQL data\nmake sql_init\n\n# Atlas migration management\nmake atlas-hash\n```\n\n## Key Development Patterns\n\n### Frontend Package Development\n- Each package follows consistent structure with `README.md`, `package.json`, `tsconfig.json`, `eslint.config.js`\n- Adapter pattern extensively used for decoupling (e.g., `-adapter` suffix packages)\n- Base/Core pattern for shared functionality (e.g., `-base` suffix packages)\n- Use workspace references (`workspace:*`) for internal dependencies\n\n### Backend Development\n- Follow DDD principles with clear domain boundaries\n- Use dependency injection via interfaces\n- Implement proper error handling with custom error types\n- Write comprehensive tests for domain logic\n\n### Model Configuration\nBefore deployment, configure AI models in `backend/conf/model/`:\n1. Copy template from `backend/conf/model/template/`\n2. Set `id`, `meta.conn_config.api_key`, and `meta.conn_config.model`\n3. Supported providers: OpenAI, Volcengine Ark, Claude, Gemini, Qwen, DeepSeek, Ollama\n\n## Testing Strategy\n\n### Coverage Requirements by Package Level\n- **Level 1**: 80% coverage, 90% increment\n- **Level 2**: 30% coverage, 60% increment\n- **Level 3-4**: 0% coverage (flexible)\n\n### Testing Framework\n- **Frontend**: Vitest for unit/integration tests\n- **Backend**: Go's built-in testing framework\n- **E2E**: Separate e2e subspace configuration\n\n## Common Issues & Solutions\n\n### Frontend Development\n- Use `rush update` instead of `npm install` at root level\n- Build packages in dependency order using `rush build`\n- For hot reload issues, check Rsbuild configuration in specific package\n\n### Backend Development\n- Ensure middleware services are running (`make middleware`)\n- Check database connectivity and schema sync\n- Verify model configurations are properly set\n\n### Docker Issues\n- Ensure sufficient resources (minimum 2 Core, 4GB RAM)\n- Check port conflicts (8888 for frontend, various for services)\n- Use `make clean` to reset Docker volumes if needed\n\n## IDL and Code Generation\n\nThe project uses Interface Definition Language (IDL) for API contract management:\n- IDL files in `idl/` directory (Thrift format)\n- Frontend code generation via `@coze-arch/idl2ts-*` packages\n- Backend uses generated Go structs\n\n## Plugin Development\n\nFor custom plugin development:\n- Reference templates in `backend/conf/plugin/pluginproduct/`\n- Follow OAuth schema in `backend/conf/plugin/common/oauth_schema.json`\n- Configure authentication keys for third-party services\n\n## Contributing\n\n- Use conventional commits via `rush commit`\n- Run linting with `rush lint-staged` (pre-commit hook)\n- Ensure tests pass before submitting PRs\n- Follow team-based package organization and tagging conventions"},"items":[{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n\n## Project Overview\n\nCoze Studio is an all-in-one AI agent development platform with both frontend (React + TypeScript) and backend (Go) components. The project uses a sophisticated monorepo architecture managed by Rush.js with 135+ frontend packages organized in a hierarchical dependency system.\n\n## Development Commands\n\n### Environment Setup\n```bash\n# Clone and setup\ngit clone https://github.com/coze-dev/coze-studio.git\ncd coze-studio\n\n# Install frontend dependencies\nrush update\n\n# For Docker-based development\ncd docker\ncp .env.example .env\n# Configure model settings in backend/conf/model/\ndocker compose up -d\n# Access at http://localhost:8888\n```\n\n### Development Workflow\n```bash\n# Start middleware services (MySQL, Redis, Elasticsearch, etc.)\nmake middleware\n\n# Start Go backend in development mode\nmake server\n\n# Start frontend development server\ncd frontend/apps/coze-studio\nnpm run dev\n\n# Full development environment\nmake debug\n```\n\n### Build Commands\n```bash\n# Build frontend only\nmake fe\n\n# Build Go server\nmake build_server\n\n# Build everything with Docker\nmake web\n\n# Rush monorepo commands\nrush build                    # Build all packages\nrush rebuild -o @coze-studio/app  # Build specific package\nrush test                     # Run all tests\nrush lint                     # Lint all packages\n```\n\n### Testing\n```bash\n# Run tests (Vitest-based)\nrush test\nnpm run test                  # In specific package\nnpm run test:cov             # With coverage\n\n# Backend tests\ncd backend && go test ./...\n```\n\n## Architecture Overview\n\n### Frontend Architecture\n- **Monorepo**: Rush.js with 135+ packages across 4 dependency levels\n- **Build System**: Rsbuild (Rspack-based) for fast builds\n- **UI Framework**: React 18 + TypeScript + Semi Design + Tailwind CSS\n- **State Management**: Zustand for global state\n- **Package Organization**:\n  - `arch/`: Core infrastructure (level-1)\n  - `common/`: Shared components and utilities (level-2)\n  - `agent-ide/`, `workflow/`, `studio/`: Feature domains (level-3)\n  - `apps/coze-studio`: Main application (level-4)\n\n### Backend Architecture (Go)\n- **Framework**: Hertz HTTP framework\n- **Architecture**: Domain-Driven Design (DDD) with microservices\n- **Structure**:\n  - `domain/`: Business logic and entities\n  - `application/`: Application services and use cases\n  - `api/`: HTTP handlers and routing\n  - `infra/`: Infrastructure implementations\n  - `crossdomain/`: Cross-cutting concerns\n\n### Key Architectural Patterns\n- **Adapter Pattern**: Extensive use for loose coupling between layers\n- **Interface Segregation**: Clear contracts between domains\n- **Event-Driven**: NSQ message queue for async communication\n- **API-First**: Comprehensive OpenAPI specifications\n\n## Database & Infrastructure\n\n### Docker Services Stack\n- **Database**: MySQL 8.4.5\n- **Cache**: Redis 8.0\n- **Search**: Elasticsearch 8.18.0 with SmartCN analyzer\n- **Vector DB**: Milvus v2.5.10 for embeddings\n- **Storage**: MinIO for object storage\n- **Message Queue**: NSQ (nsqlookupd, nsqd, nsqadmin)\n- **Configuration**: etcd 3.5\n\n### Database Management\n```bash\n# Sync database schema\nmake sync_db\n\n# Dump database schema\nmake dump_db\n\n# Initialize SQL data\nmake sql_init\n\n# Atlas migration management\nmake atlas-hash\n```\n\n## Key Development Patterns\n\n### Frontend Package Development\n- Each package follows consistent structure with `README.md`, `package.json`, `tsconfig.json`, `eslint.config.js`\n- Adapter pattern extensively used for decoupling (e.g., `-adapter` suffix packages)\n- Base/Core pattern for shared functionality (e.g., `-base` suffix packages)\n- Use workspace references (`workspace:*`) for internal dependencies\n\n### Backend Development\n- Follow DDD principles with clear domain boundaries\n- Use dependency injection via interfaces\n- Implement proper error handling with custom error types\n- Write comprehensive tests for domain logic\n\n### Model Configuration\nBefore deployment, configure AI models in `backend/conf/model/`:\n1. Copy template from `backend/conf/model/template/`\n2. Set `id`, `meta.conn_config.api_key`, and `meta.conn_config.model`\n3. Supported providers: OpenAI, Volcengine Ark, Claude, Gemini, Qwen, DeepSeek, Ollama\n\n## Testing Strategy\n\n### Coverage Requirements by Package Level\n- **Level 1**: 80% coverage, 90% increment\n- **Level 2**: 30% coverage, 60% increment\n- **Level 3-4**: 0% coverage (flexible)\n\n### Testing Framework\n- **Frontend**: Vitest for unit/integration tests\n- **Backend**: Go's built-in testing framework\n- **E2E**: Separate e2e subspace configuration\n\n## Common Issues & Solutions\n\n### Frontend Development\n- Use `rush update` instead of `npm install` at root level\n- Build packages in dependency order using `rush build`\n- For hot reload issues, check Rsbuild configuration in specific package\n\n### Backend Development\n- Ensure middleware services are running (`make middleware`)\n- Check database connectivity and schema sync\n- Verify model configurations are properly set\n\n### Docker Issues\n- Ensure sufficient resources (minimum 2 Core, 4GB RAM)\n- Check port conflicts (8888 for frontend, various for services)\n- Use `make clean` to reset Docker volumes if needed\n\n## IDL and Code Generation\n\nThe project uses Interface Definition Language (IDL) for API contract management:\n- IDL files in `idl/` directory (Thrift format)\n- Frontend code generation via `@coze-arch/idl2ts-*` packages\n- Backend uses generated Go structs\n\n## Plugin Development\n\nFor custom plugin development:\n- Reference templates in `backend/conf/plugin/pluginproduct/`\n- Follow OAuth schema in `backend/conf/plugin/common/oauth_schema.json`\n- Configure authentication keys for third-party services\n\n## Contributing\n\n- Use conventional commits via `rush commit`\n- Run linting with `rush lint-staged` (pre-commit hook)\n- Ensure tests pass before submitting PRs\n- Follow team-based package organization and tagging conventions","category":"root","tokens":1503}]}