Psychologie UX pour le Design Web

VérifiéSûr

Couche consultative pour les décisions de conception web qui met en avant les principes de psychologie comportementale. Priorise l'identité de marque, l'accessibilité et la qualité technique.

Spar Skills Guide Bot
DeveloppementIntermédiaire
22/07/2026
Claude CodeCursorWindsurfCopilotCodex
#ux-design#behavioral-psychology#conversion#web-design#design-review

Recommandé pour

Synthèse automatique

Une couche de conseil qui fait remonter des principes de psychologie comportementale (ancrage, preuve sociale, aversion à la perte, etc.) lors de la conception ou de la revue de pages et de parcours web.

Points forts

  • Fournit des prescriptions prêtes à l'emploi par type de page : landing, tarifs, onboarding, tableau de bord, tunnel de paiement
  • Établit une hiérarchie de pondération explicite où l'identité de marque et l'accessibilité priment sur les principes psychologiques
  • Prend explicitement position contre les dark patterns et limite l'usage à une application éthique
  • Demande des recommandations concrètes et implémentables (markup, mise en page, copywriting) plutôt que des conseils abstraits

Limites

  • Les conseils étendus et les erreurs courantes renvoient à des fichiers de connaissances externes absents du SKILL.md
  • S'appuie sur des heuristiques théoriques, sans boucle de mesure ni de test pour valider les effets réels
  • N'est pas un substitut à la recherche utilisateur ni à un audit d'accessibilité ou de performance
Quand l'utiliser

À utiliser après avoir construit une landing page, une page de tarifs, un onboarding ou un tunnel de paiement, pour une relecture informée par la psychologie du comportement.

Quand l'éviter

À éviter si vous cherchez des données utilisateurs validées, un audit WCAG ou une optimisation de performance plutôt que des heuristiques de design.

Analyse de sécurité

Sûr
Score qualité82/100

This is a purely advisory design/psychology document with no declared tools and no executable instructions. It contains no shell commands, network calls, credential access, file writes, or attempts to disable safety mechanisms. The only content is prose guidance and static HTML/CSS examples for pricing-page layout, and it explicitly subordinates itself to brand, accessibility, and user trust, disclaiming dark patterns.

Aucun point d'attention détecté

Comment cette analyse est faite

Exemples

Review a pricing page
I just finished the pricing page for my SaaS. Run the UX psychology lens on it and tell me which 3-5 principles apply, where I'm missing them, and the exact markup or copy changes to make.
Audit an onboarding flow
Here's my 6-field sign-up form. Apply the onboarding prescription from the UX psychology skill — progressive commitment, cognitive load, Zeigarnik — and show me how to restructure it step by step.
Landing page first impression
Review my landing page hero: does it communicate value in under 3 seconds, and is social proof visible early? Suggest specific edits to the HTML and copy.

UX Psychology Skill

Advisory layer for web design decisions. Surfaces relevant behavioral psychology principles during page and component design. This is a weighted input — it informs decisions, it does not override aesthetic judgment, brand identity, or creative direction.

When to Use

Invoke after building or designing pages, components, or flows. The skill works best as a review layer — build first, then run the psychology lens to find what you're missing:

  • Landing pages, pricing pages, onboarding flows
  • Subscription/conversion funnels
  • Dashboard layouts and data presentation
  • Navigation and information architecture
  • E-commerce product pages and checkout flows
  • Any page where you want users to take a specific action

Decision Process

When activated, follow this order:

  1. Identify the page type — landing, pricing, onboarding, dashboard, checkout, etc.
  2. Pull the 3-5 most relevant principles from the page-type prescriptions below
  3. For each principle, state: what it is → how to apply it to THIS specific page → what the anti-pattern looks like
  4. Weight against constraints — brand identity, accessibility, and technical requirements always take priority
  5. Recommend specific, implementable changes — not abstract advice. Show what to change in the markup, layout, or copy. If you can point to a line of code, do it.

How to Weight

Psychology principles are one input among many. The weighting hierarchy:

  1. Brand identity and creative vision (highest — the site must look and feel right)
  2. Accessibility and usability (non-negotiable — WCAG compliance, touch targets, contrast)
  3. Technical quality (performance, SEO, responsive design)
  4. Psychology principles (this skill — subtle influence, not heavy-handed manipulation)

