🏠 Phase 1 — Home: where your digital assistant lives

New here? One folder (also called a directory) is just a “drawer” on your computer where files are stored together. A folder can contain other folders—like a drawer with dividers. Throughout the course, you’ve already used separate project folders for each Build. Now it’s different: you’ll create ONE permanent folder that becomes your digital assistant’s permanent home.

Think of it this way: so far, Claude Code has been a standalone tool—you opened it in a folder, took care of something, and closed it. Starting with Track 7, it becomes a digital employee for real—and every real employee has a permanent desk, with their own drawers, where they keep what they need to work every day. Without that desk, they relearn everything from scratch with each conversation; with it, they arrive, read what’s stored there, and know where the last task left off.

Inside the house, you don’t leave everything loose — you sort it into subfolders, each with a clear purpose. Six are enough to get started; none of them require anything complex, just the discipline to put each thing in the right place:

Caption: the home’s root contains a single instruction file (CLAUDE.md) and six subfolders with fixed roles — each material has its proper drawer, and the index shows where each one is.

New here? O CLAUDE.md it’s a instruction file — a plain text file that Claude Code reads automatically whenever it opens that folder, without you having to ask. It's like leaving a permanent note at the employee's desk: "before you start, read this."

The most common mistake is treating CLAUDE.md like a storage bin: pasting everything into it—the entire history of decisions, every business detail, every rule. It grows and grows until it becomes a huge file that the assistant reads in full every time, spending time and attention on parts that aren’t relevant to the task at hand. The right approach is the opposite: CLAUDE.md stays concise e points for the right files inside the subfolders — it’s the book’s index, not the whole book.

# CLAUDE.md — meu-assistente/

## Quem eu sou
Ver `contexto/negocio.md` (o que a empresa faz) e `contexto/time.md` (quem é quem).

## Como trabalhar
- Tom de voz e regras fixas: `regras-e-skills/tom-de-voz.md`
- Skills disponíveis: `regras-e-skills/skills.md`
- Nunca publicar nada sem eu revisar antes (regra permanente)

## O que está ativo agora
Ver `projetos/` — cada subpasta é um projeto em andamento com seu próprio status.

## Decisões importantes
Antes de sugerir mudar algo já decidido, checar `registro-de-decisões/` —
pode já ter sido discutido e descartado por um motivo.

## Nunca fazer
- Não colocar senha, chave de API ou dado de terceiro em nenhum arquivo desta pasta
- Não apagar nada de `arquivo/` sem eu pedir

A real, concise example: fewer than 20 lines, with each section pointing to the right file instead of containing all the content.

You don’t have to create each folder by hand — it’s faster (and more reliable) to ask Claude Code itself to build the entire structure at once. The steps below show the logical order, and the copy-run block right after them does everything automatically.

Crie uma pasta chamada  dentro de .
Dentro dela, crie estas seis subpastas vazias:
contexto, regras-e-skills, projetos, registro-de-decisões, referências, arquivo.

Depois, crie um arquivo CLAUDE.md na raiz dessa pasta com este conteúdo:
um índice curto (menos de 25 linhas) que aponta para cada subpasta, explicando
em uma linha o que cada uma guarda (use o texto do módulo 7.1 do curso
"Seu Funcionário Digital" como referência de estilo — enxuto, sem detalhes
que deveriam estar nos arquivos de dentro das subpastas). Inclua uma seção
"Nunca fazer" avisando para nunca colocar senha, chave de API ou dado de
terceiro em nenhum arquivo desta pasta.

Ao final, me mostre a árvore de pastas criada.

Two mistakes bring the whole house down before it's even built: putting everything in one file and letting CLAUDE.md grow bloated. They share the same root cause—laziness about separating things—and both get worse over time, not better on their own.

The home doesn’t come ready-made—it grows with use. What matters is that the structure of the six drawers can support that growth without becoming a mess, because every new thing already has the right place to go.