[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASJZDE8RPN92NVCW2EMZS0":3,"skill-same:01M7ASJZDE8RPN92NVCW2EMZS0":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASJZDE8RPN92NVCW2EMZS0","ui-ux-cognition-heuristics-and-navigation",null,"Use when reasoning about why an interface works or fails, or structuring one. Covers the four form factors honestly compared (the router for the whole ui-ux-design-principles reference), motor control (Fitts's law), decision and attention (Hick's law), perception and grouping (Gestalt), memory of the experience (peak-end), learning and expertise, Nielsen's 10 heuristics with their failure modes, Norman's model (affordances, signifiers, the gulfs), confirmation vs undo, progressive disclosure and defaults, the IA questions in order, navigation patterns by form factor, search, and wayfinding.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-cognition-heuristics-and-navigation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-ux-cognition-heuristics-and-navigation\ndescription: \"Use when reasoning about why an interface works or fails, or structuring one. Covers the four form factors honestly compared (the router for the whole ui-ux-design-principles reference), motor control (Fitts's law), decision and attention (Hick's law), perception and grouping (Gestalt), memory of the experience (peak-end), learning and expertise, Nielsen's 10 heuristics with their failure modes, Norman's model (affordances, signifiers, the gulfs), confirmation vs undo, progressive disclosure and defaults, the IA questions in order, navigation patterns by form factor, search, and wayfinding.\"\n---\n\n# UI\u002FUX Design: The Science Underneath, Usability Heuristics, and Information Architecture\n\n> **Part 1 of 5** of the *UI\u002FUX Design Principles — Mobile, Tablet, Web, Desktop* reference (plugin `ui-ux-design-principles`), covering §0–§3. Sibling skills: `ui-ux-interaction-layout-and-visual-design` (§4–§6), `ui-ux-design-systems-platforms-and-accessibility` (§7–§9), `ui-ux-writing-forms-research-and-ethics` (§10–§14), `ui-ux-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `ui-ux-reference` for the currency snapshot and what goes stale first.\n>\n> **Related:** Overlaps the `frontend-design:graphic-ux-ui-design` skill. That one is oriented to implementation-time component and token decisions; this one is oriented to design reasoning, cross-form-factor principles, research method, and the regulatory landscape. Use both.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — grounded in perception, cognition, motor control, or decades of\n>   replicated research. Does not expire. Trust it.\n> - **[PLATFORM]** — a convention of Apple, Google, Microsoft, GNOME\u002FKDE, or the web.\n>   Verify against the current HIG; these change.\n> - **[CONTESTED]** — competent practitioners disagree, or the evidence is thinner than the\n>   confidence with which it's usually asserted. Both cases given.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that survive design review and get caught in\n> production, in court, or in the analytics.\n>\n> **The framing that organizes everything below:** an interface is a *proposal about how\n> a person should think*. Good design makes the proposal match how they already think.\n> Every principle in this document is a specialization of that idea — to a thumb, a\n> screen size, a screen reader, a legal regime, or an attention budget.\n\n---\n\n## §0. Routing\n\n### 0.1 The four form factors, honestly compared\n\n| | **Mobile** | **Tablet** | **Web (desktop browser)** | **Desktop (native)** |\n|---|---|---|---|---|\n| Primary input | Thumb, one hand, imprecise | Two hands \u002F stylus | Mouse + keyboard | Mouse + keyboard, heavy shortcut use |\n| Pointer precision | ~9 mm finger contact | ~9 mm, better reach | ~1 px | ~1 px |\n| Session length | Seconds–minutes | Minutes | Minutes | Hours |\n| Attention | Divided, interrupted, mobile | Semi-focused, leisure | Task-focused, multi-tab | Deep focus, expert |\n| Context | Anywhere, any light, any network | Couch, desk, kiosk | Desk | Desk |\n| Information density | Minimum viable | Medium | Medium-high | **High — and users want it** |\n| Navigation idiom | Tab bar \u002F bottom sheet \u002F stack | Split view, sidebar | Header nav + breadcrumbs | Menu bar, sidebar, panels, palettes |\n| Discoverability need | High (few affordances visible) | High | Medium | Lower (menus are a searchable index) |\n| Error cost of a mis-tap | High | Medium | Low | Low |\n| Undo expectation | Weak (usually) | Weak | Weak | **Strong — unlimited, always** |\n| Offline expectation | High | High | Low-medium | High |\n| Governing convention | Apple HIG \u002F Material 3 | Apple HIG \u002F Material 3 | Web conventions + your design system | Platform HIG (macOS\u002FWindows\u002FGNOME\u002FKDE) |\n\n**[DURABLE] The most common cross-form-factor mistake is transposing density.** Shrinking\na desktop layout produces an unusable phone screen; stretching a phone layout produces a\ndesktop app that insults its users by wasting 70% of the screen and hiding functionality\nthree taps deep. Density is not a styling decision — it's a claim about how much the user\ncan and wants to hold in view at once, and that differs by context, not just by pixels.\n\n### 0.2 The question router\n\n| Asked about... | Go to |\n|---|---|\n| Why does this feel confusing\u002Fslow\u002Fwrong? Perception, memory, attention | §1 |\n| Heuristics, usability principles, Norman's model, affordances | §2 |\n| Navigation, IA, search, findability, menu structure | §3 |\n| Touch vs pointer vs keyboard, gestures, thumb zones, input models | §4 → `ui-ux-interaction-layout-and-visual-design` |\n| Layout, grids, responsive, breakpoints, adaptive, foldables | §5 → `ui-ux-interaction-layout-and-visual-design` |\n| Typography, color, spacing, elevation, iconography, motion | §6 → `ui-ux-interaction-layout-and-visual-design` |\n| Design systems, tokens, component APIs, governance | §7 → `ui-ux-design-systems-platforms-and-accessibility` |\n| Platform conventions and how they differ | §8 → `ui-ux-design-systems-platforms-and-accessibility` |\n| Accessibility — principles, WCAG, law, testing | §9 → `ui-ux-design-systems-platforms-and-accessibility` |\n| Microcopy, error messages, empty states, tone | §10 → `ui-ux-writing-forms-research-and-ethics` |\n| Forms, onboarding, checkout, conversion | §11 → `ui-ux-writing-forms-research-and-ethics` |\n| Research methods, usability testing, sample size, analytics | §12 → `ui-ux-writing-forms-research-and-ethics` |\n| Metrics, HEART, success criteria | §12.4 → `ui-ux-writing-forms-research-and-ethics` |\n| Dark patterns, persuasion ethics, regulation | §13 → `ui-ux-writing-forms-research-and-ethics` |\n| AI-era interfaces, conversational UI, generative UI | §14 → `ui-ux-writing-forms-research-and-ethics` |\n| \"Don't do this\" | §15 → `ui-ux-reference` |\n| \"Which is better, X or Y?\" | §16 → `ui-ux-reference` (contested) |\n| Books, researchers, authoritative sources | §18 → `ui-ux-reference` |\n| \"Is this still current?\" | §17 → `ui-ux-reference` |\n\n---\n\n## §1. The Science Underneath — why interfaces work or don't\n\nAlmost every defensible design decision reduces to one of these. Knowing them turns\n\"I don't like it\" into \"this will cost users ~600 ms per interaction and here's why.\"\n\n### 1.1 Motor control\n\n**Fitts's Law [DURABLE]** — time to acquire a target is a function of distance and size:\n`MT = a + b·log₂(2D\u002FW)`. Practical consequences, in rough order of value:\n- **Bigger targets are faster and more accurate.** Non-negotiable, measurable, and the\n  basis of every touch-target guideline in §4.2 → `ui-ux-interaction-layout-and-visual-design`.\n- **Closer targets are faster.** Put the primary action near where the user's attention\n  and pointer already are — not in a corner because the grid says so.\n- **Screen edges and corners have effectively infinite width** in one dimension, because\n  the pointer stops there. This is why the macOS menu bar (screen top) is faster to hit\n  than a Windows in-window menu bar, and why the corners are the most valuable real estate\n  on a desktop screen. On touch, edges have the *opposite* property — they're where the\n  hand occludes and where system gestures live.\n- **Dangerous actions should violate Fitts deliberately**: make Delete smaller, farther, or\n  behind a confirm. Never place Cancel adjacent to a destructive primary.\n\n**Steering Law [DURABLE]** — time to move *through* a constrained path grows with path\nlength and shrinks with tunnel width. This is why deep cascading menus are painful (you\nmust steer down a narrow corridor without leaving it) and why macOS's diagonal-tolerance\nin submenus was a genuine innovation. If your nav requires precise steering, add\ndwell tolerance or convert to click-to-open.\n\n### 1.2 Decision and attention\n\n**Hick–Hyman Law [DURABLE, but frequently over-applied]** — decision time grows\nlogarithmically with the number of *equally likely* alternatives: `RT = a + b·log₂(n+1)`.\n- Correct use: don't put 40 undifferentiated options in one flat list.\n- **⚠️ Misuse:** \"Hick's Law says fewer menu items are always better\" — false. The log is\n  cheap; a well-*categorized* list of 40 is faster than a flat list of 8 that requires\n  drilling. And options are rarely equally likely — a good default collapses the decision\n  entirely. **Categorization beats reduction.**\n\n**Miller's \"7±2\" [DURABLE finding, WIDELY misapplied]** — Miller (1956) described\nshort-term memory capacity for *chunks* in a recall task. It was never a rule about menu\nlength or navigation items, and Miller himself objected to that use. The better modern\nnumber is **Cowan's ~4±1** chunks for working memory without rehearsal. The design\nimplication is real but different: **don't require users to hold state in their heads**.\nShow the previous step. Persist the filter. Display the total. Recognition over recall\n(§2.1) is the actual principle.\n\n**Cognitive load [DURABLE]** — three types worth distinguishing:\n- *Intrinsic*: inherent difficulty of the task. You can't remove it, only sequence it.\n- *Extraneous*: load imposed by the interface itself. **This is the entire target of UI\n  design.** Inconsistent labels, hidden state, unclear hierarchy, unnecessary choices.\n- *Germane*: effort spent building a useful mental model. Worth preserving.\n\n**Attention is selective and change-blind.** Users do not see your banner. Inattentional\nblindness and **banner blindness** are well replicated: elements that look like ads, sit in\nad-shaped positions, or animate like ads get filtered out pre-consciously. If something\nmust be seen, it goes in the content flow, not the periphery.\n\n### 1.3 Perception and grouping\n\n**Gestalt principles [DURABLE]** — the visual system groups before you consciously read.\nIn rough order of strength:\n1. **Proximity** — nearest elements group. *The single most powerful and most misused tool\n   in UI layout.* If a label is equidistant between two fields, users will guess.\n2. **Similarity** — same color\u002Fshape\u002Fsize groups. This is why \"everything is a button\" and\n   \"nothing looks like a button\" are both failures.\n3. **Common region** — a shared border or background box groups strongly, and *overrides\n   proximity*. Cards work because of this.\n4. **Continuity \u002F Common fate** — aligned or co-moving elements group. Alignment isn't\n   aesthetics, it's grouping.\n5. **Closure \u002F Figure-ground** — the mind completes shapes and separates foreground.\n\n**⚠️ GOTCHA — the proximity bug.** The most common spacing error in real products:\nequal margins above and below a label, so it visually belongs to neither the field above\nnor the field below. **Rule: the space *within* a group must be smaller than the space\n*between* groups.** Almost every \"this form feels cluttered\" complaint is this.\n\n**Von Restorff (isolation) effect [DURABLE]** — the item that differs is remembered and\nfound. This is the entire justification for having exactly **one** primary button per view.\nTwo primary buttons = zero primary buttons.\n\n**Serial position effect [DURABLE]** — first and last items in a list are recalled best.\nPut the most important nav item first, the second-most last.\n\n### 1.4 Memory of the experience\n\n**Peak-End Rule [DURABLE]** — people judge an experience by its most intense moment and\nits ending, not its average. Design consequences:\n- Invest disproportionately in the **worst moment** (the error, the wait, the failed\n  payment) and the **last moment** (the confirmation, the success state, the offboarding).\n- A pleasant confirmation screen genuinely changes the remembered quality of a tedious form.\n\n**Zeigarnik effect [DURABLE-ish]** — incomplete tasks stay in memory. Progress indicators\nand \"3 of 5 steps\" work partly because of this. It is also the mechanism behind\ncompletion-pressure dark patterns (§13 → `ui-ux-writing-forms-research-and-ethics`) — same lever, different intent.\n\n**Doherty Threshold (~400 ms) [DURABLE]** — below roughly 400 ms of system response,\nusers stay in flow and productivity rises superlinearly. Above ~1 s, attention wanders.\nThis is why perceived performance is a *design* concern (§6.6 → `ui-ux-interaction-layout-and-visual-design`), not just an engineering one.\n\n**Time perception is malleable.** Progress bars that accelerate toward the end feel\nfaster. Skeleton screens feel faster than spinners because they signal *what* is coming.\nOptimistic UI (show the result immediately, reconcile later) feels instant — but you must\nthen design the failure path honestly, not silently drop the change.\n\n### 1.5 Learning and expertise\n\n**Power law of practice [DURABLE]** — performance improves as a power function of\nrepetitions. Two consequences:\n- **Novices and experts need different affordances of the same function.** A menu item\n  (discoverable, slow) and a keyboard shortcut (fast, invisible) for the same command is\n  not redundancy — it's the correct design. **Show the shortcut in the menu** so the\n  transition happens.\n- **Consistency is compound interest.** Every deviation resets the learning curve.\n\n**Jakob's Law [DURABLE]** — users spend most of their time on *other* products, so they\nexpect yours to work like those. Novel interaction models carry an enormous, usually\nunderestimated cost. Innovate on the *product*, not on where the close button lives.\n\n---\n\n## §2. Usability Heuristics and Mental Models\n\n### 2.1 Nielsen's 10 heuristics — with the failure mode of each\n\nStill the most useful evaluation checklist ever written (Nielsen & Molich 1990, refined\n1994). Below, each heuristic plus how it's commonly violated *by teams who think they're\nfollowing it*:\n\n| Heuristic | What it means | How it fails in practice |\n|---|---|---|\n| 1. **Visibility of system status** | Always tell the user what's happening | A spinner with no ETA, no cancel, and no indication of what's loading. \"Saving…\" that never resolves. Optimistic UI that silently fails. |\n| 2. **Match between system and the real world** | Speak the user's language | Internal jargon leaking into UI (\"Entity\", \"Object\", \"Instance\", \"Sync conflict\"). Icons that mean something only to the team. |\n| 3. **User control and freedom** | Emergency exits, undo | Modals with no Escape. Wizards with no Back. Destructive actions with confirm-only and no undo (§2.3). |\n| 4. **Consistency and standards** | Internal + platform consistency | Three different date pickers. A \"Save\" that means Apply on one screen and Commit on another. |\n| 5. **Error prevention** | Prevent > handle | Free-text where a picker belongs. No inline validation. Allowing a state the system will reject later. |\n| 6. **Recognition rather than recall** | Show, don't make them remember | Hiding the filter you applied. Requiring a code from a previous screen. Icon-only toolbars with no labels. |\n| 7. **Flexibility and efficiency of use** | Accelerators for experts | No keyboard shortcuts. No bulk actions. No saved views. Optimizing solely for first-run. |\n| 8. **Aesthetic and minimalist design** | No irrelevant information | **Most misread heuristic.** It says *irrelevant* — not *sparse*. Hiding necessary controls to look clean is a violation, not compliance. |\n| 9. **Help users recognize, diagnose, recover from errors** | Plain language, cause, remedy | \"Error 0x8007.\" \"Something went wrong.\" Errors that don't say which field. |\n| 10. **Help and documentation** | Findable, task-oriented | A 60-page PDF. A help center that doesn't cover the thing that's confusing. |\n\n### 2.2 Norman's model — the vocabulary for diagnosing *why*\n\n- **Affordance** — what an object *permits* (a real relationship between object and user).\n- **Signifier** — the *perceivable cue* that communicates the affordance. In UI, you almost\n  always mean signifier. A flat rectangle affords clicking; it needs a signifier to say so.\n- **Mapping** — relationship between control and effect. Natural mapping = spatial\n  correspondence (the volume slider goes up for louder).\n- **Feedback** — immediate, informative confirmation that the system received the action.\n- **Constraints** — physical, semantic, cultural, logical limits on what can be done.\n- **Conceptual model** — the user's story about how the thing works.\n\n**The Gulf of Execution** (how do I do it?) and the **Gulf of Evaluation** (did it work?).\nEvery usability problem lives in one of these two gaps. When someone says \"the UX is bad,\"\nask which gulf — the answers are completely different interventions.\n\n> **⚠️ GOTCHA — the flat-design signifier deficit.** The flat\u002Fminimal aesthetic that has\n> dominated since ~2013 systematically removed signifiers (shadows, bevels, borders,\n> underlines). Research repeatedly finds users hesitate over, or fail to find, weak-signifier\n> controls — and it disproportionately affects older and less experienced users. **Ghost\n> buttons, borderless inputs, and unlined links are aesthetic choices with a measurable\n> usability cost.** Make it deliberate, and compensate (hover states, cursor changes,\n> generous targets, at minimum a border on inputs).\n\n### 2.3 Confirmation vs. undo\n\n**[DURABLE] Undo beats confirmation almost always.** Confirmation dialogs:\n- are dismissed reflexively after the third exposure (habituation),\n- interrupt flow for the 99% of cases that were intentional,\n- and provide no help in the 1% where the user was wrong but *confident*.\n\nPrefer: perform the action → show a **toast with Undo** → make it durable for a reasonable\nwindow. Reserve confirmation for actions that are genuinely irreversible *and* consequential\n(deleting an account, sending money, publishing). When you must confirm:\n- Name the specific object (\"Delete *Q3 Budget.xlsx*?\"), never \"Are you sure?\"\n- Label buttons with **verbs**, not Yes\u002FNo (\"Delete\" \u002F \"Cancel\").\n- State the consequence, including irreversibility.\n- Make the destructive option *not* the default and *not* adjacent to the safe one.\n\n### 2.4 Progressive disclosure and defaults\n\n**[DURABLE] Defaults are the most powerful design decision you make.** Most users never\nchange them; the default *is* the product for the majority. Choose them for the user's\nbenefit, and be aware that choosing them for yours is what regulators now call a dark\npattern (§13 → `ui-ux-writing-forms-research-and-ethics`).\n\n**Progressive disclosure** — show the common case; make the advanced case reachable, not\nabsent. The discipline is: (a) the entry point to the hidden layer must be visible,\n(b) hiding must be based on *frequency of use*, not on *how tidy it looks*, and (c) never\nhide something the user needs in order to understand what's on screen.\n\n---\n\n## §3. Information Architecture and Navigation\n\n### 3.1 The IA questions, in order\n\n1. **What are the objects?** (Not screens — *things*. Documents, orders, patients, tracks.)\n2. **What are their attributes and relationships?**\n3. **How will people look for them?** (Known-item search vs. exploratory browse vs.\n   re-finding something they saw before — these are different behaviours needing\n   different affordances.)\n4. **What vocabulary do *they* use?** (Not your database's.)\n5. **What's the primary organizing scheme?**\n\n**Organizing schemes [DURABLE]:**\n- *Exact* schemes (alphabetical, chronological, geographic) — unambiguous, good for\n  known-item lookup, useless for exploration.\n- *Ambiguous* schemes (by topic, task, audience, metaphor) — support exploration, require\n  the user to guess your model. Most product IA is ambiguous, which is why card sorting\n  (§12.2 → `ui-ux-writing-forms-research-and-ethics`) exists.\n- *Hybrid* schemes fail when they mix at the same level (\"Products, Support, For Teams,\n  Pricing, 2024 Archive\"). Mixing across levels is fine; mixing within one is confusing.\n\n### 3.2 Navigation patterns by form factor\n\n| Pattern | Best for | Capacity | Watch out |\n|---|---|---|---|\n| **Bottom tab bar** (mobile) | 3–5 top-level, equally important, frequently switched destinations | 5 max (iOS shows \"More\" beyond 5) | Not for actions. Not for >5. Not for hierarchy. |\n| **Navigation drawer \u002F hamburger** | Many destinations, infrequent switching | ~10 | **Measurably reduces discoverability and engagement of hidden items.** Acceptable for secondary nav; bad for primary. |\n| **Segmented control \u002F tabs** | Switching *views of the same object* | 2–5 | Not for navigation to different objects |\n| **Stack \u002F push navigation** | Drilling into hierarchy | Any depth (but >3 feels lost) | Must show where you are and how to get back |\n| **Bottom sheet** | Contextual actions, secondary content, mobile modality | — | Don't nest. Don't hide primary tasks. |\n| **Split view \u002F sidebar** (tablet, desktop) | Master–detail | Large | Reflow when narrow; don't just clip |\n| **Top nav + mega menu** (web) | Broad, shallow site structure | Large | Keyboard and screen reader support is usually broken |\n| **Breadcrumbs** (web, desktop) | Deep hierarchy, orientation | — | Only if a real hierarchy exists; not for linear flows |\n| **Command palette** (⌘K) | Expert users, large command surface | Unlimited | Excellent *supplement*, never the only path |\n| **Menu bar** (desktop) | Complete, searchable command index | Unlimited | Every command should be here (§8.4 → `ui-ux-design-systems-platforms-and-accessibility`) |\n\n**[CONTESTED] The hamburger menu.** The evidence that hiding navigation reduces usage of\nhidden items is strong and replicated. The counterargument is equally real: on a 375 px\nscreen with eight destinations, there is no alternative that doesn't consume the content\narea, and a tab bar with eight items is worse. The defensible position: **use a tab bar for\nthe 3–5 things people do constantly and a drawer for the long tail**, and never put a\nprimary revenue or activation path behind the hamburger.\n\n### 3.3 Search\n\n- **If the catalogue is large, search is the primary navigation** — treat it as a feature,\n  not a text box in the corner.\n- **Support the failure cases**: typos (fuzzy matching), synonyms and the user's vocabulary,\n  zero results (offer alternatives, never a dead end), and scoped search (this folder vs.\n  everything).\n- **Show what was searched and what filters are active.** Losing your query on the results\n  page is a top-tier frustration.\n- **Autocomplete** shifts the task from recall to recognition — one of the highest-value\n  patterns available. Show *categories* of suggestions, not just strings.\n\n### 3.4 Wayfinding — the three questions\n\nEvery screen must answer, without effort: **Where am I? Where can I go? How do I get back?**\nMechanisms: persistent nav with a current-state indicator, page titles that match the link\nthat got you there (label consistency — a startling number of products fail this),\nbreadcrumbs, and a Back that does what the platform Back is supposed to do.\n\n> **⚠️ GOTCHA — hijacking Back.** On Android, the system Back gesture\u002Fbutton has defined\n> semantics. On the web, the browser Back must work in a SPA (History API, not just\n> client-side routing that leaves the URL stale). Users trust Back more than they trust\n> your UI; breaking it destroys that trust immediately and permanently.\n","# UI\u002FUX Design: The Science Underneath, Usability Heuristics, and Information Architecture\n\n> **Part 1 of 5** of the *UI\u002FUX Design Principles — Mobile, Tablet, Web, Desktop* reference (plugin `ui-ux-design-principles`), covering §0–§3. Sibling skills: `ui-ux-interaction-layout-and-visual-design` (§4–§6), `ui-ux-design-systems-platforms-and-accessibility` (§7–§9), `ui-ux-writing-forms-research-and-ethics` (§10–§14), `ui-ux-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `ui-ux-reference` for the currency snapshot and what goes stale first.\n>\n> **Related:** Overlaps the `frontend-design:graphic-ux-ui-design` skill. That one is oriented to implementation-time component and token decisions; this one is oriented to design reasoning, cross-form-factor principles, research method, and the regulatory landscape. Use both.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — grounded in perception, cognition, motor control, or decades of\n>   replicated research. Does not expire. Trust it.\n> - **[PLATFORM]** — a convention of Apple, Google, Microsoft, GNOME\u002FKDE, or the web.\n>   Verify against the current HIG; these change.\n> - **[CONTESTED]** — competent practitioners disagree, or the evidence is thinner than the\n>   confidence with which it's usually asserted. Both cases given.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that survive design review and get caught in\n> production, in court, or in the analytics.\n>\n> **The framing that organizes everything below:** an interface is a *proposal about how\n> a person should think*. Good design makes the proposal match how they already think.\n> Every principle in this document is a specialization of that idea — to a thumb, a\n> screen size, a screen reader, a legal regime, or an attention budget.\n\n---\n\n## §0. Routing\n\n### 0.1 The four form factors, honestly compared\n\n| | **Mobile** | **Tablet** | **Web (desktop browser)** | **Desktop (native)** |\n|---|---|---|---|---|\n| Primary input | Thumb, one hand, imprecise | Two hands \u002F stylus | Mouse + keyboard | Mouse + keyboard, heavy shortcut use |\n| Pointer precision | ~9 mm finger contact | ~9 mm, better reach | ~1 px | ~1 px |\n| Session length | Seconds–minutes | Minutes | Minutes | Hours |\n| Attention | Divided, interrupted, mobile | Semi-focused, leisure | Task-focused, multi-tab | Deep focus, expert |\n| Context | Anywhere, any light, any network | Couch, desk, kiosk | Desk | Desk |\n| Information density | Minimum viable | Medium | Medium-high | **High — and users want it** |\n| Navigation idiom | Tab bar \u002F bottom sheet \u002F stack | Split view, sidebar | Header nav + breadcrumbs | Menu bar, sidebar, panels, palettes |\n| Discoverability need | High (few affordances visible) | High | Medium | Lower (menus are a searchable index) |\n| Error cost of a mis-tap | High | Medium | Low | Low |\n| Undo expectation | Weak (usually) | Weak | Weak | **Strong — unlimited, always** |\n| Offline expectation | High | High | Low-medium | High |\n| Governing convention | Apple HIG \u002F Material 3 | Apple HIG \u002F Material 3 | Web conventions + your design system | Platform HIG (macOS\u002FWindows\u002FGNOME\u002FKDE) |\n\n**[DURABLE] The most common cross-form-factor mistake is transposing density.** Shrinking\na desktop layout produces an unusable phone screen; stretching a phone layout produces a\ndesktop app that insults its users by wasting 70% of the screen and hiding functionality\nthree taps deep. Density is not a styling decision — it's a claim about how much the user\ncan and wants to hold in view at once, and that differs by context, not just by pixels.\n\n### 0.2 The question router\n\n| Asked about... | Go to |\n|---|---|\n| Why does this feel confusing\u002Fslow\u002Fwrong? Perception, memory, attention | §1 |\n| Heuristics, usability principles, Norman's model, affordances | §2 |\n| Navigation, IA, search, findability, menu structure | §3 |\n| Touch vs pointer vs keyboard, gestures, thumb zones, input models | §4 → `ui-ux-interaction-layout-and-visual-design` |\n| Layout, grids, responsive, breakpoints, adaptive, foldables | §5 → `ui-ux-interaction-layout-and-visual-design` |\n| Typography, color, spacing, elevation, iconography, motion | §6 → `ui-ux-interaction-layout-and-visual-design` |\n| Design systems, tokens, component APIs, governance | §7 → `ui-ux-design-systems-platforms-and-accessibility` |\n| Platform conventions and how they differ | §8 → `ui-ux-design-systems-platforms-and-accessibility` |\n| Accessibility — principles, WCAG, law, testing | §9 → `ui-ux-design-systems-platforms-and-accessibility` |\n| Microcopy, error messages, empty states, tone | §10 → `ui-ux-writing-forms-research-and-ethics` |\n| Forms, onboarding, checkout, conversion | §11 → `ui-ux-writing-forms-research-and-ethics` |\n| Research methods, usability testing, sample size, analytics | §12 → `ui-ux-writing-forms-research-and-ethics` |\n| Metrics, HEART, success criteria | §12.4 → `ui-ux-writing-forms-research-and-ethics` |\n| Dark patterns, persuasion ethics, regulation | §13 → `ui-ux-writing-forms-research-and-ethics` |\n| AI-era interfaces, conversational UI, generative UI | §14 → `ui-ux-writing-forms-research-and-ethics` |\n| \"Don't do this\" | §15 → `ui-ux-reference` |\n| \"Which is better, X or Y?\" | §16 → `ui-ux-reference` (contested) |\n| Books, researchers, authoritative sources | §18 → `ui-ux-reference` |\n| \"Is this still current?\" | §17 → `ui-ux-reference` |\n\n---\n\n## §1. The Science Underneath — why interfaces work or don't\n\nAlmost every defensible design decision reduces to one of these. Knowing them turns\n\"I don't like it\" into \"this will cost users ~600 ms per interaction and here's why.\"\n\n### 1.1 Motor control\n\n**Fitts's Law [DURABLE]** — time to acquire a target is a function of distance and size:\n`MT = a + b·log₂(2D\u002FW)`. Practical consequences, in rough order of value:\n- **Bigger targets are faster and more accurate.** Non-negotiable, measurable, and the\n  basis of every touch-target guideline in §4.2 → `ui-ux-interaction-layout-and-visual-design`.\n- **Closer targets are faster.** Put the primary action near where the user's attention\n  and pointer already are — not in a corner because the grid says so.\n- **Screen edges and corners have effectively infinite width** in one dimension, because\n  the pointer stops there. This is why the macOS menu bar (screen top) is faster to hit\n  than a Windows in-window menu bar, and why the corners are the most valuable real estate\n  on a desktop screen. On touch, edges have the *opposite* property — they're where the\n  hand occludes and where system gestures live.\n- **Dangerous actions should violate Fitts deliberately**: make Delete smaller, farther, or\n  behind a confirm. Never place Cancel adjacent to a destructive primary.\n\n**Steering Law [DURABLE]** — time to move *through* a constrained path grows with path\nlength and shrinks with tunnel width. This is why deep cascading menus are painful (you\nmust steer down a narrow corridor without leaving it) and why macOS's diagonal-tolerance\nin submenus was a genuine innovation. If your nav requires precise steering, add\ndwell tolerance or convert to click-to-open.\n\n### 1.2 Decision and attention\n\n**Hick–Hyman Law [DURABLE, but frequently over-applied]** — decision time grows\nlogarithmically with the number of *equally likely* alternatives: `RT = a + b·log₂(n+1)`.\n- Correct use: don't put 40 undifferentiated options in one flat list.\n- **⚠️ Misuse:** \"Hick's Law says fewer menu items are always better\" — false. The log is\n  cheap; a well-*categorized* list of 40 is faster than a flat list of 8 that requires\n  drilling. And options are rarely equally likely — a good default collapses the decision\n  entirely. **Categorization beats reduction.**\n\n**Miller's \"7±2\" [DURABLE finding, WIDELY misapplied]** — Miller (1956) described\nshort-term memory capacity for *chunks* in a recall task. It was never a rule about menu\nlength or navigation items, and Miller himself objected to that use. The better modern\nnumber is **Cowan's ~4±1** chunks for working memory without rehearsal. The design\nimplication is real but different: **don't require users to hold state in their heads**.\nShow the previous step. Persist the filter. Display the total. Recognition over recall\n(§2.1) is the actual principle.\n\n**Cognitive load [DURABLE]** — three types worth distinguishing:\n- *Intrinsic*: inherent difficulty of the task. You can't remove it, only sequence it.\n- *Extraneous*: load imposed by the interface itself. **This is the entire target of UI\n  design.** Inconsistent labels, hidden state, unclear hierarchy, unnecessary choices.\n- *Germane*: effort spent building a useful mental model. Worth preserving.\n\n**Attention is selective and change-blind.** Users do not see your banner. Inattentional\nblindness and **banner blindness** are well replicated: elements that look like ads, sit in\nad-shaped positions, or animate like ads get filtered out pre-consciously. If something\nmust be seen, it goes in the content flow, not the periphery.\n\n### 1.3 Perception and grouping\n\n**Gestalt principles [DURABLE]** — the visual system groups before you consciously read.\nIn rough order of strength:\n1. **Proximity** — nearest elements group. *The single most powerful and most misused tool\n   in UI layout.* If a label is equidistant between two fields, users will guess.\n2. **Similarity** — same color\u002Fshape\u002Fsize groups. This is why \"everything is a button\" and\n   \"nothing looks like a button\" are both failures.\n3. **Common region** — a shared border or background box groups strongly, and *overrides\n   proximity*. Cards work because of this.\n4. **Continuity \u002F Common fate** — aligned or co-moving elements group. Alignment isn't\n   aesthetics, it's grouping.\n5. **Closure \u002F Figure-ground** — the mind completes shapes and separates foreground.\n\n**⚠️ GOTCHA — the proximity bug.** The most common spacing error in real products:\nequal margins above and below a label, so it visually belongs to neither the field above\nnor the field below. **Rule: the space *within* a group must be smaller than the space\n*between* groups.** Almost every \"this form feels cluttered\" complaint is this.\n\n**Von Restorff (isolation) effect [DURABLE]** — the item that differs is remembered and\nfound. This is the entire justification for having exactly **one** primary button per view.\nTwo primary buttons = zero primary buttons.\n\n**Serial position effect [DURABLE]** — first and last items in a list are recalled best.\nPut the most important nav item first, the second-most last.\n\n### 1.4 Memory of the experience\n\n**Peak-End Rule [DURABLE]** — people judge an experience by its most intense moment and\nits ending, not its average. Design consequences:\n- Invest disproportionately in the **worst moment** (the error, the wait, the failed\n  payment) and the **last moment** (the confirmation, the success state, the offboarding).\n- A pleasant confirmation screen genuinely changes the remembered quality of a tedious form.\n\n**Zeigarnik effect [DURABLE-ish]** — incomplete tasks stay in memory. Progress indicators\nand \"3 of 5 steps\" work partly because of this. It is also the mechanism behind\ncompletion-pressure dark patterns (§13 → `ui-ux-writing-forms-research-and-ethics`) — same lever, different intent.\n\n**Doherty Threshold (~400 ms) [DURABLE]** — below roughly 400 ms of system response,\nusers stay in flow and productivity rises superlinearly. Above ~1 s, attention wanders.\nThis is why perceived performance is a *design* concern (§6.6 → `ui-ux-interaction-layout-and-visual-design`), not just an engineering one.\n\n**Time perception is malleable.** Progress bars that accelerate toward the end feel\nfaster. Skeleton screens feel faster than spinners because they signal *what* is coming.\nOptimistic UI (show the result immediately, reconcile later) feels instant — but you must\nthen design the failure path honestly, not silently drop the change.\n\n### 1.5 Learning and expertise\n\n**Power law of practice [DURABLE]** — performance improves as a power function of\nrepetitions. Two consequences:\n- **Novices and experts need different affordances of the same function.** A menu item\n  (discoverable, slow) and a keyboard shortcut (fast, invisible) for the same command is\n  not redundancy — it's the correct design. **Show the shortcut in the menu** so the\n  transition happens.\n- **Consistency is compound interest.** Every deviation resets the learning curve.\n\n**Jakob's Law [DURABLE]** — users spend most of their time on *other* products, so they\nexpect yours to work like those. Novel interaction models carry an enormous, usually\nunderestimated cost. Innovate on the *product*, not on where the close button lives.\n\n---\n\n## §2. Usability Heuristics and Mental Models\n\n### 2.1 Nielsen's 10 heuristics — with the failure mode of each\n\nStill the most useful evaluation checklist ever written (Nielsen & Molich 1990, refined\n1994). Below, each heuristic plus how it's commonly violated *by teams who think they're\nfollowing it*:\n\n| Heuristic | What it means | How it fails in practice |\n|---|---|---|\n| 1. **Visibility of system status** | Always tell the user what's happening | A spinner with no ETA, no cancel, and no indication of what's loading. \"Saving…\" that never resolves. Optimistic UI that silently fails. |\n| 2. **Match between system and the real world** | Speak the user's language | Internal jargon leaking into UI (\"Entity\", \"Object\", \"Instance\", \"Sync conflict\"). Icons that mean something only to the team. |\n| 3. **User control and freedom** | Emergency exits, undo | Modals with no Escape. Wizards with no Back. Destructive actions with confirm-only and no undo (§2.3). |\n| 4. **Consistency and standards** | Internal + platform consistency | Three different date pickers. A \"Save\" that means Apply on one screen and Commit on another. |\n| 5. **Error prevention** | Prevent > handle | Free-text where a picker belongs. No inline validation. Allowing a state the system will reject later. |\n| 6. **Recognition rather than recall** | Show, don't make them remember | Hiding the filter you applied. Requiring a code from a previous screen. Icon-only toolbars with no labels. |\n| 7. **Flexibility and efficiency of use** | Accelerators for experts | No keyboard shortcuts. No bulk actions. No saved views. Optimizing solely for first-run. |\n| 8. **Aesthetic and minimalist design** | No irrelevant information | **Most misread heuristic.** It says *irrelevant* — not *sparse*. Hiding necessary controls to look clean is a violation, not compliance. |\n| 9. **Help users recognize, diagnose, recover from errors** | Plain language, cause, remedy | \"Error 0x8007.\" \"Something went wrong.\" Errors that don't say which field. |\n| 10. **Help and documentation** | Findable, task-oriented | A 60-page PDF. A help center that doesn't cover the thing that's confusing. |\n\n### 2.2 Norman's model — the vocabulary for diagnosing *why*\n\n- **Affordance** — what an object *permits* (a real relationship between object and user).\n- **Signifier** — the *perceivable cue* that communicates the affordance. In UI, you almost\n  always mean signifier. A flat rectangle affords clicking; it needs a signifier to say so.\n- **Mapping** — relationship between control and effect. Natural mapping = spatial\n  correspondence (the volume slider goes up for louder).\n- **Feedback** — immediate, informative confirmation that the system received the action.\n- **Constraints** — physical, semantic, cultural, logical limits on what can be done.\n- **Conceptual model** — the user's story about how the thing works.\n\n**The Gulf of Execution** (how do I do it?) and the **Gulf of Evaluation** (did it work?).\nEvery usability problem lives in one of these two gaps. When someone says \"the UX is bad,\"\nask which gulf — the answers are completely different interventions.\n\n> **⚠️ GOTCHA — the flat-design signifier deficit.** The flat\u002Fminimal aesthetic that has\n> dominated since ~2013 systematically removed signifiers (shadows, bevels, borders,\n> underlines). Research repeatedly finds users hesitate over, or fail to find, weak-signifier\n> controls — and it disproportionately affects older and less experienced users. **Ghost\n> buttons, borderless inputs, and unlined links are aesthetic choices with a measurable\n> usability cost.** Make it deliberate, and compensate (hover states, cursor changes,\n> generous targets, at minimum a border on inputs).\n\n### 2.3 Confirmation vs. undo\n\n**[DURABLE] Undo beats confirmation almost always.** Confirmation dialogs:\n- are dismissed reflexively after the third exposure (habituation),\n- interrupt flow for the 99% of cases that were intentional,\n- and provide no help in the 1% where the user was wrong but *confident*.\n\nPrefer: perform the action → show a **toast with Undo** → make it durable for a reasonable\nwindow. Reserve confirmation for actions that are genuinely irreversible *and* consequential\n(deleting an account, sending money, publishing). When you must confirm:\n- Name the specific object (\"Delete *Q3 Budget.xlsx*?\"), never \"Are you sure?\"\n- Label buttons with **verbs**, not Yes\u002FNo (\"Delete\" \u002F \"Cancel\").\n- State the consequence, including irreversibility.\n- Make the destructive option *not* the default and *not* adjacent to the safe one.\n\n### 2.4 Progressive disclosure and defaults\n\n**[DURABLE] Defaults are the most powerful design decision you make.** Most users never\nchange them; the default *is* the product for the majority. Choose them for the user's\nbenefit, and be aware that choosing them for yours is what regulators now call a dark\npattern (§13 → `ui-ux-writing-forms-research-and-ethics`).\n\n**Progressive disclosure** — show the common case; make the advanced case reachable, not\nabsent. The discipline is: (a) the entry point to the hidden layer must be visible,\n(b) hiding must be based on *frequency of use*, not on *how tidy it looks*, and (c) never\nhide something the user needs in order to understand what's on screen.\n\n---\n\n## §3. Information Architecture and Navigation\n\n### 3.1 The IA questions, in order\n\n1. **What are the objects?** (Not screens — *things*. Documents, orders, patients, tracks.)\n2. **What are their attributes and relationships?**\n3. **How will people look for them?** (Known-item search vs. exploratory browse vs.\n   re-finding something they saw before — these are different behaviours needing\n   different affordances.)\n4. **What vocabulary do *they* use?** (Not your database's.)\n5. **What's the primary organizing scheme?**\n\n**Organizing schemes [DURABLE]:**\n- *Exact* schemes (alphabetical, chronological, geographic) — unambiguous, good for\n  known-item lookup, useless for exploration.\n- *Ambiguous* schemes (by topic, task, audience, metaphor) — support exploration, require\n  the user to guess your model. Most product IA is ambiguous, which is why card sorting\n  (§12.2 → `ui-ux-writing-forms-research-and-ethics`) exists.\n- *Hybrid* schemes fail when they mix at the same level (\"Products, Support, For Teams,\n  Pricing, 2024 Archive\"). Mixing across levels is fine; mixing within one is confusing.\n\n### 3.2 Navigation patterns by form factor\n\n| Pattern | Best for | Capacity | Watch out |\n|---|---|---|---|\n| **Bottom tab bar** (mobile) | 3–5 top-level, equally important, frequently switched destinations | 5 max (iOS shows \"More\" beyond 5) | Not for actions. Not for >5. Not for hierarchy. |\n| **Navigation drawer \u002F hamburger** | Many destinations, infrequent switching | ~10 | **Measurably reduces discoverability and engagement of hidden items.** Acceptable for secondary nav; bad for primary. |\n| **Segmented control \u002F tabs** | Switching *views of the same object* | 2–5 | Not for navigation to different objects |\n| **Stack \u002F push navigation** | Drilling into hierarchy | Any depth (but >3 feels lost) | Must show where you are and how to get back |\n| **Bottom sheet** | Contextual actions, secondary content, mobile modality | — | Don't nest. Don't hide primary tasks. |\n| **Split view \u002F sidebar** (tablet, desktop) | Master–detail | Large | Reflow when narrow; don't just clip |\n| **Top nav + mega menu** (web) | Broad, shallow site structure | Large | Keyboard and screen reader support is usually broken |\n| **Breadcrumbs** (web, desktop) | Deep hierarchy, orientation | — | Only if a real hierarchy exists; not for linear flows |\n| **Command palette** (⌘K) | Expert users, large command surface | Unlimited | Excellent *supplement*, never the only path |\n| **Menu bar** (desktop) | Complete, searchable command index | Unlimited | Every command should be here (§8.4 → `ui-ux-design-systems-platforms-and-accessibility`) |\n\n**[CONTESTED] The hamburger menu.** The evidence that hiding navigation reduces usage of\nhidden items is strong and replicated. The counterargument is equally real: on a 375 px\nscreen with eight destinations, there is no alternative that doesn't consume the content\narea, and a tab bar with eight items is worse. The defensible position: **use a tab bar for\nthe 3–5 things people do constantly and a drawer for the long tail**, and never put a\nprimary revenue or activation path behind the hamburger.\n\n### 3.3 Search\n\n- **If the catalogue is large, search is the primary navigation** — treat it as a feature,\n  not a text box in the corner.\n- **Support the failure cases**: typos (fuzzy matching), synonyms and the user's vocabulary,\n  zero results (offer alternatives, never a dead end), and scoped search (this folder vs.\n  everything).\n- **Show what was searched and what filters are active.** Losing your query on the results\n  page is a top-tier frustration.\n- **Autocomplete** shifts the task from recall to recognition — one of the highest-value\n  patterns available. Show *categories* of suggestions, not just strings.\n\n### 3.4 Wayfinding — the three questions\n\nEvery screen must answer, without effort: **Where am I? Where can I go? How do I get back?**\nMechanisms: persistent nav with a current-state indicator, page titles that match the link\nthat got you there (label consistency — a startling number of products fail this),\nbreadcrumbs, and a Back that does what the platform Back is supposed to do.\n\n> **⚠️ GOTCHA — hijacking Back.** On Android, the system Back gesture\u002Fbutton has defined\n> semantics. On the web, the browser Back must work in a SPA (History API, not just\n> client-side routing that leaves the URL stale). Users trust Back more than they trust\n> your UI; breaking it destroys that trust immediately and permanently.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-cognition-heuristics-and-navigation",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill ui-ux-cognition-heuristics-and-navigation",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill ui-ux-cognition-heuristics-and-navigation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill ui-ux-cognition-heuristics-and-navigation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-cognition-heuristics-and-navigation\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]