Skip to main content
Every flashcard deck can contain custom cards alongside seeded content. Custom cards use the same scheduler and persistence flow as seeded cards.

​
Adding a card to a deck

Cards currently support these core fields:
​
required
The question or prompt shown before you flip the card.
​
required
The answer shown after you flip the card.
​
Optional supporting code or command example.
Once added, the card is stored through the backend and becomes part of that deck’s future review queue.

​
Card field formatting

Keep card content simple and readable. Favor:
  • One prompt per front
  • One answer per back
  • Small code examples only when they make recall more concrete

​
Editing a card inline during study

Card content can be edited without changing the underlying learning model. Content updates do not exist to reset progress. They exist to improve the card. The important behavior is that editing content should not wipe the progress state for that card.