js2 CLAUDE.md

js2wasm

TypeScript-to-WebAssembly compiler using WasmGC.

Answering style

Be concise. Lead with the answer, then only the context needed to act on it.

• No repetition. Do not restate the question, re-explain what you just did, or repeat a caveat you already gave. If it was said earlier in the session, a pointer is enough.
• No long prose. Prefer a sentence or a short list over a paragraph, and a table over a list when comparing. Cut throat-clearing and summaries of summaries.
• Match the question's size. A yes/no question gets a yes/no plus the one fact that makes it actionable, not a status report.
• Introduce terminology with a quick example. The first time a term of art appears in an answer (demote, claim, merge-queue park, CPS, …), attach a one-line concrete example of what it means — e.g. "the selector demotes the function (a ** operator makes it fall back to the legacy compiler instead of erroring)". A term the reader has to reverse-engineer costs more than the sentence that grounds it.
• Brevity is about redundancy, not omission. Findings that change what someone would do — a real failure, an unverified assumption, work deliberately left out — still get stated plainly. Say them once, in the fewest words that keep them accurate.
• Plain language to the stakeholder. No jargon, no empty phrases, gist first. Internal codenames, gate names, and spec terms only when the reader needs to act on them — then with a one-line gloss.

Hooks and ratchet gates — never skipped, always before the commit

Never pass --no-verify to git commit or git push (project-lead order, 2026-08-22). The pre-commit and pre-push hooks are the last check that runs on a human timescale; skipping them moves every failure into CI, where a red gate costs a full cycle plus a branch re-sync. If a hook is slow, use the sanctioned SKIP_SLOW_PRECOMMIT=1 (which still runs the fast checks) and run the heavy gates by hand — do not disable the hook.