Product design skill for developers who build with AI coding agents. Use when you need to know what to build before prompting your agent — domain model, workflows, edge cases, product states, and UX gaps handled upfront. Works alongside Cursor, Claude Code, Codex, Gemini, Pi. Any stack, any UI library. Do NOT use for…
Shape intended product behavior in Lamina's transactional graph when explicitly invoked as lamina-design or when passive implementation preparation reports design gaps. Publish an implementation-ready graph version without editing application source.
Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify. Run isolated Persona and live UI audits; explicit verification is source-read-only.
This skill should be used when the user asks to "run a heartbeat", "run the agent loop", "process GitHub issues", "check for work", or runs the /heartbeat command. Executes the WoterClip heartbeat — picks up GitHub issues, resolves personas, does work, and reports back.
This skill should be used when the user asks to "initialize woterclip", "set up woterclip", "woterclip init", "configure woterclip for this repo", or runs the /woterclip-init command. Scaffolds a repo with WoterClip config, persona directories, and GitHub labels.
This skill should be used when the user asks to "check woterclip status", "show agent status", "what is woterclip doing", "show heartbeat status", "what's in the queue", or runs the /woterclip-status command. Shows current WoterClip state, issue queue, and blocked items.
Run Pragmatic Institute market discovery and validate real market problems before anything gets built. Use when a PM says "I want to build a feature", "do market research", "talk to customers", "discovery", "validate this idea", "is this problem real", "NIHITO", or "who should I interview". Enforces the outside-in…
Build a Pragmatic Institute Product Canvas / business case to justify investing in an opportunity — the market-driven way. Use when the PM asks to "make the business case", "justify this to leadership", "size the market", "should we buy, build or partner", "what's the ROI", "build a product canvas", or "get buy-in for…
Run a Pragmatic Institute Win/Loss analysis — understand why recent evaluators did or did not buy and the steps they took in their buying process. Use when a PM says "why did we win/lose", "win-loss", "why do deals slip", "churn reasons", "why did they pick the competitor", or "interview a lost prospect". Enforces the…
Use when running the full background-job loop: design, TDD, retry, monitor. Trigger words: background job, async processing, Sidekiq, Solid Queue, Active Job, worker.
Compare two URL variants with the same persona to determine which provides a better user experience. This skill guides the comparison logic and report generation.
This skill provides visual annotation capabilities for screenshots taken during user testing. Annotations help highlight issues, confusion points, and notable elements in test screenshots.