# /kicad/gerbers

Generated Gerber files for design review and verification.

## Purpose
This directory contains Gerber files generated during the design process for:
- Design review and verification
- Quick prototyping
- Sharing with colleagues for feedback
- Design iteration tracking

**Note**: Final production Gerbers should be placed in `/manufacturing/gerbers/`

## File Types
- **`.gbr`**: Gerber files for copper layers
- **`.gbrjob`**: Gerber job file (KiCad 6+)
- **`.drl`**: Excellon drill files
- **`.pdf`**: PDF plots for review

## Generating Gerbers in KiCad
1. Open your PCB file (`.kicad_pcb`)
2. Go to **File → Fabrication Outputs → Gerbers**
3. Select output directory: `kicad/gerbers/`
4. Configure layers and options
5. Click **Plot**
6. Generate drill files: **File → Fabrication Outputs → Drill Files**

## Typical Layer Files
```
gerbers/
├── ProjectName-F_Cu.gbr        # Front copper
├── ProjectName-B_Cu.gbr        # Back copper
├── ProjectName-F_SilkS.gbr     # Front silkscreen
├── ProjectName-B_SilkS.gbr     # Back silkscreen
├── ProjectName-F_Mask.gbr      # Front solder mask
├── ProjectName-B_Mask.gbr      # Back solder mask
├── ProjectName-F_Paste.gbr     # Front solder paste
├── ProjectName-B_Paste.gbr     # Back solder paste
├── ProjectName-Edge_Cuts.gbr   # Board outline
├── ProjectName.drl             # Drill file
├── ProjectName-NPTH.drl        # Non-plated holes
└── ProjectName-job.gbrjob      # Job file
```

## Review Checklist
- [ ] All layers present and correct
- [ ] Board outline properly defined
- [ ] Drill files include all holes
- [ ] Silkscreen readable and not overlapping pads
- [ ] Solder mask openings correct
- [ ] Component references visible
- [ ] No missing copper or shorts

## Gerber Viewers
- **KiCad Gerber Viewer**: Built into KiCad
- **gerbv**: Open source Gerber viewer
- **Online viewers**: PCBWay, JLCPCB gerber viewers
- **Manufacturer tools**: Most PCB fabs provide online viewers

## Version Control
- Include gerbers in git for design history
- Tag important milestones
- Use descriptive commit messages
- Consider file size when committing frequently