GitHub PowerShell Daily Trending Repositories

dartraiden/NVIDIA-patcher

Adds 3D acceleration support for P106-090 / P106-100 / P104-090 / P104-100 / P102-100 / CMP 30HX / CMP 40HX / CMP 50HX / CMP 70HX / CMP 90HX / CMP 170HX mining cards as well as RTX 3060 3840SP, RTX 3080 Ti 20 GB, RTX 4070 10 GB, L40 ES, and RTX 5080M ES N22W-ES-A1.

English | Русский

English

NVIDIA patched drivers

How to use it

Windows

Linux

Donation

If you like my project, please press "Star" in the top right corner. You can also donate me some money:

Boosty
YooMoney
WebMoney
Crypto:
- BTC: bc1qakj06mgfcv8ypqeg38d6svwpefxluz90scmwvd
- LTC: ltc1qmhvewg7zjmmjw2uuyl37g26vxjjpywteppt6s9
- ETH: 0xf27585a4d02ac0308297621fac33763cd100c9f0
- USDT (Ethereum, ERC20): 0xf27585a4d02ac0308297621fac33763cd100c9f0
- TRX: TF3yJNg9wctvbNT9PteXezxc3zuzpvHk22
- USDT (Tron, TRС20): TF3yJNg9wctvbNT9PteXezxc3zuzpvHk22
- XMR (Monero): 86kq7awBWZKQt6ndJFJSdNEkAZzZQp6Fz4ToenTLNNjmGZS83LUbWEL9xtem3jwTy23KGfZr2sqK5TH5gy7bFr53QY5RN1D

Русский

Пропатченные драйверы NVIDIA

Добавляют поддержку 3D-ускорения майнинговым картам P106-090 / P106-100 / P104-100 / P104-101 / P102-100 / CMP 30HX / CMP 40HX / CMP 50HX / CMP 70HX / CMP 90HX / CMP 170HX, а также картам RTX 3060 3840SP, RTX 3080 Ti 20 GB, RTX 4070 10 GB, L40 ES и RTX 5080M ES N22W-ES-A1.

Как пользоваться

Windows

Linux

Поддержать проект

Если вам понравился этот проект, нажмите «Звезду» в правом верхнем углу. Кроме того вы можете заслать мне деньги:

Boosty
YooMoney
WebMoney
Криптовалюта:
- BTC: bc1qakj06mgfcv8ypqeg38d6svwpefxluz90scmwvd
- LTC: ltc1qmhvewg7zjmmjw2uuyl37g26vxjjpywteppt6s9
- ETH: 0xf27585a4d02ac0308297621fac33763cd100c9f0
- USDT (Ethereum, ERC-20): 0xf27585a4d02ac0308297621fac33763cd100c9f0
- XMR (Monero): 86kq7awBWZKQt6ndJFJSdNEkAZzZQp6Fz4ToenTLNNjmGZS83LUbWEL9xtem3jwTy23KGfZr2sqK5TH5gy7bFr53QY5RN1D

iiroak/Kindle-Filler-Disk

Kindle Disk Filler

Fill Kindle storage to block automatic updates on unregistered tablets. Useful for jailbreak preparation.

What this is (and what it is not)

There are two different things the community calls "filler", and mixing them up causes a lot of confusion:

OTA blocker filler (this tool). Fills the device's free space with dummy files so the Kindle cannot download an over-the-air (OTA) update. This is what Filler.sh / Filler.ps1 do.
SpringBreak filler folders. Some jailbreak guides (e.g. SpringBreak) ask you to create specific folders as part of their flow. Those folders are not the same thing and do not block OTA by themselves.

If your goal is to stop automatic updates, use this tool. If you are following a jailbreak guide, follow that guide's steps for its own folders — do not mix the two.

Quick Run

Linux / macOS:

curl -fsSL https://github.com/iiroak/Kindle-Filler-Disk/raw/main/Scripts/Filler.sh | bash

Windows (PowerShell):

irm https://github.com/iiroak/Kindle-Filler-Disk/raw/main/Scripts/Filler.ps1 | iex

Windows (CMD):

powershell -Command "irm https://github.com/iiroak/Kindle-Filler-Disk/raw/main/Scripts/Filler.ps1 | iex"

Which method should I use? (decision tree)

1. Does your Kindle show up as a USB drive/volume on your computer?
   - Yes  -> Mass Storage. The script fills it directly. (older Kindles)
   - No   -> It is probably MTP (11th gen+, Scribe, Basic 2024, PW5/PW6).
             The script writes into the device's storage folder over MTP.

2. Do you want to BLOCK OTA updates, or are you following SpringBreak?
   - Block OTA      -> use this tool (fill mode).
   - SpringBreak    -> follow that guide's folder steps; don't mix them.

3. Did the per-file fill fail on your MTP device?
   - Yes -> the script offers the pre-built ZIP fallback (last resort).
   - Or use the GUI alternative (jannikac/mtp-filler).

4. Already blocked OTA and want to read normally again?
   - Run the script and choose "Remove filler files" to reclaim space.

5. Kindle still shows "storage full" after removing?
   - Empty the Trash (.Trashes on macOS), disconnect/reconnect,
     and reboot the Kindle.

Modes: fill and remove

When you run the script it first asks what to do:

Fill — creates dummy files to occupy free space and block OTA updates. Before writing, it shows the destination, connection type and free space and asks for confirmation. You choose how much space to leave:
- 20 MB aggressive OTA block (may trigger "storage almost full" notifications)
- 50 MB balanced
- 100 MB daily use (fewer notifications, still blocks most OTA)
Remove — deletes the fill_disk/ folder and reports free space before and after, so you can verify the space was reclaimed.

Safety

The script never fills your PC by accident: it only writes to a detected Kindle or a device you explicitly pick, and it refuses system/home paths (/, /home, Desktop, Downloads, the Windows system drive, …).
On Windows, if the script is launched by double-click and hits an error, it now shows the error and waits instead of closing the window silently.

Supported Devices

Kindle Model	Connection	Supported
Kindle Basic (older)	Mass Storage	Yes
Kindle Paperwhite (up to 11th gen)	Mass Storage	Yes
Kindle Paperwhite 12th gen	MTP	Yes (Linux/Windows)
Kindle Basic 2024	MTP	Yes (Linux/Windows)
Kindle Scribe	MTP	Yes (Linux/Windows)

How It Works

The script automatically detects your Kindle's connection type:

Mass Storage (older Kindles): appears as a regular USB drive. Files are created directly on the device.
MTP (modern Kindles): appears as a portable device. Files are created locally then transferred via MTP protocol.

MTP nested storage structure

MTP devices are not writable at their root. The device root contains one or more storage folders, and files can only be written inside one of them:

Kindle                          <- device root (NOT writable)
└── Internal Storage            <- storage folder (write here)
    └── fill_disk/              <- the script writes the filler files here

The name of the storage folder is localized and varies by device (Internal Storage, Almacenamiento interno compartido, Espace de stockage interne, SD card, …). The scripts detect it automatically: if there is a single storage folder they use it; otherwise they match a multilingual list of known names and fall back to the first available folder.

Detection Methods

OS	Mass Storage Detection	MTP Detection
Linux	`findmnt` by volume label "Kindle"	`gio mount -l` (requires `gvfs`)
macOS	`/Volumes/Kindle`	Not supported (macOS lacks MTP)
Windows	Drive with volume name "Kindle"	`Shell.Application` COM (portable devices)

MTP Support (Linux)

For newer Kindles that use MTP protocol, you need gvfs installed:

# Ubuntu/Debian
sudo apt install gvfs gvfs-backends

# Fedora
sudo dnf install gvfs gvfs-mtp

# Arch Linux
sudo pacman -S gvfs gvfs-mtp

For the pre-built ZIP fallback (below) you also need unzip and curl (or wget), which are present on most systems by default.

Pre-built ZIP fallback (last resort)

If the normal per-file fill method fails on your device (e.g. an MTP device that refuses scripted writes), the scripts offer a fallback: they download a pre-built archive of zero-filled files from this repo's Zips/ folder and copy its contents into fill_disk/ on the device.

The archives are tiny to download (~8–66 MB) but expand to ~8/16/32/64 GB (zeros compress about 1000:1).
The script picks the largest archive that fits your device's free space (fill_8gb.zip, fill_16gb.zip, fill_32gb.zip, fill_64gb.zip). If free space can't be read, it asks for your Kindle's size.
On MTP the archive is streamed one file at a time, so it does not need gigabytes of scratch space on your PC.

This is only triggered when the primary method wrote nothing; you are always prompted before anything is downloaded.

GUI alternative

