---
name: markdownto-flashcards
description: Create or revise Markdown To study decks with focused retrieval prompts and accurate answers.
---

# Markdown To flashcards

## Contract and workflow

Read `mdto spec flashcards` (or the adjacent `SPEC.md` in a checkout) and the
[shared conventions](https://markdownto.ai/specs/conventions.md) before authoring or
repairing content. Outside a checkout, use the [published spec](https://markdownto.ai/specs/flashcards.md).
This skill accompanies `flashcards@0.1`. The spec and its fixtures govern conformance;
editorial advice below is non-normative and should adapt to the user's brief.
If the source declares another version, obtain its matching contract before changing it.

Use `markdownto: flashcards@0.1`. Every level-2 heading is a nonempty, case-insensitively
unique question followed by a nonempty answer. Do not put content before the first card
or add other heading levels beyond the optional leading title. Answers may contain rich
Markdown blocks. Review state is presentation only; the spec stores no study history.

## Content quality

Ask for one assessable idea per card, with enough context to answer outside the source
chapter. Prefer retrieval or application over prompts that reveal their own answer. Put
the direct answer first, then a short explanation or discriminating example. Split
multi-part prompts when partial correctness would be hard to judge. Ground answers in
the supplied material and avoid fabricating facts to reach a requested card count.

## Check and deliver

Validate the file with `mdto validate <path>` before editing existing content and again
after changes. Read diagnostics against the spec's rationale; preserve meaning when
repairing syntax. Prefer spec-owned verbs for edits they support, checking their current
`--help`; otherwise make a focused source edit, preserving unrelated content and IDs.
Render with `mdto render <path>` and inspect the result when available. Validation checks
structure, not editorial quality: review the content against the user's purpose as well.
Without the CLI, use the contract and examples and report that validation was not run.
Deliver the Markdown source and any requested artifacts, stating what was actually checked.
