taptap-maker-local

To initialize local development for a TapTap Maker project, the workflow handles clone and download flows and prepares the local AI dev kit after checkout. It guides you through the correct CLI or MCP path to set up your environment safely.

To resolve Git conflicts during a Maker project sync, the workflow diagnoses conflicts, build blockers, and settings issues. It provides safety checks and repair advice to recover your local project integrity.

The correct workflow to submit local changes to a Maker project involves checking local readiness, inspecting changes, and guiding the submit or push operations. It ensures safe sequencing and validates project policies before submission.

Yes, you need the Maker CLI to check local project status and readiness. The workflow requires Maker CLI status checks, Git state awareness, and project policy validation to preserve local project integrity during sync operations.

Your Maker build workflow requires user approval before pushing changes to ensure safe sequencing and project policy validation. This prevents unverified modifications from compromising local project integrity during submit or push operations.