AI skills that find the design decisions you didn't make. Eight forces, eleven skills, scored output.
Skill Claude CodeCodex
Run a full review of a design through all eight forces (clarity, continuity, constraint, consequence, context, cost, confidence, correctability) and produce a balanced scorecard with weakest-force identification. Use this whenever the user asks for a "full review," "complete audit," "review everything," wants a…
Skill Claude CodeCodex
Analyze a design or screen for clarity — whether a stranger can read the intent in five seconds. Use this whenever the user asks about hierarchy, what stands out, what gets noticed first, whether a CTA is obvious, whether labels make sense, why users miss something on a screen, or why a layout feels cluttered or…
Skill Claude CodeCodex
Analyze the evidence standing behind a design decision — research, data, intuition, or assumption. Use this whenever the user asks "how do we know this is right," wants a research review, asks about user research, A/B test results, or interviews. Also trigger when the user says "I think users want X" or "we believe Y"…
Skill Claude CodeCodex
Analyze what a design forecloses and what it opens — second-order effects, irreversible actions, path foreclosure, data implications, future-design lock-in. Use this whenever the user asks about side effects, what happens after a user clicks, what gets stored or exposed, whether an action is reversible, what this…
Skill Claude CodeCodex
Analyze which hard limits a design honors — technical, accessibility, brand, legal, time, and platform. Use this whenever the user asks about feasibility, accessibility, WCAG, screen readers, contrast, performance budgets, platform guidelines (iOS HIG, Material), legal requirements (GDPR, CCPA, accessibility law)…
Skill Claude CodeCodex
Analyze who a design is for, when they use it, where, on what device, and in what state. Use this whenever the user asks about audience fit, mobile responsiveness, breakpoints, loading states, error states, empty states, offline behavior, onboarding context, returning users, edge cases, or "what happens when X." Also…
Skill Claude CodeCodex
Analyze whether a new design fits the system that already exists — conventions, components, vocabulary, and visual rules of the product it lives in. Use this whenever the user asks about consistency, whether something "feels off," whether a new screen matches the rest of the product, whether to fork or reuse a…
Skill Claude CodeCodex
Analyze how reversible a design is if it turns out to be wrong — both user-side undo and system-side rollback. Use this whenever the user asks about launch risk, rollout plan, A/B tests, feature flags, telemetry, monitoring, kill switches, "what if we're wrong," or "how do we know when to roll this back." Also trigger…
Skill Claude CodeCodex
Analyze the build cost, support burden, maintenance cost, and technical debt of a design. Use this whenever the user asks "is this worth building," "how much will this cost," "is this maintainable," "what's the support burden," or wants a complexity review. Also trigger when comparing two design options and asking…
Skill Claude CodeCodex
Imagine a design has already launched and failed, then work backward to figure out why. Use this whenever the user asks "what could go wrong," "what are the risks," wants a pre-launch review, asks for a devil's-advocate read, or says "argue against this." Also trigger when the user is confident about a design and you…
Skill Claude CodeCodex
Walk a design decision backward through its dependencies and forward through its consequences using the decision graph stored in .mindit/decisions/. Use this whenever the user asks "why did we decide X," "what does this depend on," "what depends on this," "show me the history of this decision," "what evidence was this…