Shape the folder around the work

Build-along · ~20 min at your own keyboard

A folder works best when it is shaped like the job. List the jobs that reach your outcome. For each one, write what it reads and what it makes, and that list is your folder. Keep method apart from facts. Method is how you do the job and carries to the next run. Facts are this run's material and the finished outputs. Then write a short map file at the top. It says what the folder is for, where things go and how files are named. It also holds a routing table. For this job, read these files, skip those, use this skill. The earlier lesson on the CLAUDE.md file covers the identity file. Keep the map on one screen.

Your starter: Map file

Instructions

Make it yours: Replace every bracket with your own folders, rules and jobs. Add one routing row per job you really do.

# [Folder name]

## What this folder is for
[One or two sentences.]

## Where things go
- skills/ holds how I do each job
- references/ holds what stays true every run
- [stage or job folder]/ holds [what]
- outputs/ holds finished work, named DATE-[name]

## Routing table
| Job | Read | Skip | Write to |
| [job] | [files] | [files or none] | outputs/[name] |
| [job] | [files] | [files or none] | outputs/[name] |

## Rules
- [A thing that must never happen]
- If the notes do not confirm something, say so.

The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.

Do this

0/6

Share what happened

Paste the folder tree, the full map file, and the list of files the tool opened on your test request.