Freeze the task list and project state to disk when a session ends, and thaw it back when the next one starts — the cryo-mirror of /kompact. /kompact compacts the context window *within* one session (you stay, its summary lives on in-thread); kontinuum crosses a hard session boundary — a /exit into a brand-new session in a fresh process, where the conversation thread breaks and an on-disk note is the only channel that survives. One trigger, two modes auto-detected by whether SESSION-HANDOFF.md exists at the repo root: FREEZE / SAVE (write the note on the way out, anchored to the exact commit sha) or THAW / RESTORE (git pull --ff-only FIRST, print a drift report of what landed while the session was frozen, reconcile WORK_COORDINATION.md claims when the repo has one, re-pin the OPEN tasks, print the summary, delete the note only once the restore succeeded). Use this skill whenever the user is about to /exit and start a new session, or says "kontinuum", "freeze the session", "congela la sesion antes de salir", "
Track lifecycle for multi-developer parallel work coordinated through WORK_COORDINATION.md. Two modes — /sprint claims a track + branches from main against the Next planned table; /sprint close runs the verification gate, opens a PR with a structured body, auto-merges when eligible, then post-merge syncs WORK_COORDINATION and flips the plan-NNN frontmatter status. Use this skill whenever someone says start plan, claim track, open track, ship plan, close plan, ready for PR, post-merge sync, flip track done, sprint close, or partial ship — even when they do not name the skill. First use in a project: instantiate WORK_COORDINATION.template.md (same directory) at the repo root.
Reference contract for creating, editing, or reviewing Kadmon Harness agent files (`.claude/agents/*.md`). Covers the mandatory/recommended/optional section taxonomy, the opus-vs-sonnet model decision tree, K-first naming convention, anti-patterns enforced by `/medik` Check
Rewrite Hebrew marketing, landing, and UI copy so it reads as native Israeli writing instead of machine-translated Hebrew. Fixes the two things that instantly mark Hebrew copy as translated: gendered second-person address (the default-masculine אתה trap that excludes half your customers) and literal English calques. Produces a native-quality, gender-safe, professional-warm draft. Use this whenever writing, reviewing, localizing, or polishing ANY customer-facing Hebrew — a landing page, hero copy, a marketing site, UI microcopy, a bot or voice persona, ad or WhatsApp copy — and especially when the Hebrew was translated from English/Spanish, when someone says the Hebrew "sounds translated / stiff / generic / off", when it mixes masculine and plural address inconsistently, or when you need Hebrew that works for both male and female readers. Trigger even if the user only says "fix the Hebrew" or "make the Hebrew sound native". It raises the floor to ~native; it does not replace a final native-speaker glance on sh
De-slop marketing, UX, and landing copy: strip the "tells" that make prose read as AI-generated (em-dash overuse, "not just X but Y", rule-of-three triads, slop vocabulary like seamlessly / robust / elevate / unlock / delve, hedging, and generic openers) and tighten it to concrete, human, on-brand writing. Use this whenever polishing or reviewing ANY customer-facing prose — landing pages, hero copy, marketing sites, product emails, UX microcopy, app-store descriptions, ad copy, social posts — and especially when the user says "make this sound human", "less AI", "punchier", "tighter", "this feels generic", or "clean up the copy", even if they never say the word "de-slop". Works per-language (English, Spanish, and others). It is a quality-and-voice tool, NOT an AI-detector-evasion tool.
Offer the user an explicit choice of response depth (25% / 50% / 75% / 100%) before answering, with token estimates based on prompt complexity. Use this skill whenever the user says "token budget", "token count", "response length", "answer depth", "short version", "tldr", "brief answer", "detailed answer", "exhaustive answer", "cuántos tokens", "ahorrar tokens", "respuesta corta", "dame la versión corta", "responde al 50%", or clearly asks to control how much context/response to consume. Do NOT trigger when "token" refers to auth/JWT/payment tokens, when the user has already set a depth this session (maintain it silently), or when the answer is trivially one line.
Scan all `.claude/skills/` to extract cross-cutting principles that appear in 2+ skills, and distill them into rules — append to existing rule sections, revise outdated content, or create new rule files. Use this skill whenever the user says "extract rules from skills", "distill patterns", "update rules", "pull common principles", "what's repeated across skills", or periodically (monthly or after adding 5+ new skills) to keep `rules/` in sync with what the skills actually teach. Applies the "deterministic collection + LLM judgment" pattern — scripts collect facts exhaustively, then judgment produces verdicts.
Audit all `.claude/skills/` for quality and drift — produce Keep/Improve/Update/Retire/Merge verdicts with evidence-backed reasons, in Quick Scan (changed skills only) or Full Stocktake (complete review) mode. Use this skill whenever auditing the skill library, checking for stale references, looking for duplication across skills, deciding what to prune or merge, reviewing skill quality before a release, or when the user says "audit skills", "review our skills", "are these skills still good", "skill quality", "skill drift", or "can we consolidate these". Also use when alchemik runs `/evolve` and needs a structured quality report on the skill inventory.