If you’ve been using Claude for a few months and you’re starting to wonder “is there more to this?”, the answer is yes. A lot more. And none of it requires you to be a developer.
Most people discover Claude the same way. They type a question, get an answer, and think that’s the whole tool. It’s not. Claude has a layer of customization most casual users never find, and once you find it, you don’t go back to the basic version.
This post walks you through four features that change how Claude works for you: Projects, Custom Styles, Memory, and what I call building a working instruction set. None of these require code. They require clarity about what you need and about 30 minutes of your time.
Let’s get into how to build Claude Skills.
What “Build Claude Skills” Actually Means
Before we go further, I want to clear something up. When people say “Claude skills,” they usually mean one of two things: either the ability to use Claude well (prompting skills), or the ability to configure Claude so it works the way you need it to (customization skills).
This post is about the second kind. Specifically, how to set up Claude so it already knows things about you, your business, your voice, and your preferences before you type a single word in a new conversation.
Think of it like briefing a new assistant before their first day. You don’t want to explain your business from scratch every time you need help. You want them to already know the basics.
That’s what these features do.
Step 1: Set Up a Claude Project
Projects are the foundation. If you’re not using them, you’re starting over every single time you open Claude, and that’s a waste.
A Project is a dedicated workspace inside Claude where you can store instructions, background information, and documents that Claude reads before every conversation in that Project. You can have multiple Projects for different areas of your business or life.
How to create one:
1. In Claude, look for “Projects” in the left sidebar
2. Click “New Project”
3. Give it a name that’s clear to you (Client Work, Content Creation, Email Drafts, whatever fits)
4. You’ll see a section called “Project Instructions” — this is where the real work happens
What to put in Project Instructions:
This is where you write a plain-language briefing for Claude. Don’t overthink it. Write it the same way you’d explain things to a new contractor. Here’s a starting framework:
You are helping [your name] with [what you do].
About me:
- I [describe your work in one sentence]
- My clients are [describe your clients]
- My tone is [describe how you communicate]
When writing for me:
- [list 3-5 rules about your voice or style]
- [anything you want Claude to always do]
- [anything you want Claude to never do]
The more specific you are, the better Claude performs. Vague instructions produce vague results.
A real example:
Instead of writing “write in a friendly tone,” write “write conversationally, like you’re talking to a small business owner who is smart but not technical. Don’t use jargon. Don’t be overly formal. Get to the point.”
That specificity is what makes the difference between Claude sounding like you and Claude sounding like every other AI output on the internet.
Step 2: Upload Reference Documents to Your Project
Projects let you upload files Claude can reference in every conversation. This is where things get genuinely useful.
If you have a services page, a bio, a brand guide, a list of FAQs, or any document that explains who you are and what you do, upload it. Claude will read it and use it without you having to paste it in every time.
What’s worth uploading:
A document describing your business, services, and clients
- Your pricing or package descriptions
- Sample content that represents your voice
- A list of topics you do and don’t cover
- Anything you find yourself explaining repeatedly to Claude
Format doesn’t have to be perfect. A plain text document works fine. A Word doc works. A PDF works. You don’t need to clean it up or make it look professional. Claude is reading it for information, not grading your formatting.
Keep your documents reasonably concise. Long, sprawling documents where important information is buried on page 12 are less useful than focused documents organized around what Claude actually needs to know.
Step 3: Create a Custom Style
Claude’s Custom Styles feature lets you define how Claude writes. This is separate from your Project Instructions, and it lives in your general Claude settings rather than inside a specific Project.
Think of a Style as your writing fingerprint. You can create one based on samples of your own writing, or you can describe your style preferences and Claude will follow them.
How to set it up:
- Go to Claude settings
- Look for “Styles” or “Custom Styles”
- You can either paste in samples of your writing (3-5 examples works well) or describe your style in plain language
Describing your style:
If you write the description yourself rather than feeding in samples, be specific about what you want and don’t want. A few things worth defining:
- Sentence length (short and punchy? Longer and more conversational?)
- Formality level (casual, professional, somewhere in between?)
- What to avoid (jargon, filler phrases, passive voice, certain words or phrases you hate)
- Structural preferences (do you like bullet lists or prose? Subheadings or flowing paragraphs?)
You can also specify things Claude should never do. If you hate the phrase “it’s worth noting,” put that in there. If you never use exclamation points, say so.
These details matter because they’re the difference between content that sounds like you and content that sounds like Claude trying to sound like you.
Step 4: Build a Working Instruction Set
This is the step most people skip, and it’s the one that separates people who get consistent results from Claude from people who get inconsistent results.
A working instruction set is a document you create and refine over time that tells Claude exactly how you want it to behave. You paste it (or upload it) into your Project Instructions, and you update it as you learn what works and what doesn’t.
It doesn’t have to be fancy. It can be a simple text document you keep in a Google Doc or Notion page.
What goes in it:
Start with the basics and add from there.
Who you are and what you do. Two to three sentences. Your name, your business, who you serve.
Your voice rules. List the specific things that make your writing sound like you. Include phrases you hate and phrases you use often. Be specific.
Task instructions. If you use Claude for the same types of tasks repeatedly (writing emails, drafting blog posts, creating social content), write instructions for each one. What format do you want? What length? What should Claude always include or always skip?
What Claude should never do. This matters as much as the positive instructions. If Claude keeps doing something that annoys you, document it here so it stops.
An example structure:
ABOUT ME
[2-3 sentences about your work and clients]
MY VOICE
- Write conversationally, not formally
- Use short paragraphs
- Never use [list phrases you hate]
- Always [list things you want consistently]
BLOG POSTS
- Aim for [length]
- Include [structural elements you want]
- My primary audience is [describe them]
EMAILS
- Keep them under [word count]
- [Tone guidelines specific to email]
NEVER DO
- [List anything Claude does that you don't want]The first version doesn’t have to be perfect. Write what you know, use Claude for a week, notice what keeps going wrong, and update the document. Within a month, you’ll have a solid instruction set that makes Claude dramatically more useful.
Step 5: Understand How Memory Works
Claude’s Memory feature is different from Projects and Styles. Memory is Claude’s ability to remember things about you across conversations, even outside of a specific Project.
When memory is turned on, Claude can store things it learns about you and reference them in future conversations. You can also tell Claude to remember something specific: “Remember that I prefer short paragraphs” or “Remember that my business name is [name].”
A few practical things to know:
Memory updates periodically, so something you tell Claude today might not show up immediately in a new conversation. It’s not instant syncing.
You can view and edit your memories in Claude’s settings. If something got stored incorrectly, you can fix it or delete it. You’re in control of what stays.
Memory works best for stable facts about you — your name, your business, your general preferences. It’s less reliable for nuanced or frequently changing instructions. Those belong in your Project Instructions, where you have more direct control.
Don’t rely on Memory alone to carry important instructions. Use it as a layer that supports your Project Instructions, not as a replacement for them.
Putting It All Together
Here’s the practical sequence if you’re starting from scratch:
First, create a Project for your primary work area. Write a basic instruction set in the Project Instructions — even a rough one is better than nothing. Upload any relevant documents you have about your business.
Second, set up a Custom Style using either writing samples or a written description of your voice.
Third, turn on Memory if it isn’t already, and tell Claude the most important basics about you and your work.
Fourth, use Claude for real work for a week. Notice what keeps working, what keeps failing, and what you keep having to correct. Take those notes and update your Project Instructions.
That’s the whole system. There’s no magic to it. It’s just being deliberate about setup instead of hoping Claude figures you out on its own.
What This Actually Changes
When your setup is working, Claude stops feeling like a generic tool and starts feeling like something that understands your context. You stop spending the first paragraph of every conversation re-explaining who you are. You stop rewriting AI output because it doesn’t sound like you.
The people who get the most out of Claude aren’t necessarily the most technical. They’re the most specific. They took the time to document what they need, built that into their settings, and refined it over time.
You can do that without writing a single line of code.
Frequently Asked Questions
Do I need a paid Claude plan to use Projects and Styles?
Some features require a paid plan. Projects, Custom Styles, and extended memory are generally available on Claude Pro. The free plan has more limited access to these features, so if you’re serious about using Claude for your business, the paid plan is worth it.
How long should my Project Instructions be?
Long enough to cover the essential context, short enough that nothing important gets buried. For most people, 200 to 500 words covers the basics well. You can always add more as you learn what Claude needs to know.
Can I have different instructions for different types of work?
Yes, that’s exactly what multiple Projects are for. You could have one Project for client work, one for your own content, one for email drafting. Each has its own instructions and can have its own uploaded documents.
What if Claude still doesn’t follow my instructions consistently?
A few common reasons: instructions are too vague, there are too many instructions competing with each other, or the instruction is in memory rather than in your Project (where it has stronger influence). Try rewriting vague instructions with more specificity and move your most important rules into Project Instructions.
Do uploaded documents expire?
They stay in your Project until you remove them. You’re in control of what’s there and can update documents as your business changes.
Want Help Setting This Up?
If you’ve read this and thought “I understand the concept but I’d rather have someone walk me through my specific situation,” that’s exactly what I do.
I work with small business owners, authors, and coaches who want to use AI tools without wasting time on trial and error. We look at your actual workflow, figure out what setup makes sense for you, and build it together. Let’s do this thing!
