
from get-shit-pretty35
Translate design chunks into production-ready frontend code using a phased build pipeline.
Phase 5 of the GSP project diamond: implement designs as production-ready code via a 7-phase pipeline with compile checkpoints.
.design/projects/{project}/design/...).design/branding/{brand}/patterns/){PROJECT_PATH}/brief, config.json)APP_PATH){project}/build/BUILD-LOG.md, SCAFFOLD-LOG.md, INDEX.md, and manifest filesgsp-project-builder agents for foundation/component/screen steps.GSP Project Build is a sophisticated phased pipeline skill that translates design chunks into production-ready frontend code. It defines a 7-phase build pipeline with compile checkpoints, parallel agent spawning, and resume support. The SKILL.md is extremely detailed and well-structured but the skill has no bundled scripts for independent verification. It's part of the larger 'Get Shit Pretty' ecosystem and depends heavily on companion skills (gsp-scaffold, gsp-brand-apply, gsp-phase-transition) and a specific directory structure (.design/projects/), making it powerful within that ecosystem but harder to use standalone.
No security concerns found. The skill reads/writes within the project directory, uses standard build commands (next build, vite build, tsc), and asks user confirmation before proceeding. No hardcoded credentials, no network calls to suspicious hosts, no destructive commands without guards. The skill is well-architected with clear phase separation, checkpoint gates, and resume support. Its main limitation is ecosystem lock-in — it only works within the GSP project framework.