Dev experience: foldered context wins

Developers are converging on a simple idea: put an artificial intelligence assistant’s instructions in folders and files, not in a heavy orchestration layer. (arxiv.org) A March 2026 paper calls the approach “Interpretable Context Methodology” and describes workflows where numbered folders mark stages, Markdown files hold prompts, and local scripts handle routine steps. The authors argue that teams doing sequential, human-reviewed work can skip much of the code needed by multi-agent frameworks. (arxiv.org) That maps closely to the reaction in recent developer posts praising folder-based context systems for being easier to change. In the paper’s description, swapping a prompt, reordering a step, or removing a stage can be done by editing files instead of changing framework code and redeploying. (arxiv.org) The underlying problem is context: large language model tools need the right instructions and reference material at the right moment, but many systems still wire that up through configuration files, framework abstractions, or custom agent code. OpenAI’s Model Context Protocol, for example, connects models to tools and external context through server configuration stored in `config.toml`. (developers.openai.com) A folder-based setup tackles the same problem with the file system developers already use every day. The paper says one orchestrating agent can read the right files at each stage, while the directory structure itself determines what context the agent or any sub-agent receives. (arxiv.org) The same preference for lighter setup is showing up in user-interface work, where teams are trying to shorten the handoff between Figma and code. Vercel said on January 27, 2025 that its v0 tool can import Figma files, extract visual layout and design tokens such as colors and spacing, and feed that context into generation. (vercel.com) Vercel’s documentation tells users not to dump an entire product mockup into one prompt. It recommends splitting designs into smaller frames such as navigation bars, forms, and landing-page sections, then refining components one by one before composing a full interface. (v0.app) That stepwise workflow helps explain reports from practitioners who say v0 has cut Figma turnaround from weeks to hours for early testing. Vercel says some teams have reduced the time from design to implementation on new features by up to three times when they align their design systems with v0 and shadcn/ui. (vercel.com) The common thread is not that configuration disappeared. It moved into places developers already understand: folders, frames, prompts, and reusable components. (arxiv.org; v0.app)