Never sacrifice aesthetics or user trust for a psychology trick. If a principle conflicts with good design, good design wins.

What This Skill Is NOT

  • NOT a dark patterns handbook — every principle here is ethical application only
  • NOT a complete design system — it augments existing design skills
  • NOT a replacement for user research — real user data always beats theory
  • NOT a rigid checklist — use the principles that fit, ignore the ones that don't

Page-Type Prescriptions (Inline)

The top principles per page type, self-contained for quick reference. See knowledge/page-prescriptions.md for expanded guidance and common mistakes.

Homepage / Landing Page

| Principle | Application | |-----------|------------| | First Impressions | Hero communicates value in under 3 seconds. Formed in 50ms — no second chances. | | Anchoring | Lead with your strongest metric or claim. First number seen sets the reference. | | Social Proof | Real numbers visible early (users, results, track record). Vague claims don't convert. | | Information Scent | Clear navigation — user knows exactly where to go next. | | Aesthetic-Usability | Visual polish earns trust before content does. Beautiful feels easier to use. |

Pricing / Subscription

| Principle | Application | |-----------|------------| | Anchoring | Show premium tier first or most visually prominent. Everything else feels like a deal. | | Loss Aversion | Frame around what free users MISS, not just what paid users get. Losing hurts 2x more. | | Default Effect | Pre-select the recommended tier. Most users never change defaults. | | Commitment/Consistency | Users who already used free features are primed to subscribe — each step leads to the next. |

Onboarding / Sign-Up

| Principle | Application | |-----------|------------| | Progressive Commitment | Small free action first, account second, payment last. | | Cognitive Load | One question per screen beats a long form. Remove everything non-essential. | | Zeigarnik Effect | Show progress (step 2 of 4). Incomplete tasks nag — users come back to finish. | | Reciprocity | Give value before asking for info. Free tool access, preview, or sample result. |

Dashboard / Data Display

| Principle | Application | |-----------|------------| | Chunking | Group data by category or priority — not one giant list. | | Spatial Memory | Consistent layout so returning users find things instantly. Don't move things. | | Satisficing | Highlight the single most important insight. Users pick the first acceptable option. | | Recognition Over Recall | Show full context (labels, timestamps, icons) — don't make users remember. |

Checkout / Payment

| Principle | Application | |-----------|------------| | Cognitive Load | Guest checkout option. Minimal form fields. One decision at a time. | | Transparency | Show ALL costs before the payment step. Surprise fees are the #1 abandonment cause. | | Loss Aversion | Trust badges and guarantees NEXT TO the payment button, not in the footer. | | Default Effect | Pre-select standard shipping. Pre-check "save info." Reduce decisions. |

About / Trust Page

| Principle | Application | |-----------|------------| | Authority | Methodology, data sources, team expertise — prove you know what you're doing. | | Hierarchy of Trust | This page serves users at level 2-3 (interest → confidence). Don't ask for the sale here. | | Transparency | Honest about limitations, not just strengths. Vulnerability builds trust. |


Code-Level Implementation Examples

Anchoring (Pricing Page)

Before — all tiers equal, no anchor:

<div class="plans">
  <div class="plan">Basic — $19/mo</div>
  <div class="plan">Pro — $49/mo</div>
  <div class="plan">Enterprise — $99/mo</div>
</div>

After — Pro anchored as the visual default:

<div class="plans">
  <div class="plan">Basic — $19/mo</div>
  <div class="plan featured">        <!-- visually prominent, pre-selected -->
    <span class="badge">Most Popular</span>
    Pro — $49/mo
  </div>
  <div class="plan">Enterprise — $99/mo</div>
</div>

Why: The featured tier becomes the anchor. Basic feels like a bargain by comparison. Enterprise exists to make Pro look reasonable. The "Most Popular" badge adds social proof.

Loss Aversion (Subscription CTA)

Before — gain-framed:

<button>Get Premium Access</button>
<p>Unlock all features and premium content.</p>

After — loss-framed:

<button>Keep My Premium Access</button>
<p>Without Premium, you'll lose access to daily insights,
   saved dashboards, and priority support.</p>

