kendex: Skill for Claude Code

Project Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

React

• A store selector returns a stable reference: never mint an array, object or Set inside one, since a fresh value re-renders forever and blanks the page.
• An effect that positions or measures rendered content takes what is drawn as its trigger, not a list of state names; the exhaustive-dependencies lint checks only what the effect reads.

Platform rules

Enforce a rule on the platform where it can hold it (GitHub settings and rulesets, a harness's own settings). Keep a hook, script or instruction guard only where it cannot, and state why at the guard.

Compatibility

From 1.0, kendex keeps a retired consumer-visible form reading, with one warning that names the new form, until the next major release. This overrides § Cleanup's no-shim line here; the rule is changelog.d/README.md § Release standard.

Code Quality

Repo-specific standards live in each repo's ## Project Instructions section and add to these rules. Before changing code, load the reference for each affected stack under § Language Discipline.

Core Principle

Do not trade correctness for a smaller change. A failed check limits the evidence; it does not establish a product defect. Name the reachable failure before claiming user impact.

Correctness

• Fix the cause in its existing owner. If the correct fix exceeds the scope, report that conflict instead of adding a workaround.
• A dependency failure must not become a passing result or a default value. A required gate refuses when it cannot read or evaluate its evidence. An advisory check reports unavailable with the cause. An absent or unknown application input is a separate contract choice; state why refusing it is necessary where that choice is made.
• When changing a state with mutually exclusive cases, use one tagged value with exhaustive handling. Do not start a refactor of untouched fields without a reachable invalid state.
• A gate, guard or scanner adds no enumerated exemption list. State the rule at the point where the code cannot judge.
• An unexpected branch asserts or returns the violated invariant. An error names the failed operation, not a neighbouring dependency.
• An automated tool's refusal or notice starts with a stable key and the value acted on. Put the human explanation on later lines. Keep each diagnostic in one place.