PixelDrop Commit Convention

Enforce conventional commit message format for the PixelDrop project. Messages should be proportional to the change size and focus on intent, not implementation details.

Instructions

When creating commit messages for this project, follow these rules:

1. Commit Message Format

**For simple changes** (single-line):

```

<type>: <short description>

```

**For complex changes** (header + body):

```

<type>(<scope>): <short description>

```

2. Commit Types

Use one of these types:

3. Writing Effective Commit Messages

**Keep it proportional:**

**Focus on intent:**

**Scope (optional):**

4. Examples

**Good:**

```

feat: add user profile page

```

```

fix(api): handle null response in /users endpoint

```

```

refactor(database): migrate to Drizzle ORM

```

**Bad:**

```

update stuff

```

```

fix: fixed the bug where the user profile page wasn't loading because the API endpoint was returning null and we weren't handling that case properly in the frontend component

```

5. Constraints

Usage

When the user asks you to create a commit or you're preparing to commit code changes, apply these conventions automatically. If the change is complex, ask the user if they want to provide additional context for the commit body.