SGDK puzzle

Make the board authoritative. A sprite crossing a cell boundary is presentation, not proof that a push, rotation or clear is legal. SGDK supplies input, tiles and audio; puzzle rules are application C code.

Choose the rules before the renderer

Identify the puzzle family: push-and-switch, falling blocks, matching, routing, or something else. Ask about uncertain rules that affect legality or outcomes. Do not turn every puzzle into the included examples. Their art, music, board layouts, scoring, rotation rules and timing are illustrative, not prescriptions.

Read responsibility boundaries before crossing into map importing, collision, input, saves or replay. Keep the game's established clock and input snapshot; do not introduce another gameplay framework.

Treat a move as a transaction