Scattered to Shipped

A page shipped to a design team to walk them onto four tools, with the argument made before any tool is named. Two problems open it. Where's that thing again? The knowledge is good, we just can't find it, shown as a knot of tool chips that untangles as you hover. Then every chat starts from zero: the AI has amnesia, and you are its memory.

Then three numbered acts, each a tool, each demonstrated rather than described.

Where it lives. A shared markdown vault for the whole team, every link, meeting note, prototype, decision, PRD and research finding in one place, reachable over MCP from wherever you work. It feeds itself from the team's conversations and meeting notes. The page hands you three lines for the top of an agent's instructions, so it reads the vault first:

Your knowledge source is a vault reachable over MCP.
On every session start:
1. Load the vault context
2. Read the README at the root of the vault
3. Return a summary of what you found before doing anything else

Plug in. A wizard that runs inside a chat installs git, SSH and the vault client, so the shared brain and the team's repos are a few clicks away. The more people plugged in, the better the shared brain gets.

Build. An interview analyzer that runs locally on your own keys, so it is private, and the team's design system inside a design tool, built on the real frontend components and tokens, so what comes out already looks like the product.

Always shipping, never done. A changelog that keeps scrolling, because what lands next is decided by what people flag.

It ends on an ask rather than a recap. Go build. Try to break it. Then tell me what sucked, because every rough edge you hit makes the next version better.

The page itself is not here, because it names the team's tools and shows their product. What transfers is the shape: problem before tool, demonstration before description, and an ask instead of a summary. It was generated from a skill whose first instruction is not to build yet.