preflight-permissions
Preflight Permissions
Ensure all macOS system permissions are granted before automated UI tests run. This prevents XCUITests from hanging on permission dialogs or failing silently when TCC blocks access.
When to Use
Run this skill once when starting a new project, after cloning, or whenever tests fail
with permission-related errors. It is a prerequisite for journey-builder and journey-loop.
What It Does
- Sets up a self-signed code signing certificate (so permissions persist across rebuilds)
- Builds the app and test runner with that certificate
- Detects which TCC permissions the app needs
- Guides the user to grant each permission in System Settings
- Runs a smoke XCUITest to verify permissions work
- Reports pass/fail for each permission
More from sunfmin/autocraft
autocraft
>
20journey-builder
Build and test the longest uncovered user journey from spec.md. Reads the product spec, checks existing journeys, picks the longest untested path, writes a UI test with screenshots at every step, then runs 3 polish rounds (testability → refactor UI test → UI review) until everything is clean. Use when the user says "next journey", "add journey", "test the next flow", "journey builder", or "cover more user paths".
4journey-loop
Orchestrates a continuous journey-builder → refine → restart loop. Runs journey-builder and refine-journey sequentially, improving the skill each iteration. Loops until all spec requirements are covered by journeys and the score reaches 95%.
4refine-journey
Evaluate the output of a journey-builder run, identify instruction gaps, and edit the project root AGENTS.md (or add pitfalls to the gist) to fix those gaps. Does NOT modify the journey-builder skill itself.
3