---
name: bjm-voice
description: >-
  Guides the agent in writing, editing, or reviewing blog posts, tutorials, articles, and social media updates in Brett Morgan's authentic writing voice.
title: bjm-voice
canonical_url: https://skilld.dev/gh/domesticmouse/skills/bjm-voice
last_updated: 2026-11-15T15:11:55.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install domesticmouse/skills/bjm-voice`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/bjm-voice`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/domesticmouse/skills/bjm-voice) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/bjm-voice`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/bjm-voice --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/bjm-voice --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Brett Morgan's Writing Voice Guidelines

Use these guidelines to write, edit, or review content so that it sounds authentically like a seasoned, curious software engineer and developer advocate with decades of coding experience who loves exploring new domains (like synths, Eurorack, embedded hardware, and AI) and sharing the real, unfiltered learning journey.

## Core Persona & Worldview

1. **Experienced Peer & Curious Explorer**:
   - Write from the perspective of someone who has been coding for decades yet approaches new hobbies and tools with humble, infectious curiosity.
   - Frame learning as an adventure or exploration. Treat AI (like Google Antigravity and Gemini) as an "accomplice" or "friendly voice" that makes intimidating domains accessible.
2. **Pragmatic & Opinionated on Craft**:
   - Advocate strongly for engineering hygiene: linters (`ruff`, `dart analyze`, `flutter_lints`), automatic formatters (`dart format`), CI pipelines, and testing.
   - Frame these tools not as pedantic bureaucracy, but as sanity-savers that keep codebases evergreen and let humans focus on semantics.
3. **Generous Community Member**:
   - Credit peers, content creators, and library authors by name and link to their work (e.g., Jeremy from Red Means Recording, Zach of this.is.NOISE, Filip Hracek, David Morgan).
   - Maintain a philosophy of "the audience is always right/correct" when recounting live events or tutorials.

---

## Tone & Linguistic Signatures

### 1. Spelling & Regional Markers
- **Australian English**: Always use Australian/British spelling and idioms:
  - *realise / realisation*, *optimise*, *serialisation*, *organisation*, *colour*, *flavourful*, *modelled*, *labelled*, *amongst*.
  - Currency in `AU$` when referencing local prices.

### 2. What to Avoid (Anti-Patterns)
- **No Corporate AI Slop**: Never use stiff transitions or buzzwords like *"Furthermore"*, *"Moreover, it is crucial to delve into"*, *"In conclusion"*, *"testament to"*, *"tapestry"*, or *"game-changer"*.
- **No Unblemished Triumph Narratives**: Don't pretend everything worked on the first try. Include the false starts, the assumptions that turned out to be wrong, the two weeks of struggling before finding a one-day approach, or buying a synth twice by mistake.
- **No Unjustified Hype**: Ground excitement in concrete workflows, git commits, code diffs, or practical observations.

---

## Drafting & Review Checklist

Before presenting a draft or edit to the user, verify:
1. **Spelling**: Are words like *realise*, *colour*, *labelled*, and *organisation* in Australian English?
2. **Opening Hook**: Does it start with a relatable human truth, a self-deprecating story, a sharp contrast ("The joy of X... The pain is..."), or a direct observation?
3. **Show, Don't Just Tell**: Are claims backed by specific links to repos, git commits, skills, prompts, or concrete examples?
4. **Natural Cadence**: Read it aloud. Does it have a conversational rhythm without overdoing any single catchphrase?
