agentleFS
Sign inStart free
moasqmoasq/ios-dev-agent/.agents/skills/build/SKILL.md

build

Skill4 starsChanged 6 months agoMITView on GitHub

Use when building the Xcode project, managing simulators, or diagnosing build failures. Covers xcodebuild commands, simulator selection, clean builds, and build flag reference.

156 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, finances and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • GerardoRdz96Skill

    finances

    Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".

    Also in 3 projects that use this

  • cpiprintSkill

    favicon

    Generate favicons from a source image

    Also in 3 projects that use this

  • madeehahassanSkill

    Go-Live

    Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.

    Also in 3 projects that use this

  • JuliusBrusseeSkill

    deepen

    Optional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T edits, never silent rewrites. Triggers when the user says "deepen this", "improve the design", "this module feels shallow", "pull complexity down", "use spare budget on the codebase", or invokes /ck:deepen. Leans on the codebase-design skill's deep-module vocabulary when present.

    Also in 3 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 143 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Run /fix-error to investigate and resolve.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 143 edited versions of this file we could read. “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

Build the project for iOS Simulator.

Quick Start

bash "$PWD/.agents/scripts/xcode-build.sh"

Options

# Clean build
bash .agents/scripts/xcode-build.sh --clean

# Specific device
bash .agents/scripts/xcode-build.sh --device "iPhone Air"

# Specific scheme
bash .agents/scripts/xcode-build.sh --scheme "<SchemeName>"

Available Simulators (iOS 26.4)

DeviceUDID
iPhone 17 ProBCDEE28F-9718-42CC-A78D-1F890D421702
iPhone 17 Pro Max4497F487-B57E-4492-B7D9-CD59D5640DA3
iPhone AirF96B54FE-3D32-4EBF-B122-23A0CCDBF373
iPhone 17A94318CF-7CCC-4C56-8EC9-3335BCA4B081
iPhone 17e1596C7FE-DE81-4C51-B608-7F3123F5D03A

Common Build Failures

ErrorCauseFix
No .xcodeproj foundProject not generatedRun xcodegen generate
Cannot find type in scopeMissing importAdd import Framework
Actor-isolated propertySwift 6 concurrencyAdd @MainActor or snapshot values
Ambiguous use ofDuplicate typeRemove duplicate declaration
Value of type has no memberDeprecated APICheck /swiftui reference

Error Integration

Build failures are automatically logged to .agents/errors/errors.md via hook. Run /fix-error to investigate and resolve. Run /consolidate-errors to feed fixes back.

Reference

  • build-flags.md — xcodebuild flags and settings
  • simulator-management.md — simctl commands

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.

Check your setup, free