Skip to content

borghei/Claude-Skills / product-team/product-designer

product-designer

Verified

Turns user research into design decisions: journey maps with gap checks, SUS and task scoring, and heuristic design critique. Use when mapping a journey, scoring a usability test, or critiquing a flow before it ships.

references/heuristics.json

View on GitHub
{
  "_about": "Checklist for design_critique.py: Nielsen's 10 usability heuristics, three accessibility groups and the 0-3 severity scale. Edit wording here; ids are referenced in reports.",
  "heuristics": [
    {
      "id": "N1",
      "name": "Visibility of system status",
      "description": "The design keeps users informed about what is happening through appropriate feedback within reasonable time.",
      "checkpoints": [
        "Loading states are visible for operations >1 second",
        "Progress indicators shown for multi-step processes",
        "Success/error feedback appears after user actions",
        "Current location is clear in navigation"
      ]
    },
    {
      "id": "N2",
      "name": "Match between system and real world",
      "description": "The design uses language, concepts, and conventions familiar to the user.",
      "checkpoints": [
        "Labels use user language, not internal jargon",
        "Icons follow established conventions",
        "Information appears in natural and logical order",
        "Metaphors match real-world expectations"
      ]
    },
    {
      "id": "N3",
      "name": "User control and freedom",
      "description": "Users can easily undo, redo, or exit unwanted states.",
      "checkpoints": [
        "Undo is available for destructive actions",
        "Cancel/back options are clearly visible",
        "Users can exit flows without losing progress",
        "Confirmation dialogs for irreversible actions"
      ]
    },
    {
      "id": "N4",
      "name": "Consistency and standards",
      "description": "Users don't have to wonder whether different words, situations, or actions mean the same thing.",
      "checkpoints": [
        "UI elements behave the same way throughout",
        "Terminology is consistent across all pages",
        "Visual patterns (spacing, colors) are consistent",
        "Platform conventions are followed"
      ]
    },
    {
      "id": "N5",
      "name": "Error prevention",
      "description": "Good design prevents problems from occurring in the first place.",
      "checkpoints": [
        "Form validation occurs before submission",
        "Constraints prevent invalid inputs",
        "Destructive actions require confirmation",
        "Default values reduce user effort and errors"
      ]
    },
    {
      "id": "N6",
      "name": "Recognition rather than recall",
      "description": "Minimize the user's memory load by making elements, actions, and options visible.",
      "checkpoints": [
        "Options are visible rather than requiring memorization",
        "Help and instructions are easily accessible",
        "Recently used items are easily accessible",
        "Search and filter options are visible"
      ]
    },
    {
      "id": "N7",
      "name": "Flexibility and efficiency of use",
      "description": "Accelerators allow experienced users to speed up interaction.",
      "checkpoints": [
        "Keyboard shortcuts available for frequent actions",
        "Customizable interface elements",
        "Shortcuts or recent items for repeat tasks",
        "Batch operations for power users"
      ]
    },
    {
      "id": "N8",
      "name": "Aesthetic and minimalist design",
      "description": "Interfaces should not contain irrelevant or rarely needed information.",
      "checkpoints": [
        "Each screen focuses on one primary action",
        "Visual hierarchy guides attention to important elements",
        "Whitespace used effectively",
        "No unnecessary decorative elements that distract"
      ]
    },
    {
      "id": "N9",
      "name": "Help users recognize, diagnose, and recover from errors",
      "description": "Error messages should be expressed in plain language and suggest a solution.",
      "checkpoints": [
        "Error messages are in plain language (no codes)",
        "Error messages indicate what went wrong specifically",
        "Error messages suggest how to fix the issue",
        "Errors are visually prominent and close to the source"
      ]
    },
    {
      "id": "N10",
      "name": "Help and documentation",
      "description": "Help information should be easy to search, focused on the task, and not too large.",
      "checkpoints": [
        "Help is easily accessible from any screen",
        "Contextual help is provided where needed",
        "Onboarding guides new users through key features",
        "Documentation is searchable and task-focused"
      ]
    }
  ],
  "accessibility": [
    {
      "id": "A1",
      "name": "Color contrast",
      "checkpoints": [
        "Text meets 4.5:1 contrast ratio (WCAG AA)",
        "Large text meets 3:1 contrast ratio",
        "Color is not the only way to convey information",
        "Focus indicators have sufficient contrast"
      ]
    },
    {
      "id": "A2",
      "name": "Keyboard navigation",
      "checkpoints": [
        "All interactive elements reachable via Tab key",
        "Focus order follows logical reading order",
        "Focus ring is visible on all interactive elements",
        "No keyboard traps (user can always navigate away)"
      ]
    },
    {
      "id": "A3",
      "name": "Screen reader support",
      "checkpoints": [
        "All images have meaningful alt text",
        "Form inputs have associated labels",
        "ARIA attributes used correctly for dynamic content",
        "Headings follow logical hierarchy (h1 > h2 > h3)"
      ]
    }
  ],
  "severity_levels": {
    "0": {
      "label": "Cosmetic",
      "action": "Fix when possible",
      "color": "gray"
    },
    "1": {
      "label": "Minor",
      "action": "Low priority fix",
      "color": "yellow"
    },
    "2": {
      "label": "Major",
      "action": "Fix before next release",
      "color": "orange"
    },
    "3": {
      "label": "Critical",
      "action": "Fix immediately",
      "color": "red"
    }
  }
}
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall