cognitive-fluency-psychology
Apply cognitive fluency principles to improve clarity, trust, and conversion. Use when designing landing pages, writing copy, creating interfaces, or optimizing any content for better user comprehension and engagement.
Best use case
cognitive-fluency-psychology is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply cognitive fluency principles to improve clarity, trust, and conversion. Use when designing landing pages, writing copy, creating interfaces, or optimizing any content for better user comprehension and engagement.
Teams using cognitive-fluency-psychology should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cognitive-fluency-psychology/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cognitive-fluency-psychology Compares
| Feature / Agent | cognitive-fluency-psychology | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply cognitive fluency principles to improve clarity, trust, and conversion. Use when designing landing pages, writing copy, creating interfaces, or optimizing any content for better user comprehension and engagement.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Cognitive Fluency - Psychology of Ease
Cognitive fluency is the ease with which our brains process information. When
something feels simple and easy to understand, our minds interpret that
simplicity as a signal that it must be true, safe, or worth engaging with.
Clarity always beats cleverness.
## When to Use This Skill
- Designing landing pages and marketing content
- Writing UI copy and microcopy
- Evaluating brand names and messaging
- Auditing content for readability
- Optimizing conversion funnels
- Creating training materials and documentation
## Core Principle
```
Processing Fluency Impact:
Easy to process → Feels familiar
↓ ↓
Feels trustworthy → Feels valuable
↓ ↓
Higher engagement → Better conversion
The brain's rule: "If it's easy, it must be good."
```
## Key Research Findings
### Truth and Repetition
| Finding | Implication |
| -------------------------------------------- | ------------------------------------------- |
| Repeated statements feel more true | Use consistent messaging across touchpoints |
| Simple fonts increase perceived truthfulness | Choose clarity over creativity in key areas |
| High contrast increases credibility | Prioritize readability over aesthetics |
| Familiar words feel more accurate | Use everyday language, not jargon |
### Task Perception Studies
```
Font Impact on Task Perception:
Simple, clear font:
├── Estimated task time: 8 minutes
├── Perceived difficulty: Low
└── Likelihood to start: High
Complex, decorative font:
├── Estimated task time: 15+ minutes
├── Perceived difficulty: High
└── Likelihood to start: Low
Same instructions, different perception.
```
### Cognitive Effort Discounting (COGED)
The brain reduces subjective value when tasks require more mental effort:
- Processing difficulty = perceived "cost"
- People avoid cognitive load instinctively
- Fluent experiences create positive emotions
- Effort required transfers to value judgment
## Fluency Audit Framework
### Step 1: Identify High-Stakes Content
Map where fluency matters most:
```
Priority Content:
├── Headlines and value propositions (Critical)
├── CTAs and conversion points (Critical)
├── Onboarding instructions (High)
├── Pricing and plans (High)
├── Error messages (Medium)
└── Help documentation (Medium)
```
### Step 2: Apply the 5-Second Test
For each critical element:
1. Show to someone unfamiliar with your product
2. Give them exactly 5 seconds to read
3. Ask them to explain:
- What is this?
- Who is it for?
- What should I do next?
4. If they struggle → rewrite for fluency
### Step 3: Check Fluency Factors
| Factor | Check | Fix |
| -------------------- | ------------------------------- | -------------------- |
| **Typography** | Is font ≥16px for body? | Increase size |
| **Contrast** | Is ratio ≥4.5:1? | Improve contrast |
| **Sentence length** | Are sentences <20 words? | Split long sentences |
| **Word choice** | Would a 12-year-old understand? | Simplify vocabulary |
| **Visual hierarchy** | Is main point obvious? | Strengthen hierarchy |
| **White space** | Is content breathing? | Add spacing |
### Step 4: Test and Measure
| Metric | What it Shows |
| --------------- | ----------------------- |
| Time on page | Processing difficulty |
| Scroll depth | Engagement with content |
| Bounce rate | Initial fluency failure |
| Conversion rate | End-to-end fluency |
| Task completion | Instruction clarity |
## Common Fluency Killers
### Design Problems
```
❌ Fluency Killers:
Typography:
├── Poor contrast ratios
├── Tiny or decorative fonts
├── Inconsistent sizing
└── ALL CAPS for long text
Layout:
├── Cluttered composition
├── Competing visual elements
├── No clear focal point
└── Walls of text
```
### Content Problems
```
❌ Content Fluency Killers:
Language:
├── Industry jargon
├── Complex sentences
├── Passive voice overuse
└── Unclear pronouns
Structure:
├── Too many concepts at once
├── Buried key information
├── Missing headings/breaks
└── No logical flow
```
## Output Template
After completing audit, document as:
```markdown
## Cognitive Fluency Audit
**Page/Content:** [Name]
**Date:** [Date]
### 5-Second Test Results
| Tester | What is it? | Who for? | Next action? | Pass? |
| ------ | ----------- | ---------- | ------------ | ----- |
| [1] | [Response] | [Response] | [Response] | ✅/❌ |
| [2] | [Response] | [Response] | [Response] | ✅/❌ |
### Fluency Score
| Factor | Current | Target | Priority |
| ---------- | ------- | ------- | -------- |
| Typography | [Score] | [Score] | [H/M/L] |
| Contrast | [Score] | [Score] | [H/M/L] |
| Language | [Score] | [Score] | [H/M/L] |
| Structure | [Score] | [Score] | [H/M/L] |
### Recommendations
#### Immediate Fixes
- [Fix 1]
- [Fix 2]
#### Requires Rewrite
- [Item 1]
- [Item 2]
### Before/After Examples
**Before:** [Original text] **After:** [Improved text] **Why:** [Fluency
principle applied]
```
## Real-World Applications
### Landing Pages
```
Before (low fluency):
"Leverage our cutting-edge, AI-powered solution to
optimize your workflow efficiency and drive ROI."
After (high fluency):
"Get more done in less time with AI that actually works."
Changes:
├── Removed jargon (leverage, cutting-edge, optimize)
├── Shortened sentence (13 words → 10 words)
├── Made benefit concrete (workflow efficiency → more done)
└── Added relatability (actually works)
```
### Brand Names
Research shows companies with easy-to-pronounce names:
- Perform better after IPOs
- Are remembered more often
- Get recommended more frequently
- Build trust faster
```
High Fluency Names: Low Fluency Names:
├── Apple ├── Xobni
├── Google ├── Qwikster
├── Slack ├── Tronc
└── Zoom └── Quibi
```
### Product Interfaces
```
Fluent Interface Patterns:
Forms:
├── One question per screen (not multi-field)
├── Smart defaults pre-filled
├── Inline validation (not page-level)
└── Progress indicator visible
Navigation:
├── Familiar patterns (hamburger, tabs)
├── Maximum 5-7 top-level items
├── Clear current location indicator
└── Predictable behavior
```
## Integration with Other Methods
| Method | Combined Use |
| -------------------------- | -------------------------------------- |
| **Cognitive Load** | Fluency reduces extraneous load |
| **Progressive Disclosure** | Reveal fluent chunks sequentially |
| **Hick's Law** | Fewer, clearer choices improve fluency |
| **Five Whys** | Why is content not converting? |
| **A/B Testing** | Test fluency improvements |
## Quick Reference
```
FLUENCY CHECKLIST
Typography:
□ Font size ≥16px body
□ High contrast (≥4.5:1)
□ Consistent hierarchy
□ Professional, readable font
Language:
□ Short sentences (<20 words)
□ Simple words (everyday vocabulary)
□ Active voice
□ One idea per paragraph
Structure:
□ Clear headings
□ Bullet points for lists
□ Plenty of white space
□ Visual hierarchy guides eye
Testing:
□ 5-second test passed
□ Non-expert can explain
□ Readability score acceptable
□ Key metrics improving
```
## Resources
- [Thinking, Fast and Slow - Daniel Kahneman](https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow)
- [Don't Make Me Think - Steve Krug](https://sensible.com/dont-make-me-think/)
- [Hemingway Editor](https://hemingwayapp.com/) - Readability checker
- [WebAIM Contrast Checker](https://webaim.org/resources/contrastchecker/)Related Skills
visual-cues-cta-psychology
Design effective CTAs using visual attention and gaze psychology principles. Use when designing landing pages, button hierarchies, conversion elements, or optimizing user attention flow through interfaces.
trust-psychology
Build trust signals that reduce perceived risk and enable user action. Use when designing landing pages, checkout flows, onboarding experiences, or any conversion point where user hesitation is a barrier.
social-proof-psychology
Leverage social proof principles to build trust and influence user behavior. Use when designing landing pages, adding testimonials, displaying user stats, or optimizing conversion elements with social validation.
loss-aversion-psychology
Leverage loss aversion in product design and messaging. Use when designing retention features, pricing strategies, onboarding flows, or any experience where framing around potential loss can drive behavior.
halo-effect-psychology
Apply the halo effect in product design and UX. Use when designing first impressions, brand perception, feature presentation, or understanding how one positive attribute influences perception of others.
cognitive-load
Design experiences that optimize mental resources using Cognitive Load Theory. Use when designing interfaces, creating onboarding flows, planning information architecture, or improving task completion rates.
cognitive-biases
Apply cognitive bias knowledge to product design and decision-making. Use when designing user experiences, analyzing user behavior, improving conversions, or ensuring ethical design practices.
what-not-to-do-as-product-manager
Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
value-realization
Analyze if end users discover clear value. Use when evaluating product concepts, analyzing adoption, or uncertain about direction.
user-story-fundamentals
Capture requirements from user perspective with structured user stories. Use when writing backlog items, defining acceptance criteria, prioritizing features, or communicating requirements between product and development.
typescript-satisfies-operator
Guides proper usage of TypeScript's satisfies operator vs type annotations. Use this skill when deciding between type annotations (colon) and satisfies, validating object shapes while preserving literal types, or troubleshooting type inference issues.