Why: "You'll lose access" triggers loss aversion (~2x stronger than equivalent gains). The CTA uses "Keep" — framing it as protecting something they already have.

Zeigarnik Effect (Onboarding Progress)

Before — no progress indication:

<form>
  <h2>Tell us about yourself</h2>
  {/* 8 fields on one page */}
</form>

After — stepped with visible progress:

<div className="progress-bar">
  <div className="step completed">Profile</div>
  <div className="step active">Preferences</div>   {/* current */}
  <div className="step">Review</div>
</div>
<form>
  <h2>Step 2 of 3 — Your Preferences</h2>
  {/* 2-3 fields only */}
</form>

Why: Incomplete progress bars create psychological tension. Users return to finish what they started. Breaking 8 fields into 3 steps of 2-3 fields reduces cognitive load AND creates the pull to complete.

Cognitive Load (Checkout)

Before — forced account creation:

<h2>Create Account to Continue</h2>
<input placeholder="Email" />
<input placeholder="Password" />
<input placeholder="Confirm Password" />
<button>Create Account & Checkout</button>

After — guest checkout with deferred account creation:

<h2>Checkout</h2>
<input placeholder="Email (for receipt)" />
<button>Pay Now</button>
<p class="subtle">Want to save your info for next time?
   <a href="/create-account">Create an account</a> after checkout.</p>

Why: Every extra field is a decision point that causes abandonment. Get the sale first. Account creation is a small ask AFTER they've already committed (Commitment/Consistency principle).


Principle Categories (11)

| Category | Count | Core Insight | |----------|-------|--------------| | Attention | 4 | Users see less than you think | | Gestalt | 8 | Visual grouping drives comprehension | | Memory | 10 | Recognition beats recall; chunk everything | | Sensemaking | 3 | Mental models shape expectations | | Decision Making | 5 | Fewer choices, clearer outcomes | | Motor/Interaction | 3 | Big targets, fast responses | | Motivation | 4 | Autonomy + competence + relatedness | | Cognitive Biases | 10 | Defaults persist; first impressions anchor | | Persuasion | 9 | Trust before ask; prove before promise | | Emotion | 6 | Beautiful feels easier; delight earns loyalty | | Ethics | 3 | Bright line between persuasion and manipulation |

Total: 65 principles — see knowledge/principles.md for the complete database with definitions and design implications.


Anti-Patterns (Never Do)

  • Fake scarcity counters — if it's not real, don't show it
  • Confirmshaming — "No, I don't want to save money" is manipulative
  • Hidden costs at checkout — the #1 cause of cart abandonment
  • Forced continuity — hard-to-cancel subscriptions erode all trust
  • Misdirection — visual tricks to force wrong clicks
  • Fake social proof — fabricated testimonials or inflated numbers
  • Dark defaults — pre-checking opt-ins the user didn't ask for
  • Roach motel patterns — easy to get in, impossible to get out

Source

Principles derived from NN/g's Psychology for UX study guide (112 resources across 11 categories), adapted into actionable design patterns. Academic foundations: Kahneman (Prospect Theory), Norman (Emotional Design), Cialdini (Influence), Hick, Fitts, Miller, Zeigarnik.

Du fichier au premier essai

Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.

Consulter la source et ses fichiers annexes

Ce téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.

1. Télécharger le fichier

Télécharger SKILL.md

Depuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/ux-psychology-for-web-design-mrwake3m/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.

Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.

mkdir -p '.skill-downloads/ux-psychology-for-web-design-mrwake3m' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ux-psychology-for-web-design-mrwake3m/download' --output '.skill-downloads/ux-psychology-for-web-design-mrwake3m/SKILL.md.part' && mv '.skill-downloads/ux-psychology-for-web-design-mrwake3m/SKILL.md.part' '.skill-downloads/ux-psychology-for-web-design-mrwake3m/SKILL.md'

2. Vérifier les prérequis

Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.

Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.

Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.

3. Charger la skill

Le fichier ne fournit pas un en-tête name/description exploitable pour cette procédure native. Le téléchargement reste disponible pour lecture ; utilisez le mode manuel ci-dessous.

Mode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.

4. Faire un premier essai

Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :

Lis .skill-downloads/ux-psychology-for-web-design-mrwake3m/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.

Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.

Skills similaires