Anki_DAMS_prompt

I want you to help me make Anki cloze cards in my personal, highly optimized style for medical exam prep.

You must follow these instructions exactly — every single rule here is critical to ensure consistency with my workflow.



⸻



1. Card Style

 • Use cloze deletion format: {{c1::<b>answer</b>::hint}}.

 • Bold all keywords inside <b> </b>.

 • Always number clozes from left to right within each card (c1, c2, c3…).

 • Test multiple related facts in the same card using multiple clozes (e.g., both the name of a classification and its defining feature).

 • Use subtle hints after :: — only enough to differentiate, not give away the answer.

 • Avoid basic Q&A format — instead, write complete, natural sentences with clozes inserted.



⸻



2. Multiple Cloze + Comparative Extra Rule

 • If the source is a table or classification, every card must:

 1. Have multiple clozes testing all relevant facts (including eponyms/names).

 2. Include the entire table/classification in the Extra field as a clear comparative summary so I can see all options at a glance.

 3. Make sure the Extra is concise but complete — one item per line.



Example Extra format for classification:



Comparison:

- Kraissl = max skin tension, living people

- Langer = collagen orientation, cadavers

- Blaschko = normal skin development, whorls/patches/streaks/segmental pattern





⸻



3. Mnemonics & Memory Aids

 • Whenever possible, create a short, punchy mnemonic for the card and put it in the Extra field below the summary.

 • Mnemonics can be in English or mixed Hindi-English if that makes them more memorable.



⸻



4. Export Workflow

 • Compile into a tab-separated TSV (Text + Extra columns).

 • Go through the entire PDF file meticulously, not missing out on any fact or flowchart, as all are very high yield topics.

 • I want you to add the name of the topic/chapter at the beginning before you start making cards for that specific topic/chapter, and I want you to add a line break after you're done making cards for every chapter.

• Once you're done processing the entire file, I want you to compile all generated cards into a TSV file.


⸻



5. Formatting Rules for TSV

 • Two columns only: Text (cloze sentence) and Extra.

 • Use \n for new lines inside the Extra field.

 • Never include HTML image tags; just mention Attach: filename.png in Extra if needed.

 • Always use <b> for bold inside clozes.

 • Keep each card to a one-liner cloze sentence with explanations in Extra.



⸻



6. Logic Rules

 • Never miss a single fact from the source image/text — even if it requires more cards.

 • Break long lists into multiple cloze cards rather than cramming too much into one.

 • For bidirectional recall, test both term → definition and definition → term within the same card using multiple clozes.

 • Classification tables must compare all entries in Extra.



⸻



7. Example Card



Text:

{{c1::<b>Kraissl’s lines</b>::name}} are lines of {{c2::<b>maximum skin tension</b>::function}} measured in {{c3::<b>living individuals</b>::population}}.



Extra:



Comparison:

- Kraissl = max skin tension, living people

- Langer = collagen orientation, cadavers

- Blaschko = normal skin development, whorls/patches/streaks/segmental pattern



Mnemonic: K = Tension-Live, L = Collagen-Dead, B = Dev-Pattern





⸻



When I give you any image, table, or text, your job is to:

 1. Extract every high-yield fact.

 2. Write multi-cloze one-liner sentences for each fact.

 3. Add comparative summaries in Extra if it’s a classification/table.

 4. Add mnemonics whenever possible.

 5. Maintain my TSV formatting rules.



⸻



Do not deviate from this style. This is my standardized Anki workflow, and I expect every card you make to be exactly in this format so I can merge them into my main deck without edits. Make sure to double check your wok to ensure that you do not make any mistakes or factual errors in the creation of these flashcards. I also want you to add an extra column for each card in each topic called Tags, this is to facilitate Anki to automatically assign those during import to all relevant cards. Tagging should be done in the following format for each card of each topic : Tag - DAMS::Back_to_Basics::$Subject::$Topic_Name


$Subject will the name of the subject, which will be found on the first or second page of the PDF file.
$Topic_Name should be in sentence case instead of uppercase and there should be an underscore between multiple words in the topic names.

Make sure that the format of the file is like this for example (this is the starting of another .tsv file which i made to import a bunch of flashcards into anki along with a few sample cards, each on a different line):
"Text	Extra	Tags
The embryological origin of the gonads is the {{c1::<b>genital ridge</b>}}, which is identifiable at {{c2::<b>5 weeks</b>::time}} of embryonic life and is initially {{c3::<b>bipotential</b>}}.		DAMS::Back_to_Basics::Gynaecology::Embryological_development
In a {{c1::<b>46 XX</b>}} karyotype, the absence of the Y chromosome causes the genital ridge to develop into an {{c2::<b>ovary</b>}} by the {{c3::<b>8th week</b>}}, influenced by genes like {{c4::<b>WNT4</b>}}, {{c5::<b>FOXL2</b>}}, and {{c6::<b>RSPO1</b>}}.		DAMS::Back_to_Basics::Gynaecology::Embryological_development
In a {{c1::<b>46 XY</b>}} karyotype, the {{c2::<b>SRY region</b>}} on the short arm of the Y chromosome signals {{c3::<b>SOX9</b>}}, leading to the development of {{c4::<b>testes</b>}} by approximately the {{c5::<b>7th week</b>}}.		DAMS::Back_to_Basics::Gynaecology::Embryological_development"

Go through the entire generated output and ensure that the each line in each topic is a note, each field is separated by a single "\t" tab character instead of "&#9;" such that the anki desktop application can correctly import all cards with the correct and intended fields and with values in appropriate fields.

I don't want any mentions of [cite_start] or [cite: x] anywhere in the entire file,  make sure to remove all such instances, leaving only the requested part in the desired format in the final output.