CloudLaunch Development Assistant

Assists developers working on CloudLaunch, an Electron-based game launcher with save data synchronization, React frontend, and AWS S3 cloud storage.

Project Context

CloudLaunch is a game launcher and save data synchronization application built with:

Instructions for AI Agent

Language Requirements

**CRITICAL**: All output must be in Japanese (日本語). The development team works in Japanese.

Development Workflow

When working on code changes, follow this sequence:

1. **Make code changes** as requested

2. **Run quality checks** (run separately to avoid timeouts):

- `npm run format` - Format code with Prettier

- `npm run typecheck` - TypeScript type checking

- `npm run lint` - ESLint validation

3. **Run tests** if test files exist:

- `npm run test` or `npm run test:vitest`

- Fix any test failures before completing

4. **DO NOT run** `npm run build` unless explicitly requested

Code Quality Standards

#### Documentation Requirements

- What the function does

- Parameter descriptions

- Return value description

- Example usage if complex

#### Type Safety

```typescript

// eslint-disable-next-line @typescript-eslint/no-explicit-any

const variable: any = something;

```

#### Naming Conventions

Follow these consistent naming patterns:

#### Error Handling

#### Security

Project Structure

```

src/

├── main/ # Electron main process (Node.js)

│ ├── ipcHandlers/ # IPC communication handlers

│ ├── service/ # Business logic services

│ └── utils/ # Utility functions

├── preload/ # Electron preload bridge (security)

│ └── api/ # API definitions for renderer

├── renderer/ # React frontend

│ ├── components/ # Reusable UI components

│ ├── pages/ # Route-based pages

│ ├── state/ # Jotai state atoms

│ └── utils/ # Frontend utilities

└── types/ # Shared TypeScript definitions

```

Key Development Commands

```bash

Development

npm run dev # Start dev server with hot reload

Quality Checks (run separately)

npm run format # Format with Prettier

npm run typecheck # TypeScript type checking

npm run lint # ESLint validation

Database

npx prisma migrate dev # Apply migrations

npx prisma generate # Generate Prisma client

npx prisma db seed # Seed test data

Platform Builds (if needed)

npm run build:win # Windows

npm run build:mac # macOS

npm run build:linux # Linux

```

Architecture Patterns

#### IPC Communication

1. Define handler in `src/main/ipcHandlers/`

2. Register handler in `src/main/registerHandlers.ts`

3. Expose safe API in `src/preload/api/`

4. Use type-safe interfaces from `src/types/`

#### State Management

#### Database Schema

Current models:

When Creating New Features

1. **Read existing code** in similar features first

2. **Follow existing patterns** for IPC, state, components

3. **Add comprehensive comments** in Japanese

4. **Test thoroughly** before marking complete

5. **Update documentation** if adding significant functionality

Reference Documentation

For detailed guidelines, refer to:

Constraints

Example Usage

**User**: "Add a feature to filter games by play status"

**Agent**:

1. Reads existing filter implementation in `src/renderer/state/home.ts`

2. Adds new Jotai atom for play status filter

3. Updates UI in `src/renderer/pages/Home.tsx`

4. Adds Japanese comments explaining the feature

5. Runs `npm run format`, `npm run typecheck`, `npm run lint`

6. Reports completion in Japanese with file locations