---
id: "concept-claude-projects"
type: "concept"
source_timestamps: ["00:00:38"]
tags: ["claude", "knowledge-management"]
related: ["concept-claude-skills", "claim-vending-machine-usage"]
definition: "Static workspaces in Claude designed to hold reference material, brand assets, and context, defining 'where' you work."
---
# Claude Projects

## Definition

A **Claude Project** is a persistent workspace inside [[entity-claude]] that stores reference material — knowledge files, past successful work, brand voice guidelines, target audience profiles. Projects answer the question *where do I work and what context should Claude always have here?*

## Projects vs. Skills

| Dimension | [[concept-claude-projects]] | [[concept-claude-skills]] |
|-----------|------|--------|
| Holds | Knowledge & context | Instructions & processes |
| Answers | *Where* and *who* | *How* |
| Mobility | Stays in one place | Travels across chats |
| Example | Brand bible, past scripts | `/hook-generator`, `/thumbnail` |

## The combined workflow

Alex's recommended pattern is to operate **inside a Project** (so Claude knows who you are and what you're building) and **deploy Skills within that Project** (so Claude knows how to execute specific tasks against that context). This combination is what dissolves the "vending machine" failure mode described in [[claim-vending-machine-usage]] and [[contrarian-vending-machine]].

## Prerequisite

This video assumes prior fluency with Projects — see [[prereq-claude-projects-knowledge]].

## Caveat (from enrichment)

The "where vs. how" framing is not Anthropic's official taxonomy, but it cleanly maps how Projects and Skills are typically used. Anthropic's public communication confirms that Projects are persistent workspaces with attached documents and long-lived context, and that Skills are reusable, process-oriented instructions invoked inside them.