---
name: ai-movara-conventions
description: Development conventions and patterns for Ai_Movara. JavaScript project with freeform commits.
---

# Ai Movara Conventions

> Generated from [marlo9981/Ai_Movara](https://github.com/marlo9981/Ai_Movara) on 2026-03-16

## Overview

This skill teaches Claude the development patterns and conventions used in Ai_Movara.

## Tech Stack

- **Primary Language**: JavaScript
- **Architecture**: hybrid module organization
- **Test Location**: mixed
- **Test Framework**: unknown

## When to Use This Skill

Activate this skill when:
- Making changes to this repository
- Adding new features following established patterns
- Writing tests that match project conventions
- Creating commits with proper message format

## Commit Conventions

Follow these commit message conventions based on 3 analyzed commits.

### Commit Style: Free-form Messages

### Message Guidelines

- Average message length: ~15 characters
- Keep first line concise and descriptive
- Use imperative mood ("Add feature" not "Added feature")


*Commit message example*

```text
first commit
```

*Commit message example*

```text
lists all modified, added, or deleted files that
```

*Commit message example*

```text
Create Repo
```

## Architecture

### Project Structure: Single Package

This project uses **hybrid** module organization.

### Configuration Files

- `.github/workflows/python.yml`
- `Claude/everything-claude-code-main/.github/workflows/ci.yml`
- `Claude/everything-claude-code-main/.github/workflows/maintenance.yml`
- `Claude/everything-claude-code-main/.github/workflows/monthly-metrics.yml`
- `Claude/everything-claude-code-main/.github/workflows/release.yml`
- `Claude/everything-claude-code-main/.github/workflows/reusable-release.yml`
- `Claude/everything-claude-code-main/.github/workflows/reusable-test.yml`
- `Claude/everything-claude-code-main/.github/workflows/reusable-validate.yml`
- `Claude/everything-claude-code-main/.opencode/package.json`
- `Claude/everything-claude-code-main/.opencode/tsconfig.json`
- `Claude/everything-claude-code-main/.prettierrc`
- `Claude/everything-claude-code-main/eslint.config.js`
- `Claude/everything-claude-code-main/package.json`
- `Claude/everything-claude-code-main/tests/brainstorm-server/package.json`

### Guidelines

- This project uses a hybrid organization
- Follow existing patterns when adding new code

## Code Style

### Language: JavaScript

### Naming Conventions

| Element | Convention |
|---------|------------|
| Files | camelCase |
| Functions | camelCase |
| Classes | PascalCase |
| Constants | SCREAMING_SNAKE_CASE |

### Import Style: Mixed Style

### Export Style: Mixed Style


## Testing

### Test Framework: unknown

### File Pattern: `*.test.js`

### Test Types

- **Unit tests**: Test individual functions and components in isolation
- **Integration tests**: Test interactions between multiple components/services

### Coverage

This project has coverage reporting configured. Aim for 80%+ coverage.


## Error Handling

### Error Handling Style: Try-Catch Blocks


*Standard error handling pattern*

```typescript
try {
  const result = await riskyOperation()
  return result
} catch (error) {
  console.error('Operation failed:', error)
  throw new Error('User-friendly message')
}
```

## Best Practices

Based on analysis of the codebase, follow these practices:

### Do

- Write tests using unknown
- Follow *.test.js naming pattern
- Use camelCase for file names
- Prefer mixed exports

### Don't

- Don't skip tests for new features
- Don't deviate from established patterns without discussion

---

*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*