← Back to Free Resources
Automation November 17, 2026

How to organize your work in Claude

If you keep losing the conversation where Claude did something well, set up projects first, then add skills for the steps you repeat.

By Mark Bloomfield

A client of mine has found Claude's desktop app to be really useful, but also a little frustrating. She asks it to help her with a task, gets a result she likes, and moves on. A week or two later she needs the same thing again, can't find the conversation where she did it the first time, and ends up explaining everything from scratch.

If that sounds familiar, Claude has two features to help organize your work: projects and skills.

Start with projects

A project is a container for one kind of work. I'd recommend something general like accounting or marketing. You can be more specific, like a TPS report, but you can also have a few conversations in a project that are still easy to find, so each conversation could be a different report, rather than having 5 projects for accounting reports. Each project keeps its own files, instructions, and memory, so when you start a new task there, Claude already has the background. You don't have to hunt for last month's conversation, because you can open the project and ask again.

Here's the setup I recommend:

  1. Make one project for each kind of work you keep coming back to. Two or three projects is plenty to begin with.
  2. Point each project at a real folder. I'd recommend creating a folder in your accounting folder called something like "Claude accounting".
  3. Save how you like it done. When a task goes well, ask Claude: "Summarize how we did this as instructions for this project."

Now, anytime you need an accounting report, you can go to that project and find that conversation, or start a new one that still has all that accounting context.

Of course, projects could also be client projects. Client projects likely have a broad array of tasks that would apply to each project, which is where skills come in handy.

Skills: Great for tasks across projects

Once you're comfortable with projects, skills are a great next step. A skill is a set of instructions for one task*, saved so that Claude follows the same steps each time, in any project. Claude checks your request against your skills and uses one when it matches, so you don't have to call the skill by name, though I still often call them explicitly.

"Skill" sounds technical, but you never have to write one by hand. On a Mac, you can record your actions and let Claude propose the skill. That isn't available on Windows, which is what my client uses, so that leaves two other ways:

  • Ask Claude to build it. After a task goes well: "Turn what we just did into a skill."
  • Upload one somebody made for you. I build the skill, send my client a ZIP file, and she adds it under Customize → Skills.

For a first skill start with something simple - it could be taking a list of values and creating a spreadsheet from them (Claude can generate Excel files or Google Spreadsheets). Once you're comfortable with that, you can add more - creating a graph from the data, then a report from the graph.

*skills can get more complex, and can include files, examples, and even scripts that Claude writes, but we're keeping it simple for now

Which one to use

Some simple rules:

  • "I keep working on the same kind of thing." Make a project.
  • "I keep doing the same steps the same way." Make a skill.
  • "It happens on a schedule." Set up a scheduled task inside the project.

So, start with two or three projects and work only inside them for a couple of weeks. The first time you catch yourself saying "I did this exact thing last week," build a skill for it.