nhouseholder/cursor-laptop-skills
Account-wide Cloud slash commands plus Engram Cloud MCP and Tailscale iMac MCP that self-heal on every Cloud Agent.
Same behavior; new seams / folders / decoupling. Convert code to clean architecture — separate concerns, increase modularity, reduce coupling.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Runs a formal 3-round debate between Claude (Proposer) and Gemini 3.1 Pro (Challenger), ending with an AI verdict via backend API. Use when the user says "debate", "debate this topic", "challenge my idea", or wants to adversarially stress-test a position through structured argument.
ALWAYS ACTIVE on Cloud Agents. Save decisions, conventions, and finished work to the existing Engram MCP (mem_save / mem_session_summary) so other agents can mem_search them. Do not wait for /wrap-up. If the Engram namespace is error, say so.
Effort, time, and complexity estimation before starting a task. Use when a task feels large, when the user asks "how long will this take", or before entering plan mode on a multi-step task. Produces a breakdown with confidence intervals — does NOT start implementation.
Follow your best recommendation — pick one course, execute it, do not interview. Hand off only secrets, GUI login, or a decision you cannot make.
Session start, read-only. Orient from Engram standing decisions plus recent handoffs, git status, and open todos. Never write a handoff.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Always-on standing law for every Cloud Agent on any ProjectsHQ repo: honesty about what was run, fail-closed on unknowns, real-money safety for betting picks, and the things a Cloud Agent must never do. Distilled from ~/AGENTS.md, which does not exist inside a container.
Alias of /kg — audit open work, pick the highest-leverage task, implement it, verify, and report the next action.
Keep going — audit open work, pick the highest-leverage task, implement it end-to-end, verify, then immediately take the next highest-leverage step. Do not pause for routine confirmation. Do not stop because one commit, push, or PR landed.
Performance engineer loop — speed, memory, scalability, extra rendering. Find the bottleneck, then ship a measured fix against an explicit target.
Session retrospective — review what was accomplished in this session versus the original goal. Use when closing a session, doing a mid-session check-in on what we did so far, or validating progress. Captures deviations and learning. Not an artifact producer.
ALWAYS ACTIVE on Cloud Agents. Join the tailnet in userspace, reach JobHub on nicholass-imac, fix Cloud git extraheader, use GitHub and Cloudflare APIs already injected. Do not print secrets. Do not wait to be asked.
Join an unfamiliar product repo: map architecture and data flow, then apply the highest-ROI structural / duplication / perf / maintainability refactors.
Strategic next-action prioritizer: anchors on the project's north star, scores impact vs effort vs confidence vs decay, filters already-killed work, and audits its own prior recommendations. Triggers on 'whats next', 'what's next', 'what should i do', 'prioritize', 'what now', or /whats-next.
Session end. Write a lean handoff in this project's handoffs/, commit it on the current branch. Do not auto-ship. Save standing memory to Engram MCP.