builder

Automates creation of a live drop website from selected Fashion Designer products, outputting builder-output.json.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/neilsanghrajka/drip --skill builder-neilsanghrajka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builder
Source: https://github.com/neilsanghrajka/drip/tree/main/agent/codex-agent/.agents/skills/builder
Command: npx skills add https://github.com/neilsanghrajka/drip --skill builder-neilsanghrajka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builder enables teams to convert selected Fashion Designer product visuals into a reviewed, deployed, one-page limited-drop website and outputs a builder-output.json for verification.

Core Features & Use Cases

  • Orchestrates plan and subagent workflow to generate a live drop site from chosen products.
  • Ensures static site build, QA review, and deployment coordination, producing a deterministic output artifact.
  • Supports inputs like selectedMocks, siteDir, output, and deployment parameters, while inferring defaults when omitted.

Quick Start

Provide the selected Fashion Designer products and the builder will orchestrate the site briefing, static build, reviewer QA, and deployment.

Frequently Asked Questions about builder

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

FAQPage Schema
How do I automate a fashion drop site from product visuals to deployment?

Automating a fashion drop site requires orchestrating asset preparation, static site generation, visual QA, and deployment coordination into a single end-to-end workflow. This builder processes selected Fashion Designer products to produce a reviewed, deployed, one-page limited-drop website and outputs a builder-output.json artifact for verification.

What is included in an automated limited-drop website layout?

An automated limited-drop website layout features a single-viewport page design with a top urgency timer, a centered product carousel, visible product pricing, a 24-hour countdown, and a dummy Buy button. These elements are generated during the static site build to maximize conversion urgency for fashion drops.

Can I use selected fashion product mocks to generate a static site without manual coding?

Selected fashion product mocks can be directly used to generate a reviewed static site without manual coding. The workflow accepts inputs like selectedMocks, siteDir, output, and deployment parameters, automatically inferring defaults when omitted to streamline the ideation-to-deployment pipeline.

Does the automated website deployment workflow include visual QA review?

The automated website deployment workflow includes a dedicated subagent for visual QA review before final deployment. This ensures the generated static drop site meets the required layout specifications and visual standards, verifying the single-viewport layout and interactive elements prior to going live.

What is the best way to verify a generated drop website before it goes live?

The best way to verify a generated drop website is to review the deterministic builder-output.json artifact produced at the end of the workflow. This output file captures the results of the site briefing, static build, and reviewer QA stages for final pre-deployment verification.

Why does my static drop site generation require a 24-hour countdown timer?

Static drop site generation requires a 24-hour countdown timer to create the limited-time urgency essential for fashion drops. This top urgency timer, combined with a dummy Buy button, simulates the live drop environment required by the single-viewport page layout specification.