Designing cards

Cards are the workhorse component of modern board games, and the difference between a good card and a frustrating one is almost entirely layout discipline. A player should be able to identify a card from across the table by its most important attribute, usually a cost, a type, or a color, and read its full effect in a few seconds when it is in hand.

Put information where hands expect it. Costs go in the top corners, because that is what shows when cards are fanned in hand. Names go along the top. Card type and rules text sit in the middle or lower half. Whatever positions you choose, keep them ruthlessly consistent across the whole deck, because players learn the layout once and then read by position, not by searching.

Write rules text like an instruction, not a paragraph. Short sentences. Consistent verbs: if one card says "draw 2 cards" and another says "take two cards from the deck," players will wonder if those are different actions. Build a small glossary of your game's terms early and audit every card against it. Icons can replace repeated phrases once players have learned them, which shrinks text and speeds up play.

During prototyping, manage cards as data, not as individual art files. Keep every card in a spreadsheet with columns for name, cost, type, and text, then generate the deck from it. This makes rebalancing a column edit instead of a design session. Tabletop Runner supports this directly: you import a card list from CSV and the deck updates from your spreadsheet.