← ClaudeAtlas

wails-architectlisted

Wails v3.1 shell around an existing web app — embedded SPA build, same-origin API proxy with server-held session cookies (WebKit drops Set-Cookie on custom schemes), per-OS window chrome, Android fetch shim and insets, packaging and Play signing. Use when scaffolding or reviewing a Wails desktop/mobile shell, or when sign-in fails inside the webview.
ralvarez-ai/ralvaskills · ★ 4 · AI & Automation · score 77
Install: claude install-skill ralvarez-ai/ralvaskills
# Wails Architecture Targets **Wails v3.1.0** on **Go 1.27.x**. Companion to [go-architect](../../languages/go-architect/SKILL.md), [react-architect](../react-architect/SKILL.md), [ui-ux-architect](../../frontend/ui-ux-architect/SKILL.md) and [repo-tooling-architect](../../tooling/repo-tooling-architect/SKILL.md). Full skeletons in [RECIPES.md](RECIPES.md); pinned versions in [STACK.md](STACK.md). ## 1. Decide whether a shell is justified A Wails shell is a **thin client** around a web app that already talks to a remote API: it embeds the build, forwards API calls and holds no data. The server, the database and the SPA stay unchanged. - **Never embed the server.** A desktop binary cannot run Postgres and the identity service, and doing so creates a second deployment. - **Mobile is experimental.** Wails v3 marks iOS/Android experimental; keep the PWA or a native wrapper as the fallback and keep the shell thin enough to swap. - **A shell must earn its place.** Ship the PWA unless you need something a browser tab cannot do (native notifications, badge, tray/menus, autostart, file association, keychain, updater). Add those after the shell works, in value order. - **Alternatives:** Tauri 2 has stable mobile but adds Rust for what is mostly configuration; Capacitor covers phones only; a PWA covers the browser. ## 2. Project layout Give the shell **its own `go.mod`**, outside the application module, with its own lint and archtest. It sits beside the SPA so the embed path is lo