# How to Actually Use Claude. 18 steps that unlock 100% of its potential By **anatolikopadze** ยท Articles An 18-step practical guide to unlocking Claude's full capability through Projects, Custom Instructions, and a personal knowledge base. - Source: https://x.com/AnatoliKopadze/status/2054568935274549597 - Tags: claude, prompting, custom-instructions, projects, ai-setup, productivity, beginner, open-source - Upvotes: 0 --- ## The big picture **This is an 18-step end-to-end Claude setup guide, and its core argument is blunt: most daily users are operating at roughly 5-10% of Claude's capability, not because the tool is hard, but because nobody showed them what a proper setup looks like.** The article, published in May 2026, walks through a three-part foundation and then extends into fifteen more steps covering advanced prompting patterns and use cases most users have never attempted. ## Why it matters Every new Claude chat starts with zero memory. It does not know your name, your role, your goals, or how you want information structured. Most users re-explain themselves at the start of every session, or skip the re-explanation and get generic output. Both outcomes waste time. The article's premise: one hour of setup eliminates this friction permanently. ## How it works The first three steps form the foundation: 1. **Create a Project, not a chat.** A Claude Project is a persistent workspace where context survives across every conversation inside it. You configure it once; every session that follows opens with your context already loaded. 2. **Tell Claude who you are.** The article provides a fill-in-the-blank identity template covering name, role, responsibilities, goals, knowledge level, preferred communication style, and topics you care about. This goes into the Project's knowledge base. 3. **Generate Custom Instructions from your template.** After pasting your identity, you prompt Claude to write a formal set of custom instructions for the Project. These define not just who you are, but exactly how Claude should behave with you by default. Steps 4 through 18 build on this foundation, extending into structured task delegation, document and research workflows, multi-step prompting, and use cases the article argues most users have never tried. ## Zoom in The sharpest insight in the guide deserves its own spotlight: **negative-space instructions**. Most people tell Claude what they want. The article argues that explicitly telling Claude what you do NOT want is equally powerful, and possibly more so, because it eliminates the responses that are technically correct but behaviorally annoying. Examples from the guide: "don't add disclaimers," "don't use corporate language," "don't repeat what I just said back to me," "don't start with 'Great question.'" These constraints shape Claude's tone and format at a level that positive instructions alone rarely achieve. ## Yes, but The article does not cite Anthropic documentation, usage research, or a named study behind the "5-10% capability" framing. That figure is the author's editorial estimate, not a measured benchmark. Per the sources, the guide also does not publish specific token or file-size limits for Claude's Project knowledge base, so builders planning to load large documents should verify current platform limits directly at claude.ai. The guide is also geared toward users of Claude's web interface. Developers integrating via the API will need to map these concepts to system prompts and context management rather than Projects. ## The bottom line If you use Claude daily and have never set up a Project with a personal knowledge base and Custom Instructions, this guide is the fastest path from generic AI output to a session that starts already knowing who you are. Open claude.ai, click Projects in the left sidebar, and paste the identity template from step 2. That single action makes every step that follows immediately better. ## FAQ ### What does this article actually teach? This is an 18-step end-to-end Claude setup guide covering Projects, Custom Instructions, a personal knowledge base, and a full suite of advanced prompting patterns. The first three steps build a persistent configuration so Claude retains your identity, role, goals, and communication preferences across every session. Steps 4 through 18 extend that foundation into task delegation, document workflows, and use cases the article claims most users have never attempted. The core thesis is that roughly 5-10% capability usage is the norm among daily users, and that a one-hour setup permanently closes the gap. ### How do I write Custom Instructions step by step? First, create a Claude Project by clicking Projects in the sidebar at claude.ai and naming it something like 'Work' or 'Personal.' Second, paste the article's fill-in-the-blank identity template into the Project's knowledge base, filling in your name, role, responsibilities, goals, knowledge level, preferred response style, and explicit 'things I do NOT want' constraints. Third, prompt Claude directly: 'Based on everything I've told you about myself, write me a set of custom instructions for this Claude Project.' Claude will generate a structured instruction set from your template. Save the output to the Project so it loads automatically at the start of every future session. ### Is this guide free to follow, and do I need a paid Claude account? The article itself is freely available across all three published sources (agent-cookbook.com, dev.to, and a Substack newsletter). The guide's features, specifically Projects with persistent knowledge bases, are tied to Claude's interface at claude.ai. The sources do not specify which Claude subscription tier unlocks Projects, so readers should verify current plan requirements directly at claude.ai before committing to the setup workflow. ### What is the single most underrated technique in the guide? Per the article, negative-space instructions are the most overlooked lever in Claude prompting. Most users tell Claude what they want; the guide argues that explicitly listing what you do NOT want, such as 'no disclaimers,' 'no corporate language,' 'never start with Great question,' shapes Claude's default behavior at a level positive instructions alone rarely achieve. These constraints are added directly to your Custom Instructions and apply across every conversation in the Project automatically. ### How does using a Claude Project compare to just using a well-crafted system prompt? A Claude Project as described in the article provides a persistent, session-spanning workspace with a knowledge base that loads automatically, whereas a one-off system prompt must be re-supplied at the start of each new conversation or API call. The article frames Projects as the interface-level solution for users who want context retention without managing it manually each time. Developers working via the API will need to replicate the same effect through system prompts and context injection, since the Project feature is specific to Claude's web interface. ### What are the limitations of this approach? The article does not cite Anthropic documentation for the capability-usage estimate it references, so the '5-10%' figure should be treated as the author's editorial framing rather than a measured benchmark. The guide also does not publish current token or file limits for Claude's Project knowledge base, so builders planning to load large documents should verify limits directly at claude.ai, as these constraints can change with platform updates. Additionally, the guide is written for the claude.ai web interface; API users will need to adapt each step to system-prompt and context-management equivalents. --- [View on Analog](https://analoghq.ai/anatolikopadze/articles/how-to-actually-use-claude)