Show HN: A simple decision layer for coding agents Developer smarchone released Signals, a Claude Code skill installed via `npx skills add smarchone/signals -g`, that records the decisions made during coding sessions and carries them across sessions so agents stop re-litigating settled calls. The tool stores each decision with its rationale and what was ruled out, and surfaces only new decisions that are hard to undo or felt by users; commands include `/signals why sqlite?`, `/signals build the first slice` and `/signals exec drop sqlite for pg`. Setup takes roughly one minute and requires Claude Code. ~/ smarchone/signals https://github.com/smarchone/signals tl;drA Claude Code skill. It captures the decisions you make as you talk and build, across sessions, and asks you only about new ones that are hard to undo or felt by users. What are you steering? the thesis → blog.html - Sessions → none of them knows what the others decided. - Prompts → prompt hell. You re-steer the same calls, prompt after prompt. - Specs → spec-driven dev. The spec is stale by build two. Back to prompting. - Decisions → signals. Decided once, it steers every build after. Big calls only Decisions, not diffs. Only the ones hard to undo, or felt by users. Decided stays decided Each keeps its why. And what was ruled out, so agents stop re‑arguing it. Exec level You stay at the top. Never variable names. Single player, for now. you talk → agent builds → you approve new decisions → remembered Get started · ~1 min · needs Claude Code bash $ npx skills add smarchone/signals -g then, in Claude Code: /signals why sqlite? answers from your decisions /signals build the first slice builds what you discussed /signals exec drop sqlite for pg the panel argues, you decide made with ♥ · @smarchone/signals https://github.com/smarchone/signals