---
id: "concept-prompt-dependency"
type: "concept"
source_timestamps: ["00:00:06", "00:00:20", "00:01:12"]
tags: ["bottlenecks", "user-experience"]
related: ["concept-claude-skills", "concept-super-prompts"]
definition: "The limitation where an AI's ability to perform complex work is bottlenecked by the user's need to repeatedly write exhaustive, highly detailed prompts."
sources: ["s40-super-prompts"]
sourceVaultSlug: "s40-super-prompts"
originDay: 40
---
# Prompt Dependency (The Tyranny of the Prompt)

## Definition

The limitation where an AI's ability to perform complex work is bottlenecked by the user's need to repeatedly write exhaustive, highly detailed prompts.

## The Core Problem

Executing hard, complex work — full financial analysis, end-to-end job-search strategy, structured vendor risk assessment — is strictly dependent on the user's willingness and ability to type long, repetitive prompts. Every new chat is a blank slate, and the user must re-supply:

- The relevant context
- All constraints
- Desired output formats
- Style and tone preferences
- Domain-specific reasoning frameworks

The speaker frames this as **"the tyranny of the prompt"** (see [[quote-tyranny-of-the-prompt]]).

## Why It Matters

Reducing prompt dependency is the entire value proposition of [[concept-claude-skills]] and [[concept-super-prompts]]. By packaging exhaustive context once into [[concept-composable-lego-bricks]], the user pays the prompting cost once and amortizes it across every future interaction.

## Related Counter-Perspective

Some practitioners argue that long context windows (e.g., Claude 200K tokens) and agentic frameworks like LangChain or AutoGPT mitigate prompt dependency more effectively than Markdown skills do. See the counter-perspectives section of [[_AGENT_PRIMER]].
