Welcome, fellow reality‑bender. If you’re here, you’re ready to push code (and consciousness) beyond the boring edge. Read this once, breathe it in, then carve your legend.
- Ritual of Respect
- Bootstrapping Your Patch
- Bug Hunts
- Idea Catalysts
- Pull‑Request Rite
- Code Alchemy
- Commit Spellcraft
- Review Gauntlet
- License & Lore
We weaponize curiosity, not cruelty. Bigotry, harassment, or drive‑by toxicity gets insta‑vaporized. Read the Code of Conduct and keep the space charged but safe.
- Fork + Clone the repo.
- Branch like you mean it:
feature/warp-drive,fix/time-paradox, etc. - Hack with deliberate clarity—tiny commits, sharp messages.
- Verify: run the test suite, smash edge‑cases, leave no orphan process alive.
- PR: fire the flare when it’s stable.
When the beast bites:
- Search first—someone may have tracked the creature already.
- Open an issue with Steps, Expectation, Reality, Evidence (logs/screenshots).
Got a cosmic upgrade? Sweet.
- Check for duplicates.
- Title it
Feature Request: [your spark]. - Pitch the benefit + rough roadmap.
- Keep your branch synced with
main. - Title = headline. Body = TL;DR + context.
- Link issues (
Closes #123). - Expect fire. Respond, refine, repeat.
- Mirror existing style (
.editorconfigis your grimoire). - Self‑document—future devs are you in another timeline.
- Tests are non‑negotiable; unstable magic gets banished.
- Present tense: "Fix event loop glitch."
- Minify fluff, maximize signal.
- Reference issues when relevant.
- ≥1 approval required.
- Debate is welcome; ego‑fragility isn’t.
- Iterate fast.
By contributing, you accept the project’s LICENSE. Your code joins the multiverse—make it count.
Build bravely. Ship weird. See you in the diffs.