The developer environment hides where dotfiles hide

dev.env and dev.env.example become .dev.env and .dev.env.example, and the five
skills that name them follow. The .gitignore rule takes the dot too; it matches
the exact name, so the example stays tracked while the real one stays out.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Opus 5 committed 2026-09-06 02:09:59 -04:00
1 parent bcf387c620
commit caac83c64a
7 files changed
+15 -15

No files matched your search

+2 -2
View File
@@ -34,8 +34,8 @@ the commonest answer to "please add this one".
1. **Classify the emoji.** Run, from the repo root:
The interpreter below is `$DEV_VENV_PYTHON` from `dev.env` at the repo root (gitignored;
`dev.env.example` shows the shape) — read it first.
The interpreter below is `$DEV_VENV_PYTHON` from `.dev.env` at the repo root (gitignored;
`.dev.env.example` shows the shape) — read it first.
```
$DEV_VENV_PYTHON .claude/skills/add-narrow-emoji/classify.py <emoji>
+2 -2
View File
@@ -15,8 +15,8 @@ stays exactly where it was, so the file's length never changes.
## Run
The interpreter below is `$DEV_VENV_PYTHON` from `dev.env` at the repo root (gitignored;
`dev.env.example` shows the shape) — read it first.
The interpreter below is `$DEV_VENV_PYTHON` from `.dev.env` at the repo root (gitignored;
`.dev.env.example` shows the shape) — read it first.
```
$DEV_VENV_PYTHON .claude/skills/fix-ans-nulls/denul.py --dry-run --width 71 meshterm/assets/splash/logo.71.ans
+2 -2
View File
@@ -14,8 +14,8 @@ on came from the real app on `/dev/tty1`.
## Reaching the device
The address, login, key and password are **not in this file**. Read `dev.env` at the
repo root first (gitignored; `dev.env.example` shows the shape) — the `$DEV_*` names
The address, login, key and password are **not in this file**. Read `.dev.env` at the
repo root first (gitignored; `.dev.env.example` shows the shape) — the `$DEV_*` names
below are its keys, and everything here is written to be run with them substituted.
`ssh -i $DEV_PICOCALC_SSH_KEY $DEV_PICOCALC_USER@$DEV_PICOCALC_HOST` (key installed;
+2 -2
View File
@@ -13,8 +13,8 @@ carrying the simulator's fingerprints and nothing else.
## Run
The interpreter below is `$DEV_VENV_PYTHON` from `dev.env` at the repo root (gitignored;
`dev.env.example` shows the shape) — read it first.
The interpreter below is `$DEV_VENV_PYTHON` from `.dev.env` at the repo root (gitignored;
`.dev.env.example` shows the shape) — read it first.
```
$DEV_VENV_PYTHON .claude/skills/purge-test-data/purge.py --dry-run
+2 -2
View File
@@ -8,8 +8,8 @@ model: haiku
## Launch
- Machine-specific values (this venv, the BLE companions below) live in `dev.env` at
the repo root — gitignored, with `dev.env.example` showing the shape. Read it first;
- Machine-specific values (this venv, the BLE companions below) live in `.dev.env` at
the repo root — gitignored, with `.dev.env.example` showing the shape. Read it first;
the `$DEV_*` names here are its keys.
- Venv interpreter: `$DEV_VENV_PYTHON`
- Run the app as a module: `python -m meshterm …` (no install step needed).
+3 -3
View File
@@ -1,12 +1,12 @@
# MeshTerm developer environment — the machine-specific half of the .claude/ skills.
#
# Copy to `dev.env` (gitignored) and fill in your own values. Nothing in here is read by
# Copy to `.dev.env` (gitignored) and fill in your own values. Nothing in here is read by
# the app: `meshterm` is configured by `config.toml` and its own `MESHTERM_*` variables.
# These are only for driving *your* hardware from a dev session, so every name is
# `DEV_`-prefixed and cannot collide with the app's.
#
# set -a; . ./dev.env; set +a # sh/bash
# Get-Content dev.env | ... # or just read the values; nothing sources it for you
# set -a; . ./.dev.env; set +a # sh/bash
# Get-Content .dev.env | ... # or just read the values; nothing sources it for you
# --- this workstation ---------------------------------------------------------------
# Full path to the venv interpreter, so a skill can run the app without an install step.
+2 -2
View File
@@ -23,8 +23,8 @@ venv/
output/
# Developer environment: the machine-specific half of the .claude/ skills (device
# addresses, logins, the local venv path). dev.env.example is tracked and shows the shape.
dev.env
# addresses, logins, the local venv path). .dev.env.example is tracked and shows the shape.
.dev.env
# Built radio firmware (scripts/xiao-radio/build-firmware.sh writes it here)
scripts/xiao-radio/*.uf2