developer

# Developer

## Purpose

Orchestrates the development workflow by understanding the domain context, mapping changes to the correct architecture layer, and implementing with consistent patterns. Uses discovered project conventions from `/developer configure`.

## When to Use

- Implementing new features or functionality
- Making code changes that span multiple areas
- Understanding where to place new code
- Ensuring changes follow project conventions

## Quick Reference

- **Setup**: `/developer configure` (run once during framework setup)
- **Usage**: `/developer` or `/dev` (uses saved config)
- **Update**: `/developer learn <path>` (analyze specific path)

### Config Location

Config path depends on how the plugin was installed:

| Plugin Scope | Config File | Git |
|--------------|-------------|-----|
| **project** | `.claude/skills/developer.yaml` | Committed (shared) |
| **local** | `.claude/skills/developer.local.yaml` | Ignored (personal) |
| **user** | `.claude/skills/developer.local.yaml` | Ignored (personal) |

**Precedence when reading** (first found wins):
1. `.claude/skills/developer.local.yaml`
2. `.claude/skills/developer.yaml`
3. Skill defaults

## Modes

| Mode | Trigger | Purpose |
|------|---------|---------|
| **configure** | `/developer configure` | Analyze project architecture and patterns |
| **learn** | `/developer learn <path>` | Learn patterns from specific path |
| **default** | `/developer` | Orchestrate development with saved config |

## Configure Mode

Auto-detect project architecture and patterns:

```
/developer configure
```

**Discovers:**
- Architecture style (layered, modular, flat, monorepo)
- Layer boundaries and naming conventions
- Import rules and dependency direction
- Domain concepts and vocabulary
- Test file patterns and locations

**Outputs:** `.claude/skills/developer.yaml`

```yaml
# Developer configuration
# Generated by: /developer configure

architecture:
  style: layered  # layered, modular, flat, monorepo
  layers