Taskfile Task Naming Conventions

This rule applies to files matching the patterns above.

# Taskfile Task Naming Conventions

## Rule
All Taskfile tasks MUST use kebab-case naming with verb-noun patterns. Included tasks use colon-separated namespaces.

## Format
```yaml
tasks:
  # Good: kebab-case, verb-noun
  build-app:
    desc: Build the application
  run-tests:
    desc: Run test suite
  docker-build:
    desc: Build Docker image
  deploy-staging:
    desc: Deploy to staging

  # Namespaced (from includes)
  # docker:build, docker:push, test:unit, test:e2e
```

## Naming Patterns
| Pattern | Example | Use Case |
|---------|---------|----------|
| Simple verb | build, test, lint, clean | Standard actions |
| Verb-noun | docker-build, run-tests | Specific actions |
| Namespace:verb | docker:build, test:unit | Included tasks |

## Standard Names (Use These)
| Task | Purpose |
|------|---------|
| setup | First-time project setup |
| dev | Start development mode |
| build | Build production artifact |
| test | Run all tests |
| lint | Run all linters |
| clean | Remove artifacts |
| deploy | Deploy to target |

## Good
```yaml
build-docker:
  desc: Build Docker image

test-unit:
  desc: Run unit tests
```

## Bad
```yaml
buildDocker:    # camelCase — wrong
Build_Docker:   # snake_case with caps — wrong
bd:             # Too short, undescriptive
```