Your personal IT guy for macOS — remembers your machine, guards every action, explains what it did, and leaves reusable tools behind. A plugin for Claude Code and Codex, for people who are not programmers.
Use when the user wants help looking after their Mac — a health checkup, reclaiming disk space, organising files, diagnosing a problem in plain language, setting up backups, fixing Wi-Fi or a home network, automating a repetitive chore, or understanding what just happened. Also the entry point when the user types it…
Decision logic for home network work — isolating whether a problem is the device, the Wi-Fi, the router, or the ISP before spending money; the fix ladder from free to hardware; router and mesh buying judgement; and the boundaries of whose network may be touched. Load before any /mac-it-guy-pro:network work.
Core conventions for all mac-it-guy-pro commands and agents — the safety contract, plain-language rules, report formats, and state file layout. Load before any IT task (checkup, cleanup, organize, fix, automate, backup, onboard).
How the IT guy remembers, refreshes, and retires what it knows about this machine — the profile schema, provenance classes, expiry by evidence, the belief ledger, demotion to history, the visit log, and undo manifests. Load when reading, writing, reviewing, or pruning anything in /ITGuy/.
Exact macOS commands for IT diagnostics and safe actions — disk, memory, startup items, updates, Time Machine, battery, SMART, duplicate detection, Trash-based deletion, HEIC conversion, photo dates, launchd scheduling. Load before running any diagnostic or maintenance command on a Mac.
Decision logic for building a personal unrestricted-internet connection from a censored network — which architecture to use (CDN-fronted vs direct), which protocols work and which are detectable, and the boundaries of what to help with. Load before any /mac-it-guy-pro:open-internet work.
The micro-product contract for the IT Guy toolbox — acceptance criteria, directory layout, README template, registry schema, dry-run requirement, double-clickable wrappers, the evolution ladder, and the pattern catalogue used to offer a user automations they did not know to ask for. Load when building, listing…
How the IT guy explains rather than just fixes — the two teaching modes (just-in-time and deliberate study), the learning-map structure, grounding lessons in the user's own measurements, depth scaling, and the pull-not-push rule. Load before any /mac-it-guy-pro:learn work or when a user asks why something was the fix.