How to use Claude like the top 1% of users
Here are the setups, hacks, and real workflows that make it feel like a completely different product
Here is how most people use Claude:
Open it. Type something. Get an answer. Close it.
Every session starts from zero. Claude knows nothing about who they are, what they are building, or how they think. So it produces something generic. And that is exactly why it disappoints them.
The people getting genuinely different results treat Claude as a system. They onboard it once. They build structure around it. The returns compound every day after.
This is that system. Files, prompts, Cowork hacks, context tricks, and the workflows that actually move the needle.
Part 1: The file system
Set this up once. Benefit from it forever.
The core idea: Claude reads a set of files before every session. Those files tell it who you are, how you work, and what good output looks like for you. You stop re-explaining yourself. Claude stops starting from zero.
Everything Claude has shipped in 2026 points toward the same direction: the model is getting better fast, but context is still the biggest lever available to users right now.
Here are the five files worth building first.
about-me.md
Tells Claude who you are before every task. Your role, your company, your current priorities, the decisions you have already made.
What to write: Your role and industry. What you are focused on this quarter. Decisions already made that Claude should build on, not question. Your single biggest current goal.
voice-profile.md
This is the file most people skip. It is also the reason most Claude outputs sound like they came from the same person who writes every corporate email.
Your voice is your beliefs, your contrarian takes, your sentence rhythm, the things you find cringe. A generic prompt will never give Claude that. This file will.
The best way to build it: ask Claude to interview you. Give it the role of a sharp journalist. Tell it to ask hard questions about how you think, what you believe, and what you would never say. You will surface things about your own voice you did not know were there.
Once you have it, every piece of content Claude writes for you starts sounding like you. That is the unlock behind creating content with Claude that actually sounds human.
anti-ai-writing-style.md
Taste is what you reject.
This file is a list of everything Claude should never sound like when writing as you. Words. Structures. Tones. Formatting rules.
A starting banned list: utilize, synergy, leverage, foster, delve, tapestry, testament, showcase, pivotal, underscore. Long intros. Summaries at the end. Rule-of-three adjective chains. Excessive bold. The full system for this is in Your Writing Sounds Like a Robot.
The Cowork folder
The four-folder structure Claude navigates when it works on your machine.
ABOUT ME/ — your identity and writing rules
PROJECTS/ — one subfolder per project, with brief, drafts, references
TEMPLATES/ — finished work you reuse as patterns
CLAUDE OUTPUTS/ — the only place Claude delivers work
Point Claude Cowork at this folder and it reads your entire context before touching anything. It knows what project it is working on. It knows your templates. It knows where to put the output. The 10 Cowork workflows that actually save time all start from this structure.
Global Instructions
Rules Claude follows before every single task. Set once in Settings → Cowork → Edit Global Instructions. Run forever.
Useful ones to set:
Always read ABOUT ME/ before starting
Always read the matching PROJECTS/ subfolder
Only deliver work in CLAUDE OUTPUTS/
Use this naming convention: project_content-type_v1.ext
Two hours to build this properly. After that, every session starts from full context. The compounding starts immediately.
Part 2: The prompting shifts that actually change outputs
Most people think prompting is about finding the right magic phrase. It is not. It is about giving Claude the right structure to reason well.
The golden rule: show your prompt to a colleague with minimal context on the task and ask them to follow it. If they would be confused, Claude will be too.
Stop giving orders. Start asking questions.
The highest-leverage shift in prompting is asking Claude what questions it would need answered to do the task well, rather than just telling it what to produce.
This is Socratic prompting. Claude surfaces assumptions you did not know you were making. Output quality jumps.
The prompt that makes this work:
I want to [TASK] so that [SUCCESS CRITERIA].
First, read my folder. Then ask me questions.
Refine the approach with me before you execute.
Claude generates a clickable form. You answer. Claude shows a plan. You approve. It executes. If something is off, you redirect. Claude recalibrates.
This single pattern is responsible for more output quality improvement than anything else in this article.
Use XML tags for complex prompts
Real power users write structured prompts with XML tags, explicit output formats, and domain-specific context.
<context>
[background on the situation]
</context>
<task>
[what you want produced]
</task>
<constraints>
[format, length, tone, what to avoid]
</constraints>
<examples>
[one or two samples of what good looks like]
</examples>
Claude processes each section cleanly. Output consistency goes up significantly.
Give Claude a role and a reason
Providing context or motivation behind your instructions helps Claude better understand your goals and deliver more targeted responses. Claude is smart enough to generalize from the explanation.
“You are a senior financial analyst. I need this to help a non-technical founder understand their burn rate. Prioritize clarity over precision.” That framing produces a completely different output than “summarize this spreadsheet.”
Build skills for repeatable workflows
Every time you re-explain your preferences in a new session, you are paying a tax.
Skills fix this. A skill is a saved, reusable workflow that Claude triggers automatically when the context matches. You teach it once. It runs every time. No more repeating your newsletter format, your writing rules, or your output structure in every conversation.
This is the direct application of context engineering, which has replaced prompt engineering as the real leverage point in 2026. The model is rarely the bottleneck. Context almost always is.
Interview Claude before asking it to produce
For larger or ambiguous tasks, have Claude interview you first. Start with a minimal prompt and ask Claude to interview you. Claude asks about things you might not have considered, including implementation details, edge cases, and tradeoffs.
This works for anything. An article. A strategy doc. A system you want to design. An agent you want to build. Claude asking you questions first consistently produces better final outputs than jumping straight to production.
Make AI take the work seriously
There is a specific prompting technique for tasks where you need Claude to reason carefully rather than produce quickly. You tell it the stakes. You tell it who will see this. You tell it what failure looks like.
Making AI take the work seriously is one of the most underrated shifts in how people use Claude. The model responds to framing. Give it a reason to care.
Part 3: Cowork hacks most people miss
Claude Cowork triggered a $285 billion software selloff when it launched. The gap between people using it well and people using it like a chatbot is real and growing.
Use outcome-based descriptions
Cowork works best with outcome-oriented descriptions rather than step-by-step instructions. Instead of “open this file, then copy column B, then...” try “Analyze this spreadsheet and produce a Word report summarizing spending by category, with an executive summary and a table of the top 5 expenses.”
Claude plans the work. You review. You approve or redirect. It executes.
Process files in parallel
Processing 10 files in parallel instead of one-by-one turns a roughly 30-minute wait into about 4 minutes.
Frame the task to make the parallelism obvious: “Process each of these 10 files and produce a separate one-page summary for each one.” Cowork’s sub-agents handle the rest.
Set recurring tasks and walk away
Scheduled tasks let you describe a recurring job once, then have Cowork run it automatically on a cadence, as long as your computer is awake.
Friday file cleanup. Weekly expense report. Morning inbox triage. Meeting prep the night before. Set them once. The same principles behind making Claude Code your chief of staff apply directly here.
Stack connectors for cross-app workflows
The real power is when multiple connectors work together. If your team takes meeting notes in Notion but auto-generates transcripts in Google Drive, you can tell Cowork to check the transcript against the notes in Notion and surface commitments that did not make it into the notes.
Add Slack. Google Drive. Notion. Gmail. Calendar. Microsoft 365. Each connection multiplies the value of every other one.
Use Projects to stop context bleeding
Every Cowork workstream deserves its own Project. Its own instructions. Its own files. Its own memory.
Without Projects, Claude carries assumptions from your marketing work into your financial analysis. With Projects, each context is clean and contained. This is the single most underused Cowork feature among people who have been using it for months.
Use Dispatch to control it from your phone
Dispatch creates a persistent connection between Claude mobile and your desktop. Pair once with a QR code. Send tasks from anywhere while your computer does the work.
Queue tasks from bed in the morning. Walk into finished deliverables. That is the practical version of the Claude SEO agency workflow and the slide-making system we have covered in depth. Both run unattended once queued.
Part 4: Context tricks that change how Claude reasons
A Claude session at 90% context usage is not just slower. It is producing worse outputs. Important instructions get buried. The model starts making mistakes it would not make with a clean window.
Most people blame the model when this happens. It is almost always a context problem.
Start fresh for every new topic
When you start a new conversation, Claude performs at its best because it does not have all the added complexity of processing previous context. As conversations get longer, performance goes down. Start a new conversation for every new topic, or whenever performance starts to drop.
Counterintuitive. Worth internalizing.
Write a handoff document before starting fresh
When you are mid-task and need a new session:
Summarize what we have done, what worked, what the next
step is, and any decisions made. Write it so that a fresh
Claude with no prior context can pick up exactly where
we left off and finish the task.
Save the handoff to your PROJECTS/ folder. Load it at the start of the next session. Clean context. Full continuity.
Tell Claude the context it is operating in
Claude performs differently depending on whether it knows it is inside a Cowork session, a Claude Code agent, or a standard chat. Tell it explicitly at the start of complex tasks. “You are working inside a Cowork session with access to the PROJECTS/ folder. The session has persistent file access. Save all outputs to CLAUDE OUTPUTS/.”
That one paragraph removes a class of errors most people encounter.
Use context engineering, not just prompting
The techniques that worked in 2024 now actively hurt results in some cases. The model has changed. The leverage point has shifted from what you say to what you load. System prompts. Files. Memory. Examples. The structure around the task matters more than the wording of the task itself.
Part 5: Four Claude use cases worth going deeper on
Investing
Claude for investing has a four-level system that most people using it for stock research have never seen. Level one is search-engine-style questions. Level four is running institutional-grade research workflows with structured prompts, multi-source synthesis, and copy-paste prompts for hedge fund-style stock analysis. Most retail investors using AI are at level one. The gap to level four is mostly just knowing the framework.
Content creation
The prompt that drives 3 million weekly views is one prompt. The full content workflow using Claude and the AI Corner system is not complicated. It is just structured. Voice profile, anti-AI file, output templates, and a prompting loop that produces content that sounds like a person wrote it.
Building agents
Most people have no idea how to actually build an agent. The architecture behind agents that work without failing silently is in Stop Blaming the Model. Fix the Architecture. The Karpathy case study on letting an agent tune code autonomously for two days shows what this looks like at the frontier. Claude Managed Agents is the fastest way to go from idea to production deployment right now.
Revenue
The agency owner case study on using Claude Code to build an agent pipeline that replaced the proposal writing process entirely is the clearest example of what this looks like as a business model. The delta between consultants charging $500/month and $50,000 is mostly workflow architecture, not skill.
The one shift that ties all of this together
Most people are still using Claude the way they used ChatGPT in 2023.
One-off prompts. No structure. No memory. No context. Starting from zero every session.
Prompting is no longer about clever wording. The people pulling ahead are building systems. Files that load automatically. Skills that trigger when needed. Workflows that run while they sleep. Agents that handle the repeatable work so they can focus on the irreplaceable parts.
The tools are all there. Everything Anthropic has shipped in 2026 points in one direction: the gap between users who treat Claude as infrastructure and users who treat it as a chatbot is getting wider every month.
The setup described in this article takes a weekend to build properly. The compounding starts immediately after.
FAQ Section
Frequently asked questions about Claude in 2026
What is the single most impactful thing you can do to improve Claude outputs?
Build a persistent context system before you prompt for anything. This means creating at minimum three files: an identity file telling Claude who you are and what you are working on, a voice profile capturing how you think and write, and an anti-AI-writing file listing the words, structures, and tones Claude should never use when writing as you. Load these automatically through Global Instructions in Cowork settings. The improvement in output quality from this setup alone is larger than switching models.
What is context engineering and why does it matter more than prompting in 2026?
Context engineering is the practice of structuring everything Claude receives before and during a task, including system prompts, files, memory, examples, role framing, and constraints, rather than focusing on the exact wording of individual prompts. In 2026, model quality has improved to the point where the structure around a task matters more than how cleverly the task is phrased. Prompting technique is still relevant. Context architecture is what separates users getting consistently strong outputs from users getting inconsistent ones.
How do Claude Skills work and when should you build one?
A Claude Skill is a saved, reusable workflow Claude triggers automatically when the context matches. You teach Claude how to perform a task well once, refine the output until it meets your standard, then save that process as a skill. After that, Claude applies it consistently without you re-explaining preferences each session. Build a skill for any task you do more than once a week with consistent output requirements: content formats, code review patterns, research synthesis structures, slide templates, outreach writing, and anything else that follows a repeatable pattern.
What is Socratic prompting and how do you use it with Claude?
Socratic prompting means asking Claude what questions it would need answered to do a task well, rather than telling it directly what to produce. The basic structure is: “I want to [TASK] so that [SUCCESS CRITERIA]. Ask me questions before you execute.” Claude generates a form of clarifying questions, you answer them, Claude shows you a plan, you approve or redirect, then it executes. This approach surfaces unstated assumptions, eliminates the most common failure modes in long outputs, and produces better results than jumping straight to production on any task with meaningful complexity.
What is the difference between Claude Chat, Claude Cowork, and Claude Code?
Claude Chat is the standard conversation interface, best for quick questions, feedback, and short-form tasks. Claude Cowork is the desktop agent that accesses your local files directly, runs sub-agents in parallel, connects to external tools via connectors, and executes long-running tasks autonomously, including recurring scheduled work. Claude Code is the full agentic coding environment in the terminal, built for developers who want the deepest level of control over agent behavior and codebase interaction. Most people doing knowledge work get the most value from Cowork. Most developers building products get the most value from Claude Code. Many serious users run both depending on the task.
How do you stop Claude outputs from sounding like AI?
Three things together fix this almost completely. First, build a voice profile through a Claude interview that captures your beliefs, writing mechanics, sentence rhythm, and contrarian takes. Second, build an anti-AI-writing file that explicitly bans the words, structures, and tones you reject. Third, use Socratic prompting to make Claude ask you questions before writing, so the output reflects your actual thinking rather than a generic synthesis. The full system for this is covered in our piece on making AI writing sound human.
What are the best Claude Cowork workflows for saving time?
The highest-impact Cowork patterns are: outcome-based task descriptions rather than step-by-step instructions, parallel file processing across sub-agents for batch work, scheduled recurring tasks for weekly repeatable jobs like expense reports and inbox triage, stacked connectors for cross-app workflows pulling from Slack, Notion, Google Drive, and Gmail simultaneously, separate Projects for each workstream to prevent context bleeding, and Dispatch to queue tasks remotely from your phone while your computer executes them overnight.
When should you start a new Claude session instead of continuing an existing one?
Start a new session for every new topic, whenever output quality starts dropping, or whenever a task has no meaningful dependency on earlier context in the same conversation. A Claude session at high context usage produces worse outputs because important instructions get buried and earlier context degrades the model’s focus. The practical fix is to ask Claude to write a handoff document summarizing what was done, what worked, and what the next step is before starting fresh. Save that handoff to your PROJECTS/ folder and load it at the start of the new session. You get clean context without losing continuity.
How do Claude connectors work and which ones are worth adding?
Claude connectors plug Claude directly into apps you already use, giving it read access to your actual data rather than requiring uploads or screenshots. The highest-value connectors for most knowledge workers are Slack for message search and channel reading, Google Drive for document access, Notion for page referencing, Gmail for inbox access, and Calendar for meeting context. Microsoft 365 is the most powerful single connector for enterprise users, giving Claude access to Outlook, SharePoint, OneDrive, and the full M365 suite. Add them through Settings → Connectors → Browse → Add. Each connector multiplies the value of every other one when used in cross-app workflows.
What is Claude Projects and why does it matter for Cowork users?
Claude Projects are isolated workspaces inside Cowork, each with their own instructions, files, scheduled tasks, and memory. Without Projects, every Cowork session shares the same context, so assumptions from one type of work bleed into another. With Projects, each workstream is clean and contained. A marketing project has no awareness of your financial analysis project. This is one of the most underused features among regular Cowork users and one of the highest-leverage configuration changes available.
How do you use Claude for investing and stock research?
Using Claude for investing follows a progression from basic to institutional-grade. At the entry level, Claude answers factual questions about companies and markets. At the intermediate level, it synthesizes multiple sources into structured research briefs. At the advanced level, it runs structured research workflows using copy-paste prompts designed to replicate the output of professional equity analysts, including competitive positioning, risk factor analysis, management credibility assessment, and scenario modeling. The four-level system for Claude investing and the specific prompts for hedge fund-style stock research cover this in full.
What is the best way to use Claude for content creation at scale?
The system that works at scale combines four elements: a voice profile file that captures your writing identity, an anti-AI-writing file that enforces your standards, a content template file with proven formats to reference, and a prompting loop that starts with Claude asking you questions before it writes anything. Claude generates the structure, you fill in the thinking, Claude produces the draft, you refine. The output sounds like a person wrote it because it is built from your actual perspective rather than a generic synthesis. This approach scales from single LinkedIn posts to full newsletter issues without the output quality collapsing.
Great Ruben! I agree with your suggested approach to Claude and I'd like you could add the cloud option. How could one work with Claude Code from there with GitHub and other cloud-based services, instead of one's own laptop? Is it feasible?
Strong article! : )