agentleFS
clideyclidey/whodb/.agents/skills/desktop-feature/SKILL.md

desktop-feature

Skill5.1k starsChanged 3 days agoApache-2.0View on GitHub

Add or modify desktop app functionality (Wails-based native apps)

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 8 mentionsApr 2026: 4 mentionsMay 2026: 5 mentionsJun 2026: 6 mentionsJul 2026: 5 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 9 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the clidey/whodb repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about clidey/whodb

The biggest 5 of 60 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 60

Talked about on GitHub, Bluesky and Hacker News (60 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

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
  1. Very specific:

    All window logic lives in desktop-common/app.go (App struct methods).

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Desktop App Feature

Architecture

desktop-common/         # Shared: App struct, window management, menus, RunApp()
desktop-ce/             # CE entry point, Makefile, wails.json

desktop-ce/main.go calls common.RunApp(common.RunConfig{Edition: "ce", ...}) with the embedded assets, GraphQL schema and engine initializer.

Adding Desktop-Specific Behavior

1. Runtime Detection

import "github.com/clidey/whodb/core/src/env"

if env.GetIsDesktopMode() {
    // Desktop-specific behavior
}

It reads WHODB_DESKTOP on every call because the app sets the variable after package initialization.

2. Menu / Accelerator Changes

Edit desktop-common/app.go. Wails accelerators are separate from frontend keyboard shortcuts — both must be updated for shared shortcuts.

3. Window Management

All window logic lives in desktop-common/app.go (App struct methods).

Build and Test

Development

cd desktop-ce && make dev    # Hot reload mode

Production Build

cd desktop-ce && make build          # Current platform
cd desktop-ce && make build-mac      # macOS universal binary
cd desktop-ce && make build-all      # All platforms

Verification

# Must build with workspace
GOWORK=$PWD/go.work.desktop-ce go build -C desktop-ce -o test-build
rm -f desktop-ce/test-build

# Frontend must also build (it gets embedded)
cd frontend && pnpm run build:ce

macOS Packaging (release only)

make package-mac-signed    # Signed .pkg (CODESIGN_ID, INSTALLER_ID)
make notarize-mac          # Notarize with Apple
make dmg-mac               # DMG installer
make release-mac           # Build, sign, notarize and staple

Notarization needs NOTARY_PROFILE or APPLE_ID, TEAM_ID and APPLE_APP_PASSWORD. Run make help for every target.

Key Rules

  • Entry points are thin — call common.RunApp()
  • Edition not controlled by build tags, only by which entry point compiles
  • WHODB_DESKTOP=true is set automatically at runtime
  • Go workspace file: go.work.desktop-ce

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.