simplicity Shipped
What this lens looks for
Simple means no interleaving of concerns — not just "familiar"; optimizing for easy (convenient) leads to complexity that kills velocity; before adding abstraction to a skill or workflow, ask "am I braiding two concerns together?"; complexity in instructions compounds — resist at introduction time
What its verifier checks
Skill/rule complexity reviewed before adding new abstraction; each new layer has a clear, single justification; skills do not mix orchestration and domain logic; no convenience helpers that obscure what is actually happening