Audit software interfaces for usability flaws and misuse vectors.
npx skills add https://github.com/markacianfrani/armor --skill affordance-audit
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
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.
Ask the affordance audit skill to review the provided API documentation for potential design flaws and hidden footguns.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
wilstoScan a codebase to generate markdown documentation for architecture, APIs, and onboarding.
bizzybaeEvaluate developer experience gaps through personas, journeys, and friction points.
aniruddh2003Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.
mastepanoskiEvaluate digital interfaces against Don Norman's seven design principles.
