ffc-dev-desktop
Skill16 starsChanged 37 days agoMITView on GitHub
Change Foxmayn Frappe Desktop, the Wails v3 + React 19 + shadcn/ui (Base UI) app in desktop/ of the foxmayn_frappe_cli repository - the nested Go module and its services (AppService, SitesService, AssistantsService), events, the typed frontend backend layer and generated bindings, the browser mock mode, CI and desktop-v* releases. Use it whenever you touch anything under desktop/, the desktop workflows, or internal/ packages the app imports (sitesetup, mcpinstall, config, release, sitecache). Load ffc-dev first.
- Installs packages
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- desktop/CLAUDE.mdCLAUDE.md
- ffc-bulk-lifecycleSkill
- ffc-coreSkill
- ffc-dev-clientSkill
- ffc-dev-commandSkill
- ffc-dev-mcp-toolSkill
- ffc-devSkill
- ffc-dev-testingSkill
- ffc-files-collabSkill
- ffc-mcpSkill
- ffc-reports-apiSkill
- ffc-setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 53
Never make a desktop release GitHub's "latest": install.sh, install.ps1 and ffc up to v1.11.0 read releases/latest.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Foxmayn Frappe Desktop (desktop/)
A desktop app that manages ffc sites and connects AI assistants to them through the same Go code as the CLI. Windows and macOS only. desktop/README.md is the source of truth for features; read it first.
Module boundary
desktop/is its own Go module,github.com/nasroykh/foxmayn_frappe_cli/desktop. Its path under the ffc module path is what lets it importinternal/packages. Never rename it to an unrelated path.- Wails, Node and CGO stay in
desktop/go.mod, never in the rootgo.mod(the CLI release is CGO-free). - Root
go test ./...andgo vet ./...skip it; rootgofmt -l .does check its Go files. desktop.yml runs its own vet and tests. - The root
.gitignoreentry/foxmayn_frappe_cliis anchored on purpose: unanchored it ignored the bindings directoryfrontend/bindings/github.com/nasroykh/foxmayn_frappe_cli/. - The app reuses prompt-free, cobra-free packages:
internal/sitesetup(setup, OAuth, revoke),internal/mcpinstall(assistant entries),internal/config(onlyconfig.Edit/config.Overwrite),internal/release(installing ffc),internal/sitecache. Keep those packages free of prompts and cobra; a change there affects both programs.
Services (desktop/services)
| Service | Owns |
AppService | environment, ffc detection and installer (install.go, through internal/release, never by running install.sh/install.ps1), update check, opening links and folders |
SitesService | sites, OAuth sign-in, config watch |
AssistantsService | MCP entries through internal/mcpinstall with a preview first |
- Errors reach the UI as
services.Error(code,message,detail, ...). - Events:
config:changed,signin:progress,installer:log(constants in host.go). - Stored tokens and secrets never go back to the web view: services return sites without credentials; a typed secret travels only from the form to Go.
- The services'
TestMainpointssitecache.UserCacheDirat a temp dir; keep tests off the real config and cache.
Frontend (desktop/frontend)
src/lib/backend.tsis the typed layer over the generated bindings infrontend/bindings. Screens call backend.ts, never the bindings directly. After changing a service signature, regenerate:wails3 generate bindings -clean=true -ts -i, and commit the result. CI fails when the bindings orpackage-lock.jsondiffer after a build.- UI is shadcn/ui on Base UI: style
base-nova, Tabler icons, components insrc/components/ui. Base UI composes with therenderprop (<TooltipTrigger render={<SidebarTrigger />} />), not Radix'sasChild. - Mock mode:
npm run dev:mockindesktop/frontendserves the UI at http://127.0.0.1:9245 againstsrc/mock/backend.ts. Query parameters pick a scenario (?sites=none,?update=available,?update=fail,?ffc=missing,?wsl=1,?os=darwin,?signin=noreg,?slow=1,?fail=sites; full list at the top of the mock). Only the Vitemockmode aliases it, so production builds never contain it. Add a scenario when you add a state the UI must show. - The update check runs at most once a day (
localStoragekeyffd-update-checked).
Build and verify
go install github.com/wailsapp/wails/v3/cmd/wails3@v3.0.0-beta.28 # match desktop/go.mod
cd desktop/frontend && npm ci && npm run build # go vet/test need frontend/dist
cd .. && go vet ./... && go test ./...
wails3 dev # hot reload
wails3 build # binary in desktop/bin/desktop.yml runs on windows-latest and macos-latest when desktop/, internal/ or go.mod change: npm ci, tsc + vite build, go mod tidy -diff, vet, tests, wails3 build, bindings and lockfile unchanged, govulncheck (macOS).
Releases
- Tag
desktop-v<semver>(neverv*, which is the CLI release) after writingdesktop/release-notes/<version>.md..github/workflows/desktop-release.ymlbuilds a per-user NSIS installer (Windows amd64) and a universal macOS dmg, signschecksums.txtwith relsign, attests provenance, and publishes with--latest=false(prerelease for 0.x or a-suffix). A PR touching the workflow ordesktop/build/**, and a manual run, are dry runs. - Never make a desktop release GitHub's "latest": install.sh, install.ps1 and ffc up to v1.11.0 read
releases/latest.release.Latestskips non-v<digit>tags for newer ffc. - The version comes from ldflags
-X github.com/nasroykh/foxmayn_frappe_cli/desktop/services.AppVersion=<semver>(APP_VERSIONin the Windows/darwin Taskfiles); a local build is0.0.0-devand never gets an update offer. - Builds are unsigned until the Apple and Windows signing secrets exist; those signing steps have never run (UNVERIFIED in the workflow).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

