clean

Clean Xcode build artifacts and reset the iOS simulator.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/Pjpj42/GridRacer --skill clean-pjpj42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean
Source: https://github.com/Pjpj42/GridRacer/tree/main/.claude/skills/clean
Command: npx skills add https://github.com/Pjpj42/GridRacer --skill clean-pjpj42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes stale build artifacts and resets the simulator to a clean state, speeding up fresh iterations and reliable testing.

Core Features & Use Cases

  • Clean Xcode Build: Remove compiled artifacts for the selected scheme to ensure fresh builds.
  • Clear DerivedData: Delete DerivedData to resolve caching issues and speed up rebuilds.
  • Reset Simulator: Terminate the running app on the booted simulator and uninstall it to simulate a fresh environment.
  • Verification: Confirm no stale caches remain before the next build.

Quick Start

Run a clean cycle to remove build artifacts and reset the simulator for a fresh start.

Frequently Asked Questions about clean

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean Xcode build artifacts and DerivedData to fix caching issues?

Cleaning Xcode build artifacts removes compiled outputs for the selected scheme and deletes DerivedData to resolve caching issues. This ensures fresh builds and speeds up reliable iterations by eliminating stale cached state.

What is the best way to reset the iOS simulator to a clean state for testing?

Resetting the iOS simulator involves terminating the running app on the booted simulator and uninstalling it. This provides a fresh environment for testing, ensuring no cached application state affects your debugging or performance testing workflows.

When should I clear DerivedData during my iOS development workflow?

You should clear DerivedData during iOS development when debugging, after build failures, or before performance testing. Removing stale build artifacts avoids cached state and provides a clean environment for reliable testing and fresh iterations.

Does cleaning build artifacts and resetting the simulator verify that no cached data remains?

Yes, cleaning build artifacts and resetting the simulator includes a verification step to confirm no stale caches remain. This ensures your Xcode development environment is completely clean before initiating the next build cycle.

Why does my iOS app still show cached state after a build failure?

Cached state persists after a build failure because stale DerivedData and installed simulator apps are not automatically removed. You must explicitly clean Xcode build artifacts, uninstall the app from the simulator, and verify no cached data remains.