> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bach builds Windows installers from one bach.toml with the bach command: bach init, bach check, bach preview, bach build. Installs are per user and need no administrator rights by default. installer.scope = "machine" installs for every user after one Windows prompt. On Windows, run setup files with Start-Process -Wait -PassThru in PowerShell, and give signtool arguments that start with the word sign.

# Use Bach with coding agents: the Bach skill

> Install the Bach skill so coding agents like Claude Code and Codex can package a Windows app with bach.toml, and see the rules they follow when using it.

Bach ships a skill for coding agents, so an agent can package a Windows app without you explaining Bach first. The skill is a single `SKILL.md` that teaches the commands, the config and the safety habits.

## Install the skill

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
npx skills add usebach/bach
```

The skill lives at [skills/bach/SKILL.md](https://github.com/usebach/bach/blob/main/skills/bach/SKILL.md) in the repository.

## What the skill teaches

* How to get the `bach` command on Windows, macOS and Linux, with `npm install --global @usebach/cli` or the install scripts, never with administrator rights, and to run `bach doctor`.
* How to find or produce the one folder Bach installs, for Rust, Electron, Tauri, .NET, Go and PyInstaller apps.
* How to write `bach.toml` from the project's own metadata instead of inventing a name, version or publisher, and to never change `[app] id` after a release.
* To run `bach check`, treat every `warning:` as something to fix or mention, and look at the window with `bach preview`.
* To build with `bach build`, then sign, then write the feed or winget manifests.
* To add the one-click release with `bach workflow` instead of writing a workflow by hand, and to raise versions with `bach version` instead of editing several files. See [One-click releases](/docs/guides/releasing.md).

## Safe habits for agents

> [!WARNING]
>
> Never run a real install of the built setup file on someone's machine unless they ask.

* Use `bach preview` to see every page. It pretends each step and changes nothing.
* When a real end-to-end test is wanted, use a silent install and remove it again afterwards: `Setup.exe --silent`, then `uninstall.exe --silent`.
* Read the log at `%TEMP%\<app id>-setup.log` when something fails instead of guessing.
* Fix the setting that `bach check` names. Do not work around the checker.

## Read these docs as Markdown

Every page of this site can be copied as Markdown or opened in an AI assistant from the contextual menu at the top of the page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.