affordance-audit

Audit software interfaces for usability flaws and misuse vectors.

6|Updated Jan 14, 2026

Search Tags:#design #api #audit #usability #ergonomics #footgun

Ready to run

npx skills add https://github.com/markacianfrani/armor --skill affordance-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: affordance-audit
Source: https://github.com/markacianfrani/armor/tree/main/skills/affordance-audit
Command: npx skills add https://github.com/markacianfrani/armor --skill affordance-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers and designers identify anti-affordances and usability traps in APIs, CLIs, and configuration surfaces that lead to bugs and poor user experiences.

Core Features & Use Cases

Surface Analysis: Systematically evaluates entry points to determine if the easy path is also the correct path.
Footgun Detection: Identifies common design pitfalls like order dependence, unclosed resources, and lack of input validation.
Use Case: Use this during a code review of a new SDK to ensure that the default configuration is safe and that common misuses are made impossible by the design.

Quick Start

Ask the affordance audit skill to review the provided API documentation for potential design flaws and hidden footguns.

Frequently Asked Questions about affordance-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify API design flaws and usability traps during a code review?▼

To identify API design flaws, you systematically evaluate entry points to ensure the easy path is the correct path, checking for order dependence, unclosed resources, and missing input validation. This process distinguishes intended affordances from dangerous anti-affordances.

What is an API footgun and how do I detect it in my SDK?▼

An API footgun is a design pitfall that leads to bugs and poor user experiences by allowing misuse. You detect footguns by performing a surface analysis on your SDK to identify common pitfalls like order dependence and lack of input validation.

Can I audit command-line tools and configuration surfaces for potential misuse vectors?▼

Yes, you can audit command-line tools and configuration surfaces for potential misuse vectors. The process requires a structured audit of entry points to evaluate usability flaws and determine if default configurations are safe for users.

What's the best way to review public APIs for anti-affordances before release?▼

The best way to review public APIs for anti-affordances is to conduct a structured surface analysis during the design phase. This ensures common misuses are made impossible by the design and verifies that intended affordances guide users correctly.

Does this usability audit work for both design and review phases of software interfaces?▼

Yes, this usability audit applies to both the design and review phases of software interfaces. It evaluates APIs, SDKs, and command-line tools to distinguish between intended affordances and dangerous anti-affordances.

How do I ensure the default configuration of my SDK is safe for users?▼

To ensure your SDK default configuration is safe, audit the interface entry points to identify usability traps. This confirms the easy path is also the correct path and makes common misuses impossible by design.