Detailed Analysis
A Reddit thread in r/Anthropic titled "Prompt Candy" surfaces a grassroots practice among Claude power users: the development of personal, reusable prompt heuristics designed to steer model behavior toward more productive outcomes. The original poster describes a technique of explicitly allocating percentages of effort between research/validation and actual building—for example, instructing the model to "spend 30% of your time on research and validation... and no less than 70% of your time building"—as a way to prevent the model from spiraling into what the poster calls "endless speculation." This is paired with a workflow habit of periodically asking the model to update a persistent "AI guide doc" after several hours of work, effectively creating a handoff artifact that lets the user start a fresh context window without losing accumulated project knowledge. The poster also notes explicitly telling Claude to stop "testing my assumptions" and instead act as a compliant "workhorse" that flags concerns but defers to the user's judgment rather than pushing back conversationally.
These practices point to a broader, informal body of knowledge that has emerged around prompt engineering for long-horizon, agentic coding and research tasks—distinct from simple one-off prompting tips. Users working on complex, multi-hour projects with Claude are running into two recurring friction points: models that over-index on caution, hedging, or exploratory reasoning at the expense of forward progress, and context-window limitations that force periodic resets. The percentage-based time allocation trick is essentially a crude but effective control mechanism for tuning a model's implicit "temperature" between deliberation and execution, while the persistent guide-doc habit is a manual analog to memory or context-compaction features that AI labs have been building natively into their products.
The mention of needing to explicitly override Claude's tendency to "test assumptions" or engage in Socratic pushback is notable because it reflects a known and often-praised trait of Claude's personality: relatively strong epistemic caution, a tendency to seek clarification, and reluctance to simply execute without scrutiny. While this behavior is generally viewed as a safety and quality-control feature, some power users experienced in a domain find it inefficient when they already possess the necessary context and want the model to function as a direct executor rather than a collaborative interlocutor. This tension—between models designed for careful, values-aligned reasoning and users wanting frictionless task execution—is a live design question across the industry, and Anthropic's own system prompts and constitutional AI approach explicitly bake in some of this "pushback" behavior deliberately.
More broadly, this thread is a small window into how the practice of "prompt engineering" is evolving in 2025–2026: less about clever one-liner tricks and more about building lightweight operational frameworks—memory documents, phase-based task allocation, explicit behavioral contracts—that treat the LLM like a semi-autonomous collaborator or employee that needs onboarding, management, and clear role definition. This mirrors broader industry moves toward agentic workflows, persistent memory, and tool use in models like Claude, where the model is expected to operate over long sessions with minimal supervision. The organic emergence of these user-generated "best practices," shared informally on Reddit rather than in official documentation, also underscores a gap between what AI labs publish as guidance and the tacit, experiential knowledge that experienced users develop through iteration—knowledge that increasingly shapes how these tools are used in real, complex projects rather than in short demo-style interactions.
Read original article →