THE START GUIDE

One folder of markdown that turns your coding agent into a delivery coach. Drop it into your repository, say the oldest words in programming, and every gate — architecture, security, tests, deploy — locks until it is evidenced and you say GO. Three guards ship as real git hooks, so the rules that matter most do not depend on anyone remembering them — and a fourth draws your run screen: milestones and gates on one picture, redrawn by your own commits, offline, no account.

Attract mode · a replay of the coach’s own screensREADY

COACH READY — SkillBoss Start Guide v2
KIT .............. installed (start-guide/, checksum verified)
CONTRACT ......... loaded (CONTRACT-CARD.md, 12 rules)
GATE MAP ......... 10 gates, 00-KICKOFF -> 90-SHIP
STATE ............ nothing created yet — nothing has been built
AWAITING ......... the magic word

INSERT COIN — say the two words every program says first.

Insert coin

INSTALL
One paste. Your agent fetches the kit, checks its fingerprint, and stands ready.
INSERT COIN
Say "Hello World". Ten gates open, one at a time, and none of them opens without your GO.

Expected SHA-256: 8ea039a08deaa7b9c62344c1900cd5c3b5b3b38f5d7a4c27794472ea6e2313f0

What you are downloading

30 markdown documents — the contract, the method, the screens, the ten gates, the guides, the glossaries, a worked example run, a changelog.
4 POSIX shell scripts — the git hooks, plus their installer. Nothing else executes, anywhere in the kit.
1 example CI workflow, a licence (Apache-2.0) and its notice.
No install script runs on download or unzip. The hooks are installed later, at gate 05, by a command you run.
No network call, ever: no telemetry, no beacon, no account.

The prompt has your agent check this list against the kit’s own manifest after unzipping, and stop if the two disagree.

Download the .zip instead

The gate map

00KICKOFFRepository, mission on the record, your milestones, the walking skeleton named.
05AGENT WORKBENCHThe coach installs itself: memory files, rules, three git guards, and the run screen.
10ARCHITECTUREBoring tech, hard boundaries, twelve-factor config, explicit errors, testable seams.
20SECURITYSecrets discipline, deny-by-default routes, validated input, least privilege.
40TESTSPart of done: critical flows named, one command to green, deterministic suite.
50CI/CDCI runs your one command on every push; build once, promote the artifact.
60DOCKERMulti-stage, non-root, pinned bases — waived up front if your stack has none.
70DEPLOYMENTRollback written first, rehearsed deploys, safe migrations, a tested restore.
80OBSERVABILITYHealth contract, structured logs, errors reach a human before users do.
90SHIPThe final boss: evidence review, launch runbook — and the Ship Check at /launch.

The run ladder: WHITE -> YELLOW -> ORANGE -> GREEN -> BLUE -> BROWN -> BLACK · earned by facing the gates, never lost

Gate 90 hands you here

The final boss of the run is the Launch Bay: ten ship-ready systems to verify the week you ship. Start coached, ship checked.

Enter the Launch Bay →

The Start Guide is a coach, not a certification: its guardrails are heuristic defaults applied by your own agent. It hardens the builder; it never certifies the app.

Free forever · no login · nothing leaves your browser