adam-coding-local

Launch a new, top-level, interactive Claude Code session in a new Windows Terminal tab — native Windows or inside WSL — in a chosen folder, optionally remote-controllable and optionally seeded with an initial prompt or a handoff file. Use this WHENEVER the user asks to start / open / launch / spawn a new (top-level, separate, fresh, detached, background) Claude Code session, hand off to a fresh session, or launch Claude in a new terminal, tab or window, on Windows or in WSL, even if they don't name every detail. It clears the nested-session marker a launch from Claude's own shell tool would inherit (so the session is saved and shows in --resume), resolves claude's full path, and handles the quirks that silently break naive attempts: ConPTY via Windows Terminal, wt.exe's ';' splitting, prompt quoting, session-id vs initial-prompt openers, and the workspace-trust gate.

Inventory, clean up, and migrate Claude Code auto-memory stores found under ~/.claude/projects/<munged-path>/memory/ on this machine. Use this skill to list every memory store with its decoded project path, file count, size, and freshness; to identify ORPHANED stores whose original workspace no longer exists (so a human can review and delete them); and to migrate a chosen store into a repo's git-tracked .claude/memory/ directory so the memory travels with the repo across machines and is visible to hosted/cloud Claude sessions. Trigger on requests like "clean up claude memory", "migrate claude memory", "inventory memory stores", "orphaned memory", "sync memory across machines", "make memory portable", or any mention of `~/.claude/projects` or `autoMemoryDirectory`. LOCAL-ONLY: this skill reads and writes files under this machine's `~/.claude` directory and CANNOT run in a hosted/cloud Claude session that has no local `~/.claude` on disk — do not invoke it there.

Sync Claude Code settings.json between a Windows home and a WSL home. Triggers on requests to "sync Claude Code settings", "merge my settings.json", "keep WSL and Windows Claude settings in sync", or mentions of reconciling %USERPROFILE%\.claude\settings.json with ~/.claude/settings.json in WSL. Backs up both files with an Eastern-time-stamped prefix, then merges per property (union for permissions.allow/ask/deny and spinnerVerbs.verbs; per-key merge for env; more-recently-modified-wins with optional prompt for scalars like theme, model, effortLevel; OS-bound keys such as hooks, statusLine, defaultShell, sandbox, apiKeyHelper, permissions.additionalDirectories and env.CCSTATUSLINE_WIDTH are kept per-file and never copied across). Preserves each file's existing newline style, UTF-8 BOM presence and trailing newline. Windows-only (needs PowerShell 7+ and access to the WSL UNC share). Use when the user wants the two settings.json files reconciled, not when they want a single file edited in place.

Handle "Access is denied" from powershell.exe or pwsh.exe run inside WSL — Register-ScheduledTask / Set-ScheduledTask on a RunLevel=HighestAvailable task, a service change (Set-Service, Stop-Service, New-Service), an LSA rights grant such as "Log on as a batch job" (SeBatchLogonRight, secedit, ntrights), an HKLM registry write, or any other change to Windows state from a WSL session. Use it BEFORE attempting such a write from WSL and the moment one is denied. PowerShell run from WSL inherits the elevation of the session that launched WSL, and an agent's session is not elevated: reads succeed (Get-ScheduledTask, Get-Service, the registry) so the surface looks available, writes that need elevation fail, and no flag, retry, Start-Process -Verb RunAs, schtasks, sudo, SYSTEM principal or downgraded RunLevel fixes it. Compose the command from WSL, export what it will overwrite (Export-ScheduledTask), then hand the operator the exact line for an elevated Windows prompt and say it needs elevation.