agentleFS
r0shir0shi/harborclerk/.claude/skills/build-macos/SKILL.md

build-macos

Skill3 starsChanged 33 days agoMITView on GitHub

Build macOS apps (Harbor Clerk Server + Harbor Clerk) and report results. Optionally launch the server app.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are 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.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run make apps in macos/ to build both macOS apps.

    line 8
  2. Very specific:

    Check output for BUILD SUCCEEDED or BUILD FAILED / error: lines

    line 15
  3. Very specific:

    If the user said "and run" or "and launch", open the server app: open macos/build/output/HarborClerkServer.app

    line 25
  4. Very specific:

    If the build stops at configure: error: C compiler cannot create executables, the Command Line Tools SDK is newer than Xcode's linker.

    line 28

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

Build macOS Apps

Run make apps in macos/ to build both macOS apps. Parse the output for build success/failure and report a summary. All paths are relative to the repository root.

Steps

  1. Run (cd macos && make apps 2>&1)
  2. Check output for BUILD SUCCEEDED or BUILD FAILED / error: lines
  3. Report:
    • Whether each app (HarborClerkServer, HarborClerk) built successfully
    • Any build errors (show the actual error lines)
    • App sizes from the "Server app" / "Client app" lines
    • The ==> Version line: package.sh derives it from git describe (scripts/build-version.sh), so an untagged commit builds as <last tag> (<commits since>) and a dirty tree adds .dirty to the stamp. Report it as printed; never "fix" it in the pbxproj (see docs/releasing.md).
  4. If the user said "and run" or "and launch", open the server app: open macos/build/output/HarborClerkServer.app

If the build stops at configure: error: C compiler cannot create executables, the Command Line Tools SDK is newer than Xcode's linker; see the SDKROOT note in macos/AGENTS.md. Signing (make sign) is never run by an agent.

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.