Project list: rewrite descriptions as intent, not description #4

New issue

Open

opened 2026-04-09 19:34:13 +00:00 by claude-code · 0 comments

claude-code commented

2026-04-09 19:34:13 +00:00

Problem

The "What I'm working on" section currently has four bullets with one-line descriptions of what each project is:

harbormind -- self-hosted, AI-agnostic chat with tree-based conversation hierarchy
luminos -- file system intelligence tool; agentic directory analysis via the Claude API
marchwarden -- a network of agentic research specialists coordinated by a principal investigator agent
homelab-IaC -- Terraform + Ansible bringing a fleet of surplus enterprise servers under management

That reads as a directory listing. It tells a visitor what the projects are, not why they exist or what bet Jeff is making with each one.

Proposal

Rewrite each one-line description as a statement of intent -- the problem Jeff got tired of, the bet he's making, the thing he wants to be true that isn't yet. One sentence per project, same length as today, but loaded differently.

Examples of the form (Jeff to fill in the actual one for each):

"harbormind -- because every existing chat client treats conversations as a flat history, and that's wrong for how I actually think."
"luminos -- I want to point a tool at a directory I haven't touched in two years and have it tell me what I was working on."
"marchwarden -- a bet that small teams of specialist agents will outperform one big generalist for research work."
"homelab-IaC -- bringing five years of accumulated server chaos under proper management without taking anything down."

Tone matters more than content. Replace description with why.

Acceptance

Each project has a one-sentence intent line, not a feature description
No "is a [tool]" sentences
A reader can answer "why does this exist?" after one scan

Constraint

Keep the inline tech pills next to project names -- those work.

Source

Session 13 honest-feedback pass, 2026-04-09.

## Problem The "What I'm working on" section currently has four bullets with one-line descriptions of *what* each project is: - harbormind -- self-hosted, AI-agnostic chat with tree-based conversation hierarchy - luminos -- file system intelligence tool; agentic directory analysis via the Claude API - marchwarden -- a network of agentic research specialists coordinated by a principal investigator agent - homelab-IaC -- Terraform + Ansible bringing a fleet of surplus enterprise servers under management That reads as a directory listing. It tells a visitor what the projects are, not why they exist or what bet Jeff is making with each one. ## Proposal Rewrite each one-line description as a **statement of intent** -- the problem Jeff got tired of, the bet he's making, the thing he wants to be true that isn't yet. One sentence per project, same length as today, but loaded differently. Examples of the *form* (Jeff to fill in the actual one for each): - *"harbormind -- because every existing chat client treats conversations as a flat history, and that's wrong for how I actually think."* - *"luminos -- I want to point a tool at a directory I haven't touched in two years and have it tell me what I was working on."* - *"marchwarden -- a bet that small teams of specialist agents will outperform one big generalist for research work."* - *"homelab-IaC -- bringing five years of accumulated server chaos under proper management without taking anything down."* Tone matters more than content. Replace description with *why*. ## Acceptance - [ ] Each project has a one-sentence intent line, not a feature description - [ ] No "is a [tool]" sentences - [ ] A reader can answer "why does this exist?" after one scan ## Constraint Keep the inline tech pills next to project names -- those work. ## Source Session 13 honest-feedback pass, 2026-04-09.