agentleFS
huihuisanghuihuisang/ajigu-skills/skills/macos-finder-extension/SKILL.md

macos-finder-extension

Skill0 starsChanged 21 days agoMITView on GitHub

Design, implement, debug, and verify macOS Finder Sync extensions for context menus, badges, toolbar actions, monitored directories, and host-app communication. Use when implementing Finder integration or diagnosing missing menus, incorrect icon colors, sandbox access, localization, signing, registration, or stale builds; do not use as a File Provider sync-engine guide.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Do not change signing, entitlements, sandbox status, bundle identifiers, App Groups, or embedding outside the user's authorized scope.

    line 13
  2. Distinctive:

    Read the focused references when relevant:

    line 23
  3. Distinctive:

    Always read architecture.md when implementing or restructuring a Finder Sync extension.

    line 25
  4. Distinctive:

    Read sandbox-permissions.md when the workflow reads or writes files outside an existing authorized root, or when macOS prompts unexpectedly.

    line 26
  5. Distinctive:

    Read verification.md before installing, diagnosing registration, or handing off a build.

    line 27
  6. Very specific:

    Read menu-icons.md whenever adding or changing menu icons or diagnosing their color.

    line 28
  7. Distinctive:

    Read icon-actions.md only for custom-icon/reset-icon work or when its failure patterns match the current bug.

    line 29
  8. Distinctive:

    Use the bundled inspection script after building or installing:

    line 31

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

macOS Finder Extension

Build Finder Sync extensions as thin Finder UI adapters, with durable state and substantial work owned by the containing app or its existing service layer.

Before implementation, decide whether Finder Sync is the correct extension point. Finder Sync is appropriate for menus, badges, labels, and toolbar UI in monitored directories. File Provider is appropriate for synchronized or virtualized file domains; a Service or Quick Action may be enough for one simple command.

Do not change signing, entitlements, sandbox status, bundle identifiers, App Groups, or embedding outside the user's authorized scope. Reuse approval already given for the task; ask only when a required change adds scope.

Workflow

  1. Inspect the existing project and distribution model before adding targets or capabilities.
  2. Define Finder-facing features, monitored-directory scope, app communication, state ownership, and file-authorization needs separately.
  3. Implement the smallest extension surface that satisfies the request.
  4. Localize extension UI in the extension target. For menu icons, read menu-icons.md, choose template or intentional full-color rendering, and check the actual colors in Finder.
  5. Build the exact signed candidate, install one canonical copy, register it once, restart Finder, and test the real UI.

Read the focused references when relevant:

  • Always read architecture.md when implementing or restructuring a Finder Sync extension.
  • Read sandbox-permissions.md when the workflow reads or writes files outside an existing authorized root, or when macOS prompts unexpectedly.
  • Read verification.md before installing, diagnosing registration, or handing off a build.
  • Read menu-icons.md whenever adding or changing menu icons or diagnosing their color. A runtime symbol with isTemplate = true is not sufficient evidence.
  • Read icon-actions.md only for custom-icon/reset-icon work or when its failure patterns match the current bug.

Use the bundled inspection script after building or installing:

bash <skill-path>/scripts/inspect_finder_extension.sh \
  /path/to/App.app \
  Contents/PlugIns/FinderExtension.appex \
  com.example.App.FinderExtension

The bundle identifier is optional. The script inspects the extension point, signing teams, actual signed entitlements, and registration count without assuming a specific permission policy.

Completion Standard

A successful build is not enough. Verify the requested menus, badges, or toolbar behavior in Finder; verify host communication against the installed app; exercise every requested location or file class; and prove that signed permissions and extension registrations match the intended architecture. Menu icons require observed normal and highlighted states in both Light and Dark appearances; report any untested state as incomplete.

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.