usemindit

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 comprehensive design review, says "find what's wrong," or pastes a design without specifying which lens to use. Also the right starting skill when the user is new to mindit. Produces a scorecard with one score per force and a recommendation for where to focus.

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 confusing. Also trigger when the user pastes a screenshot or URL and asks "what's wrong with this" or "is this clear" without specifying which force. Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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" — the skill surfaces what the team actually knows vs. what they're assuming. Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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 prevents the team from doing later, or knock-on effects on other features. Also trigger when the user is about to ship a destructive flow (deletion, payment, account changes) and asks for a review. Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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), brand restrictions, or engineering capacity. Also trigger when a user says "can we ship this," "is this realistic," or "what are we forgetting." Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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 trigger when the user mentions a specific user segment, persona, or use environment (driving, dark mode, slow network, etc.). Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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 component, whether terminology lines up, or whether a feature feels like a different product was glued on. Also trigger when the user is adding a feature to an existing product and asks for a review. Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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 when the user is about to ship a broad-impact change (default change, pricing, schema migration, brand refresh). Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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 which is cheaper to ship, or when the user is reviewing a design that introduces a new component, library, or pattern. Produces a structured decision artifact with score, criteria, and anti-pattern matches.

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 want to surface the failure modes they may not see. Produces a structured artifact listing the most likely failure scenarios ranked by probability and severity, with mitigations.

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 based on," or wants to understand the chain of reasoning behind a current design state. Also trigger when the user is debating a change and wants to see what other decisions would be affected. Reads from the .mindit/decisions/ directory and produces a traceback artifact.