The Design of Everyday Things: Don Norman's framework
Apply affordances, signifiers, constraints, feedback and conceptual models — the two gulfs, seven stages of action and error taxonomy from Norman's classic
- What
- Apply affordances, signifiers, constraints, feedback and conceptual models — the two gulfs, seven stages of action and error taxonomy from Norman's classic
- Cost
- Free
- Needs
- nothing — the skill is guidance only, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @wondelai's framework version of Don Norman's *The Design of Everyday Things*: the two gulfs of execution and evaluation, seven design principles (discoverability, affordances, signifiers, mappings, constraints, feedback, conceptual models), the seven stages of action, the human-error taxonomy (slips vs mistakes, design-for-error rules), a 10-point quick diagnostic to score any design, plus the human-centered design loop (observe → ideate → prototype → test) and worked teardown references. By @wondelai, listed here with credit to its creator. Honest caveats: the skill is guidance only — no code, no accounts needed; its further-reading section links to books on Amazon; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing — the skill is guidance only, no accounts or keys required Install "The Design of Everyday Things: Don Norman's framework" for me. It teaches the agent Norman's human-centered design framework — affordances, signifiers, constraints, feedback, conceptual models, the two gulfs, the seven stages of action and the human-error taxonomy — with a 10-point diagnostic to score any design. Repository: https://github.com/wondelai/skills/blob/main/design-everyday-things/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "design-everyday-things". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a design framework; invoke it when a product feels confusing or error-prone). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.