Menú
Canonical format for Pnimit (InternalMedicine) `.cowork/<slug>.md` handoff files. Load whenever writing or reading a handoff.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Background knowledge for Hebrew medical terminology used in Israeli clinical practice. Claude loads this when editing any Hebrew content in data/notes.json, data/questions.json, data/flashcards.json, data/highyield.json, or any UI string in pnimit-mega.html / src/. Ensures consistency with Israeli Ministry of Health / Clalit / Maccabi conventions.
Authoritative schema reference for data/questions.json, data/notes.json, data/drugs.json, and data/flashcards.json in Pnimit Mega (InternalMedicine). Claude must load this whenever editing any of those files. Contains exact field names, allowed values, the 24-topic map (P0064-2025), and the version trinity. Complements the /add-questions command.
Repo-local snapshot of audit-fix-deploy SS E for InternalMedicine. Use when working on this repo to know current version, test baseline, schema state, and the 16-binding window contract.
Complete development skill for Pnimit Mega (שלב א מגה — פנימית), an Israeli internal medicine board exam PWA. ALWAYS use this skill when: modifying Pnimit Mega code, fixing bugs, adding features, parsing new exam PDFs, adding questions/flashcards/notes, pushing to GitHub, or anything related to the InternalMedicine repo. Also trigger on: "pnimit", "internal medicine board", "פנימית מגה", "P0064-2025", references to eiasash.github.io/InternalMedicine, "parse exam", "add questions", "pnimit bug", or any mention of the InternalMedicine repo. Contains repo structure, data formats, deployment pipeline, exam parsing patterns, and content creation conventions. Always read this before touching any Pnimit code.
| name | handoff-format |
| description | Canonical format for Pnimit (InternalMedicine) `.cowork/<slug>.md` handoff files. Load whenever writing or reading a handoff. |
Handoff files live at .cowork/<slug>.md, one per active branch, committed.
# <slug>
**Branch:** cowork/<slug>
**Last session:** YYYY-MM-DD (model)
**Status:** in-progress | blocked: <reason> | ready-to-land
One paragraph. Never edit after the first session — this is the anchor.
Snapshot from /cowork:start:
data/questions.json length at branch-off.data/flashcards.json length at branch-off.data/notes.json length at branch-off.Paths this branch is actively editing. Managed by /cowork:claim and surfaced by /cowork:collisions. Format:
### Claimed
- data/questions.json (2026-04-19T08:15Z)
- src/ui/quiz-view.js (2026-04-19T08:15Z)
A parallel cowork branch touching a claimed path is a hard warning (not an auto-fail — overlaps in data/questions.json are common and usually resolvable). Missing this section is fine for solo work.
Concrete bullets with artifact + scope. Examples:
data/questions.json +12 (topic: nephrology, ids: q0612–q0623).src/ui/quiz-view.js: fixed RTL stray LTR mark in quiz-nav.One or two concrete actions with file paths. Imperative. Examples:
[ ] Add 4 questions for topic "electrolytes" (ti=8) to data/questions.json.[ ] Continue, [ ] Review.One line per suite, current state:
npm test -- quiz : PASSnpm run lint : FAIL (3, pre-existing)Non-obvious only:
window.fn binding left in place pending a circular-import fix.git diff.