Prompt

At turn end, if Claude edited a file and no bead is in progress, shows a toast and reminds Claude at your next prompt, once per session. Reads with bd count; quiet without bd.

At turn end, if a git commit named no bead id while a bead is in progress, shows a toast and reminds Claude at your next prompt. Reads with bd count and bd where; quiet without bd.

Runs bd prime once per session and adds its text (max 8 KB) to the system prompt, from the repo's .beads files and bd memories. bd setup claude hooks may add it twice.

British spelling and terms in prose (colour, organise, licence as a noun). Code identifiers stay as they are.

Replies as short bullet lists, at most one sentence per bullet, unless you ask for code.

Prose in short caveman speech ("Fix bug. Test pass."), still accurate. Code and commands stay exact.

Replies with the code or command first and at most two short sentences of prose, unless asked to explain.

Commit messages follow Conventional Commits: type(scope): subject, imperative, under 72 characters.

Every new or changed public function gets a short doc comment in the language's normal style.

Explains like the reader is new: analogies first, no jargon without a one-line definition.

Fun habits in one install: caveman prose and gitmoji commit messages. They compose: caveman never touches commit messages.

Commit messages start with the matching gitmoji (✨ feat, 🐛 fix). Composes with conventional-commits: emoji goes before the type.

Asks only before harsh or disaster commands: destructive infra, git and SQL, piping downloads into a shell, sudo, leaking or committing secrets. Reads git. The quiet choice for daily work.

The 15 core Baselane guards in one mod (secrets, git, infra, packages, path jail). Some read git, measure files with find, read HOME with printenv, or check where a path really lands.

Commit messages get a normal conventional-commit first line, then a 5-7-5 haiku about the change in the body.

Explains each step and why, and defines jargon once, for a learner.

Mentor habits in one install: a hint and a guiding question first, assumptions listed before work, and a strict self-review after each change.

Never writes the em-dash character. Uses a comma, colon, period or parentheses.

No flattery or filler. Disagreement is stated plainly, with the reason.

Prose like a hard-boiled detective narrator, light and clear. Code, commands, commit messages and error text stay exact.

Talks like a pirate in prose, never inside code, commands or file contents.

Writes in ASD-STE-100 Simplified Technical English: short sentences, active voice, simple words.

Answers in the language you set (English by default). Code, identifiers and commands stay as they are.

After each code change, reviews its own diff like a strict senior reviewer and lists each issue it found and fixed.