Wait for the actual state change instead of a fixed delay. Add this `TestHelpers.swift` to your test target (the lint rules already exclude `*TestHelpers.swift`):

Spend the expensive model only at a task's few load-bearing moments; let a cheaper/faster model handle the rest.

Apply these whenever touching widgets, animations, networking, or background work.

A quick self-check, not a pipeline: read back over this conversation, find places where the human corrected something a project rule should have already covered, and propose a small, bounded edit. Nothing here gets applied without the human reviewing it first.

Implement a feature, review a change, delegate work, or resume a session in a Lacquer-managed project.

A design document reads as settled fact whether or not anyone checked. That is the whole failure mode: an unverified sentence in a PCD becomes an interface, then a dependency, then a week of work, and nothing in the process ever asks "how do we know that?"

Use when asked to take a GitHub issue number, implement a fix, run builds/tests, commit with a closing message, and push. End-to-end workflow using gh CLI, local code changes, and git.

Build or test an iOS app, diagnose missing tests or simulator logs, or keep DerivedData inside a worktree.

Add Swift files, change app architecture, write Swift tests, or fix DocC and local iOS checks.

Release an iOS app, upload to TestFlight, or fix App Store validation, archive placement, and upload processing.

Configure iOS service keys, Secrets.xcconfig, CI signing credentials, or release secret injection and provenance.

Verify simulator UI, debug accessibility interactions, measure control contrast, or check SwiftUI performance and API usage.

Platform mechanics for macOS apps — windows, menus, sandboxing, AppKit bridging, ScreenCaptureKit, and where SwiftUI on macOS diverges from iOS. This complements narrower macOS skills already in this profile: `macos-ci-recipes` (CI-only) and `release-macos-spm-packaging` (SwiftPM scaffolding/build

When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

`gh search code` — GitHub's code search API through the CLI you already have authenticated, scoped to exactly the repos/orgs you need instead of a raw `gh api` call.

A skill earns its place by being the thing someone reaches for at the right moment, not by existing. Every line either helps a reader recognize when to use it or tells them exactly what to do — nothing else survives review.

A skill earning its place in the lacquer (per `skill-authoring-standard`) is a judgment call today. This loop adds a second, empirical bar: does a proposed edit measurably reduce the friction real sessions hit, without regressing what already works? Run it via the `skill-tuning-loop` Workflow — ne

Audit and safely clean Xcode-related developer storage on macOS. Use whenever a developer mentions low disk space, Xcode storage, DerivedData, simulator devices or runtimes, stale beta platforms in Xcode Settings, DeviceSupport, archives, dSYMs, CocoaPods caches, simulator dyld caches, project .build folders, downloaded Xcode DMGs/XIPs, duplicate Xcode installers, or old Xcode applications. Also use this skill proactively when you hit low storage during other work, such as a build, download, or install failing with an out-of-disk-space error. Always measure first, report recoverable GiB with evidence, and obtain explicit itemized approval before any mutation.

Symbolicate and triage iOS/macOS crash reports (.ips, MetricKit, legacy .crash, Xcode Organizer .xccrashpoint) via the `xcsym` CLI. Use when given a crash file to diagnose, when TestFlight/App Store Connect crashes need triage, when a crash comes back unsymbolicated, or when asked what kind of crash something is.