windows-local-build
Skill from yybd/app-factory
Install
npx skills add yybd/app-factory --skill windows-local-build
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add yybd/app-factory
/plugin install windows-track@app-factory
This skill is part of the plugin “windows-track”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the windows-local-build skill do?
Description from the SKILL.md in the source repository.
Questions about windows-local-build
What does the windows-local-build skill do?
Build a Tauri app's Windows version on a Mac and test it in a local VM, with no GitHub Actions and no Windows PC: cross-compile the exe and NSIS installer with cargo-xwin, then install, run a windowless self-test, screenshot, cut the network and roll back snapshots in a Parallels VM through prlctl. Use when the user wants a Windows build without CI, has run out of Actions minutes, asks to cross-compile for Windows, test in Parallels or compare x64 and arm64, when makensis crashes with std::bad_alloc, or says "לבנות לווינדוס מהמק", "לבדוק בווינדוס בלי GitHub", "בנייה מקומית לווינדוס". It does NOT add the updater or write the feed (windows-direct-distribution), does not Authenticode-sign, and does not measure speed on real x64 hardware.
How do I install windows-local-build?
In a terminal: npx skills add yybd/app-factory --skill windows-local-build. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use windows-local-build?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is windows-local-build safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from yybd/app-factory
Find real bugs and broken flows in a Capacitor app — the JavaScript that runs inside the WebView and the seams where it meets the native shell.
Build an app's product profile — the one document every piece of copy about it is later derived from: store listings, site pages, campaigns.
Decide an app's NAME for both stores, and own the project README as the source of truth for the name, subtitle / short description, and detected feature list.
Set up the app factory in a repo, or say why its skills are not loading. Use when a store or release skill that should exist is missing, when the user asks …
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React …
Audit and manage the in-app localization of a Capacitor / web-shell app, whose UI strings live in JavaScript and HTML rather than in .strings, .xcstrings or strings.xml.
Take a built macOS app from an Xcode archive, package it into a signed DMG, notarize it with Apple, staple the ticket, and verify that everything — the app AND the DMG …
Audit and manage IN-APP localization for a macOS or iOS Xcode project — the user-facing strings inside the app (Localizable.strings / .xcstrings String Catalogs), NOT the App Store listing text.
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any …
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.