wayfinding-physical-spatial-metaphors
Use this skill when deciding whether (and how) to borrow physical-world wayfinding metaphors for software — rooms, doors, paths, maps, landmarks. Trigger when designing app shells with multiple "spaces," when picking metaphors for navigation (workspace, channel, board, project), when reviewing skeuomorphic vs. flat navigation choices, or when the user mentions "feels like a maze" or "where's the front door of this app." Sub-aspect of `wayfinding`; read that first.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- wayfinding-physical-spatial-metaphors
- description
- Use this skill when deciding whether (and how) to borrow physical-world wayfinding metaphors for software — rooms, doors, paths, maps, landmarks. Trigger when designing app shells with multiple "spaces," when picking metaphors for navigation (workspace, channel, board, project), when reviewing skeuomorphic vs. flat navigation choices, or when the user mentions "feels like a maze" or "where's the front door of this app." Sub-aspect of `wayfinding`; read that first.
02 资源文件 1
- 参考文档references/metaphor-cases.md6.6 KB
03 SKILL.md 正文
Wayfinding through physical-spatial metaphors
Software navigation borrows from physical-world wayfinding all the time — sometimes deliberately, often by accident. "Folders" mimic filing cabinets; "rooms" and "channels" mimic conference rooms; "boards" and "lists" mimic whiteboards; "drilling down" and "zooming out" are spatial verbs. Used well, these metaphors give users an instant cognitive map. Used carelessly, they create expectations the software can't meet.
When physical metaphors help
The metaphor must satisfy three conditions to be net-positive:
- The user already knows the source. A "folder" works because filing cabinets are universal. A "Kanban board" works for users who know Kanban; less for those who don't.
- The mapping is consistent. If your "rooms" can be entered, exited, and have walls, then they should behave like rooms — opening one closes the other (or layers it visibly), entering signals a context shift, leaving returns to the previous space.
- The user gains something the metaphor uniquely provides. Spatial metaphors usually provide spatial intuitions: where things are relative to each other, what's nearby, what's deeper.
When all three hold, the metaphor offloads cognitive work to the user's existing model.
When metaphors backfire
- Mismatch between metaphor and behavior. A "Trash" that empties itself silently every 30 days is not a trash — physical trash sits there until you take it out. The metaphor implies one behavior, the system does another, and trust degrades.
- Forced metaphors that don't fit. Apple's mid-2000s reach for skeuomorphism (leather-bound calendars, felt-textured Game Center) borrowed metaphors that added no informational value and aged poorly.
- Cross-cultural assumptions. A "front porch" or "lobby" metaphor presumes architectural conventions that don't translate universally.
- Mixing incompatible metaphors. "Drag this folder into the room you want to share it with" combines a filing-cabinet verb with a building-room metaphor; it works only if the user squints.
Useful spatial metaphors in modern software
Rooms / Channels / Spaces
Slack channels, Discord servers, Notion workspaces, Microsoft Teams. The metaphor: a named container with members and a context. Each room has its own conversations and norms.
Wayfinding implications:
- Switching rooms feels like changing context (visual transition; current-room highlighted).
- Entering a room you've never visited shouldn't feel arbitrary — recent activity, who's there, what's pinned should orient you.
- A "lobby" or "general" channel acts as the entry-room equivalent.
Boards / Lanes / Cards
Trello, Linear, Asana boards. The metaphor: a flat surface (board) with regions (lanes/columns) and movable items (cards). Maps to whiteboards, post-it walls, kanban systems.
Wayfinding implications:
- The whole board is visible at once — no drilling down required for the primary view.
- Cards have positions; moving them carries meaning.
- Zooming out to see "all boards" requires a different metaphor (a folder of boards, a workspace).
Folders / Trees / Hierarchies
The original spatial metaphor: file systems. Folders within folders within folders.
Wayfinding implications:
- Depth reads as "deeper into" — backwards/up is the universal escape.
- Tree views show siblings and parents simultaneously; flat folder views show only contents (the file manager pattern).
- Breadcrumbs make hierarchy navigable without committing to a tree view.
The trap: deep hierarchies are easier to create than to navigate. Wayfinding research consistently finds that 4+ levels of depth become frustrating; users prefer broader, shallower structures.
Maps and Canvases
Figma, Miro, FigJam. The metaphor: an infinite 2D plane that the user pans and zooms across.
Wayfinding implications:
- Position carries meaning; spatial proximity is grouping.
- Mini-maps and zoom-to-fit are wayfinding tools borrowed directly from physical maps.
- Without these tools, users get lost on infinite canvases ("where's the design I made yesterday?").
Stacks / Decks / Stories
Card-stack metaphors (Stories on Instagram, swipeable decks). The metaphor: a stack of cards consumed sequentially.
Wayfinding implications:
- Position-in-sequence is the orientation (3 of 7).
- Forward/back are the only navigation verbs; usually no "jump to" without breaking the metaphor.
- Works well for short sequences; fails for long ones (no random access).
Cross-domain examples
Museum and gallery wayfinding
Museums have used spatial metaphors for centuries: rooms grouped by period, by region, by artist. Visitors orient by which "room" they're in. Modern museum apps mirror this — the audio tour app shows you which room corresponds to your current location, and tapping a room reveals its contents.
The lesson: when the physical space is well-organized, the digital equivalent inherits that organization for free.
City vs. suburban wayfinding
Cities organized on grids (Manhattan, parts of Tokyo) are easier to wayfind than organic-grown cities (Boston, Lisbon, much of London). Grid metaphors translate to software well: a settings page laid out as a grid of categories (Profile, Notifications, Security, Billing) is easier to navigate than one organized by some idiosyncratic logic.
When your IA naturally has a grid-like structure, expose it. When it has an organic structure, lean into landmarks.
"Skeuomorphism revisited"
The flat-design movement (post-2013) rejected literal skeuomorphism (leather-bound calendars, felt poker tables). What survived: spatial intuitions without literal visual mimicry. Sliding panels still feel like opening drawers; cards still feel like tangible objects. The visual style went flat; the spatial metaphors stayed.
The current trend (post-2020) is "neo-skeuomorphism" — subtle depth cues, careful shadows, motion that respects spatial logic. The principle: borrow the physics, not the textures.
Anti-patterns
- Inventing metaphors no user has ever encountered. "Rendezvous Spaces" or "Wisdom Pods" sound clever in design reviews and confuse everyone in production.
- Treating containers as both folders and tags. A folder is exclusive (a file lives in one folder); a tag is inclusive (a file can have many tags). Hybrid systems where a "folder" can also be applied as a tag confuse users.
- The infinite map without a home. Infinite-canvas tools without a "go to my home" or "fit to content" are wayfinding deserts.
- Animation that contradicts the spatial metaphor. Closing a sheet and having it shrink to a corner unrelated to where it opened from breaks the spatial intuition.
Heuristics
- Name the metaphor explicitly. "We're treating these as rooms — that means entering signals a context shift, exiting returns to where you were." Once named, the team can audit consistency.
- The "what would the physical version do?" check. When in doubt about a behavior, ask: what would the physical-world equivalent do? Does the software match?
- The new-user metaphor test. Onboard a new user without explaining your metaphors. If they intuit "channel," "board," "folder" correctly, the metaphor is doing its work. If they ask "what's a Space?", the metaphor is too clever.
Related sub-skills
wayfinding(parent) — the principle and four-stage framework.wayfinding-search-and-recovery— when spatial metaphors fail, search recovers.wayfinding-breadcrumbs-and-context— making the "where am I" answer load-bearing.mental-model— physical metaphors work because they leverage existing mental models.mimicry— the broader principle of borrowing successful patterns.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.