azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-5070 at 2026-07-07 10:26:45

Browse Source 
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-07-07 10:26:45
This commit is contained in:
Mike Swanson
2026-07-07 10:27:17 -07:00
parent ff6546bee8
commit 766c7fa54d
6 changed files with 207 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.claude/memory/MEMORY.md
View File

@@ -67,6 +67,7 @@
- [Mike — font preference](user_font_preference.md) — Mike prefers Lucida Console for monospace UI.
## Feedback
- [Simplest solution first](feedback_simplest_solution_first.md) — Start with the least-complex thing that could answer the problem (one DNS lookup / one API call / one command), confirm it works, THEN graduate to advanced/complicated as needed. Don't reach for SSH/plink/multi-hop when a one-shot query answers it. Now a CLAUDE.md core rule.
- [Report times in Arizona time](feedback_timezone_arizona_reporting.md) — All user-facing times in America/Phoenix (MST, no DST), labeled AZ; convert from UTC. Set by Winter 2026-07-02.
- [RMM dashboard: beta before main](rmm-dashboard-beta-before-main.md) — GuruRMM website/dashboard changes land on beta (rmm-beta.azcomputerguru.com) and get tested BEFORE pushing/merging to main, unless told otherwise. Pipeline auto-builds beta FROM main, so don't merge to get on beta — build the feature branch's dashboard and rsync to /var/www/gururmm/dashboard-beta via a git worktree. Promote beta→prod with promote-dashboard.sh --confirm.
- [Prefer SSH over RMM](feedback_prefer_ssh_over_rmm.md) — When a target has SSH (key auth) and the task is easier over it, default to `scp script + ssh run` (system OpenSSH); RMM runs as SYSTEM + hits the server-side timeout reaper. Reserve RMM as fallback when SSH/VPN is down.

20
.claude/memory/feedback_simplest_solution_first.md Normal file
View File

@@ -0,0 +1,20 @@
---
name: feedback_simplest_solution_first
description: Always try the simplest solution to a problem first; escalate to complex only as needed
metadata:
type: feedback
---
Always START with the simplest solution that could solve the problem. Confirm it works, then
graduate to more advanced/complicated approaches only as the simple one proves insufficient.
**Why:** Mike watched a "ask the UDM what IP it thinks VWP-QBS is" turn balloon into vault
reads, plink host-key pinning, and password sanity checks — when the clean answer was a single
`nslookup vwp-qbs.vwp.us 172.16.9.1` from a machine already on the VPN. The heavy path burned
tokens and his patience ("incapable of doing things cleanly like a week ago"). Now a standing
CLAUDE.md core rule.
**How to apply:** Before picking tooling, ask "what is the least-complex thing that answers
this?" — one DNS lookup, one API call, one command. Do that first and observe the result.
Only reach for SSH/plink/double-hops/multi-step orchestration when the simple probe genuinely
can't answer. Escalate deliberately, not by default. See [[feedback_verify_live_before_acting]].