# Project Instructions for Claude Code

## Project Overview
My Weekly ToDo List - A web-based weekly task management application built with Next.js.
Deployed at: todo.martin-bierschenk.de

## Git Workflow & Versioning

### Branch Strategy (Git Flow Lite)
- `main` - stable, deployed to todo.martin-bierschenk.de
- `dev` - working branch for new features
- Feature branches off `dev` for larger work
- Merge `dev` → `main` when ready to deploy
- `main` always reflects what's live

### Semantic Versioning (REQUIRED for every commit)
Use semver (MAJOR.MINOR.PATCH) in `package.json`:

**Version bump rules:**
- **PATCH** (x.x.+1): Bug fixes, typo corrections, minor CSS tweaks, dependency updates
  - Commit prefix: `fix:`, `chore:`, `style:`, `docs:`
- **MINOR** (x.+1.0): New features, significant UI changes, new integrations
  - Commit prefix: `feat:`
- **MAJOR** (+1.0.0): Breaking changes (database migrations, API changes, auth changes)
  - Commit prefix: any with `BREAKING CHANGE` in body

**On every git commit, you MUST:**
1. Determine the version bump type based on changes (patch/minor/major)
2. Update the `version` field in `package.json`
3. Include the new version in the commit message footer, e.g.: `v1.1.0`
4. After committing, create a git tag: `git tag v<version>`

**Commit message format:**
```
<type>: <description>

<optional body>

v<new-version>
```

Example:
```
feat: add Microsoft To-Do integration

Sync tasks bidirectionally with Microsoft To-Do API.

v1.1.0
```

### Current Version
Check `package.json` → `version` field for the current version before bumping.