Design a retro game within 16K

A tiny file-size budget is a design constraint. It encourages procedural graphics, short sound effects and a rule set that can be explained quickly. Begin with a single strong interaction rather than a large game squeezed into a small package.

Budget code, visuals and sound before adding polish. Reuse shapes, generate patterns from a seed and count the final packaged size after each meaningful addition. Compression helps, but it does not replace deliberate scope.

Treat a remake as a study of mechanics rather than permission to reuse someone else’s art or audio. Give the prototype its own visual identity and describe the influence without claiming an affiliation.

A compact prototype target

• One control scheme and one scoring rule.
• A complete round with failure and restart.
• Procedural visuals and optional sound.
• A documented size measurement for the delivered file.