Team Conventions

---
name: team-conventions
description: The conventions this team actually follows — naming, branching, review, and the decisions someone already made so nobody re-litigates them. Use when writing or reviewing code here, opening a PR, or when unsure "how do we do this".
---

# Team conventions

Replace this file with yours. It ships as the example because it is the skill
every team turns out to need first: the answers a new teammate — or a new agent
session — otherwise asks for one at a time.

Delete the sections that do not apply. A short skill that is true beats a
complete one that is aspirational.

## Naming

- Say the shape here: files, branches, tests, whatever your team argues about.
- One line each. If a rule needs a paragraph, it is a decision, not a naming rule.

## Before opening a PR

1. The command that has to pass.
2. What the description must contain.
3. Who reviews what.

## Decisions already made

Things a session should not reopen, and one line of why:

- *(example)* Dates are stored UTC, formatted at the edge — mixed zones cost us a release once.

## Where things live

A short map of the repo or the folder, aimed at someone who has never opened
it: where a new file goes, and what the directory nobody understands is for.

---

*Every teammate's agent reads this file, on their machine, on their next
session. Keep it current — and keep secrets, tokens and anything you would not
paste in a group chat out of it.*