Teaches Claude the reactive patterns OpenWork uses for SolidJS, specifically how to avoid the "shared global flag" trap that causes UI bugs. The core idea is simple: give each async action its own pending signal instead of reusing one busy() flag everywhere, derive UI state with createMemo(), and treat signal values as immutable. It's focused on preventing state coupling bugs, which in SolidJS usually show up as unrelated UI elements getting stuck rather than rerender issues. If you're building with signals and keep running into mysterious button states or disabled inputs that shouldn't be disabled, this codifies the scoping discipline that prevents those problems.
npx skills add https://github.com/different-ai/openwork --skill solidjs-patterns