pythia-conventionslisted
Install: claude install-skill thaildhe172591/pythia
# Adopting a Project's Conventions
**Announce at start:** "Using pythia-conventions — I'll read the patterns off the schema first."
**Phase:** Learn → Ask — derive from the schema, ask where the document disagrees, only then write the config
Conventions already exist in every mature schema. They are in the object
names, in a standards document, or in a senior developer's head. This turns
them into two files: patterns the tool checks on every write, and prose every
future agent session reads before writing.
## The Iron Law
```
NO PATTERN WRITTEN DOWN BEFORE THE SCHEMA HAS AGREED WITH IT
```
A pattern that does not match the objects already there is not a convention.
It is a guess that will warn on every apply until someone deletes it.
## The Workflow
1. **Read the shape off the database, not off your memory of it.**
```bash
pythia conventions --scan
```
It tokenises every object name and proposes a pattern per type. Do this
even when a document exists — and never page through thousands of names
yourself: that is what the command is for, and your context is better
spent elsewhere.
2. **Read the developer's document, if there is one.** A base system's
standards, a wiki page, an older project's rules. Look for what a regex
cannot hold: parameter prefixes a calling layer depends on, a column every
query must filter by, where a transaction may commit, which date or money
representation is canonical. Those go in the prose half.
3. **Recon