GSP Project Build

Phase 5 of the GSP project diamond: implement designs as production-ready code via a 7-phase pipeline with compile checkpoints.

What it does

• Runs scaffold, foundations, component, and screen phases to produce code in the repository.
• Verifies builds at checkpoints and merges phase logs into a single BUILD-LOG.
• Supports Figma fallback and a revision mode for handling QA issues.

Inputs

• Design chunks (.design/projects/{project}/design/...)
• Brand system (.design/branding/{brand}/patterns/)
• Project brief and config ({PROJECT_PATH}/brief, config.json)

Outputs

• Code changes in the target app path (APP_PATH)
• {project}/build/BUILD-LOG.md, SCAFFOLD-LOG.md, INDEX.md, and manifest files

How it works (high level)

1. SCAFFOLD: init project scaffold and verify build
2. FOUNDATIONS: integrate tokens, global styles, root layout, utilities
3. FOUNDATION REVIEW: interactive approval before components
4. COMPONENTS: build/install/customize components (partitioned, parallel agents)
5. SCREENS: build screens in parallel using existing components
6. EXTRACTION REVIEW: automated scan for hardcoded values and duplication
7. FINALIZE: write INDEX, MANIFEST, update STATE, invoke phase transition

Notes

• Uses gsp-project-builder agents for foundation/component/screen steps.
• Leaves changes unstaged; writers should review before committing.
• Strong emphasis on brand token verification and compile checkpoints.