Nexus-Organization-Infosec

Make a timestamped backup of the whole project — a full copy of the file tree plus an infos.txt with the date, project name, size, file…

Go behind a program to discover what it ACTUALLY uses — its real dependencies, libraries, syscalls, files, network endpoints, env/config…

Like /improve, but every change is BIG — bold, ambitious, high-impact rewrites and redesigns rather than small safe tweaks.

Proactively hunt the codebase for bugs of every size — major reliability bugs (connection/network failures, missing timeouts, unhandled…

Rebuild an existing thing from scratch — same purpose, but better and self-made.

Enter "careful mode" — work with maximum caution about which files you touch and how far a change reaches.

Put a list of ideas in front of the user as a clickable approval checklist — a bundled CustomTkinter window with a checkbox per idea and a…

Revamp a codebase into a clean, well-organized, production-ready state — remove dead/old code, reorganize files into a sensible folder…

The user is back at the keyboard — resume work.

An addon (best paired with [[work-until-limit]], but works for any long/autonomous run) that gives the user a physical red STOP button — a…

Produce deep, comprehensive documentation of an entire project — everything that was built and how it works, the architecture and data…

Do everything the prompt asked, all the way to done, without stopping partway to ask permission.