Skip to content
axint docs

Xcode Happy Path

This is the shortest path from nothing installed to a working Xcode repair loop.

The goal is simple:

  1. Build
  2. Read the check
  3. Copy the repair prompt if something broke
  4. Rerun

  1. Install Axint.

    Terminal window
    npm install -g @axint/compiler

  2. Wire the local Xcode helpers once.

    Terminal window
    axint xcode install --project .
    axint doctor --dir .

    This gives your agentic tooling the local Axint path, project memory pack, Xcode guard proof, and durable MCP config without you having to manually edit configs.

    In a new Xcode agent chat, start with axint.project-start if your MCP client exposes prompts. Otherwise paste the start prompt from Xcode setup.

  3. Build in Xcode or swift build.

    Axint’s compile/validate plugin flow writes two layers of output:

    • a lightweight Axint Check
    • a richer Fix Packet

  4. Read the latest result first.

    Terminal window
    axint project index --changed Sources/Feature.swift
    axint xcode check Sources/Feature.swift
    axint xcode packet --kind validate

    That gives you the quick answer:

    • pass
    • needs review
    • fail

    plus the top finding and the next step.

  5. If something broke, fetch the exact repair prompt.

    Terminal window
    axint xcode packet --kind validate --format prompt

    Paste that prompt into your AI tool or use it as a manual repair checklist.

  6. For a real UI repair, make the proof focused.

    Terminal window
    axint validate-swift Sources/Feature.swift Sources/HomeView.swift
    axint run --dir . --scheme MyApp --only-testing MyAppUITests/MyAppUITests/testComposerStillAcceptsInput
    axint run status --dir .

    Axint feeds passing focused selectors back into Cloud Check, so the final report can reconcile static warnings with actual Xcode proof.

  7. Send compiler feedback when Axint caused or missed the issue.

    Terminal window
    axint cloud check Sources/Feature.swift --feedback

    The feedback signal is the redacted bug report Axint can turn into a fixture, generator fix, validator rule, or docs update.

  8. Fix and rebuild.

    Keep the loop tight:

    • build
    • packet
    • packet prompt
    • fix
    • rerun

Which command should I use?

  • axint xcode packet
    • use this first for the latest result
    • add --format prompt when you need the full repair brief
    • AI prompt
    • full diagnostics
    • artifact hints for Swift / plist / entitlements
  • axint xcode check <file>
    • use this for an existing Swift file that is acting up
    • refreshes local context before returning the top issue
  • axint project index
    • use this before Cloud Check when the bug depends on nearby files
  • axint run --only-testing
    • use this for focused Xcode UI proof after a SwiftUI interaction repair

What “good” looks like

The loop is working when:

  • your build produces a local Axint Check
  • you can read the latest result without hunting through DerivedData
  • you can copy one repair prompt into your AI tool
  • passing focused UI tests show up in the final Axint run artifact
  • rerunning Axint moves the result to pass

Keep going