Skip to content
Jake Moore edited this page Aug 31, 2026 · 1 revision

KamiCommon wiki

The published documentation for KamiCommon. Source of truth for every claim here is Jake-Moore/KamiCommon and Jake-Moore/KamiCommonNMS.

A push is live immediately

There is no PR, no review and no undo. Verify a claim against source before writing it, not after.

Writing

Apply https://github.com/cursor/plugins/blob/main/pstack/skills/unslop/SKILL.md to every page and to commit messages. Zero em dashes anywhere.

  • Formal, impersonal and explanatory. Match the surrounding prose.
  • Never narrate investigation or recent work. No "recently fixed", no "as of alpha.NN", no dated stamps, no status updates. The docs explain the library as it is.
  • Write as though the current version has shipped.
  • No AI-isms: no "it's worth noting", no "seamless", "robust", "leverage", "delve", no tricolon padding, no bolded lead-ins that restate the sentence.

Never mention LuxiousNetwork or LuxiousLabs. The Nexus repository URL at repo.luxiouslabs.net is the sole exception and is expected.

Commit messages end with exactly this and nothing else:

Co-Authored-By: Claude Code <noreply@anthropic.com>

No model name, no context window, no session link. History was rewritten once to remove those; do not reintroduce them.

Do not use the source repository's tags

They are Dependabot and Renovate artifacts and do not match their names. Measured: pre-v5.0.0-alpha.17 declares 5.0.0-alpha.12, pre-v5.0.0-alpha.26 declares alpha.23, and alpha.18 and alpha.21 are the same commit. A review pass nearly filed a confident, wrong finding on their strength.

To establish what the code looked like at any version, walk the branch and read the VERSION line:

git log origin/release/v5 -S'5.0.0-alpha.NN' -- build.gradle.kts

That commit is that version; its parent is the state before it.

Scope-dated content is not stale content

v5-Migration-Guide.md declares near its end that it covers 4.0.0 through 5.0.0-alpha.20. A signature that is wrong against today but right at that scope is correct, provided the alpha.20 to 5.0.0 page carries the change forward. Check the forward-carry before changing anything.

The recurring defect in that guide is the opposite: a change made between two v5 alphas, filed as a v4 change. AbstractSubsystem and FeatureManager did not exist at tag 4.0.0.

Layout

Pages live under v5/, with topic pages at the top level and migration guides in subdirectories. Each directory carries its own _Sidebar.md. GitHub flattens the URLs, so a page in v5/migration/guide/ is linked as /wiki/v5-Migration-Guide.

Clone this wiki locally