What problem does it solve? Preparing a Replit project for a Designathon or public competition involves more than shipping code: judges need an organized canvas, working artifacts, two live URLs, and a readable commit history, and multi-day builds lose continuity between sessions. This Skill provides the full playbook for turning a working build into a reviewable submission. ## Core Features & Use Cases - Judge-ready canvas organization: Switch the canvas from building mode to judging mode with a hero row of three primary deliverables, numbered zone labels, standard gutters, and a focusCanvasShapes call. - Dual deployment discipline: Maintain both a Replit Publish URL and a GitHub Pages URL, with a three-step post-merge sync process and both links in the README. - Session handoff and provenance conventions: Write one-page handoff documents with four fixed sections, and keep every published figure traceable to its script, seed range, or decision log row. - Use Case: The night before a Designathon deadline, ask for a pre-submission review and receive a checklist covering canvas state, artifact quality, deployment URLs, and documentation accuracy. ## Quick Start Ask the AI to prepare your Replit project for Designathon judging, including canvas organization, dual deployment, and a session handoff document.
