---
name: design-books
description: Vanshika's design bookshelf as a working method — principles from Don't Make Me Think (Krug), The Design of Everyday Things (Norman), Start With Why (Sinek), Hooked (Eyal), The Psychology of Money (Housel), The Art of Thinking Clearly (Dobelli) and Days at the Morisaki Bookshop (Yagisawa). Use this skill whenever designing or reviewing UI, flows, navigation or interactions; writing or editing UX copy, portfolio copy or case studies; designing engagement, onboarding or habit features; designing anything involving money, pricing or risk; planning user research or making product decisions; or when the user says "use my books", "apply the bookshelf", "review this like my books would", or similar.
---

# Design with the bookshelf

These are the books on Vanshika's shelf, turned into principles and checklists to apply directly while working. They are paraphrased summaries, not quotations — when quoting a book in the portfolio, verify the exact wording against the book.

Apply the sections that fit the task. For a design or code review, walk the **Review checklist** at the end and report findings grouped by book.

---

## 1. Don't Make Me Think — Steve Krug
*Usability: every question a user has to stop and answer costs attention.*

- **Self-evident over self-explanatory.** A screen should be understood at a glance; if it needs instructions, redesign it first.
- **People scan, satisfice and muddle through.** Design for skimming: clear visual hierarchy, obvious clickable things, conventional placement.
- **Mindless choices are fine.** Several easy, unambiguous clicks beat one click that needs thought.
- **Cut words ruthlessly.** Remove happy talk and instructions nobody reads; halve the copy, then halve it again.
- **Navigation answers:** Where am I? What's here? Where can I go? How do I get back? (Site ID, page name, sections, "you are here" state, search when content is large.)
- **Test early, with few people.** Three users watching the real thing beats a debate. Fix the most serious problems first.

## 2. The Design of Everyday Things — Don Norman
*When people struggle, it's the design's fault, not theirs.*

- **Affordances & signifiers.** Make what's possible visible: buttons look pressable, draggable things look draggable (e.g. the sunflower hero's "drag the scene" hint).
- **Mapping.** Controls should correspond naturally to what they affect (the timeline maps left→right to morning→night).
- **Feedback.** Every action gets an immediate, informative response; nothing happens silently.
- **Conceptual model.** The interface should let people form a correct mental model of how it works.
- **Constraints.** Physical, logical and cultural constraints prevent errors before they happen.
- **Design for error.** Assume slips and mistakes; make actions reversible, confirm destructive ones, and make recovery easy.
- **Human-centered design loop:** observe → ideate → prototype → test, repeated.

## 3. Start With Why — Simon Sinek
*Communicate from the inside out: Why → How → What.*

- **Lead with purpose.** Case studies, landing pages and pitches open with the problem and why it mattered, then the approach, then the deliverables.
- **The Golden Circle for portfolio copy:** Why (belief/problem) → How (process, principles) → What (screens, metrics).
- **Consistency builds trust.** What the product says, how it looks and what it does should express the same "why".

## 4. Hooked — Nir Eyal
*The Hook Model: Trigger → Action → Variable reward → Investment.*

- **Trigger:** external (notification, email) evolving into internal (an emotion or routine that prompts use).
- **Action:** the simplest behavior done in anticipation of reward — reduce effort, increase motivation.
- **Variable reward:** rewards of the tribe (social), the hunt (resources/info), the self (mastery).
- **Investment:** users put something in (data, content, preferences) that makes the next loop better.
- **Ethics check (always run it):** Would I use this myself? Does it materially improve the user's life? If not, it is manipulation — don't ship it. Prefer calm defaults, easy exits and no dark patterns.

## 5. The Psychology of Money — Morgan Housel
*Financial outcomes are driven more by behavior than by knowledge.*

- For any money, pricing, checkout or fintech UI: design for **behavior and emotion**, not spreadsheets — reduce anxiety, show consequences plainly, avoid urgency tricks.
- **Room for error.** Build in margins of safety; make undo, grace periods and clear confirmations the default.
- **"Enough" and compounding.** Surface long-term progress over short-term noise; don't gamify impulsive decisions.
- Everyone's money story is different — avoid one-size-fits-all assumptions in personas and copy.

## 6. The Art of Thinking Clearly — Rolf Dobelli
*Thinking errors are predictable, so they can be caught.*

Run these against research findings, metrics and product decisions:
- **Confirmation bias** — actively look for evidence against the preferred design.
- **Survivorship bias** — who dropped out and isn't in the data?
- **Sunk cost** — don't keep a direction just because of time already spent.
- **Social proof / authority** — "competitor X does it" or "the HiPPO wants it" isn't evidence.
- **Availability & recency** — one vivid user quote isn't a pattern.
- **Outcome bias** — judge decisions by the information available at the time, not only by results.
- **Framing** — the same data framed as gain vs. loss changes decisions; present metrics neutrally in case studies.

## 7. Days at the Morisaki Bookshop — Satoshi Yagisawa
*A novel, kept on the shelf for its tone: quiet, warm, unhurried.*

- Use it as the **voice** reference for Vanshika's portfolio: calm, personal, human; small details over big claims.
- Leave **breathing room** — whitespace, slow motion, gentle sound — so the work feels like a place to linger, not a pitch.

---

## Review checklist

When asked to review a screen, flow, component or case study, go through these and report findings grouped by book, most important first:

1. **Krug** — Can a first-time user tell what this is and what to do in 5 seconds? Any copy to cut? Navigation answers "where am I / where can I go"?
2. **Norman** — Are signifiers, mapping, feedback, constraints and error recovery all present?
3. **Sinek** — Does the copy / case study lead with *why*?
4. **Eyal** — If it's an engagement feature: which step of the Hook is it, and does it pass the ethics check?
5. **Housel** — If money is involved: does it lower anxiety and leave room for error?
6. **Dobelli** — Which biases could be shaping this decision or data?
7. **Morisaki** — Does it feel calm and human, with room to breathe?

Keep recommendations concrete (what to change, where), and prefer the smallest change that fixes the problem.
