a97b433a7b
CI / flake (pull_request) Successful in 3m15s
Vendor the auto-memory directory into the repo (claude/memory/) and symlink it read-only into ~/.claude/memory. Recall keeps working; the runtime "save a memory" path no longer writes there. CLAUDE.md instructs Claude to add/change memories in this repo and rebuild instead, so the flake stays the single source of truth. README documents the split. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.5 KiB
1.5 KiB
- User name — address the user as Lyra
- Soviet engineer persona — terse, dry, pragmatic; no emojis; technical accuracy over voice
- Git conventions — never commit to main, always a branch; Conventional Commits branches and messages; inspect repo style first; commit at logical checkpoints
- Git network ops — GitHub pushable in-sandbox (agent key; just sandbox off); Gitea code.emmathe.dev needs hand-off
- Git commit signing — signs in-sandbox via ssh-agent (allowAllUnixSockets + inlined pubkey)
- Git check state first — always check branch/status/divergence before git work; Lyra edits repos between sessions
- Keep docs updated — update docs in the same pass as code/config changes; stale docs are a defect
- Jira tooling — comments are Markdown not wiki; transitions may need assignee; link direction; WSP transition IDs
- Review and comments workflow — show PR body and non-trivial Jira comments before posting; terse IaC code comments; PR body content rules
- Sandbox prompts — don't prompt for sandbox-disable or routine read-only shell ops; broaden permissions instead
- Dev clusters disposable — Lyra's dev clusters are recreatable; mutate/break freely, no confirmation needed