| name | claudr |
| description | Alan's Claude environment — skills, commands, conventions, and the clawdrs/clawdr project. Use this skill when working with Claude tooling (skills, commands, CLAUDE.md files), when the user asks about Claude setup or workflow, when about to suggest a Claude command or skill the user may have forgotten, or when working in /opt/clones/github/jalanb/clawdrs/.
|
claudr — How We Do Claude Round Here
The clawdrs/clawdr Project
Development home for Alan's Claude skills and commands:
/opt/clones/github/jalanb/clawdrs/clawdr/
GitHub is source of truth. ~/.claude/ is production.
just pull <skill>
just push <skill>
just push-skills
Skills live in skills/<name>/src/SKILL.md.
Each skill has its own justfile with pull and push targets.
When editing a skill: edit in clawdrs/clawdr/skills/<name>/src/, then just pull.
Skills
Deployed to ~/.claude/skills/:
| Skill | Purpose |
|---|
bashr | Alan's bash/shell vocabulary — read before suggesting shell commands |
claudr | This skill — how Claude works for Alan |
iterm3 | iTerm2 workspace management |
barium | Barium histogram |
cutter | New Python project scaffolding |
design-an-interface | Parallel interface design exploration |
grill-me | Interview/stress-test a plan |
local-standards | Local coding standards |
In development only (not yet deployed): smbc — SMBC bank work context.
Commands
Slash commands in ~/.claude/commands/ — easy to forget, worth hinting at:
| Command | When to hint |
|---|
/chatpoint | Before a long session that might compact |
/clclean | CLAUDE.md is getting bloated |
/clones | User asks about local repo state |
/deep-init | Entering a new project for the first time |
/diskclean | Disk space concern |
/g | Git operations |
/group-commits | Many uncommitted changes need organising |
/mytube | YouTube URL appears |
/oldies | Old project needs updating |
/read-hubs | Hub files may have changed |
/recent | User asks what was changed recently |
/related | User asks about related local projects |
/rtfc | User asks how Claude Code works |
/wwid | User asks what they were working on |
Session Patterns
Advisory vs Executive
When Alan says "just advise", "I'm working in another session", or "don't write":
- Read-only only. No file edits, no shell writes.
- Show text; let Alan copy/paste into the active session.
- Say this upfront so both sides stay aligned.
Cross-session caution
Conclusions from "the other session said..." can carry misinterpretations.
Verify against source before acting on them.
Plan hygiene
Plans capture non-obvious decisions and their why.
Do not document absences ("we decided not to do X") — that's self-evident.
Do not let ephemeral chat reasoning accumulate into plan files.
Key Paths
| Path | What |
|---|
~/.claude/ | Production Claude config |
~/.claude/skills/ | Deployed skills |
~/.claude/commands/ | Slash commands |
~/.claude/plans/ | Active plans |
~/.claude/rules/ | Always-on rules (python.md, etc.) |
/opt/clones/github/jalanb/clawdrs/clawdr/ | Skills/commands development root |
