- Editor: Cursor, etc. Any VS Code compatible editor.
- Recommended extensions are listed in
.vscode/extensions.json.
- Install extensions: Biome, oxc
- Copy the example settings file to your local Zed config:
cp .zed/settings.json.example .zed/settings.json
- Customize
.zed/settings.jsonas needed (it is git-ignored).
This project uses symlinks to synchronize files such as AGENTS.md and skills. Windows developers must enable symlink support before cloning:
- Enable Developer Mode (Settings → Update & Security → For developers), or grant
SeCreateSymbolicLinkPrivilegeviasecpol.msc. - Configure Git:
git config --global core.symlinks true - Clone (or re-clone) the repository after enabling symlink support.
pnpm installThe required Node.js version is defined in .node-version. Use a version manager like nvm or fnm to install it automatically:
nvm installThe pnpm version is locked in the packageManager field of package.json. Just enable corepack and it will use the correct version automatically:
corepack enablepnpm installcp .env.example .envpnpm devBy default, development runs append Dev to Electron's default userData
directory, keeping local dev data separate from packaged app data. To run
multiple development instances at the same time, give each instance a unique
suffix. You can set it in .env:
CS_DEV_USER_DATA_SUFFIX=DevQuitoOr pass it inline when starting a dev instance:
CS_DEV_USER_DATA_SUFFIX=DevQuito pnpm dev
CS_DEV_USER_DATA_SUFFIX=DevParis pnpm devBlank values are ignored and fall back to Dev.
pnpm debugThen input chrome://inspect in browser
pnpm test# For windows
$ pnpm build:win
# For macOS
$ pnpm build:mac
# For Linux
$ pnpm build:linux