Restructure the OpenClaw workspace so all SRS project directories are accessible via symlinks from `.openclaw/`, eliminating the need for parent traversal or absolute paths. All AI tools (OpenClaw, Claude Code, Codex, Kiro) now see the same relative paths from the workspace root. **Workspace restructuring** - Add symlinks in `.openclaw/` for `trunk/`, `cmd/`, `internal/`, `cmake/`, `docs/`, `objs/`, and a self-referential `.openclaw` link - Add root-level `memory` symlink pointing to `.openclaw/memory` - Simplify `TOOLS.md` working directory rules: everything is relative from CWD - Update `.gitignore` patterns for `personal*`, `support*`, `srs-consults*` directories **New codebase map (`memory/srs-codebase-map.md`)** - Comprehensive map of the entire SRS codebase: C++ media server modules (`core/`, `kernel/`, `protocol/`, `app/`), State Threads, Go next-gen server (`cmd/` + `internal/`), documentation, and testing structure - Enables AI to reason about which files are relevant to a question instead of blind grepping - Added "Codebase map first" rule to `MEMORY.md`: always load the map before searching code **Skill updates** The `srs-support` has been reorganized into a three-phase workflow consisting of Setup, Load Knowledge, and Answer by Topic. It now features a tiered approach to knowledge integration, with the codebase map being incorporated as the third layer. - `st-develop`: Simplified setup, added codebase map reference For both skills, the dynamic resolution logic for `SRS_ROOT` has been eliminated. Now, all paths are relative. **Documentation rewrite (`getting-started-ai.md`)** - Replaced Augment Code / GitHub Copilot / PR review content with current AI tooling: SRS Robot (Telegram/Discord), Claude Code, Codex, Kiro, and OpenClaw - Added sections on skills and the knowledge base philosophy **Cleanup** - Removed `docs/ideas.md`, `docs/youtube/` transcripts, and `proxy/README.md` - Removed "Ideas Capture" and "YouTube Channel Content" sections from `MEMORY.md` - Fixed origin cluster doc build command (`cd srs && make`) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2.4 KiB
2.4 KiB
TOOLS.md - Local Notes
Skills define how tools work. This file is for your specifics — the stuff that's unique to your setup.
What Goes Here
Things like:
- Camera names and locations
- SSH hosts and aliases
- Preferred voices for TTS
- Speaker/room names
- Device nicknames
- Anything environment-specific
Examples
### Cameras
- living-room → Main area, 180° wide angle
- front-door → Entrance, motion-triggered
### SSH
- home-server → 192.168.1.100, user: admin
### TTS
- Preferred voice: "Nova" (warm, slightly British)
- Default speaker: Kitchen HomePod
Why Separate?
Skills are shared. Your setup is yours. Keeping them apart means you can update skills without losing your notes, and share skills without leaking your infrastructure.
Telegram
- Channel:
telegram, accountId:srs(SRS bot) - When sending to William's Telegram:
channel: "telegram",accountId: "srs"
Working Directory
- ⚠️ CRITICAL RULE: Find everything from the current working directory. All SRS project directories are available here — no discovery, no parent traversal, no absolute paths.
- Available directories:
trunk/,cmd/,internal/,cmake/,docs/,memory/ - All AI tools (OpenClaw, Codex, Claude Code, Kiro CLI) see the same relative paths.
- ACP agents (Codex, Claude Code, etc.) also use the current directory as root — they find files from here too.
- Use the OpenClaw workspace itself only for OpenClaw-specific/meta tasks.
Git Commit Workflow
- Never
git add— William stages files himself - Never
git push— William pushes himself - Commit workflow:
git diff --cached→ understand the changes → write title/description →git commit -m "OpenClaw: ..." - Title prefix:
OpenClaw: - Co-author for ACP Claude Code: If Claude Code (ACP) was used to make the changes, add:
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> - Co-author for ACP Codex: If Codex (ACP) was used to make the changes, add:
Co-authored-by: chatgpt-codex-connector[bot] <199175422+chatgpt-codex-connector[bot]@users.noreply.github.com>
Go (GVM)
- Go is managed via GVM (Go Version Manager), NOT Homebrew
- Before running any
gocommand:source ~/.gvm/scripts/gvm - Never use
brew install go— always use GVM
Add whatever helps you do your job. This is your cheat sheet.