If you prefer a graphical tool instead of these scripts, jannikac/mtp-filler is a mature cross-platform option (Rust + libmtp/Windows WPD) that ships a GUI and a CLI in a single pre-built binary for Windows, macOS and Linux. It does the same job (fill an MTP device's storage to block OTA updates) with a point-and-click interface.

Notes

Recommended free space: 20-50 MB to block updates
The filler is written as 100 MB files (file_0, file_1, … in fill_disk), using smaller 50/10/1 MB pieces only for the final tail. This is intentional: to add a book later you can delete a single file to free 100 MB and copy it in, while the device stays full enough to keep OTA updates blocked — no need to remove everything.
Multiple runs are safe — continues from where it left off
To free the space again, run the script and pick Remove filler files (it reports free space before/after). Deleting fill_disk/ by hand also works.
The script will not create files on your PC — it only targets the Kindle device
If no Kindle is detected, the script aborts with a clear error message

Running from File (Windows)

If you download Filler.ps1 and run it locally, PowerShell may block it with an execution policy error. Solutions:

# Option A: Run with bypass (one-time)
powershell -ExecutionPolicy Bypass -File .\Filler.ps1

# Option B: Change policy permanently (recommended)
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

The irm | iex command works without any changes because it runs in the current session.

Troubleshooting

"No Kindle device detected"

Ensure your Kindle is connected via USB cable
Unlock the Kindle and make sure it shows the home screen
For MTP Kindles on Linux: install gvfs gvfs-backends
Try disconnecting and reconnecting the USB cable

Script fills PC storage instead of Kindle (FIXED in v2.1)

This issue was fixed in v2.1. The script now detects the Kindle device before creating any files.

"El archivo no está firmado digitalmente" (Windows)

See Running from File above.

MTP is slow

MTP transfers are inherently slower than mass storage. The script writes 100MB files in both modes (with a 50/10/1MB tail); on MTP each file is streamed one at a time, which balances speed and reliability.

Manual

Copy Filler.ps1 (Windows) or Filler.sh (Linux/macOS) to Kindle root via USB, then run.

Credits

iiroak — Original author
vinaooo — MTP detection and auto-detection for Linux (#8)
simoneeti — gio-based MTP approach for Linux (#34)
johnabs — dd single-file suggestion (#18)
zhangyoufu — mkfile performance issue on macOS (#19)
SkylarPlayz348 — pre-built MTP filler archives used by the zip fallback
jannikac — mtp-filler, the cross-platform GUI/CLI alternative

actions/runner-images

GitHub Actions runner images

GitHub Actions Runner Images

Table of Contents

About

This repository contains the source code used to create the VM images for GitHub-hosted runners used for Actions, as well as for Microsoft-hosted agents used for Azure Pipelines. To build a VM machine from this repo's source, see the instructions.

Available Images

Image	Architecture	YAML Label	Included Software
Ubuntu 26.04	x64	`ubuntu-26.04`	ubuntu-26.04
Ubuntu 26.04 Arm64	arm64	`ubuntu-26.04-arm`	ubuntu-26.04-arm64
Ubuntu 24.04	x64	`ubuntu-latest` or `ubuntu-24.04`	ubuntu-24.04
Ubuntu 24.04 Arm64	arm64	`ubuntu-24.04-arm`	ubuntu-24.04-arm64
Ubuntu 22.04	x64	`ubuntu-22.04`	ubuntu-22.04
Ubuntu 22.04 Arm64	arm64	`ubuntu-22.04-arm`	ubuntu-22.04-arm64
Ubuntu Slim	x64	`ubuntu-slim`	ubuntu-slim
Xcode 27	arm64	`xcode-27` or `xcode-27-xlarge`	xcode-27
macOS 26	x64	`macos-latest-large`, `macos-26-intel`, `macos-26-large`	macOS-26
macOS 26 Arm64	arm64	`macos-latest`, `macos-26` or `macos-26-xlarge`	macOS-26-arm64
macOS 15	x64	`macos-15-large`, or `macos-15-intel`	macOS-15
macOS 15 Arm64	arm64	`macos-15`, or `macos-15-xlarge`	macOS-15-arm64
macOS 14	x64	`macos-14-large`	macOS-14
macOS 14 Arm64	arm64	`macos-14` or `macos-14-xlarge`	macOS-14-arm64
Windows Server 2025	x64	`windows-latest`, `windows-2025`, or `windows-2025-vs2026`	windows-2025-vs2026
Windows Server 2022	x64	`windows-2022`	windows-2022
Windows 11 Arm64	arm64	`windows-11-arm`	windows-11-arm64
Windows 11 Arm64 with Visual Studio 2026	arm64	`windows-11-vs2026-arm`	windows-11-vs2026-arm64

Label scheme

In general the -latest label is used for the latest OS image version that is GA.
Before moving the -latest label to a new OS version we will announce the change and give sufficient lead time for users to update their workflows.
The -xlarge and -large suffixes are unique to macOS images and are only available for GitHub Actions. Learn more about GitHub Actions larger runners.

Announcements

See notable upcoming changes by viewing issues with the Announcement label.

Image Definitions

Beta

The purpose of a Beta is to collect feedback on an image before it is released to GA. The goal of a Beta is to identify and fix any potential issues that exist on that image. Images are updated on a weekly cadence. Any workflows that run on a beta image do not fall under the customer SLA in place for Actions. Customers choosing to use Beta images are encouraged to provide feedback in the runner-images repo by creating an issue. A Beta may take on different availability, i.e. public vs private.

GA

A GA (General Availability) image has been through a Beta period and is deemed ready for general use. Images are updated on a weekly cadence. In order to be moved to GA the image must meet the following criteria:

Has been through a Beta period (public or private)
Most major software we install on the image has a compatible version for the underlying OS and
All major bugs reported during the Beta period have been addressed.

This image type falls under the customer SLA for actions. GA images are eventually deprecated according to our guidelines as we only support the latest 2 versions of an OS.

Latest Migration Process

GitHub Actions and Azure DevOps use the -latest YAML label (ex: ubuntu-latest, windows-latest, and macos-latest). These labels point towards the newest stable OS version available.

The -latest migration process is gradual and happens over 1-2 months in order to allow customers to adapt their workflows to the newest OS version. During this process, any workflow using the -latest label, may see changes in the OS version in their workflows or pipelines. To avoid unwanted migration, users can specify a specific OS version in the yaml file (ex: macos-14, windows-2022, ubuntu-22.04).

Image Releases

How to best follow along with changes

Find the latest releases for this repository here.
Subscribe to the releases coming out of this repository, instructions here.
Upcoming changes: A pre-release is created when the deployment of an image has started. As soon as the deployment is finished, the pre-release is converted to a release. If you have subscribed to releases, you will get notified of pre-releases as well.
- You can also track upcoming changes using the awaiting-deployment label.
For high impact changes, we will post these in advance to the GitHub Changelog on our blog and on X.
- Ex: breaking changes, GA or deprecation of images

Cadence

We typically deploy weekly updates to the software on the runner images.

Software and Image Support

Support Policy

Tools and versions will typically be removed 6 months after they are deprecated or have reached end-of-life
We support (at maximum) 2 GA images and 1 beta image at a time. We begin the deprecation process of the oldest image label once the newest OS image label has been released to GA.
The images generally contain the latest versions of packages installed except for Ubuntu LTS where we mostly rely on the Canonical-provided repositories.
Popular tools can have several versions installed side-by-side with the following strategy:

Tool name	Installation strategy
Docker images	not more than 3 latest LTS OS\tool versions. New images or new versions of current images are added using the standard tool request process
Java	all LTS versions
Node.js	3 latest LTS versions
Go	3 latest minor versions
Python Ruby	5 most popular `major.minor` versions
PyPy	3 most popular `major.minor` versions
.NET Core	2 latest LTS versions and 1 latest version. For each feature version only latest patch is installed. Note for Ubuntu images see details.
GCC GNU Fortran Clang GNU C++	3 latest major versions
Android NDK	1 latest non-LTS, 2 latest LTS versions
Xcode	- only one major version of Xcode will be supported per macOS version - all minor versions of the supported major version will be available - beta and RC versions will be provided "as-is" in the latest available macOS image only no matter of beta/GA status of the image - when a new patch version is released, the previous patch version will be replaced
Xcode Platforms	- only three major.minor versions of platform tools and simulator runtimes will be available for installed Xcode, including beta/RC versions

Package managers usage

We use third-party package managers to install software during the image generation process. The table below lists the package managers and the software installed.

Note

Third-party repositories are re-evaluated every year to identify if they are still useful and secure.

Operating system	Package manager	Third-party repos and packages
Ubuntu	APT	docker Eclipse-Temurin (Adoptium) Erlang Firefox git-lfs git Google Cloud CLI Heroku HHvm MongoDB Mono MS Edge PostgreSQL R
	pipx	ansible-core yamllint
Windows	Chocolatey	No third-party repos installed
macOS	Homebrew	aws-cli v2 azure/bicep mongodb/brew
	pipx	yamllint

Image Deprecation Policy

Images begin the deprecation process of the oldest image label once a new GA OS version has been released.
Deprecation process begins with an announcement that sets a date for deprecation.
As it gets closer to the date, GitHub begins doing scheduled brownouts of the image.
During this time there will be an Announcement pinned in the repo to remind users of the deprecation.
Finally, GitHub will deprecate the image and it will no longer be available.

Preinstallation Policy

In general, these are the guidelines we follow when deciding what to pre-install on our images:

Popularity: widely-used tools and ecosystems will be given priority.
Latest Technology: recent versions of tools will be given priority.
Deprecation: end-of-life tools and versions will not be added.
Licensing: MIT, Apache, or GNU licenses are allowed.
Time & Space on the Image: we will evaluate how much time is saved and how much space is used by having the tool pre-installed.
Support: If a tool requires the support of more than one version, we will consider the cost of this maintenance.

Default Version Update Policy

In general, once a new version is installed on the image, we announce the default version update 2 weeks prior to deploying it.
For potentially dangerous updates, we may extend the timeline up to 1 month between the announcement and deployment.

How to Interact with the Repo

Issues: To file a bug report, or request tools to be added/updated, please open an issue using the appropriate template
Discussions: If you want to share your thoughts about image configuration, installed software, or bring a new idea, please create a new discussion. Before making a new discussion, please make sure no similar topics were created earlier in the actions category.
For general questions about using the runner images or writing your Actions workflow, please open requests in the GitHub Community discussion Actions category.

FAQs

What images are available for GitHub Actions and Azure DevOps?

The availability of images for GitHub Actions and Azure DevOps is the same. However, deprecation policies may differ. See documentation for more details:

What image version is used in my build?

Usually, image deployment takes 2-3 days, and documentation in the main branch is only updated when deployment is finished. To find out which image version and what software versions are used in a specific build, see Set up job (GitHub Actions) or Initialize job (Azure DevOps) step log.

Looking for other Linux distributions?

We do not plan to offer other Linux distributions. We recommend using Docker if you'd like to build using other distributions with the hosted runner images. Alternatively, you can leverage self-hosted runners and fully customize your VM image to your needs.

How do I contribute to the macOS source?

macOS source lives in this repository and is available for everyone. However, macOS image-generation CI doesn't support external contributions yet so we are not able to accept pull-requests for now.

We are in the process of preparing macOS CI to accept contributions. Until then, we appreciate your patience and ask you to continue to make tool requests by filing issues.

How does GitHub determine what tools are installed on the images?

For some tools, we always install the latest at the time of the deployment; for others, we pin the tool to specific version(s). For more details please see the Preinstallation Policy

How do I request that a new tool be pre-installed on the image?

Please create an issue and get an approval from us to add this tool to the image before creating the pull request.

What branch should I use to build custom image?

We strongly encourage customers to build their own images using the main branch. This repository contains multiple branches and releases that serve as document milestones to reflect what software is installed in the images at certain point of time. Current builds are not idempotent and if one tries to build a runner image using the specific tag it is not guaranteed that the build will succeed.

ntdevlabs/tiny11builder

Scripts to build a trimmed-down Windows 11 image.

tiny11builder

Scripts to build a trimmed-down Windows 11 image - now in PowerShell!

Introduction :

Tiny11 builder, now completely overhauled.
After more than a year (for which I am so sorry) of no updates, tiny11 builder is now a much more complete and flexible solution - one script fits all. Also, it is a steppingstone for an even more fleshed-out solution.

You can now use it on ANY Windows 11 release (not just a specific build), as well as ANY language or architecture. This is made possible thanks to the much-improved scripting capabilities of PowerShell, compared to the older Batch release.

This is a script created to automate the build of a streamlined Windows 11 image, similar to tiny10. The script has also been updated to use DISM's recovery compression, resulting in a much smaller final ISO size, and no utilities from external sources. The only other executable included is oscdimg.exe, which is provided in the Windows ADK and it is used to create bootable ISO images. Also included is an unattended answer file, which is used to bypass the Microsoft Account on OOBE and to deploy the image with the /compact flag. It's open-source, so feel free to add or remove anything you want! Feedback is also much appreciated.

Also, for the very first time, introducing tiny11 core builder! A more powerful script, designed for a quick and dirty development testbed. Just the bare minimum, none of the fluff. This script generates a significantly reduced Windows 11 image. However, it's not suitable for regular use due to its lack of serviceability - you can't add languages, updates, or features post-creation. tiny11 Core is not a full Windows 11 substitute but a rapid testing or development tool, potentially useful for VM environments.

⚠️ Script versions:

tiny11maker.ps1 : The regular script, which removes a lot of bloat but keeps the system serviceable. You can add languages, updates, and features post-creation. This is the recommended script for regular use.
⚠️ tiny11coremaker.ps1 : The core script, which removes even more bloat but also removes the ability to service the image. You cannot add languages, updates, or features post-creation. This is recommended for quick testing or development use.

Instructions:

Download Windows 11 from the Microsoft website or Rufus
Mount the downloaded ISO image using Windows Explorer.
Open PowerShell 5.1 as Administrator.
Change the script execution policy :

Set-ExecutionPolicy Bypass -Scope Process

Using -Scope Process you keep your original policy intact as this change only lasts for the current PowerShell session.

Start the script :

C:/path/to/your/tiny11/script.ps1 -ISO <letter> -SCRATCH <letter>

You can see of the script by running the get-help command.

Select the drive letter where the image is mounted (only the letter, no colon (😃)
Select the SKU that you want the image to be based.
Sit back and relax 😃
When the image is completed, you will see it in the folder where the script was extracted, with the name tiny11.iso

What is removed:

Tiny11maker	Tiny11coremaker
Clipchamp News Weather Xbox GetHelp GetStarted Office Hub Solitaire PeopleApp PowerAutomate ToDo Alarms Mail and Calendar Feedback Hub Maps Sound Recorder Your Phone Media Player QuickAssist Internet Explorer Tablet PC Math Edge OneDrive	all from regular tiny + Windows Component Store (WinSxS) Windows Defender (only disabled, can be enabled back if needed) Windows Update (wouldn't work without WinSxS, enabling it would put the system in a state of failure) WinRE

Keep in mind that you cannot add back features in tiny11 core!
You will be asked during image creation if you want to enable .net 3.5 support!

Known issues:

Although Edge is removed, there are some remnants in the Settings, but the app in itself is deleted.
You might have to update Winget before being able to install any apps, using Microsoft Store.
Outlook and Dev Home might reappear after some time. This is an ongoing battle, though the latest script update tries to prevent this more aggressively.
If you are using this script on arm64, you might see a glimpse of an error while running the script. This is caused by the fact that the arm64 image doesn't have OneDriveSetup.exe included in the System32 folder.

Features to be implemented:

~~disabling telemetry~~ (Implemented in the 04-29-24 release!)
~~more ad suppression~~ (Partially implemented in the 09-06-25 release!)
improved language and arch detection
more flexibility in what to keep and what to delete
maybe a GUI???

And that's pretty much it for now!

❤️ Support the Project

If this project has helped you, please consider showing your support! A small donation helps me dedicate more time to projects like this. Thank you!

Patreon | PayPal | Ko-fi Thanks for trying it and let me know how you like it!

microsoftgraph/microsoft-graph-docs-contrib

Documentation for the Microsoft Graph REST API

Microsoft Graph documentation

Thank you for your interest in Microsoft Graph documentation! For the best experience, we recommend you view this content on Microsoft Learn.

Give us your feedback

Your feedback is important to us.

To let us know about any questions or issues you find in the documentation, leave feedback using the standard experience.
We also encourage you to fork, make the fix, and do a pull request of your proposed changes. See CONTRIBUTING.md for contributing guidelines.
To let us know about your programming experience, what you would like to see in future versions, code samples, and so on, enter your suggestions and ideas at Microsoft 365 Developer Platform Tech Community.

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Raphire/Win11Debloat

A simple, lightweight PowerShell script that allows you to remove pre-installed apps, disable telemetry, as well as perform various other changes to declutter and customize your Windows experience. Win11Debloat works for both Windows 10 and Windows 11.

Win11Debloat

Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience, no installation required! You can use it to remove pre-installed apps, disable telemetry, remove intrusive interface elements and much more. No need to painstakingly go through all the settings yourself or remove apps one by one. Win11Debloat makes the process quick and easy!

The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the ability to make changes to other Windows users. You can also easily export & import your preferred settings, allowing you to quickly apply the same settings on all your systems. Please refer to our wiki for more details.

Did this script help you? Please consider buying me a cup of coffee to support my work

Usage

Warning

Great care went into making sure this script does not unintentionally break any OS functionality, but use at your own risk! If you run into any issues, please report them here.

Quick method

Download & run the script automatically via PowerShell.

Open PowerShell or Terminal.
Copy and paste the command below into PowerShell:

& ([scriptblock]::Create((irm "https://debloat.raphi.re/")))

Wait for the script to automatically download and launch Win11Debloat.
Carefully read through and follow the on-screen instructions.

This method supports command-line parameters to customize the behaviour of the script. Please click here for more information.

Traditional method

Manually download & run the script.

Download the latest version of the script, and extract the .ZIP file to your desired location.
Navigate to the Win11Debloat folder
Double click the Run.bat file to start the script. NOTE: If the console window immediately closes and nothing happens, try the advanced method below.
Accept the Windows UAC prompt to run the script as administrator, this is required for the script to function.
Carefully read through and follow the on-screen instructions.

Advanced method

Manually download the script & run the script via PowerShell. Recommended for advanced users.

Download the latest version of the script, and extract the .ZIP file to your desired location.
Open PowerShell or Terminal as an administrator.
Temporarily enable PowerShell execution by entering the following command:

Set-ExecutionPolicy Bypass -Scope Process -Force

In PowerShell, navigate to the directory where the files were extracted. Example: cd c:\Win11Debloat
Now run the script by entering the following command:

.\Win11Debloat.ps1

Carefully read through and follow the on-screen instructions.

This method supports command-line parameters to customize the behaviour of the script. Please click here for more information.

Features

Below is an overview of the key features and functionality offered by Win11Debloat. You can visit the the wiki for more details.

Tip

All of the changes made by Win11Debloat can easily be reverted and almost all of the apps can be reinstalled through the Microsoft Store. You can visit the wiki for more information on reverting changes.

App Removal

Remove a wide variety of preinstalled apps. Click here for more info.

Privacy & Suggested Content

Disable telemetry, diagnostic data, activity history, app-launch tracking & targeted ads.
Disable tips, tricks, suggestions & ads across Windows, the lock screen and Microsoft Edge.
Disable Windows location services, app location access and Find My Device location tracking.
Hide Microsoft 365 ads on the Settings 'Home' page, or hide the 'Home' page entirely.

AI Features

Disable & remove Microsoft Copilot, Windows Recall and Click to Do.
Prevent AI service (WSAIFabricSvc) from starting automatically.
Disable AI Features in Edge, Paint and Notepad.

System

Disable the Drag Tray for sharing & moving files.
Restore the old Windows 10 style context menu.
Turn off Enhance Pointer Precision (mouse acceleration).
Disable the Sticky Keys keyboard shortcut.
Disable Storage Sense automatic disk cleanup.
Disable fast start-up to ensure a full shutdown.
Disable BitLocker automatic device encryption.
Disable network connectivity during Modern Standby to reduce battery drain.

Windows Update

Prevent Windows from getting updates as soon as they're available.
Prevent automatic restarts after updates while signed in.
Disable sharing of downloaded updates with other PCs, also known as Delivery Optimization.
Prevent Windows from auto-installing device companion apps, like LG Monitor App, Alienware Command Center and more.

Appearance

Enable dark mode for system and apps.
Disable transparency, animations and visual effects.

Start Menu & Search

Customize the start menu by removing pinned apps, hiding recommendations, and customizing the 'All Apps' section.
Disable the Phone Link mobile devices integration in the start menu.
Disable Bing web search & Copilot integration and Microsoft Store app suggestions in Windows search.

Taskbar

Change taskbar alignment.
Customize or hide taskbar buttons like the search bar, taskview and more.
Disable widgets on the taskbar & lock screen.
Enable the 'End Task' option in the taskbar right click menu to quickly force-close apps.
Enable the 'Last Active Click' behavior in the taskbar app area. This allows you to repeatedly click on an application's icon in the taskbar to switch focus between the open windows of that application.
Customize how app buttons are shown on the taskbar.

File Explorer

Change the default location that File Explorer opens to.
Show file extensions for known file types.
Show hidden files, folders and drives.
Hide the Home, Gallery or OneDrive section from the File Explorer navigation pane.
Hide duplicate removable drive entries from the File Explorer navigation pane, so only the entry under 'This PC' remains.
Add all common folders (Desktop, Downloads, etc.) back to 'This PC' in File Explorer.
Change drive letter position or visibility in File Explorer.

Multi-tasking

Disable window snapping.
Disable Snap Assist and Snap Layout suggestions when dragging or snapping windows.
Change whether tabs are shown when snapping windows or pressing Alt+Tab.

Optional Windows Features

Enable Windows Sandbox, a lightweight desktop environment for safely running applications in isolation.
Enable Windows Subsystem for Linux which allows you to run a Linux environment directly on Windows.

Other

Disable Xbox Game Bar integration & game/screen recording. This also disables ms-gamingoverlay/ms-gamebar popups if you uninstall the Xbox Game Bar.
Disable bloat in Brave browser (AI, Crypto, News, etc.)

Advanced Features

Ability to apply changes to a different user, instead of the currently logged in user.
Sysprep mode to apply changes to the Windows Default user profile. Which ensures, all new users will have the changes automatically applied to them.

Contributing

We welcome contributions of all kinds! Please see our Contributing Guidelines for detailed instructions on how to get started and best practices for contributing.

License

Win11Debloat is licensed under the MIT license. See the LICENSE file for more information.

CubeCoders/AMPTemplates

For the AMP community to share Generic Module templates.

AMP Templates

For the AMP community to share Generic Module templates.

Making generic module templates

See the wiki article for the module: https://github.com/CubeCoders/AMP/wiki/Configuring-the-'Generic'-AMP-module

You can also use the online configurator at https://config.getamp.sh/ to help with building templates.

*There is a much more robust version of the online configuration tool that is still in beta. This should provide much better results than the above even so. If you have any feedback, please contact IceOfWraith in the CubeCoders Discord.

The online configurator can be used as a starting point for making templates. However, it will not generally produce a fully functioning template. Templates produced using the generator can be deployed for personal use but will not be accepted into the CubeCoders repository.

AI generated configurations will not be accepted in this repo.

Sharing Templates

Right now the following restrictions apply to templates that may be publicly shared via this repository (some of these will be relaxed over time):

The application must not require any login/authentication in order to download (except for SteamCMD logins).
If the application does not have a Linux version you should add a Proton download via SteamCMD to support it if possible.
Applications that have customizable settings must use a Settings Manifest.
Only applications that expose some kind of Console that AMP is able to pick up.
Do not invoke any shell scripts/batch files. You must only launch actual executables.

To share a template

Create a pull request containing the following files in the top-level directory of the repository:

*APPLICATIONAME*.kvp
*APPLICATIONAME*config.json
*APPLICATIONAME*metaconfig.json (Optional)

With the names fully lower-cased.

For example, valheim.kvp, valheimconfig.json, valheimmetaconfig.json

Do not use any directories and include no-other files.

If you are only submitting a draft, make sure to append (draft) to the pull request title.

Editing templates

If you believe that a template needs either updating or changes made, please submit a pull request for that template with a justification for why that change is needed. If possible try and contact the original author first.

After submitting a template

Once you've submitted a pull request, your configuration will be tested in its as-is state by an automated tool. It will:

Load the configuration
Attempt to perform an update
Attempt to start the application
Verify that the application reaches the 'Ready' state.
Attempt to stop the application
Verify that the application reaches the 'Stopped' state.

You should ensure that your configuration can do this on both Windows and Linux before submitting your configuration.

ChrisTitusTech/winutil

Chris Titus Tech's Windows Utility - Install Programs, Tweaks, Fixes, and Updates

Chris Titus Tech's Windows Utility

A curated compilation of Windows system tasks streamline installs, debloat with tweaks, troubleshoot with config, and configure Windows updates. Run it fresh on every new Windows install.

Quick Start

WinUtil must be run as Administrator Because it performs system-wide changes.

Open PowerShell or Terminal as admin, then run:

Stable Branch (recommended)

irm https://christitus.com/win | iex

Development Branch

irm https://christitus.com/windev | iex

How to open an admin terminal

Start menu: Right-click Start → Windows PowerShell (Admin) or Terminal (Admin)
Search: Press the Windows key, and type PowerShell or Terminal, then Ctrl + Shift + Enter

Automation / Presets

Apply a predefined configuration without manual selection:

& ([ScriptBlock]::Create((irm https://christitus.com/win))) -Preset Standard

Preset	Description
`Standard`	Balanced defaults for most users
`Minimal`	Minimal changes to suit every user
`Advanced`	Deep tweaks for power users

To view exactly what each preset does, see: https://github.com/ChrisTitusTech/winutil/blob/main/config/preset.json

Build & Develop

See https://github.com/ChrisTitusTech/winutil/blob/main/.github/CONTRIBUTING.md

Resources

Support

Leave a ⭐ to show support!
Faster Dotnet Implementation for sale here: https://www.cttstore.com/windows-toolbox

Contributors

Thanks to everyone who has contributed time and effort to this project. Keep rocking 🍻

I-Am-Jakoby/Flipper-Zero-BadUSB

Repository for my flipper zero badUSB payloads. Now almost entirely plug and play.

💀 BadUSB 💀

Subscribing to my YouTube would also be greatly appreciated.

Unleash the power of your Flipper 🤓💻

Description

🥇 I am in 1st place for most payloads submitted to Hak5❗

🔓 I have taken my colllection of payloads and formatted them to work for the Flipper for all of you to use❗

⚠️ Please ENJOY and use RESPONSIBLY❗

The Payloads

This repository has been optimized to facilitate plug and play functionality.

I purchased the domain jakoby.lol for the sole purpose of creating my own short URLs.

I did this with the intention of making room for Discord webhooks and Dropbox tokens to fit in my one-liners.

This, in turn, makes it so the user no longer needs to host their own version of the script.

Payloads	Description	Plug'n'Play	Author
VoiceLogger	Activates your target's microphone, converts their speech to text, and exfils it to Discord.	✅	Jakoby
Evil-Goose	A payload that hires a goose to hack your target in real time.	✅	Jakoby
ADV-Recon	A script used to do an advanced level of recon on the target's computer.	✅	Jakoby
AcidBurn	A script I put together to be used on your friends or foes. Prepare to be roasted.	✅	Jakoby
Jump-Scare	Just a little jumpscare that changes the target's wallpaper.	✅	Jakoby
Jump-Scare V2	Just a little jumpscare that plays a video in the target's PowerShell console.	✅	Jakoby
ADV-RickRoll	RickRoll that plays in the PowerShell console after a mouse movement is detected.	✅	Jakoby
PineApple	Connect a target's PC to your WiFi PineApple.	⛔	Jakoby
Play-WAV	Download a WAV file and play it after a mouse movement is detected.	✅	Jakoby
Rage-Pop-Ups	Generates an infinite loop of insulting pop-ups.	⛔	Jakoby
Subscribe	Used to make your target subscribe to your YouTube channel.	✅	Jakoby
Must Sub	A script used to make your target subscribe to 15 of Jakoby's favorite YouTube channels.	✅	Jakoby
PS-Draw	A script used to generate and draw images in the PowerShell window.	⛔	Jakoby
WallPaper-Troll	Collects sensitive info from your target and displays it as their wallpaper to taunt them.	✅	Jakoby
WallPaper-URL	Sets the target's wallpaper to an image you provide via a URL after a mouse movement is detected.	✅	Jakoby
We-Found-You	Opens a map with your target's current location on it.	✅	Jakoby
YT-Tripwire	Opens any YouTube video after a mouse movement is detected.	✅	Jakoby
Credz-Plz	A script used to prompt the target to enter their credentials to later be exfiltrated.	✅	Jakoby
Shortcut Jacker	A script used to embed malware in the shortcut on your target's desktop.	⛔	Jakoby
Wifi Grabber	Grabs your target's WiFi passwords and uploads them to either Dropbox, Discord, or both.	✅	Jakoby
IP Grabber	Grabs your target's IP addresses and uploads them to either Dropbox, Discord, or both.	✅	Jakoby
Browser Data	This payload can be used to retrieve the browsing history and bookmarks of your target.	✅	Jakoby

Contact

📱 My Socials 📱

YouTube

Twitter

Instagram

Discord

TikTok

Acknowledgments

(back to top)

sp00n/CoreCycler

Script to test single core stability, e.g. for PBO & Curve Optimizer on AMD Ryzen or overclocking/undervolting on Intel processors

CORECYCLER -

https://github.com/sp00n/corecycler

WHAT?

A PowerShell script to test the stability for single core loads. Modern CPUs can adjust their CPU frequency depending on their load, and have mechanism that allow them to clock higher when only one or two cores are loaded ("boost" clock). With this script you can test the stability for each core, which helps you to validate if your Ryzen "PBO" resp. "Curve Optimizer" settings are actually stable. It also works to test Intel's "Active-Core" Turbo-Boost settings.

HOW?

Double click the "Run CoreCycler.bat" file.

DANGER!

I do not take any responsibility if you damage your computer using this script! Temperatures while using a stress test can become very high, especially if the cooling solution is suboptimal. And although modern CPUs should automatically throttle or shut down if the temperature becomes too high, there's a certain risk of degradation for your chip if it's running at it max temperature for a prolonged period of time. Also, using PBO technically voids the warranty of a Ryzen CPU, so use it at your own risk!

DESCRIPTION

This script will run your selected stress test (Prime95, y-cruncher, Aida64) with only one (or two) worker threads and sets the affinity of the stress test process alternating to each physical core, cycling through all of them. This way you can test the stability of your Curve Optimizer / Active-Core setting for each core individually, much more thoroughly than e.g. with Cinebench or the Windows Repair, and much easier than manually setting the affinity of the process via the Task Manager. It will still need a lot of time though. If, for example, you're after a 12h "prime-stable" setup which is common for regular overclocks, you'd need to run this script for 12x12 = 144 hours on a 5900X with 12 physical cores, because each core is tested individually, and so each core also needs to complete this 12 hour test individually. Respectively, on a 5600X with its 6 physical cores this would be "only" 6x12 = 72 hours.

Unfortunately such an all-core stress test with Prime95 or other stress tests is not effective for testing single-core stability, because the cores cannot boost as high if all of them are stres tested, and therefore you won't be able to detect instabilities that only occur at a higher clock speed. For example, with my 5900X I was able to run a Prime95 all-core stress test for 24 hours with an additional Boost Override of +75 MHz and a Curve Optimizer setting of -30 on all cores. However, when using this script, and with +0 MHz Boost Override, I needed to go down to -9 on one core to have it run stable (on the other hand, another core was still happy with a -30 setting even in this case).

When you start the script for the first time, it will generate a config.ini file, in which you can then change various settings, e.g. which mode the stress test program should run in (e.g. for Prime95 SSE, AVX, AVX2, CUSTOM, where SSE causes the highest boost clock, because it's the lightest load on the processor of all the settings), how long an individual core should be stressed for before it cycles to the next one, if certain cores should be ignored, etc. For each setting there's also a description in the config.ini file.

As a starting point for Ryzen systems you could set the Curve Optimizer to e.g. -15 or -20 for each core and then wait and see which core runs through fine and which throws an error. Then you could increase the setting for those that have thrown an error by e.g. 2 or 3 points (e.g. from -15 to -13) and decrease those that were fine by 2 or 3 further into the negative (-15 to -17). Once you've crossed a certain point however there is no way around modifying the value by a single point up/down and letting the script run for a long time to find the very last instabilities.

By the way, by default it is configured so that only one thread is stressed for each core if Hyperthreading / SMT is enabled, as the boost clock is higher this way, compared to if both (virtual) threads would be stressed. But there is a setting in the config.ini to enable testing with two threads as well.

INCLUDED SOFTWARE

The script itself is a PowerShell script, but it uses other, inlcuded software to do the actual stress testing, for example Prime95, y-cruncher, and Intel's Linpack. You can also move your own copy of the stress test programs in to the respective folders in the /test_programs/ directory (e.g. /test_programs/p95 for Prime95, /test_programs/y-cruncher for y-cruncher, etc). For example if you want to be on the safe side (good choice!) or want to use a dedicated version. However be aware that the stress test programs can change their settings from time to time, so if you include a version that has not been tested with CoreCycler, it may not work as intended or not even start at all.

To download Prime95, go to the official site: at https://www.mersenne.org/download/ To download y-cruncher, go to the official site at: http://www.numberworld.org/y-cruncher/#Download To download Linpack, go to the official site at: https://www.intel.com/content/www/us/en/developer/tools/oneapi/onemkl-download.html To download older versions of Linpack, you can use the Internet Archive: https://web.archive.org/web/*/https://registrationcenter-download.intel.com/* And filter for e.g. "mkl .exe" to get a list of all archived Linpack versions.

CoreCycler also supports Aida64, which however is NOT directly included due to its license. You need to download the >>>Portable Engineer<<< version yourself and extract it into the /test_programs/aida64 folder. It has to be the Portable Engineer version, because the regular "Extreme" edition doesn't support starting the stress test from the command line. To download Aida64 Portable Engineer, go to the official site at: https://www.aida64.com/downloads You can use the trial version for up to 30 days, which should give you enough time to find your stable settings.

TROUBLESHOOTING & FAQ

Q: What does "Set to Core X (CPU Y)" (e.g. "Set to Core 6 (CPU 12)") mean? A: CoreCycler - as the name suggests - cycles through your cores and informs you on which core it is currently running. When Hyperthreading / Simultaneous Multithreading (SMT) is enabled, each physical core contains two "virtual" CPUs, effectively doubling the amount of CPUs available to you (at least for Ryzen and Intel P-Cores). Since Cores and CPUs generally start with 0 (zero-based), as seen in the BIOS and in the Task Manager, CoreCycler also uses this format. So "Core 0" means your first core, and "CPU 0" the first virtual CPU. "Core 6 (CPU 12)" respectively means it's running on the 7th core (remember, zero-based!) and 13th virtual CPU.

Q: The core I select in Ryzen Master isn't the same as here! A: Yes, Ryzen Master starts it's core numbering with 1. Only AMD knows why, it's not the industry standard. In the BIOS the core numbering starts with a 0, in Windows Task Manager the CPU numbering starts with a 0, in Intel Extreme Tuning Utility the numbering starts with 0, and therefore also in CoreCycler the numbering starts with a 0. Blame AMD for breaking this naming convention.

Q: My computer crashes when running this program! A: Very likely your Boost or Curve Optimizer setting is unstable. Reduce your clock speed, increase your voltage, resp. change the CO setting to a higher or more precisely less negative value (e.g. from -15 to -12) and try again.

Q: How long should I run this for? A: Basically as long as you can. If you aim for a "12h prime-stable setup", you'd need to run every single core for 12 hours, which for a processor with 12 cores like the 5900X would sum up to a total of 144 hours of stress testing. Of course, you can also settle for less - that's totally up to you.

Q: Which setting should I use to test? A: Short answer: as many as cou can. Long answer: I've defaulted this to Prime95 without AVX and AVX2 and "Huge" FFTs. The reason behind this is that this should produce the least amount of heat and therefore the highest boost clock. But you should eventually run all of the tests to make sure that you're really error free. Also switching from Prime95 to y-cruncher, Linpack or Aida64 produces different load scenarios, which can prove useful in detecting instabilities. For y-cruncher, "04-P4P" and "19-ZN2 ~ Kagari" seem to produce the fastest results, at least for Ryzen CPUs.

Q: Why are you using SSE? AVX stresses the CPU much more! A: Yes, AVX/AVX2/AVX512 does stress the CPU more than the SSE mode. However, it is exactly this additional load on the core wich prevents the boost clock from reaching its maximum (because it is temperature and load dependent), and so you can't really detect these edge cases which eventually can cause an error sooner or later. So, while being somewhat counterintuitive, the SSE mode with its lighter load is actually the one that can find stability problems, which tests using AVX/AVX2 simply cannot. On the other hand, not testing the AVX/AVX2 instructions will also not test the transistors associated with these instructions, so you're not "fully" testing your chip. So you should indeed test both scenarios, light load / SEE and heavy load with AVX/AVX2. You can change the mode to SSE, AVX, AVX2 or AVX512 for Prime95 and Aida64 in the config.ini, and for y-cruncher you can select different test modes which require different instruction sets.

Q: What settings can I change? A: The /configs/default.config.ini contains details and an explanation for each setting, so take a look there.

Q: When starting the tool I see a "FATAL ERROR: Could not access the Windows Performance Process Counter!" message! A: For some stress test programs the script needs to check the CPU utilization to determine if here has been an error. For this, the tool requires the Windows Performance Process Counter (PerfProc) to work correctly. It may have been disabled, you can check this with either lodctr.exe /q:PerfProc or with reg.exe query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance /s and look for a "Disable Performance Counters" entry with a value larger than 0. There are various tutorials on how to re-enable the Performance Counter on the web, here are some links: https://leansentry.zendesk.com/hc/en-us/articles/360038645792-How-to-Fix-performance-counter-issues https://docs.microsoft.com/en-us/troubleshoot/windows-server/performance/manually-rebuild-performance-counters

I've also included a batch file in the /tools/ directory (enable_performance_counter.bat), which should perform all these actions for you, but no guarantees that it will actually work!

Q: When starting the tool I see a "FATAL ERROR: Could not get the localized Performance Process Counter name!" message! A: See above. You probably need to re-enable the Windows Performance Process Counter (PerfProc).

Q: When starting the tool I see a "FATAL ERROR: .NET could not be found or the version is too old!" message! A: This tool requires the .NET Framework with at least version 3.5. You can download .NET here: https://dotnet.microsoft.com/en-us/download/dotnet-framework/net481 https://dotnet.microsoft.com/en-us/download/dotnet

Q: I have overclocked my RAM and I see errors when running this program, but I'm sure my CPU is fine! A: The errors may actually come from your overclocked RAM and not your CPU directly. Best practice for overclocking is to separately test the memory overclock and the CPU overclock, i.e. test your CPU while your memory runs at stock speeds. After you're sure that both overclocks are stable on their own, you can combine them and check for instabilities again.

Q: My script freezes! It appears to be running but I see no new output! A: PowerShell scripts seem to freeze when you select some text or click with the mouse into the terminal window (which selects the current position of your cursor). Try to hit Return and see if the execution continues. See e.g. here: https://stackoverflow.com/questions/3204423/long-running-powershell-script-freezes

LICENSE AND ALL THAT STUFF

This script is provided under the "CC BY-NC-SA" Creative Commons license. Or to put it in their words: "This license lets others remix, adapt, and build upon your work non-commercially, as long as they credit you and license their new creations under the identical terms."

You are free to: Share - copy and redistribute the material in any medium or format Adapt - remix, transform, and build upon the material The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms:

Attribution You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
NonCommercial You may not use the material for commercial purposes.
ShareAlike If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
No additional restrictions You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

You can find the full license text here: https://creativecommons.org/licenses/by-nc-sa/4.0/ https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode

And also in the included LICENSE file.

So feel free to share it, modify it and adapt it to your needs, but if you find any bugs, errors or have improvement ideas, please let me know at:

https://github.com/sp00n/corecycler

The licenses of all included programs remain unaffected by this and retain their original, included license!

Prime95 https://www.mersenne.org/legal/
y-cruncher http://www.numberworld.org/y-cruncher/license.html
Linpack (current version) https://www.intel.com/content/www/us/en/developer/tools/oneapi/onemkl.html
Linpack (all included versions) 2024.2.1.0 (2024.2.0.662) - https://web.archive.org/web/20240722184607/https://registrationcenter-download.intel.com/akdlm/IRC_NAS/7816a8cf-2378-4d49-bfa6-6013a3d7be6a/w_onemkl_p_2024.2.0.662_offline.exe 2021.4.1.0 (2021.4.0.640) - https://web.archive.org/web/20211115133152/https://registrationcenter-download.intel.com/akdlm/irc_nas/18230/w_onemkl_p_2021.4.0.640_offline.exe 2019.0.3.1 (2019.3.203) - https://web.archive.org/web/20190509182800/https://registrationcenter-download.intel.com/akdlm/irc_nas/tec/15247/w_mkl_2019.3.203.exe 2018.0.3.1 (2018.3.011) - https://web.archive.org/web/20220412021802/https://registrationcenter-download.intel.com/akdlm/irc_nas/9752/w_mklb_p_2018.3.011.zip
WriteConsoleToWriteFileWrapper https://github.com/sp00n/WriteConsoleToWriteFileWrapperDll?tab=MIT-1-ov-file https://github.com/sp00n/WriteConsoleToWriteFileWrapperExe?tab=MIT-1-ov-file
APICID https://github.com/sp00n/APICID?tab=MIT-1-ov-file
BoostTester.sp00n https://github.com/sp00n/BoostTester?tab=Unlicense-1-ov-file
CoreTunerX https://github.com/CXWorld/CoreTunerX?tab=License-1-ov-file
IntelVoltageControl https://github.com/jamestut/IntelVoltageControl?tab=MIT-1-ov-file
ryzen-smu-cli https://github.com/rawhide-kobayashi/ryzen-smu-cli?tab=GPL-3.0-1-ov-file
SMUDebugTool https://github.com/irusanov/SMUDebugTool?tab=GPL-3.0-1-ov-file

Happy testing! sp00n

zamesin/Next-Move-Theory-Canon-and-Skills

Claude Code skills for product market research, value props, PRDs, and go-to-market — plus the open Next Move Theory (based on AJTBD) canon and a product advisor you can /ask-nmt

Next Move Theory Canon & Skills

Next Move Theory is a methodology with a step-by-step algorithm for every product decision: it lays out every tactical and strategic move open to you and helps you choose the best, with the odds on your side.

Advanced JTBD — v3.4 · stable. The proven foundation. Next Move Theory — v0.6 · in active development — integrating AJTBD with Riskiest Assumption Test, ABCDX Segmentation, Theory of Constraints, and Unit Economics into one operational system. Forming in the open — track it to 1.0. (changelog)

This repository holds the open canon (the methodology, written as theses) and a set of Claude Code skills that run it. It's written for the people who decide what to build: founders, indie hackers, product managers, and product marketers. The methodology and the skills are by Ivan Zamesin (X · LinkedIn).

How to start

Install it — run the install command from Install into your project ▸. The macOS / Linux one-liner, the git clone route, and the Windows PowerShell installer are all there.
Then run /nmt-chat (Claude Code) or $nmt-chat (Codex). It's the human front door to the whole methodology: paste whatever you have — a half-formed idea, messy notes, a chat thread, a doc — and it pulls out the context, separates what you know from what you're assuming, and gives you the next concrete move. No methodologically-perfect brief required.

There is an algorithm

There is an algorithm for making any product decision.

Next Move Theory is the algorithm behind every product call: how to find product-market fit, scale, position, grow conversion, improve retention. It works at every level, from this sprint's tactics to the company's strategy. There is one for each of the questions that decide a product's fate:

How to launch a product and find Product-Market Fit
How to scale a product
How to save a dying product, or know when it's time to shut it down
How to create value
How to differentiate from competitors
How to position a product
How to exit direct competition
How to create a Disruptive Innovation
How to grow conversion
How to raise average order value
How to improve retention
How to build an acquisition channel

It lays out every move open to you. Most decisions feel like a coin flip because you only see the one option you'd already fixed on. Next Move Theory lays out every tactical and strategic move actually open to you, including the ones you'd have missed.

It helps you choose the best. Scores give you comfort, not direction — you can rank a feature 1,200 and still be wrong. Next Move Theory weighs each move by how much it shifts your goal and points you to the best, with the reason why.

More of your bets land. That's the whole point. Hundreds of companies run on Next Move Theory, and across dozens of documented cases the metrics moved significantly — conversion, retention, revenue, market share.

This canon is the result of the last eight years of my work. Eight years ago I found Jobs To Be Done, saw how much it could become, and made an unreasonable decision: rebuild it from scratch so it would finally yield an algorithm. It only became that when I got lucky and found the science that explains what value really is and how a person changes behavior. That body of science sits in scientific-foundations.md, and everything else stands on it. On that foundation I rebuilt JTBD into thousands of theses, the core I call Advanced Jobs To Be Done. AJTBD alone still didn't produce the algorithm. To get there I folded in Unit Economics, the Riskiest Assumption Test, ABCDX segmentation, and Goldratt's Theory of Constraints. That integration became Next Move Theory. I've since taught it to more than 13,000 people in my home country, and this public canon is how I give its foundations to the world.

The main algorithm is here in full. Read it in the-algorithm.md. Reading the steps isn't enough, though. For the algorithm to work for you, you have to understand the foundations it runs on: what a Job is, what value is, how to segment, how to test the riskiest assumption first. That is what the rest of this canon is. These are the foundational theses the algorithm stands on, so it works for you instead of reading like an empty checklist.

The skills turn that algorithm into tools: feed in a product idea and get back a decision, not a description.

I find this methodology beautiful and powerful, and sharing it with the world is my mission. I hope it brings you real value and lets you see the moves in front of you clearly.

Who this is for

This canon is written for product builders. Same algorithm, and here's the win it lands for each:

Founders — decide what to build, with the odds on your side. See every tactical and strategic move open to you, find the Job customers will actually pay for, and pick the strategy that wins before you bet the next three months on a hunch.
Indie hackers / vibe-coders — pick a niche that actually pays. Writing code was never the problem; choosing what to ship is. Let the methodology pick the Job people pay for, so the next build is the first one with real buyers.
Product managers — a roadmap that moves the metric, not theater. Run the logic from the foundations up, find where the metric actually breaks, ship the few moves most likely to shift it, and raise the odds of growth.
Senior PMs / VPs / CPOs — the operating system your product org runs on. When every team reasons from the same strong foundations, tactic to strategy, you can stand behind every call and more of your bets pay off.
Product marketers / growth — positioning that isn't "yet another X." Find the angle in the customer's real Job, not channel tactics, and the odds it converts climb before you spend a dollar.

If you build, market, or decide the direction of a product, this is for you. You don't have to throw out what you already know. Customer interviews, CJM, ICP, willingness-to-pay, and feature backlogs all still work. They just get grounded in the right unit of analysis and tied to real business decisions instead of floating free. Expect the rewire to take practice. Most people arrive with a feature-first or persona-first model, and the Job-first model takes a few honest attempts before it feels natural.

What's here — and what's coming

This public canon is the foundation, about 25% of the whole methodology. What you have here are the foundational theses of Advanced Jobs To Be Done and Next Move Theory: what a Job is, what value is, how segmentation works, behavior change, the Job Graph, and the Riskiest Assumption Test. It also includes the main algorithm itself (the-algorithm.md).

The rest of the methodology is not coming to this public repo. It lives in the full version, available through the products and courses at nextmovetheory.com. Beyond the foundations here, the full methodology covers:

the product-diagnosis algorithm;
the step-by-step algorithms for the questions listed at the top — launch and find Product-Market Fit, scale, save a dying product, position, exit competition, grow conversion, raise average order value, improve retention, build an acquisition channel, and the rest;
the full 100+ mechanics catalog;
generating product ideas and feature ideas;
goal-setting — the algorithm for finding a company's real growth points;
demand creation and acquisition channels — how the methodology runs at the delivery stage;
branding — how to build and run a brand on Jobs;
process principles and the algorithms for rolling the methodology out across a company;
Customer Success and Support built on Jobs;
the full unit-economics integration, and more.

Subscribe to the newsletter at nextmovetheory.com so you don't miss new free materials, courses, and products as they go live.

The skills

The Skills/ directory holds the skills that run the methodology for you — a claude/ tree for Claude Code (invoke with /nmt-…) and a codex/ tree for OpenAI Codex (invoke with $nmt-…). Each skill reads the canon at runtime, so its output is grounded in this methodology, not the generic JTBD an LLM would otherwise reach for. The two trees carry the same methodology; the Codex copy only swaps Claude-specific mechanics (structured questions, parallel sub-agents) for their Codex equivalents.

Skill	What it does
`nmt-chat`	A conversational advisor you can talk to. Ask any product, strategy, segmentation, value, pricing, growth, positioning, B2B, or methodology question and get an answer grounded in the canon, not generic JTBD. It explains concepts, diagnoses your real situation, pressure-tests your hypotheses like a skeptical senior PM, and hands off to the producer skills below when you want a full artifact.
`nmt-diagnose`	A chat-first diagnostic for live products. Through up to ~15 adaptive questions it challenges the goal you walked in with (climbing your business-Job graph for a higher-leverage move), then surfaces all the risks, all the growth points, and the risky assumptions hiding inside your current initiatives. It prioritizes the first move and routes you to the skill that executes it. The front door for an existing product the way `nmt-market-research` is for a new idea.
`nmt-market-research`	Sizes the market and scores segments to answer "which Jobs of which segment should we compete for first?" Output: a GO / NARROW / PIVOT one-pager, segments scored on a five-factor screen, direct and indirect competitors, an action-first RAT plan, and alternative Big-Job markets to pivot into.
`nmt-craft-value-proposition`	Takes a chosen segment + Jobs and builds the strongest Value Proposition: value hypotheses mapped over the Job Graph and the value-creation mechanics, filtered on feasibility, unit-economics, and competitiveness, ranked, with the top RAT cards. Output includes a PRD-ready implementation spec.
`nmt-product-requirements`	Turns the chosen segment + value into a build-ready PRD (full functionality + edge cases). First it runs a "challenge the build" gate that hunts for a cheaper way to hit the same business goal before specifying the build.
`nmt-craft-go-to-market`	Turns the value proposition into ready-to-publish go-to-market: landing-page copy, ad / creative formulas, and an acquisition + growth-communication plan (channels loaded with Consideration Activators, lead magnets, viral loops, retention messaging).
`nmt-analyze-interviews`	Takes customer-interview files you already have (transcripts, notes, sales/support calls, survey open-ends) and extracts the AJTBD structure: segments by Core Jobs, personas, existing Solutions and Problems, a Consideration Set, and value hypotheses — each with an honest confidence — plus a gap list of what to interview next. The post-fieldwork counterpart to the interview guide.

Two front doors. /nmt-chat is the conversational front door for advice, explanation, or pressure-testing an idea. /nmt-diagnose is the front door for a live product: it finds your risks and growth points and routes you to the next move. Both answer from the canon and point you to the right producer skill when you need a full artifact. For a brand-new idea, start at /nmt-market-research.

The four producer skills form a pipeline, each one building on the artifact the one before it produced:

/nmt-market-research → pick the segment and the Core Jobs to compete for (with the GO / NARROW / PIVOT verdict and the riskiest assumptions to test).
/nmt-craft-value-proposition → feed it the nmt-market-research result; get the value proposition plus a PRD-ready implementation spec.
From the value proposition, branch to either (or both):
- /nmt-product-requirements → the build-ready PRD, what to build. It consumes the segment from step 1 and the value from step 2.
- /nmt-craft-go-to-market → the landing page, ads, and growth plan, how to sell it. Works best from the value proposition; also accepts the PRD or the nmt-market-research result.

You can also jump in mid-pipeline if you already know your segment and Jobs. Each skill takes what you hand it, or routes you back to the step it needs first.

All seven are user-invocable — in Claude Code as /nmt-chat, /nmt-diagnose, /nmt-market-research, /nmt-craft-value-proposition, /nmt-product-requirements, /nmt-craft-go-to-market, /nmt-analyze-interviews; in Codex as the same names with a $ ($nmt-diagnose, …), or pick them from /skills. The shared nmt- prefix keeps the whole family together in the picker. The four producers each have a fast Quick mode (no internet) and a deeper Deep mode (web research; parallel sub-agents on Claude Code, sequential on Codex). /nmt-chat and /nmt-diagnose are conversational (no file unless you ask).

The skills produce hypotheses, not conclusions. Every number is an LLM-generated estimate with a verification path attached. Validate before any decision with expensive consequences. That's the RAT discipline the methodology is built on.

Install into your project

Install the canon + skills into the root of your existing project (the folder you run your agent from) with one command:

macOS / Linux:

curl -fsSL https://nextmovetheory.com/install.sh | bash

Windows (PowerShell): clone the repo, then run the PowerShell installer:

git clone https://github.com/zamesin/Next-Move-Theory-Canon-and-Skills
powershell -ExecutionPolicy Bypass -File Next-Move-Theory-Canon-and-Skills\install.ps1 -Target .

That's the whole install: clone + setup in one step, so there's nothing to "run next." It lays everything into your project root. After install that root looks like:

your-project/
├── .claude/skills/<skill>/        # skills for Claude Code — invoke with /nmt-…
├── .agents/skills/<skill>/        # skills for Codex        — invoke with $nmt-…
├── Next-Move-Theory-Canon/        # the canon — keep this exact name (skills read it by this path)
├── AGENTS.md                      # your existing file — rules injected between markers
├── CLAUDE.md                      # your existing file — rules injected between markers
└── NextMoveTheory-README.md       # this README, renamed, for reference

Already ran git clone and got a nested Next-Move-Theory-Canon-and-Skills/ folder? That's just the raw repo, not an install. Fix it in one step. From inside that folder run:

bash install.sh            # installs into the PARENT dir (your project root)
# or: bash install.sh --target /path/to/your/project

Then invoke a skill — /nmt-… in Claude Code, $nmt-… in Codex:

/nmt-diagnose            # Claude Code — what should I do next with my product?
$nmt-diagnose            # Codex — same skill
/nmt-market-research a tool that drafts SOC 2 evidence for early-stage SaaS

Updating later: re-run the install command. It's idempotent: the canon and skills are replaced, the rules between  …  are refreshed in place, and your own text outside the markers is untouched.

Note for AI agents: if a user asks you to "install this repo," do not stop at git clone. That leaves the skills in a nested Skills/ folder where no agent will find them. Run the one-command installer (bash install.sh on macOS/Linux, install.ps1 on Windows). The skills must end up in .claude/skills/ (Claude Code) and .agents/skills/ (Codex) at the project root, never in a top-level Skills/ folder.

What the installer does (manual equivalent)

The installer enforces these rules: everything lands in the project root; .claude/.agents/canon are never nested inside one another; the Claude skills go inside .claude/skills/ and the Codex skills inside .agents/skills/ (never a standalone top-level Skills/); the canon folder keeps the exact name Next-Move-Theory-Canon (skills read it by that relative path); the rules are injected between markers into your existing CLAUDE.md/AGENTS.md (not a separate file, not overwriting your content); the README is copied in renamed; and re-running is idempotent. The equivalent by hand:

SRC=$(mktemp -d) && git clone --depth 1 https://github.com/zamesin/Next-Move-Theory-Canon-and-Skills.git "$SRC"
rm -rf ./Next-Move-Theory-Canon && cp -r "$SRC/Next-Move-Theory-Canon" ./Next-Move-Theory-Canon
mkdir -p .claude/skills .agents/skills
cp -r "$SRC"/Skills/claude/. .claude/skills/   # Claude Code copy
cp -r "$SRC"/Skills/codex/.  .agents/skills/   # Codex copy
cp "$SRC/README.md" ./NextMoveTheory-README.md
# then inject the rules block from "$SRC/CLAUDE.md" and "$SRC/AGENTS.md" between the markers
rm -rf "$SRC"

Make your AI agent methodology-aware

This repo also ships CLAUDE.md and AGENTS.md, a compact rules file that teaches a coding agent (Claude Code, Codex, Cursor, and others) to do product work with this methodology instead of the generic, often-wrong Jobs To Be Done in its training data.

What it is — the non-negotiable theses (what a Job is, what value is, how to segment) plus a routing table that tells the agent which canon file to read for a given task, so it avoids the common JTBD mistakes.
How to use it — the install above injects it for you: step 4 writes these rules into your project's CLAUDE.md (Claude Code) and AGENTS.md (Codex and most other agents), between  …  markers, so updates refresh cleanly and your own rules outside the markers stay intact. The canon it routes to sits at ./Next-Move-Theory-Canon.
Why — out of the box an agent pattern-matches to generic JTBD and gets the theses wrong. This file points it at the correct definitions and the canon, so its product reasoning is grounded in the methodology.

How to read the canon

Prefer a nicer reading experience? The same canon is available in a cleaner, more readable form on the site — read it at nextmovetheory.com/library/canon.

The canon lives in Next-Move-Theory-Canon/, around two dozen interlinked files. You don't have to read them in order. If you want the fastest path to understanding, read these four key-theses files first, in order:

Next-Move-Theory/nmt-key-theses.md — the integrative root: what the whole framework is and how its pillars (AJTBD, Unit Economics, RAT, ABCDX) plus Theory of Constraints — with OKR (Objectives & Key Results) as a supporting methodology — fit into one system. Start here for the big picture.
Advanced-Jobs-To-Be-Done/ajtbd-key-theses.md — the substrate the rest stands on: Jobs, the Job Graph, value and the Aha Moment, segmentation. The core you'll use most.
Riskiest-Assumption-Test/rat-key-theses.md — before you build: list the assumptions the idea rests on, rank them by how lethal they are if wrong, and buy the cheapest evidence against the deadliest first.
ABCDX-Segmentation/abcdx-segmentation-key-theses.md — the theory turned into a concrete operating move on a real customer base: focus the high-margin A/B, fire C/D, and read X as the signal of where to grow next.

Then read the rest in whichever cluster matches your problem.

Advanced Jobs To Be Done — Foundations

File	What it teaches
`Advanced-Jobs-To-Be-Done/ajtbd-key-theses.md`	The foundational theses — the methodology in one document. The map to everything else.
`Advanced-Jobs-To-Be-Done/scientific-foundations.md`	The brain as an energy-budget investor; why needs fail as a unit and Jobs succeed.
`Advanced-Jobs-To-Be-Done/job-structure.md`	The eight elements that fully specify a single Job, element by element, with interview questions.

The Job Graph — where strategy lives

File	What it teaches
`Advanced-Jobs-To-Be-Done/job-graph.md`	The hierarchy of Jobs around your product; the four levels, defined relative to your product's reach.
`Advanced-Jobs-To-Be-Done/job-types-and-properties.md`	The taxonomy of Jobs — Regular, Orientation, Tax, Fake, Emotional, Viral — as a diagnostic instrument.
`Advanced-Jobs-To-Be-Done/critical-chain.md`	The Job Graph projected onto time — the lived path a team actually ships, where the Aha Moment fires.

Creating value

File	What it teaches
`Advanced-Jobs-To-Be-Done/value-creation.md`	The deep canon on value: energy efficiency, success criteria as the specification of value, the Aha Moment.
`Advanced-Jobs-To-Be-Done/value-creation-mechanics.md`	The foundational catalog of value-creation mechanics — kill a Job, take a Job off the customer, climb a level.
`Advanced-Jobs-To-Be-Done/behaviour-change.md`	Why switching is swapping one Job Graph for another; a Solution as a label for the sub-graph it installs.
`Advanced-Jobs-To-Be-Done/customers-attention-management.md`	Attention as the metabolic resource every value-creation mechanism routes through.

Reaching and converting customers

File	What it teaches
`Advanced-Jobs-To-Be-Done/consideration-activators.md`	The five Consideration Activators — what you load into the customer's head to move their choice your way.
`Advanced-Jobs-To-Be-Done/barrier-removal.md`	Removing the objective barriers that make a better Job Graph non-executable for a segment.
`Advanced-Jobs-To-Be-Done/communication.md`	Communication in the language of Jobs — the value-proposition formula and the landing-page structure.

Choosing where to compete

File	What it teaches
`Advanced-Jobs-To-Be-Done/segmentation.md`	Segmentation by Job Graph similarity, not demographics — the most expensive cut to get wrong.
`ABCDX-Segmentation/abcdx-segmentation-key-theses.md`	ABCDX — splitting your paying base by margin × satisfaction; refocus on A/B, fire C/D, read X as a signal.
`Riskiest-Assumption-Test/rat-key-theses.md`	RAT — list the assumptions an idea rests on, rank them by lethality, and buy the cheapest evidence first.

Next Move Theory — the meta-framework above AJTBD

File	What it teaches
`Next-Move-Theory/nmt-key-theses.md`	The integrative root — how AJTBD, Unit Economics, RAT, ABCDX, and Theory of Constraints combine into one system, with OKR as a supporting methodology. The product is a single organism.
`Next-Move-Theory/focus-as-company-attention-management.md`	Focus as pointing the whole company's attention at specific Core Jobs of one segment; the Innovator's Dilemma as focus that ossified.
`Next-Move-Theory/subtraction.md`	Subtraction as the meta-operator across all four pillars — removing Jobs, unprofitable units, risky assumptions, and C/D customers.

Practice, B2B, and the operating loop

File	What it teaches
`HowTos/basic-ajtbd-interview-guide-and-principles.md`	The practical interview guide — principles and a question bank that reconstruct Jobs, criteria, Aha Moments, and Barriers from what a customer actually did.
`Advanced-Jobs-To-Be-Done/b2b.md`	The B2B deal as a Job Graph across roles — and why personal Jobs usually outweigh business Jobs.
`Algorithms/the-algorithm.md`	How the pieces combine into a single cyclical algorithm — and the anti-patterns that kill products.

The public canon covers the most foundational theses and mechanics. The full methodology — the product-diagnosis algorithm, the 100+-mechanic catalog, the full unit-economics integration, and more — lives in the products and courses at nextmovetheory.com. For new theses and book chapters as they're published, subscribe at nextmovetheory.com — home to the canon, the books, and the newsletter.

What's inside

Next-Move-Theory-Canon-and-Skills/
├── Next-Move-Theory-Canon/             # the methodology, written as theses
│   ├── Advanced-Jobs-To-Be-Done/       #   the Jobs framework — start with ajtbd-key-theses.md
│   ├── ABCDX-Segmentation/             #   segmenting a paying base by margin × satisfaction
│   ├── Riskiest-Assumption-Test/       #   validating ideas before you build them
│   ├── Next-Move-Theory/               #   the integrative meta-framework above AJTBD
│   ├── HowTos/                         #   practical guides — start with the interview guide
│   └── Algorithms/                     #   how the pieces combine into one loop
└── Skills/                      # the skills that run the methodology
    ├── claude/                         #   Claude Code copy — invoke with /nmt-…
    │   ├── nmt-market-research/
    │   ├── nmt-craft-value-proposition/
    │   └── nmt-product-requirements/
    └── codex/                          #   Codex copy — invoke with $nmt-…
        └── nmt-…/

How this methodology came to be

By 2018 I taught product for a living: customer research, segmentation, interviews. Yet at the root I didn't actually know how products get created. The model I taught was find the pain, build the painkiller. But I kept watching satisfied customers with no problem to solve buy anyway, and I had no explanation for it. I was also building my own company against a stronger competitor, with no rule for choosing a strategy, only a pile of plausible advice. So I made an unreasonable decision: build the methodology from scratch.

I went deep into Jobs To Be Done and kept its deepest intuition: a person sits in a situation and wants to transition into a different state. I left the rest of the machinery behind, because it never told me how to research, segment, choose where to compete, or create value.

It only came together when I got lucky and found the right science. Lisa Feldman Barrett's work led me to allostasis, prediction, and reward prediction error, which is what value actually is to a brain managing an energy budget. It also led me to the theories of needs, emotions, habit, identity, and loss aversion that explain how a person changes behavior. That body of science sits in scientific-foundations.md, and everything else stands on it. On top of it I could finally build a real algorithm for creating value, the core I called Advanced Jobs To Be Done (AJTBD).

AJTBD alone still wasn't enough. A few more methodologies turned out to be fundamental. First the Riskiest Assumption Test. Every initiative is a stack of risky assumptions, any of which might not hold, so you don't just launch and hope. In a sense the idea is already dead and you simply don't yet know what will kill it. RAT is how you find out cheaply, before you've paid for the build. Then Unit Economics. A company can only grow and fund its next bets by competing for the Jobs of segments where it can actually earn a target margin. Goldratt's Theory of Constraints taught me to find the single bottleneck that limits the system and fix that, instead of improving everything at once. Later I added goal-setting, an algorithm for finding a company's real growth points. Together it all became Next Move Theory.

Today hundreds of companies in my home country run on this work, with dozens of cases documented at nextmovetheory.com/cases. My goal now is to give the methodology to the world, so your product work stops being guesswork and becomes something you genuinely enjoy. The full story, with the scenes, the mistakes, and the moments where the wrong model stopped working, is the subject of my book.

The book — The Nature of Product

The Nature of Product is free to read on the site. It's the first book in a series, and it covers the foundation, Advanced Jobs To Be Done (AJTBD), rather than the whole of Next Move Theory. The broader framework comes in later books. Where the canon states the methodology as theses, the book tells the story of how it was discovered. It's a chain of insights, each one a moment where the wrong model stopped working and a better one had to be built. A recurring skeptic, Wes, attacks the ideas with the exact questions real students used.

It's for founders, indie hackers, PMs, marketers, and designers making product decisions on incomplete evidence, and it assumes no prior Jobs To Be Done background. Read it on the couch. The canon and skills are here when you want to get operational.

About the author

Ivan Zamesin is the author of Advanced Jobs To Be Done and Next Move Theory. Two independent industry studies ranked him the #1 product expert in his home market.

Led image search at his home market's largest tech company. Took 25% of the market from Google Images, growing share from 55% to 72%.
Trained 13,000+ founders and product managers through the most popular product course in his home market, running since 2017.
Founded and sold a startup. A therapist-matching service: built it, grew it, and exited to a larger marketplace.
Product-strategy consulting for market leaders, built on Jobs and unit economics.

nextmovetheory.com · X · LinkedIn · ivan@nextmovetheory.com

Talks & questions

Want me to speak? If you'd like me to walk your team, company, or event through the methodology — a talk, a workshop, or a conversation about how it applies to your product — I'd genuinely welcome that. Email me at ivan@nextmovetheory.com or reach out on LinkedIn.

Found an error in a thesis or a broken link? Open an issue or a pull request.

License

The canon and the skills are licensed under CC BY-NC-SA 4.0 (Creative Commons Attribution–NonCommercial–ShareAlike 4.0 International) — see LICENSE. You are free to share and adapt the material, as long as you:

Attribution — credit Ivan Zamesin and link back to this repository and the license;
NonCommercial — don't use the material for commercial purposes;
ShareAlike — license your adaptations under the same terms.

Can I use this inside my company — even a for-profit one? Yes. The license — and copyright generally — covers the material (the canon text, the skills code), not the ideas in it. Methods, processes, and principles aren't copyrightable, so applying the methodology is not a use the license governs at all. Read it, run the skills on your own product, segment your customers, build your metrics, and make product decisions on it — at any company, commercial or not. The NonCommercial term restricts only what you do with the material itself: reselling copies, bundling the text into a paid product or course, or putting it behind your own paywall. Attribution and ShareAlike kick in only when you share or adapt the material — not when you put what you learned to work. (This is the common-sense reading of the license, not legal advice; for high-stakes decisions, check with a lawyer.)

A note on the writing. I built this methodology over eight years in my own language, where it grew into thousands of theses. To bring it into English, I used Claude to render those theses as the text you're reading. The thinking is entirely mine, worked out over years of practice and teaching; the AI handled the English wording, not the ideas behind it.

Built by Ivan Zamesin. nextmovetheory.com · X · LinkedIn · ivan@nextmovetheory.com. The canon is a living document; it grows as new theses are validated in practice.