Contributing¶
qkt treats every commit as if it'll be read by a stranger years from now — because eventually, it will.
-
Development setup
Clone, build, run tests, ktlint, IDE config.
-
Conventions
Commit format, branch names, file size, naming, comments.
-
KDoc style
What to KDoc, what not to, how the Dokka site is generated.
-
Phase workflow
Brainstorm → spec → plan → ship → changelog.
-
Adding a broker
End-to-end guide for new venue integrations: package layout, translator, client, fill detection.
The single source of truth for project conventions is the qkt skill. Pages here surface the parts contributors hit most often.