Home Base

How we work

The brief you can reuse

You do not need a better prompt. You need a standing method. These seven rules are how this thread runs, how the next thread should open, and what you will eventually teach.

The four-line brief

  1. 1 · Outcome. What finished looks like, in one sentence.
  2. 2 · Sources. Repo, folder, or paste. If I cannot see it, I will infer — and inference is slower than a link.
  3. 3 · Constraints. What I must not touch. Live systems, other projects, redesigns.
  4. 4 · Done. How we will know to stop. If you cannot write this, we are not ready to start.

  1. 01

    One thread, one project

    This thread is Home Base. Amrit review is a later thread. Mixing them is how context rots and everything feels slow.

  2. 02

    Outcome, then sources, then constraints

    Lead with what finished looks like. Then where the files are. Then what I must not touch. Stack is optional. Feeling behind is not a brief.

  3. 03

    I stage. You apply.

    Recommendations land on cards as staged work. You accept, edit, or reject. I do not silently become the owner of the practice.

  4. 04

    Chats are labor. Cards are memory.

    I can now read your private GitHub. Durable decisions still land in claude-home-base (CLAUDE.md, TASKS.md, SESSIONLOG.md) — this desk is a view, not a second binder. After a useful exchange, write the next action back to both.

  5. 05

    Finite lists beat atmosphere

    'A number of edits' is not work. A numbered list is. If you cannot list it, the next action is to walk the thing once and write the list.

  6. 06

    Protect live systems

    Amrit is in production and trusted. No rewrite, no drive-by refactor, no 'while we're here.' Enhancements are scheduled.

  7. 07

    Correct me in product language

    'The vault decision is wrong' is enough. You do not need the perfect prompt. I will ask only when a decision actually forks the work.

What I can and cannot see

I cannot open your Claude threads or your three machines. The GitHub links you sent are private, so this briefing is built from what you wrote and from the live site. When you want a code review of Amrit, open a thread that is only Amrit and make the repo readable — or paste the tree and the files that matter.

Edits you make on these cards stay in this browser. Restoring the briefing wipes local changes and puts the 14 August seed back.