> ## Documentation Index
> Fetch the complete documentation index at: https://elrolio.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Three whiteboards of my own setup

> My AI group chat tried Claude's new whiteboards on our own setups. The tool routing board was the useful one, for checking my routing against the mental model I had.

## The Problem

Anthropic released a whiteboards feature for Claude, and in my AI group chat we were asking whether anybody had played with it yet or made any visualizations. One person said it is really good for looking at the architecture of a system: an actual program, or how your own working environment is set up. So we all decided to do quick overviews of our systems.

## The Approach

I gave Claude one line: use the whiteboard feature to map my skills architecture. It read my skills folder, my chain recipes and my written rules, and drew the first board. Then I asked for the hooks and usage counts on it, and asked Claude to look at the board itself and review it before I shared it with the group.

After that I asked for more: the tool routing as a map, and the chains of skills and hooks. Claude made those as two fresh boards and linked all three together.

## What Happened

The first board reads left to right: the ways a skill starts, my 89 skills, which Claude sorted into eight jobs of its own choosing, what they call on, and a loop underneath for how a lesson from one session is reloaded the next time the skill runs. Claude had written it without ever rendering it. When I asked it to look, it opened the board in Chrome, took a screenshot, and found skill names like de-llmification and portfolio-narrative split mid-word across lines. It fixed those, and only then called the board ready to share.

![Whiteboard of the skills architecture: four ways a skill starts, 89 skills in eight job groups with run counts, what skills use, the learning loop, and hooks by when they fire](https://mintcdn.com/elrolio/U0AGtJFJcfHUeJnl/images/journal/whiteboards-skills-architecture.png?fit=max\&auto=format\&n=U0AGtJFJcfHUeJnl\&q=85\&s=84530d90ce1dc0abcbce16abac6b5e2d)

The skills architecture board. Click to expand.

[Open the skills architecture board full size](https://elrolio.mintlify.site/images/journal/whiteboards-skills-architecture.png)

The usage counts came from a log one of my hooks writes. Between August 1 and November 9, two skills account for 190 of the 263 runs it logged for those 89 skills. The chains board showed the same gap between what is set up and what actually runs: of the eleven chains in my recipes file, three showed up in session logs from August to September.

![Whiteboard of skill and hook chains: one session's hook timeline, three measured chains and eight designed chains](https://mintcdn.com/elrolio/U0AGtJFJcfHUeJnl/images/journal/whiteboards-skill-hook-chains.png?fit=max\&auto=format\&n=U0AGtJFJcfHUeJnl\&q=85\&s=bec0017302c680fb8a83612464d72578)

The skill and hook chains board. Click to expand.

[Open the chains board full size](https://elrolio.mintlify.site/images/journal/whiteboards-skill-hook-chains.png)

The third board is the one I thought was really useful. It lays out my tool routing as rows: the need, the first tool to reach for, and the fallback, in five groups, with three rules that apply to every route in a box at the end. It was useful for understanding my tool routing against the mental model I had.

![Whiteboard of tool routing: 24 routes in five groups, each a need, a first tool and a fallback, plus three standing rules](https://mintcdn.com/elrolio/U0AGtJFJcfHUeJnl/images/journal/whiteboards-tool-routing.png?fit=max\&auto=format\&n=U0AGtJFJcfHUeJnl\&q=85\&s=d47c7adc1693b73efe739d628e716101)

The tool routing board. Click to expand.

[Open the tool routing board full size](https://elrolio.mintlify.site/images/journal/whiteboards-tool-routing.png)

## What I Learned

Mostly this is a demo of the whiteboard feature. The realization is that it can be useful to see how you actually use things compared to what you set up. It is even more useful when you have top-level rules built into your setup. You get used to talking about them, and you modify them over time. A visual overview every so often is a way to make sure the setup still matches the mental model you want.

***

*Drafted by my Claude from our working session. I edited and approved it.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.