mylesmcook/lawful

Evaluate substantive software architecture tradeoffs, system boundaries, ADRs, migration strategies, and architectural incident lessons. Use when alternatives, ownership, compatibility, or recovery need an explicit design decision. Do not activate for ordinary implementation, routine bug fixes, generic code review, or formatting without an architectural decision.

Use this skill when the user wants to improve the visual quality of a human-facing surface such as UI, dashboards, landing pages, ecommerce, forms, decks, editorial pages, documents, print pieces, or other front-end work. Apply it to critique, redesign direction, implementation guidance, or polish passes when the goal is clearer hierarchy, stronger structure, better typography, color, spacing, interaction feel, and a less generic or more convincing tone. Do not use it for backend debugging, data modeling, copyediting-only work, or brand strategy with no visual surface unless the request explicitly involves presentation, layout, or interaction.

Laws of UX critique skill. Use when evaluating mockups, screenshots, design specs, prototypes, flows, onboarding, checkout, dashboards, forms, or design-review requests, even when the user does not say UX or name a law. Output the 2-4 most relevant laws with specific application and law-grounded recommendations. Do not use for pure frontend implementation code review, WCAG/accessibility audits, or brand/visual-identity critique unless interaction usability is also in scope.