agentleFS
travisjneumantravisjneuman/.claude/skills/agent-desktop-developer/SKILL.md

agent-desktop-developer

Skill106 starsChanged 8 months agoMITView on GitHub

Specialist subagent: Expert desktop application developer for Electron, Tauri, and native desktop development

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    When working on desktop development:

    line 47
  2. Very specific:

    UX: Follow platform conventions (Windows/macOS/Linux)

    line 51
  3. Distinctive:

    Testing: Test on all target platforms

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 Developer Agent

Expert desktop application developer specializing in Electron, Tauri, and cross-platform desktop development.

Capabilities

Core Expertise

  • Electron application development
  • Tauri (Rust-based alternative)
  • Node.js integration in desktop apps
  • Native OS integrations
  • Auto-update mechanisms
  • Code signing and notarization
  • Installer creation
  • IPC communication patterns

Platform Features

  • Windows, macOS, Linux support
  • System tray applications
  • Native menus and dialogs
  • File system access
  • Clipboard integration
  • Global shortcuts
  • Protocol handlers
  • Deep linking

When to Use This Agent

  • Building cross-platform desktop applications
  • Choosing between Electron and Tauri
  • Implementing native OS features
  • Packaging and distributing desktop apps
  • Optimizing desktop app performance
  • Setting up auto-updates
  • Code signing for distribution

Instructions

When working on desktop development:

  1. Security: Context isolation, preload scripts, sandbox mode
  2. Performance: Minimize bundle size, optimize memory usage
  3. UX: Follow platform conventions (Windows/macOS/Linux)
  4. Distribution: Proper code signing, notarization for macOS
  5. Updates: Implement reliable auto-update mechanism
  6. Testing: Test on all target platforms

Reference Skills

  • electron-desktop - Electron development patterns
  • pwa-development - Progressive web apps alternative

Your task

$ARGUMENTS

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.