File systems are getting a brain. A UX concept published in the UX Collective proposes 'Folder Instructions,' a feature where users define persistent, natural-language rules that govern how a folder organizes, sources, and acts on its contents. The idea emerges directly from tools like Claude and Claw, which have already made file-system navigation a core AI capability. The concept identifies three instruction types: collation (gathering local or remote files matching a description), OS-level (password protection, auto-deletion, search visibility), and action-based (doing things with files, not just moving them).
The mechanism worth understanding is the 'System Rules' layer. When a user writes a folder instruction, the system auto-generates supporting rules to handle edge cases, conflicts, and ongoing behavior. Some rules default to on, others are optional. The user can tighten or loosen them. This is not a one-time sort operation. It is a persistent behavioral contract between the user and the folder. The contextual menu houses a 'New Instructions' entry and an 'Instruction History' log, though the author explicitly scopes the history and conflict-resolution mechanics out of this piece.
The full article is worth reading for its system design reasoning, not just the concept sketch. The author draws a direct line from Claude Code (powerful, heavy) to Claude Cowork (approachable, wider audience) to argue that the interface layer is now the bottleneck for agentic AI adoption. The passport renewal walkthrough, where the system downloads official forms, pulls local identity documents, and collates everything autonomously, makes the global collation case concrete. The question the piece leaves open: who writes the rules when instructions conflict across nested folders.
[READ ORIGINAL →]