toharyona2002

False Green — Development skill for Claude Code

Development community

Agent skill for the checks that pass while the thing is broken.

How to install False Green

This entry records only its repository, not the path inside it, so there is no exact command to give. Open toharyona2002/false-green and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What False Green does

Agent skill for the checks that pass while the thing is broken. Seven false-green signals with fixes, plus three dependency-free tools: an occlusion-aware screenshot guard, a live-system enumerator, and a completion-claim checker.

Alternatives in Development

Screenshot — Capture desktop, app windows, or pixel regions across OS platforms 14.6k ★
Candidates — Fetch and analyse top pool candidates with OKX smart money signals 722 ★
Ad Recon — Launch the ad-enumerator agent to run the collection phase against the defined scope, producing a structured A 108 ★

README

false-green

An agent skill for the checks that pass while the thing is broken.

Every failure here has the same shape: **the check answered a narrower question than the one being asked**, and nothing in its output said so. The screenshot saved. The assertions passed. The subagent reported success. The count came back. The metric improved. None of it was true.

Seven rules, three tools that run.

The rules

#	The green signal	What it actually answered
1	An audit of "the project" came back clean	Whatever sits in that directory — not necessarily what is running
2	A subagent reported the work as done	That it produced a report. The tree may be untouched, or quietly clobbered
3	The screenshot saved and assertions passed	That pixels were written — not that the subject was visible under the banner
4	Contrast / pixel-diff / score improved	A proxy. A layout can satisfy all of them and still be wrong
5	An existence probe returned success	That the client short-circuited. The object may not exist
6	The simulator refused it	That the host does not implement that surface. Only a device can say no
7	The third fix attempt is in flight	Nothing. Two failed fixes mean the model of the problem is wrong

Full detail and the fix for each: [`SKILL.md`](SKILL.md).

The tools

No dependencies, no build, no install.

**[`tools/screenshot-guard.js`](tools/screenshot-guard.js)** — refuses to treat a capture as evidence when its subject is covered. Checks existence, size, visibility, viewport, and hit-tests five points inside the element's box to catch anything drawn on top.

guard("#save-button")
// → { ok: false, reason: "occluded", by: "DIV#consent", hits: 0, sampled: 5 }

Distinct refusals — `not-found`, `zero-size`, `hidden`, `transparent`, `out-of-viewport`, `occluded`, `partially-occluded`, `no-viewport` — so the reason is actionable rather than a bare false. (`no-viewport` exists because a hid