AIcut Deployment Skill
This skill helps package and deploy AIcut as a standalone desktop application.
Prerequisites
Ensure you have:
- Node.js 18+
- Python 3.10+
- All dependencies installed (
bun installin AIcut-Studio)
Build Commands
Development
cd AIcut-Studio/apps/web
npm run dev # Start Next.js dev server
npm run electron # Start Electron (in another terminal)
Production Build
cd AIcut-Studio/apps/web
# Build Next.js first
npm run build
# Package for current platform
npm run electron:build
Platform-Specific Builds
The electron-builder config in package.json supports:
| Platform | Command | Output |
|---|---|---|
| Windows | electron-builder --win |
.exe installer, portable |
| macOS | electron-builder --mac |
.dmg, .zip |
| Linux | electron-builder --linux |
.AppImage, .deb |
Build Configuration
Located in AIcut-Studio/apps/web/package.json:
"build": {
"appId": "com.aicut.studio",
"productName": "AIcut Studio",
"directories": {
"output": "dist-electron"
},
"extraResources": [
{
"from": "../../../tools",
"to": "tools"
}
],
"win": {
"target": ["nsis", "portable"]
}
}
Including Python Tools
The extraResources section ensures Python scripts are bundled:
- Source:
tools/directory at project root - Destination:
resources/tools/in the packaged app
Environment Variables
For production, ensure these are set (or bundled in .env):
GROQ_API_KEY- For speech recognitionOPENAI_API_KEY- For AI features (optional)
Troubleshooting
Electron not found
node node_modules/electron/install.js
Python daemon not starting
Check electron/main.js for the Python spawn path. It should resolve correctly in both dev and production.
Large bundle size
- Ensure
node_modulesis not duplicated - Check if media files are being incorrectly bundled
Release Checklist
- Update version in
package.json - Run
npm run buildsuccessfully - Test
npm run electron:buildlocally - Verify Python daemon starts in packaged app
- Test core features (import, edit, export)
- Create GitHub release with built artifacts