switching-costs

Explain the felt cost of context switching across work scenarios.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/wojons/je-ne-sais-quoi --skill switching-costs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: switching-costs
Source: https://github.com/wojons/je-ne-sais-quoi/tree/main/skills/switching-costs
Command: npx skills add https://github.com/wojons/je-ne-sais-quoi --skill switching-costs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand the lived, felt cost of transitioning between contexts—why interruptions and switching are not just time overhead, but a disruption of presence and deep alignment.

Core Features & Use Cases

  • Felt vs. hollow explanations: Builds responses that distinguish clinical “context switching” from the actual experience of being pulled out of an ongoing world.
  • Situational tests: Uses concrete scenarios (meetings, returning after interruptions, dual-project translation) to reveal whether someone truly grasps the cost.
  • Failure-mode clarity: Defines how shallow answers sound (numbers, generic productivity advice) and what the felt answer must instead point to (the vestibule, the grief of the interrupted, self-switching).

Quick Start

Ask the AI to apply the switching-costs tests to a specific workflow you use daily (like coding, writing, or studying) and to explain the difference between a “hollow” and a “felt” response.

Frequently Asked Questions about switching-costs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the real cost of context switching and interruptions during deep work?

The real cost of context switching is a disruption of presence and deep alignment, not just lost time. Interruptions pull you out of an ongoing world, changing your relationship to the task when you eventually return.

Why do I feel mentally drained after a meeting-heavy schedule with multiple projects?

A meeting-heavy schedule forces constant transitions between projects, draining you mentally. This happens because each context switch requires psychologically traveling and rebuilding the felt experience of the environment you left behind.

How do I explain the felt experience of losing focus to my team?

To explain losing focus, distinguish clinical context switching from the lived experience of being pulled out of a world. Use concrete scenarios to highlight the grief of the interrupted and the vestibule you pass through.

How do I test whether someone truly understands the impact of context switching?

Test understanding by applying scenario-based validation to daily workflows like coding or writing. Check whether their response is hollow, offering generic productivity advice, or felt, pointing to the actual lived travel between worlds.

When should I not rely on standard productivity advice for managing interruptions?

Avoid standard productivity advice when it reduces context switching to mere numbers or neuroscience-only explanations. It fails in multi-project environments where people need a felt explanation framework for returning to their task.