Credo Configuration

RULES — Follow these with no exceptions

1. Always run mix credo gen.config first — never hand-craft .credo.exs from scratch
2. Use --strict in CI — enables additional checks that are disabled by default
3. Add inline disables sparingly — document why each exception is necessary
4. Custom checks belong in lib/credo/checks/ — never inline them in application code
5. Run Credo before every commit — catch issues before they reach CI
6. Address all findings — don't suppress without understanding why the check fires

End-to-End Workflow

Follow this sequence when setting up or customizing Credo: