contribute
Bring imagination: you do not have to write code.
The family grows through ideas as much as through patches. If you have a use case, an edge case, or a wild notion, that is a contribution. If you write code, even better.
What we expect
- Receipts over vibes - a claim arrives with a source, or it is marked as a direction, not a fact.
- Deterministic over clever - a gate that fails loudly beats a check that passes mysteriously.
- Plain verbs - say what the thing does; skip the superlatives.
- Small and focused - one change, one reason, one review.
Ways in
- File an issue - a bug, a request, or a use case on any repo. The tracker is checked.
- Open a pull request - the family law is local commits and honest diffs; PRs target the staging branch.
- Bring an idea - a scenario for the adversarial packs, a page worth pinning, a spec worth writing. No code required.
- Test in the wild - run a tool on your own project and tell us what broke. That report is worth more than a star.