Process

How this portfolio is built

While building this site, Claude and I wrote hooks and skills, listed here by date. I write one once I have had to explain the same thing twice. Several fix a specific mistake.

Where hooks and skills step into a sessionA session in six steps: open, search, write a file, finish the answer, put online, close. Each step names the skill, hook or command that acts on it.Open the sessionSkillRereads the handoffSearch the projectHookRefused if nothing was readWrite a fileHookHandoff capped at 60 linesFinish the answerHookTypes and lint must passPut onlineCommandShip: checks, pushes, waitsClose the sessionSkillUpdates the handoff, publishes
  1. 3 Sep

    The handoff capHook

    The handoff is a short file that tells the next session where the project stands. It grew with every session. A hook (a script that runs automatically, here after every file write) checks its length: past 60 lines, Claude has to shorten it right away.

    Why 60? It is the compromise between best practices, Claude's documentation and measurements of how well this kind of file works as it gets longer. To fit, the handoff keeps the state of the project, not its history.

  2. 7 Sep

    ShipCommand

    Vercel publishes whatever is pushed to GitHub, so a broken push is a broken site. One command checks types, lint and the build, then commits, pushes and waits until the live pages serve the new version.

    Why wait? A page that answers proves the site is up, not that my change is live. Only the version change proves it.

  3. 9 Sep

    Check before finishingHook

    When Claude has changed files in the project, it cannot end its answer until types (data consistency across files) and lint (the code's writing rules) pass.

    Why at the end? A change often touches several files, and the code can be broken in between. So the check runs once, at the end.

  4. 9 Sep

    Opening and closing a sessionSkills

    My opening and closing instructions were loaded into every session, needed or not. They are now two skills, procedures loaded only when they are needed. Opening reads the handoff and flags what no longer matches the files. Closing updates it from the files, then commits and publishes.

    Why reread the files? Several sessions run in parallel. Rewriting the handoff from an old read would erase the others' work.

  5. 11 Sep

    MemoryRule

    Claude added a note to my memory without proposing it, in the wrong file and the wrong format. Writing to that file now needs my approval.

    Why a permission? The written instruction already existed and was not enough. A permission is enforced by the tool, it does not depend on Claude's judgment.

  6. 15 Sep

    Blind searchHook

    Each project has a guide that says where everything is. A session searched a project without reading it. Now a search is refused until Claude has read a file of the project.

    Why? On 15 September, a session started at about 61,700 tokens (the units of text Claude reads), of which 2,700 came from my files. The cost is blind searching, not file size.