Files
sanderling/skills
pj 58168a6a3e fix(testrun): the refusal asks whether the generator drove, not whether anything did
A dead provider against folio exited 0 on a real emulator: the login
setup dispatched three actions before the generator was consulted, so
DispatchedActions was 3 and the gate never fired while the generator
drove the app zero times across 83 steps. Any spec with a login setup
was immune, which is the normal case.

Summary counts generator actions separately and the refusal reads that.
NoActionsDispatchedError becomes NoGeneratorActionsError, because a run
that dispatched three login taps was lying in the old name.
2026-08-18 16:29:03 +05:30
..

Skills for writing sanderling specs

Agent skills for adopting sanderling: getting it running against your app, writing property specifications, reviewing them for the failure modes that make a spec look like it works when it does not, and reading a run honestly.

Copy the ones you want into your agent's skills directory (.claude/skills/ for Claude Code) or point your agent at this directory directly.

Start with sanderling-setup, then sanderling-spec-authoring. Run sanderling-spec-review over anything before you trust it.

The reasoning behind the rules these encode is in docs/development/design-principles.md, section 8 in particular.