Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →okhp3/okhp3-replit-build-in-public
Full playbook for a Replit Designathon competition submission — canvas organisation for judges, artifact selection, dual deployment (Replit Publish + GitHub Pages), session-to-session narrative continuity, and building-in-public commit discipline. Activate for "designathon", "competition", "building in public", "judges", "showcase", "submission", "dual deploy", "GitHub Pages + Replit", or any request to prepare a Replit project for public or competitive review.
Passed 19 of 23 test cases with the skill, and 6 of 23 without it.
and 17 more in the full report
13 fixed6 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running the script to pan the judge view to all showcase shapes upon entering judging mode, what duration value should be passed for smooth panning animation?
| Checked | Without skill | With skill |
|---|---|---|
| Sets animateMs to 500 | Missed | Passed |
The instructions your model reads when the skill loads.
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Building in public on Replit is not just about shipping code — it is about making your process visible. This skill covers the full arc: how to organise what you have built so judges can evaluate it quickly, how to deploy it to two public surfaces, how to maintain narrative continuity across many build sessions, and how to make your commit history a readable story.
| In scope | Out of scope |
|---|---|
| Canvas as a judge showcase board | Canvas callback mechanics — read the canvas skill |
| Artifact selection for judges | GitHub Pages mechanics — read okhp3-vite-github-pages |
| Dual deployment setup | Replit deployment mechanics — read the deployment skill |
| Session handoff conventions | Multi-artifact monorepo rules — read okhp3-replit-multi-artifact |
| Commit-message discipline | Individual artifact build instructions |
Building mode — the canvas is a work surface. Iframes are scattered, some are building, labels are missing. This is fine during development; judges never see it.
Judging mode — the canvas is a showcase board. Every iframe is live, zones are labeled and numbered, a focusCanvasShapes call navigates judges to the layout automatically.
Switch to judging mode before every public review. The canvas is the first thing a judge sees in the Replit workspace.
The top strip of the board. Place your three primary deliverables here — the live interactive artifact (game, app, tool), the portfolio/pitch deck, and the showcase video. These are the artifacts judges interact with directly.
y = 100
x positions: 0, (w1 + 80), (w1 + 80 + w2 + 80), ...
test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.